WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] help recovering vms

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] help recovering vms
From: Mark Foster <mark@xxxxxxxxx>
Date: Wed, 09 Aug 2006 10:39:13 -0700
Delivery-date: Wed, 09 Aug 2006 10:40:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.5 (X11/20060719)
I could use some help trying to recover VMs on a system that used to run xen-3.0.0 under sarge. The host (Domain0) bit the dust, so I rebuilt it using SUSE Linux 10.1 which has xen-3.0.2-2 packages. xend is running and I can do xm list, xm info and so on. It still sees the LVM volume groups that the VM data resides on. My VMs are sitting on /dev/vg20/vol01, /dev/vg20/vol03 .... Because I lost the configs (doh!) I am creating /etc/xen/unknown from memory and running
xm create -c unknown
Here is what I get...
Loading xenblk Registering block device major 8 Loading reiserfs Waiting for device /dev/sdb1 to appear: ok
rootfs: major=8 minor=17 devn=2065
Mounting root /dev/sdb1
mount: unknown filesystem type 'ext3'
umount: /dev: device is busy
umount: /dev: device is busy
Kernel panic - not syncing: Attempted to kill init!

I have tried to modprobe ext3 from the Domain0 and also tried using the kernel/initrd from the VM by copying them into /boot/kernels/ (vmlinuz-2.6.9-22.0.1.EL and initrd-2.6.9-22.0.1.EL.img). The result is the same.

What now? I suppose I could create new volumes using reiserfs and rsync the data across, but I'd rather use them as is.
Thanks!

Here are the relevant lines from the "unknown" vm config.
kernel = "/boot/vmlinuz-xenpae"
ramdisk = "/boot/initrd-xenpae"
bootentry="/boot/kernels/vmlinuz-2.6.9-22.0.1.EL,/boot/kernels/initrd-2.6.9-22.0.1.EL.img"
memory = 64
name = "unknown"
vif = [ '' ]
disk = [ 'phy:/dev/vg20/vol01,sdb1,w','phy:/dev/vg20/vol02,sdb2,w' ]
dhcp="dhcp"
root = "/dev/sdb1 ro"

--
Some days it's just not worth chewing through the restraints...
Mark D. Foster, CISSP <mark@xxxxxxxxx>  http://mark.foster.cc/



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] help recovering vms, Mark Foster <=