Mauro
2011-Feb-10 08:16 UTC
[Xen-users] upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
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. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mauro
2011-Feb-11 08:11 UTC
[Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
On 10 February 2011 08:16, Mauro <mrsanna1@gmail.com> 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.I''ve solved using pygrub. So it seems that without pygrub I can''t run DomUs? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henrik Langos
2011-Feb-11 08:59 UTC
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@gmail.com> 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@lists.xensource.com http://lists.xensource.com/xen-users
Mauro
2011-Feb-11 10:04 UTC
Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
On 11 February 2011 08:59, Henrik Langos <hlangos@innominate.com> wrote:> 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@gmail.com> 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. >mail1.cfg: bootloader = ''/usr/lib/xen-default/bin/pygrub'' vcpus = ''4'' memory = ''2048'' # # Disk device(s). # root = ''/dev/xvda2 ro'' disk = [ ''phy:/dev/vg00/mail1-disk,xvda2,w'', ''phy:/dev/vg00/mail1-swap,xvda1,w'', ] # # Physical volumes # # # Hostname # name = ''mail1'' # # Networking # vif = [ ''ip=172.16.10.154,mac=00:16:3E:01:D7:24'' ] # # Behaviour # on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart It''s exactly as another DomU that runs with xen 3.2 on a debian lenny machine. The only difference is the bootloader = ''/usr/lib/xen-default/bin/pygrub''. I''ve noticed that when debootstrap install the system it install the linux-image and not linux-modules.>From mail1.log, debian squeeze and xen4.0:The following extra packages will be installed: firmware-linux-free libuuid-perl linux-base linux-image-2.6.32-5-xen-amd64 Suggested packages: linux-doc-2.6.32 grub The following NEW packages will be installed: firmware-linux-free libuuid-perl linux-base linux-image-2.6.32-5-xen-amd64 linux-image-xen-amd64 While from mail1.log with xen3.2 and debian lenny: The following NEW packages will be installed: linux-modules-2.6.26-2-xen-amd64 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henrik Langos
2011-Feb-11 11:12 UTC
Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
On Fri, Feb 11, 2011 at 10:04:44AM +0000, Mauro wrote:> On 11 February 2011 08:59, Henrik Langos <hlangos-xen@innominate.com> wrote: > > 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. > >...> > > > 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. > > > > mail1.cfg: > > bootloader = ''/usr/lib/xen-default/bin/pygrub'' > > vcpus = ''4'' > memory = ''2048'' > > # > # Disk device(s). > # > root = ''/dev/xvda2 ro'' > disk = [ > ''phy:/dev/vg00/mail1-disk,xvda2,w'', > ''phy:/dev/vg00/mail1-swap,xvda1,w'', > ] > > > # > # Physical volumes > # > > > # > # Hostname > # > name = ''mail1'' > > # > # Networking > # > vif = [ ''ip=172.16.10.154,mac=00:16:3E:01:D7:24'' ] > > # > # Behaviour > # > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart > > It''s exactly as another DomU that runs with xen 3.2 on a debian lenny machine. > The only difference is the bootloader = ''/usr/lib/xen-default/bin/pygrub''.Well, There is no "kernel=" or "ramdisk=" parameter in your mail1.cfg. So I guess you removed those when you switched to using pygrub? If you want to know what really changed when switching from lenny to squeeze you could change it back to try the two fixes that I mentioned.> I''ve noticed that when debootstrap install the system it install the > linux-image and not linux-modules. > >From mail1.log, debian squeeze and xen4.0: > > The following extra packages will be installed: > firmware-linux-free libuuid-perl linux-base linux-image-2.6.32-5-xen-amd64 > Suggested packages: > linux-doc-2.6.32 grub > The following NEW packages will be installed: > firmware-linux-free libuuid-perl linux-base linux-image-2.6.32-5-xen-amd64 > linux-image-xen-amd64 > > While from mail1.log with xen3.2 and debian lenny: > > The following NEW packages will be installed: > linux-modules-2.6.26-2-xen-amd64 >Wow, that, I think, is a good thing! The linux-image package contains the modules but by also including the kernel and the base packages it will leave you with a much more "complete" domU. You could not have booted the old lenny domU with pygrub because the domU file system didn''t even contain a kernel image or initrd. Those were always taken from dom0''s /boot/. Thats what the "root=" and "ramdisk=" parameters in your mail1.cfg are for. BUT that made your domU depend much more on the state of your dom0. Now with pygrub you can update the kernel in domU, have it reboot and pygrub will pick up the new kernel from your domU''s file system when xen creates your domU VM. (be sure to read and *understand* the release notes on xen/pygrub/grub2 issues though). I personally like that change. It will make it easier to migrate PVM domUs that I create with squeeze to the next debian release. Currently I have PVM domUs from Etch and Lenny on top of a squeeze xen-4.0.1 linux-2.6.32 and I had to copy the old domU kernels and initrds to my squeeze box as well as the /etc/xen/machine.cfg files and the domUs disk images. In the future I will only need the config file and the disk images. (Actually my domU''s disk images are now on an iSCSI storage now. So I will not have to worry about migrating those and ultimately I want to move even the config files to a location that is shared by all my xen dom0 hosts. But thats a different story and I guess I''ll have to read up on GFS(2?) or some other cluster file system.) cheers -henrik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mauro
2011-Feb-11 11:38 UTC
Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
On 11 February 2011 11:12, Henrik Langos <hlangos-xen@innominate.com> wrote:> On Fri, Feb 11, 2011 at 10:04:44AM +0000, Mauro wrote: >> On 11 February 2011 08:59, Henrik Langos <hlangos-xen@innominate.com> wrote: >> > 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. >> > > ... >> > >> > 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. >> > >> >> mail1.cfg: >> >> bootloader = ''/usr/lib/xen-default/bin/pygrub'' >> >> vcpus = ''4'' >> memory = ''2048'' >> >> # >> # Disk device(s). >> # >> root = ''/dev/xvda2 ro'' >> disk = [ >> ''phy:/dev/vg00/mail1-disk,xvda2,w'', >> ''phy:/dev/vg00/mail1-swap,xvda1,w'', >> ] >> >> >> # >> # Physical volumes >> # >> >> >> # >> # Hostname >> # >> name = ''mail1'' >> >> # >> # Networking >> # >> vif = [ ''ip=172.16.10.154,mac=00:16:3E:01:D7:24'' ] >> >> # >> # Behaviour >> # >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart >> >> It''s exactly as another DomU that runs with xen 3.2 on a debian lenny machine. >> The only difference is the bootloader = ''/usr/lib/xen-default/bin/pygrub''. > > Well, > > There is no "kernel=" or "ramdisk=" parameter in your mail1.cfg. > So I guess you removed those when you switched to using pygrub?No I don''t remove them, it is the default.> If you want to know what really changed when switching from lenny to > squeeze you could change it back to try the two fixes that I mentioned. > >> I''ve noticed that when debootstrap install the system it install the >> linux-image and not linux-modules. >> >From mail1.log, debian squeeze and xen4.0: >> >> The following extra packages will be installed: >> firmware-linux-free libuuid-perl linux-base linux-image-2.6.32-5-xen-amd64 >> Suggested packages: >> linux-doc-2.6.32 grub >> The following NEW packages will be installed: >> firmware-linux-free libuuid-perl linux-base linux-image-2.6.32-5-xen-amd64 >> linux-image-xen-amd64 >> >> While from mail1.log with xen3.2 and debian lenny: >> >> The following NEW packages will be installed: >> linux-modules-2.6.26-2-xen-amd64 >> > > Wow, that, I think, is a good thing! The linux-image package contains the modules > but by also including the kernel and the base packages it will leave you with a > much more "complete" domU. > > You could not have booted the old lenny domU with pygrub because the domU file system > didn''t even contain a kernel image or initrd. Those were always taken from dom0''s /boot/. > Thats what the "root=" and "ramdisk=" parameters in your mail1.cfg are for. BUT that made > your domU depend much more on the state of your dom0. > > Now with pygrub you can update the kernel in domU, have it reboot and pygrub will pick > up the new kernel from your domU''s file system when xen creates your domU VM. (be sure > to read and *understand* the release notes on xen/pygrub/grub2 issues though). > > I personally like that change. It will make it easier to migrate PVM domUs that I create > with squeeze to the next debian release. Currently I have PVM domUs from Etch and Lenny > on top of a squeeze xen-4.0.1 linux-2.6.32 and I had to copy the old domU kernels and > initrds to my squeeze box as well as the /etc/xen/machine.cfg files and the domUs disk > images. > > In the future I will only need the config file and the disk images. (Actually my domU''s > disk images are now on an iSCSI storage now. So I will not have to worry about migrating > those and ultimately I want to move even the config files to a location that is shared > by all my xen dom0 hosts. But thats a different story and I guess I''ll have to read up > on GFS(2?) or some other cluster file system.)Ok, you convinced me to use pygrub. I have many doubts on using DomU in a SAN system, but for this I open a new thread. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matt Richardson
2011-Feb-11 20:08 UTC
Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
On Fri, Feb 11, 2011 at 3:38 AM, Mauro <mrsanna1@gmail.com> wrote:> On 11 February 2011 11:12, Henrik Langos <hlangos-xen@innominate.com> wrote: >> On Fri, Feb 11, 2011 at 10:04:44AM +0000, Mauro wrote:<snip>>>> > >>> > >>> >> 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. >>> > >>> >>> mail1.cfg: >>> >>> bootloader = ''/usr/lib/xen-default/bin/pygrub'' >>> >>> vcpus = ''4'' >>> memory = ''2048'' >>> >>> # >>> # Disk device(s). >>> # >>> root = ''/dev/xvda2 ro'' >>> disk = [ >>> ''phy:/dev/vg00/mail1-disk,xvda2,w'', >>> ''phy:/dev/vg00/mail1-swap,xvda1,w'', >>> ] >>> >>> >>> # >>> # Physical volumes >>> # >>> >>> >>> # >>> # Hostname >>> # >>> name = ''mail1'' >>> >>> # >>> # Networking >>> # >>> vif = [ ''ip=172.16.10.154,mac=00:16:3E:01:D7:24'' ] >>> >>> # >>> # Behaviour >>> # >>> on_poweroff = ''destroy'' >>> on_reboot = ''restart'' >>> on_crash = ''restart >>> >>> It''s exactly as another DomU that runs with xen 3.2 on a debian lenny machine. >>> The only difference is the bootloader = ''/usr/lib/xen-default/bin/pygrub''. >><snip>> > Ok, you convinced me to use pygrub. > I have many doubts on using DomU in a SAN system, but for this I open > a new thread. >I just got my back up xen machine updated to squeeze and started a new guest on it to test the upgrade procedure for the production machine. I''m using Dom0''s kernel (no pygrub), installed the base system via debootstrap and I don''t have linux-image-2.6.32-5-xen-amd64 installed on the DomU: rocket.cfg #-*- mode: python; -*- kernel = "/boot/vmlinuz-2.6.32-5-xen-amd64" ramdisk = "/boot/initrd.img-2.6.32-5-xen-amd64" memory = 2048 name = "rocket" vif = [''bridge=xenbr0''] disk = [''phy:/dev/debian1/rocket-root,xvda1,w'', ''phy:/dev/debian1/rocket-home,xvda2,w'', ''phy:/dev/debian1/rocket-tmp,xvda3,w'', ''phy:/dev/debian1/rocket-usr,xvda4,w'', ''phy:/dev/debian1/rocket-var,xvda5,w'', ''phy:/dev/debian1/rocket-swap,xvda6,w''] ip = "192.168.1.7" netmask = "255.255.0.0" gateway = "192.168.1.1" hostname = "rocket" root = "/dev/xvda1 ro" extra = "console=hvc0 xencons=tty clocksource=jiffies" So the short of it is that I can confirm that the set up works without pygrub. However, I noticed that you specified ext4 in the xen-tools.cfg and I have seen elsewhere that people have had trouble with the defaults being wrong when file systems other than ext3 are specified. -- Matt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mauro
2011-Feb-11 21:40 UTC
Re: [Xen-users] Re: upgrade leny-squeeze, xen3.2-xen4.0, what''s wrong?
On 11 February 2011 20:08, Matt Richardson <shortpath@gmail.com> wrote:> On Fri, Feb 11, 2011 at 3:38 AM, Mauro <mrsanna1@gmail.com> wrote: >> On 11 February 2011 11:12, Henrik Langos <hlangos-xen@innominate.com> wrote: >>> On Fri, Feb 11, 2011 at 10:04:44AM +0000, Mauro wrote: > <snip> >>>> > >>>> > >>>> >> 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. >>>> > >>>> >>>> mail1.cfg: >>>> >>>> bootloader = ''/usr/lib/xen-default/bin/pygrub'' >>>> >>>> vcpus = ''4'' >>>> memory = ''2048'' >>>> >>>> # >>>> # Disk device(s). >>>> # >>>> root = ''/dev/xvda2 ro'' >>>> disk = [ >>>> ''phy:/dev/vg00/mail1-disk,xvda2,w'', >>>> ''phy:/dev/vg00/mail1-swap,xvda1,w'', >>>> ] >>>> >>>> >>>> # >>>> # Physical volumes >>>> # >>>> >>>> >>>> # >>>> # Hostname >>>> # >>>> name = ''mail1'' >>>> >>>> # >>>> # Networking >>>> # >>>> vif = [ ''ip=172.16.10.154,mac=00:16:3E:01:D7:24'' ] >>>> >>>> # >>>> # Behaviour >>>> # >>>> on_poweroff = ''destroy'' >>>> on_reboot = ''restart'' >>>> on_crash = ''restart >>>> >>>> It''s exactly as another DomU that runs with xen 3.2 on a debian lenny machine. >>>> The only difference is the bootloader = ''/usr/lib/xen-default/bin/pygrub''. >>> > > <snip> >> >> Ok, you convinced me to use pygrub. >> I have many doubts on using DomU in a SAN system, but for this I open >> a new thread. >> > > > I just got my back up xen machine updated to squeeze and started a new > guest on it to test the upgrade procedure for the production machine. > I''m using Dom0''s kernel (no pygrub), installed the base system via > debootstrap and I don''t have linux-image-2.6.32-5-xen-amd64 installed > on the DomU: > > rocket.cfg > > #-*- mode: python; -*- > kernel = "/boot/vmlinuz-2.6.32-5-xen-amd64" > ramdisk = "/boot/initrd.img-2.6.32-5-xen-amd64" > memory = 2048 > name = "rocket" > vif = [''bridge=xenbr0''] > disk = [''phy:/dev/debian1/rocket-root,xvda1,w'', > ''phy:/dev/debian1/rocket-home,xvda2,w'', > ''phy:/dev/debian1/rocket-tmp,xvda3,w'', > ''phy:/dev/debian1/rocket-usr,xvda4,w'', > ''phy:/dev/debian1/rocket-var,xvda5,w'', > ''phy:/dev/debian1/rocket-swap,xvda6,w''] > ip = "192.168.1.7" > netmask = "255.255.0.0" > gateway = "192.168.1.1" > hostname = "rocket" > root = "/dev/xvda1 ro" > extra = "console=hvc0 xencons=tty clocksource=jiffies" > > > So the short of it is that I can confirm that the set up works without > pygrub. However, I noticed that you specified ext4 in the > xen-tools.cfg and I have seen elsewhere that people have had trouble > with the defaults being wrong when file systems other than ext3 are > specified. >I''ve tried with ext3 too. I''ve upgraded only Dom0 from lenny to squeeze while DomUs are all fresh installations. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users