Re: upgrade to new xen domU on old xen dom0?
On Sat, 2010-03-27 at 22:09 +0100, Josip Rodin wrote: On Sat, Mar 27, 2010 at 06:11:15PM +, Ian Campbell wrote: OK, that works, thanks. We have got to get this documented somewhere now that the deprecated option is broken. There is no mention of it at http://wiki.debian.org/Xen and simple googling is far from conclusive. Would you mind updating the wiki with your findings? OK, done. Speaking of the new domU, does anyone know anything about this: [0.00] Calgary: detecting Calgary via BIOS EBDA area [0.00] Calgary: Unable to locate Rio Grande table in EBDA - bailing! The pvops kernel doesn't have as much opportunity to prevent probing of stuff you would only see on native as the old style kernels, so you will tend to see more attempts to find stuff which isn't there. This seems to be correctly not finding Calgary (something you would not expect to find domU). I find drivers which make noise even before they have tried to detect their hardware and ones that print a message when they don't find it to be a bit anti-social but other than that I think everything is fine. Ian. -- Ian Campbell You're just the sort of person I imagined marrying, when I was little... except, y'know, not green... and without all the patches of fungus. -- Swamp Thing signature.asc Description: This is a digitally signed message part
Re: upgrade to new xen domU on old xen dom0?
On Sun, 2010-03-28 at 08:41 +0100, Ian Campbell wrote: On Sat, 2010-03-27 at 22:09 +0100, Josip Rodin wrote: On Sat, Mar 27, 2010 at 06:11:15PM +, Ian Campbell wrote: OK, that works, thanks. We have got to get this documented somewhere now that the deprecated option is broken. There is no mention of it at http://wiki.debian.org/Xen and simple googling is far from conclusive. Would you mind updating the wiki with your findings? OK, done. Speaking of the new domU, does anyone know anything about this: [0.00] Calgary: detecting Calgary via BIOS EBDA area [0.00] Calgary: Unable to locate Rio Grande table in EBDA - bailing! The pvops kernel doesn't have as much opportunity to prevent probing of stuff you would only see on native as the old style kernels, so you will tend to see more attempts to find stuff which isn't there. This seems to be correctly not finding Calgary (something you would not expect to find domU). I find drivers which make noise even before they have tried to detect their hardware and ones that print a message when they don't find it to be a bit anti-social but other than that I think everything is fine. In fairness the messages in this case are at KERN_DEBUG level, so at least they wouldn't normally be printed, although they do pollute dmesg. Ian. -- Ian Campbell If I'm over the hill, why is it I don't recall ever being on top? -- Jerry Muscha signature.asc Description: This is a digitally signed message part
upgrade to new xen domU on old xen dom0?
Hi, If I try to boot 2.6.32-4-xen-amd64 on a 2.6.26-2-xen-amd64 (lenny) dom0, it gets stuck at: [0.120653] XENBUS: Device with no driver: device/vbd/769 [0.120658] XENBUS: Device with no driver: device/vif/0 [0.120663] XENBUS: Device with no driver: device/console/0 [0.120679] /build/mattems-linux-2.6_2.6.32-10-amd64-Ff7Wwa/linux-2.6-2.6.32-10/debian/build/source_amd64_xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.120822] Freeing unused kernel memory: 588k freed [0.121088] Write protecting the kernel read-only data: 4264k Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/thermal.ko): No such device [0.610445] blkfront: xvda1: barriers enabled done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... Can anything be done? I thought the domUs were supposed to be a safe upgrade? -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327105625.ga20...@orion.carnet.hr
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 11:56:25AM +0100, Josip Rodin wrote: If I try to boot 2.6.32-4-xen-amd64 on a 2.6.26-2-xen-amd64 (lenny) dom0, it gets stuck at: What was the last known working version? [0.120653] XENBUS: Device with no driver: device/vbd/769 [0.120658] XENBUS: Device with no driver: device/vif/0 [0.120663] XENBUS: Device with no driver: device/console/0 [0.120679] /build/mattems-linux-2.6_2.6.32-10-amd64-Ff7Wwa/linux-2.6-2.6.32-10/debian/build/source_amd64_xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.120822] Freeing unused kernel memory: 588k freed [0.121088] Write protecting the kernel read-only data: 4264k Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/thermal.ko): No such device [0.610445] blkfront: xvda1: barriers enabled done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... You are supposed to provide the complete log. There are several possible pitfalls. If you are upgrading from an old-style image and followed old documentation it is most likely a wrong root device. Can anything be done? I thought the domUs were supposed to be a safe upgrade? It is: | $ cat /sys/hypervisor/type | xen | $ cat /proc/version | Linux version 2.6.32-4-amd64 (Debian 2.6.32-10) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Mar 17 03:23:53 UTC 2010 Bastian -- Only a fool fights in a burning house. -- Kank the Klingon, Day of the Dove, stardate unknown -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327112530.gb...@wavehammer.waldi.eu.org
Re: upgrade to new xen domU on old xen dom0?
On Sat, 2010-03-27 at 11:56 +0100, Josip Rodin wrote: Hi, If I try to boot 2.6.32-4-xen-amd64 on a 2.6.26-2-xen-amd64 (lenny) dom0, it gets stuck at: [0.120653] XENBUS: Device with no driver: device/vbd/769 [0.120658] XENBUS: Device with no driver: device/vif/0 [0.120663] XENBUS: Device with no driver: device/console/0 [0.120679] /build/mattems-linux-2.6_2.6.32-10-amd64-Ff7Wwa/linux-2.6-2.6.32-10/debian/build/source_amd64_xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.120822] Freeing unused kernel memory: 588k freed [0.121088] Write protecting the kernel read-only data: 4264k Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/thermal.ko): No such device [0.610445] blkfront: xvda1: barriers enabled done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... xen-blkfront is a module in the pvops based 2.6.32-x-xen-amd64 where as it was statically linked in the non-pvops 2.6.26-x-xen-and64 images. This already happened in Lenny for 32 bit guests (sort of) since the -686-bigmem kernel (which supports Xen) also uses modules for the drivers. I think the change is generally a step in the right direction. Perhaps running mkinitramfs within the 2.6.26 environment causes the 2.6.32 initrd to not contain the correct module? (since it can't detect the requirement for the module because the current kernel has it statically linked?) This should be fixable with some configuration in the guest (e.g. add the modules to /etc/initramfs-tools/modules). Ian. -- Ian Campbell Not responsible for merchandise left over 30 days. signature.asc Description: This is a digitally signed message part
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 12:02:01PM +, Ian Campbell wrote: On Sat, 2010-03-27 at 11:56 +0100, Josip Rodin wrote: [0.610445] blkfront: xvda1: barriers enabled xen-blkfront is a module in the pvops based 2.6.32-x-xen-amd64 where as it was statically linked in the non-pvops 2.6.26-x-xen-and64 images. This already happened in Lenny for 32 bit guests (sort of) since the -686-bigmem kernel (which supports Xen) also uses modules for the drivers. I think the change is generally a step in the right direction. The device was properly detected, so the module is loaded. Bastian -- Worlds are conquered, galaxies destroyed -- but a woman is always a woman. -- Kirk, The Conscience of the King, stardate 2818.9 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327145351.ga5...@wavehammer.waldi.eu.org
Re: upgrade to new xen domU on old xen dom0?
On Sat, 2010-03-27 at 15:53 +0100, Bastian Blank wrote: On Sat, Mar 27, 2010 at 12:02:01PM +, Ian Campbell wrote: On Sat, 2010-03-27 at 11:56 +0100, Josip Rodin wrote: [0.610445] blkfront: xvda1: barriers enabled xen-blkfront is a module in the pvops based 2.6.32-x-xen-amd64 where as it was statically linked in the non-pvops 2.6.26-x-xen-and64 images. This already happened in Lenny for 32 bit guests (sort of) since the -686-bigmem kernel (which supports Xen) also uses modules for the drivers. I think the change is generally a step in the right direction. The device was properly detected, so the module is loaded. Oh yes, I saw the device with no driver line but missed the subsequent blkfront one. Ian. -- Ian Campbell I can write better than anybody who can write faster, and I can write faster than anybody who can write better. -- A. J. Liebling signature.asc Description: This is a digitally signed message part
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 12:02:01PM +, Ian Campbell wrote: xen-blkfront is a module in the pvops based 2.6.32-x-xen-amd64 where as it was statically linked in the non-pvops 2.6.26-x-xen-and64 images. This already happened in Lenny for 32 bit guests (sort of) since the -686-bigmem kernel (which supports Xen) also uses modules for the drivers. I think the change is generally a step in the right direction. Perhaps running mkinitramfs within the 2.6.26 environment causes the 2.6.32 initrd to not contain the correct module? (since it can't detect the requirement for the module because the current kernel has it statically linked?) This should be fixable with some configuration in the guest (e.g. add the modules to /etc/initramfs-tools/modules). I ran the default install of the image package on the guest running .18, and then copied the image and initrd over to the parent. I extracted that initrd image now and I see lib/modules/2.6.32-4-xen-amd64/kernel/drivers/block/xen-blkfront.ko in it. Are you saying it could have gotten missed by the initrd init scripts even though it's there? Couldn't we fix that automatism? I diffed the trees and noticed that kernel/drivers/net/xen-netfront.ko is missing from the initrd, but that's probably non-fatal. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327161006.ga25...@orion.carnet.hr
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 11:56:25AM +0100, joy wrote: [0.610445] blkfront: xvda1: barriers enabled done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... Can anything be done? I thought the domUs were supposed to be a safe upgrade? I missed Bastian's message as I'm not subscribed - please keep me in Cc:. What was the last known working version? The one from lenny. Well, for some values of working at least :) You are supposed to provide the complete log. There are several possible pitfalls. If you are upgrading from an old-style image and followed old documentation it is most likely a wrong root device. I just replaced the kernel and ramdisk settings on the old dom0. The relevant settings, that work with our .26 and .18, are: root= '/dev/hda1 ro' disk= [ 'phy:pavo/lastovo,hda1,w' ] What do I need to change? -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327161510.ga27...@orion.carnet.hr
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 05:15:10PM +0100, Josip Rodin wrote: I missed Bastian's message as I'm not subscribed - please keep me in Cc:. Please add this to your muttrc then: | lists @lists.debian.org What was the last known working version? The one from lenny. Well, for some values of working at least :) Well, Lenny have two variants. The early pv-ops and the oldstyle one. If you are upgrading from an old-style image and followed old documentation it is most likely a wrong root device. I just replaced the kernel and ramdisk settings on the old dom0. The relevant settings, that work with our .26 and .18, are: root= '/dev/hda1 ro' disk= [ 'phy:pavo/lastovo,hda1,w' ] Yeah, using [hs]d[a-z]* was already deprecated in Lenny. What do I need to change? Use xvda as device name. Bastian -- Every living thing wants to survive. -- Spock, The Ultimate Computer, stardate 4731.3 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327162828.ga7...@wavehammer.waldi.eu.org
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 05:28:28PM +0100, Bastian Blank wrote: What was the last known working version? The one from lenny. Well, for some values of working at least :) Well, Lenny have two variants. The early pv-ops and the oldstyle one. We had early pvops in lenny? Where? :) If you are upgrading from an old-style image and followed old documentation it is most likely a wrong root device. I just replaced the kernel and ramdisk settings on the old dom0. The relevant settings, that work with our .26 and .18, are: root= '/dev/hda1 ro' disk= [ 'phy:pavo/lastovo,hda1,w' ] Yeah, using [hs]d[a-z]* was already deprecated in Lenny. What do I need to change? Use xvda as device name. OK, that works, thanks. We have got to get this documented somewhere now that the deprecated option is broken. There is no mention of it at http://wiki.debian.org/Xen and simple googling is far from conclusive. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327170726.ga6...@orion.carnet.hr
Re: upgrade to new xen domU on old xen dom0?
On Sat, 2010-03-27 at 17:10 +0100, Josip Rodin wrote: I extracted that initrd image now and I see lib/modules/2.6.32-4-xen-amd64/kernel/drivers/block/xen-blkfront.ko in it. Are you saying it could have gotten missed by the initrd init scripts even though it's there? I was saying it might not be there but Bastian pointed out that I'd missed the log message which tells us it was loaded successfully. Couldn't we fix that automatism? No need ;-) I diffed the trees and noticed that kernel/drivers/net/xen-netfront.ko is missing from the initrd, but that's probably non-fatal. Yep, that's fine/expected. Ian. -- Ian Campbell A clever prophet makes sure of the event first. signature.asc Description: This is a digitally signed message part
Re: upgrade to new xen domU on old xen dom0?
On Sat, 2010-03-27 at 18:07 +0100, Josip Rodin wrote: On Sat, Mar 27, 2010 at 05:28:28PM +0100, Bastian Blank wrote: What was the last known working version? The one from lenny. Well, for some values of working at least :) Well, Lenny have two variants. The early pv-ops and the oldstyle one. We had early pvops in lenny? Where? :) In the 686-bigmem kernel flavour for i386. x86_64 pvops didn't happen until 2.6.27 so that was missed out of Lenny. OK, that works, thanks. We have got to get this documented somewhere now that the deprecated option is broken. There is no mention of it at http://wiki.debian.org/Xen and simple googling is far from conclusive. Would you mind updating the wiki with your findings? Thanks, Ian. -- Ian Campbell It would be illogical to kill without reason. -- Spock, Journey to Babel, stardate 3842.4 signature.asc Description: This is a digitally signed message part
Re: upgrade to new xen domU on old xen dom0?
On Sat, Mar 27, 2010 at 06:11:15PM +, Ian Campbell wrote: OK, that works, thanks. We have got to get this documented somewhere now that the deprecated option is broken. There is no mention of it at http://wiki.debian.org/Xen and simple googling is far from conclusive. Would you mind updating the wiki with your findings? OK, done. Speaking of the new domU, does anyone know anything about this: [0.00] Calgary: detecting Calgary via BIOS EBDA area [0.00] Calgary: Unable to locate Rio Grande table in EBDA - bailing! -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100327210925.ga29...@orion.carnet.hr
