Apart from one Virtual Host still running Xen/RHEL5, all our virtual capability is hosted on KVM hosts with LVM storage devices. I've stupidly attempted an Ubuntu full release upgrade on a guest running on the Xen machine, only to have it install a non-Xen kernel and refuse to boot (rookie error there).
Getting to the actual issue, the machine in question uses a single file based storage device. It's been a while since I've had to open one of these, but the process shouldn't be much different from opening an LVM volume, but for some reason I'm not seeing a partition table in device file.
root@vh1 web2.entrant # losetup -a /dev/loop2: :34603012 (storage.img) /dev/loop3: :32768005 (/srv/xen/domains/web2.entrant/disk.img) root@vh1 web2.entrant # fdisk -l /dev/loop3 Disk /dev/loop3: 68.7 GB, 68719476736 bytes 255 heads, 63 sectors/track, 8354 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/loop3 doesn't contain a valid partition table
Inspecting another machine's partition file on the same host yields the same issue (no valid partition table), though it still starts/runs fine which is strange in itself.
Edit: (Adding kpartx)
root@vh1 ~ # kpartx -av /srv/xen/domains/web2.entrant/disk.img root@vh1 ~ #
No message (as expected) stating which partitions had been added
Edit: (Trying guestfish, virt-rescue, etc)
[root@vh1 web2.entrant]# virt-rescue --rw --suggest -a /srv/web2.entrant/disk.img Inspecting the virtual machine or disk image ... This disk contains one or more filesystems, but we don't recognize any operating system. You can use these mount commands in virt-rescue (at the ><rescue> prompt) to mount these filesystems. # /dev/vda has type 'unknown'
and with guestfish:
><fs> add-ro disk.img ><fs> run ><fs> list-filesystems /dev/vda: unknown ><fs> lvs ><fs>
I'm assuming I've messed up the partition table completely, unfortunately I haven't got a copy of what the machines partition layout looked like (seeing as the other guest it was copied from (whilst booted) seems to exhibit the same empty partition table when attempting the same process)