[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what's wrong?
Hi Mauro, It would be more useful if you had included the /etc/xen/mail1.cfg as that is the file ultimately used to create the domU. The xen-tools.conf is just a tool that does a some (actually quite good) work for you by creating that file and the disk/partition volumes. xen-tools is not involved in *running* those VMs though. On Fri, Feb 11, 2011 at 08:11:27AM +0000, Mauro wrote: > On 10 February 2011 08:16, Mauro <mrsanna1@xxxxxxxxx> wrote: > > I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 > > dom0. > > My xen-tools.conf: > > > > lvm = vg00 > > size = 100Gb # Disk image size. > > memory = 2048Mb # Memory size > > swap = 2G # Swap size > > # noswap = 1 # Don't use swap at all for the new system. > > fs = ext4 # use the EXT3 filesystem for the disk image. > > dist = `xt-guess-suite-and-mirror --suite` # Default distribution to > > install. > > image = sparse # Specify sparse vs. full disk images. > > > > gateway = 172.16.10.1 > > netmask = 255.255.255.0 > > broadcast = 172.16.10.255 > > > > kernel = /boot/vmlinuz-`uname -r` > > initrd = /boot/initrd.img-`uname -r` > > > > arch = amd64 > > mirror = `xt-guess-suite-and-mirror --mirror` > > > > ext4_options = noatime,nodiratime,errors=remount-ro > > ext2_options = noatime,nodiratime,errors=remount-ro > > xfs_options = defaults > > reiserfs_options = defaults > > btrfs_options = defaults > > > > # serial_device = hvc0 #default > > # serial_device = tty1 > > # > > # disk_device = xvda #default > > # disk_device = sda > > > > then I run as usual: > > xen-create-image --hostname mail1 --ip 172.16.10.154 --vcpus 4 --role > > udev --dist squeeze > > > > at the end of domU creation I run xm console mail1 but here is what I see: > > > > Begin: Waiting for root file system ... done. > > Gave up waiting for root device. Common problems: > > - Boot args (cat /proc/cmdline) > > - Check rootdelay= (did the system wait long enough?) > > - Check root= (did the system wait for the right device?) > > - Missing modules (cat /proc/modules; ls /dev) > > ALERT! /dev/xvda2 does not exist. Dropping to a shell! > > > > Arghhhhhhh!!!!!! > > I think there is nothing wrong in my creation procedure, I have a lot of > > DomU with debian lenny and xen3.2. > > Perhaps ext4 isn't supported? > > Help please. My (wild) guess on this would be that you'd have to change the "root=" parameter in your config file to point to some "sda*" device/partition instead of "xvda*". root = "/dev/xvda2" to root= "/dev/sda2" Alternatively you'd have to change the "disk=" parameters to map your LVs to xdva* instead of sda*. disk = [ 'phy:/dev/vg00/mail1-swap,sda1,w', 'phy:/dev/vg00/mail1-disk,sda2,w', ] to disk = [ 'phy:/dev/vg00/mail1-swap,xvda1,w', 'phy:/dev/vg00/mail1-disk,xvda2,w', ] > I've solved using pygrub. > So it seems that without pygrub I can't run DomUs? You shouldn't have to use pygrub for something that simple. My guess is that there was a lack of communication between the maintainers of xen and xen-tools in regard to the default devices. cheers -henrik _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |