Mochabomb

I made some changes to a VBD based Xen server – here’s what not to do:

1. Use a password in the httpd cert – if I ran xm console server I did not see that prompt – needed to use the vnc/gui to see this – entered it and got closer
2. Spaces in device names using system-config-network – eg; eth0 was actually saved as "eth0 " – that extra space messed up starting of "eth0" and other network devices. I will bugzilla this one.
3. Pretty GUI’s are not a sign of weakness – this time it showed me what 6 hours of console hacking did not. Score +1 for the GUI!!!

Network trouble: www.linuxfromscratch.org/pipermail/lfs-support/2003-December/021076.html
solution: cd /etc; find . -print | grep ifcfg – delete any that are easily replaced – I removed all but the primary IP interface.

Mounting xen vbd img files:
http://www.brandonhutchinson.com/Mounting_a_Linux_LVM_volume.html
http://www.novell.com/coolsolutions/tip/19568.html

Now if anyone share how to effectively mount Linux LVM from a server.img file that looks like – I can mount the ext3 boot partition, but not the Linux LVM using lomount or other techniques:

[root@server vm]# fdisk -l /dev/loop0

Disk /dev/loop0: 16.7 GB, 16777216000 bytes
255 heads, 63 sectors/track, 2039 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

      Device Boot      Start         End      Blocks   Id  System
/dev/loop0p1   *           1          13      104391   83  Linux
/dev/loop0p2              14        2039    16273845   8e  Linux LVM

as Lundberg would say “That would be great”

• Previous Entry: PHP memory limit results in blank pages
• Next Entry: Fail2Ban script to verify configuration