Re: Booting DomU

Re: Booting DomU

[Stephan Böni]

Hi Kurt

> > After booting DomU (sometimes it works) i have no filesystem 
> > mounted and no
> > network started. Do i somewhat wrong?
> 
> How can it boot without finding its root filesystem?

After trying a dozen times to create my domU the root filesystem
has been mounted, but not all of the others.
 
> Anyway, I suspect your dom0 hotplug system is broken.
> What hotplug agent are you using?

Ehhh ???

> What distro?

SUSE 10.0

> - Is udevd running?

# ps aux | grep udev
root      2387  0.0  0.5   7104  1028 ?        S<s  10:30   0:02 /sbin/udevd --daemon --stop-exec-queue

> - What's /proc/sys/kernel/hotplug

# cat /proc/sys/kernel/hotplug

(nothing)

Stephan

Re: Booting DomU

[Kurt Garloff]

[-- Attachment #1.1: Type: text/plain, Size: 1087 bytes --]

Hi Stephan,

On Wed, Oct 19, 2005 at 03:31:34PM +0200, Stephan Böni wrote:
> After trying a dozen times to create my domU the root filesystem
> has been mounted, but not all of the others.

OK, not all block devs have been set up apparently.

> > Anyway, I suspect your dom0 hotplug system is broken.
> > What hotplug agent are you using?
> 
> Ehhh ???
> 
> > What distro?
> 
> SUSE 10.0

So do I (surprise!).

> > - Is udevd running?
> 
> # ps aux | grep udev
> root      2387  0.0  0.5   7104  1028 ?        S<s  10:30   0:02 /sbin/udevd --daemon --stop-exec-queue

OK, so it should work.

Your /etc/udev/rules.d/40-xen.rules
should point to /sbin/xen-vbd and xen-vif; you could add logger calls
there, so you can see what hotplug events reached your dom0 in the
syslog.

> > - What's /proc/sys/kernel/hotplug
> 
> # cat /proc/sys/kernel/hotplug
> 
> (nothing)

That's correct as well, as udevd already eats all the hotplug events.
But my fear is that the events just don't arrive :-(

Best,
-- 
Kurt Garloff, Director SUSE Labs, Novell Inc.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Booting DomU

[Gerd Knorr]

>>> - Is udevd running?
>> # ps aux | grep udev
>> root      2387  0.0  0.5   7104  1028 ?        S<s  10:30   0:02 /sbin/udevd --daemon --stop-exec-queue
> 
> OK, so it should work.
> 
> Your /etc/udev/rules.d/40-xen.rules
> should point to /sbin/xen-vbd and xen-vif; you could add logger calls
> there, so you can see what hotplug events reached your dom0 in the
> syslog.

/etc/udev/rules.d/40-xen.rules and /sbin/xen-* are not needed any more 
with latest versions.  The xen tools install a udev rules file if they 
find a udev version recent enougth, for me this works as-is.

> That's correct as well, as udevd already eats all the hotplug events.
> But my fear is that the events just don't arrive :-(

The block script calls should show up in /var/log/messages already with 
latest tools.

cheers,

   Gerd

Re: Booting DomU

[Stephan Böni]

Hi Ewan

> > > > That's correct as well, as udevd already eats all the 
> > > hotplug events.
> > > > But my fear is that the events just don't arrive :-(
> > > 
> > > The block script calls should show up in /var/log/messages 
> > > already with latest tools.
> > 
> > I can find in /var/log/messages an interesting thing. For all
> > 16 devices i've found an entry like:
> > "...xen1 logger: /etc/xen/scripts/block: bind ..."
> > But only for 9 devices i've found an entry like:
> > "...xen1 logger: /etc/xen/scripts/block: Writing backend/vbd/1/..."
> > 
> > On the second try i've found 12 "Writing backend" entries and on
> > the third try 10 of them.
> > 
> > If /dev/xenvg/inhouse-root (that's hda1) one of them, i can logon
> > to my domU. The missing /dev/hd*'s are these ones, which haven't
> > a "Writing backend" entry in the /var/log/messages file.
> 
> What version of Xen are you running?  That sounds to me like 
> a transaction
> problem in xenstore-write that was fixed on Oct 12 -- changeset 7343.

It's changeset 7398.

Stephan

Re: Booting DomU

[Stephan Böni]

Hi Ewan

> > > > That's correct as well, as udevd already eats all the 
> > > hotplug events.
> > > > But my fear is that the events just don't arrive :-(
> > > 
> > > The block script calls should show up in /var/log/messages 
> > > already with latest tools.
> > 
> > I can find in /var/log/messages an interesting thing. For all
> > 16 devices i've found an entry like:
> > "...xen1 logger: /etc/xen/scripts/block: bind ..."
> > But only for 9 devices i've found an entry like:
> > "...xen1 logger: /etc/xen/scripts/block: Writing backend/vbd/1/..."
> > 
> > On the second try i've found 12 "Writing backend" entries and on
> > the third try 10 of them.
> > 
> > If /dev/xenvg/inhouse-root (that's hda1) one of them, i can logon
> > to my domU. The missing /dev/hd*'s are these ones, which haven't
> > a "Writing backend" entry in the /var/log/messages file.
> 
> What version of Xen are you running?  That sounds to me like 
> a transaction
> problem in xenstore-write that was fixed on Oct 12 -- changeset 7343.

I'm using changeset 7398.

Stephan

Re: Booting DomU

[Stephan Böni]

Hi Gerd

> > That's correct as well, as udevd already eats all the 
> hotplug events.
> > But my fear is that the events just don't arrive :-(
> 
> The block script calls should show up in /var/log/messages 
> already with latest tools.

I can find in /var/log/messages an interesting thing. For all
16 devices i've found an entry like:
"...xen1 logger: /etc/xen/scripts/block: bind ..."
But only for 9 devices i've found an entry like:
"...xen1 logger: /etc/xen/scripts/block: Writing backend/vbd/1/..."

On the second try i've found 12 "Writing backend" entries and on
the third try 10 of them.

If /dev/xenvg/inhouse-root (that's hda1) one of them, i can logon
to my domU. The missing /dev/hd*'s are these ones, which haven't
a "Writing backend" entry in the /var/log/messages file.

Stephan

Re: Booting DomU

[Ewan Mellor]

On Wed, Oct 19, 2005 at 05:52:47PM +0200, Stephan Böni wrote:

> Hi Gerd
> 
> > > That's correct as well, as udevd already eats all the 
> > hotplug events.
> > > But my fear is that the events just don't arrive :-(
> > 
> > The block script calls should show up in /var/log/messages 
> > already with latest tools.
> 
> I can find in /var/log/messages an interesting thing. For all
> 16 devices i've found an entry like:
> "...xen1 logger: /etc/xen/scripts/block: bind ..."
> But only for 9 devices i've found an entry like:
> "...xen1 logger: /etc/xen/scripts/block: Writing backend/vbd/1/..."
> 
> On the second try i've found 12 "Writing backend" entries and on
> the third try 10 of them.
> 
> If /dev/xenvg/inhouse-root (that's hda1) one of them, i can logon
> to my domU. The missing /dev/hd*'s are these ones, which haven't
> a "Writing backend" entry in the /var/log/messages file.

What version of Xen are you running?  That sounds to me like a transaction
problem in xenstore-write that was fixed on Oct 12 -- changeset 7343.

Ewan.

Re: Booting DomU

[Stephan Böni]

Hi Kurt

> > After trying a dozen times to create my domU the root filesystem
> > has been mounted, but not all of the others.
> 
> OK, not all block devs have been set up apparently.
> 
> > > What distro?
> > 
> > SUSE 10.0
> 
> So do I (surprise!).
> 
> Your /etc/udev/rules.d/40-xen.rules
> should point to /sbin/xen-vbd and xen-vif;

Yes, it looks like. Here is the file content:

# xen-backend block devices
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vbd", ACTION=="add",    RUN+="/sbin/xen-vbd %k up"
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vbd", ACTION=="remove", RUN+="/sbin/xen-vbd %k down"
 
# xen-backend network devices
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vif", ACTION=="online", RUN+="/sbin/xen-vif %k up"
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vif", ACTION=="remove", RUN+="/sbin/xen-vif %k down"

> you could add logger calls
> there, so you can see what hotplug events reached your dom0 in the
> syslog.

How do i that? Can you explain me the syntax or just write me the needed entries?

> > > - What's /proc/sys/kernel/hotplug
> > 
> > # cat /proc/sys/kernel/hotplug
> > 
> > (nothing)
> 
> That's correct as well, as udevd already eats all the hotplug events.
> But my fear is that the events just don't arrive :-(

Yes, but only some of these events do not arrive. In my domU it looks
like that:

# ls /dev/hd*
/dev/hda1   /dev/hda13  /dev/hda3  /dev/hda8  /dev/hdb1
/dev/hda11  /dev/hda14  /dev/hda7  /dev/hda9  /dev/hdc1

The set of available hd* devices changes on every domU restart.
Sometimes i can't start my domU. I think that's when the root device
hda1 isn't present.

But in my config file are always the following devices defined:

disk = [ 'phy:xenvg/inhouse-root,hda1,w',
         'phy:xenvg/inhouse-cdb,hda2,w',
         'phy:xenvg/inhouse-comserver,hda3,w',
         'phy:xenvg/inhouse-docarchive,hda4,w',
         'phy:xenvg/inhouse-home,hda5,w',
         'phy:xenvg/inhouse-journal,hda6,w',
         'phy:xenvg/inhouse-mailserver,hda7,w',
         'phy:xenvg/inhouse-pos,hda8,w',
         'phy:xenvg/inhouse-pub,hda9,w',
         'phy:xenvg/inhouse-srv,hda10,w',
         'phy:xenvg/inhouse-tmp,hda11,w',
         'phy:xenvg/inhouse-transfer,hda12,w',
         'phy:xenvg/inhouse-usr,hda13,w',
         'phy:xenvg/inhouse-var,hda14,w',
         'phy:xenvg/inhouse-swap,hdb1,w',
         'phy:xenvg/susedvd,hdc1,r' ]

Stephan

Booting DomU

[Stephan Böni]

After booting DomU (sometime it works) i have no filesystem mounted and no
network started. Do i somewhat wrong?


Linux version 2.6.13-15d-xen (geeko@buildhost) (gcc version 4.0.2 20050901 (prer
elease) (SUSE Linux)) #1 Mon Oct 17 18:53:23 UTC 2005
kernel direct mapping tables upto 80000000 @ f5b000-135e000
On node 0 totalpages: 524288
  DMA zone: 524288 pages, LIFO batch:31
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
No mptable found.
Built 1 zonelists
Kernel command line:  root=/dev/hda1 ro 3
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 3200.110 MHz processor.
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Software IO TLB disabled
Memory: 2042880k/2097152k available (2357k kernel code, 53876k reserved, 821k da
ta, 156k init)
Calibrating delay using timer specific routine.. 6402.73 BogoMIPS (lpj=32013673)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU:                   Intel(R) Xeon(TM) CPU 3.20GHz stepping 01
checking if image is initramfs... it is
NET: Registered protocol family 16
ACPI: Subsystem revision 20050408
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: System does not support PCI
PCI: System does not support PCI
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
Grant table initialized
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1129721265.940:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
vesafb: cannot reserve video memory at 0x0
vesafb: abort, cannot ioremap video memory 0x0 @ 0x0
Trying to free nonexistent resource <00000000-ffffffffffffffff>
vesafb: probe of vesafb.0 failed with error -5
Failed to obtain physical IRQ 8
rtc: Got 0xff, disable
Non-volatile memory driver v1.2
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
Neither TPM-BE Domain nor INIT domain!
xen_blk: Initialising virtual block device driver
Registering block device major 3
Registering block device major 22
xen_net: Initialising virtual ethernet driver.
xen_tpm_fr: Initialising the vTPM driver.
mice: PS/2 mouse device common for all mice
input: PC Speaker
md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 3.38
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 524288 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
NET: Registered protocol family 1
SCSI subsystem initialized
libata version 1.12 loaded.
Fusion MPT base driver 3.03.02
Copyright (c) 1999-2005 LSI Logic Corporation
mptspi: module not supported by Novell, setting U taint flag.
Fusion MPT SPI Host driver 3.03.02
QLogic Fibre Channel HBA Driver
ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18,
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names

Re: Booting DomU

[Kurt Garloff]

[-- Attachment #1.1: Type: text/plain, Size: 650 bytes --]

Hi Stephan,

On Wed, Oct 19, 2005 at 01:38:54PM +0200, Stephan Böni wrote:
> After booting DomU (sometime it works) i have no filesystem mounted and no
> network started. Do i somewhat wrong?

How can it boot without finding its root filesystem?

Anyway, I suspect your dom0 hotplug system is broken.
What hotplug agent are you using? What distro?
- Is udevd running?
- What's /proc/sys/kernel/hotplug

Best,
-- 
Kurt Garloff                   <kurt@garloff.de>             [Koeln, DE]
Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL]
Linux: SUSE Labs (Director)    <garloff@suse.de>            [Novell Inc]

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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