FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-27-2010, 09:56 AM
Josip Rodin
 
Default 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327105625.GA20756@orion.carnet.hr">http://lists.debian.org/20100327105625.GA20756@orion.carnet.hr
 
Old 03-27-2010, 10:25 AM
Bastian Blank
 
Default 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) (maks@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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327112530.GB757@wavehammer.waldi.eu.org">http ://lists.debian.org/20100327112530.GB757@wavehammer.waldi.eu.org
 
Old 03-27-2010, 11:02 AM
Ian Campbell
 
Default 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.
 
Old 03-27-2010, 01:53 PM
Bastian Blank
 
Default upgrade to new xen domU on old xen dom0?

On Sat, Mar 27, 2010 at 12:02:01PM +0000, 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327145351.GA5982@wavehammer.waldi.eu.org">htt p://lists.debian.org/20100327145351.GA5982@wavehammer.waldi.eu.org
 
Old 03-27-2010, 02:16 PM
Ian Campbell
 
Default 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 +0000, 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
 
Old 03-27-2010, 03:10 PM
Josip Rodin
 
Default upgrade to new xen domU on old xen dom0?

On Sat, Mar 27, 2010 at 12:02:01PM +0000, 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327161006.GA25224@orion.carnet.hr">http://lists.debian.org/20100327161006.GA25224@orion.carnet.hr
 
Old 03-27-2010, 03:15 PM
Josip Rodin
 
Default 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 = [ 'phyavo/lastovo,hda1,w' ]

What do I need to change?

--
2. That which causes joy or happiness.


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327161510.GA27318@orion.carnet.hr">http://lists.debian.org/20100327161510.GA27318@orion.carnet.hr
 
Old 03-27-2010, 03:28 PM
Bastian Blank
 
Default 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 = [ 'phyavo/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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327162828.GA7246@wavehammer.waldi.eu.org">htt p://lists.debian.org/20100327162828.GA7246@wavehammer.waldi.eu.org
 
Old 03-27-2010, 04:07 PM
Josip Rodin
 
Default 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 = [ 'phyavo/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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100327170726.GA6753@orion.carnet.hr">http://lists.debian.org/20100327170726.GA6753@orion.carnet.hr
 
Old 03-27-2010, 05:08 PM
Ian Campbell
 
Default 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.
 

Thread Tools




All times are GMT. The time now is 06:13 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org