[Xen-users] (no subject)

[Laurent.Henry@xxxxxxxx]

Hi,
      I am using a Suse 10.2 Dom0 (xen 3.0.3) on an old Dell poweredge.
I succesfully installed a Suse 10.2 DomU (paravirtualization).
All is fine and working very well.

Now i am trying a Suse 10.3 domU on the same machine.

I tried different ways, and each time i can't achieve my setup:

- xm create -c /mnt/sdb1/vm-suse10.3.cfg 
kernel=/root/Kernel/inst.xen-2.6.22.5-31-i586-kernel
initrd=/root/Kernel/inst.xen-2.6.22.5-31-i586-ramdisk

is waiting forever during boot:
"[...]Non-volatile memory driver v1.2
NET: Registered protocol family 17
loop: module loaded
XENBUS: Waiting for devices to initialise:
295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
XENBUS: Timeout connecting to device: device/vbd/769 (local state 3,
remote state 2)
XENBUS: Timeout connecting to device: device/vbd/770 (local state 3,
remote state 2)
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path."

-Using a 10.3 network boot cd to launch the domU setup shows well the
firsts yast setup menues but the install fails after the parameters steps
as well.

Has someone experienced the same and have some idea to get rid of this ?

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