Xen users - Aug 2011 - Xen 4.0.1 DomU vbd timeouts under pvops dom0-kernel

Good day,

I succesfully built a 2.6.39.4 with all the relevant xen support and booted my
dom0 into this (previously this machine ran the RHEL5 kernel-xen with no
glitches).

DomU machines get succesfully started as far as Xen is concerned (all devices
connected, domain unpaused), but then I get the dreaded "XENBUS: Waiting
for devices to initialise: 295s...290s...285s..." for both vbd''s
assigned to the guest.

After the timeouts, the guest goes into a kernel panic. Guest worked fine when
dom0-kernel was 2.6.18 and nothing else was changed.

This is the output of xm block-list for the guest. I dont know what "state
3" means.

(51713
    ((virtual-device 51713)
        (device-type disk)
        (protocol x86_64-abi)
        (backend-id 0)
        (state 3)
        (backend /local/domain/0/backend/vbd/2/51713)
        (ring-ref 8)
        (event-channel 8)
    )
)
(51714
    ((virtual-device 51714)
        (device-type disk)
        (protocol x86_64-abi)
        (backend-id 0)
        (state 3)
        (backend /local/domain/0/backend/vbd/2/51714)
        (ring-ref 9)
        (event-channel 9)
    )
)

Am I missing something?

Cheers,
Pim


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

Same effect running Xen4.1.1.

Devices initialize correctly, but domU cannot connect to them.

Pi

On Aug 11, 2011, at 10:54 , Pim van Riezen wrote:
> Good day,
> 
> I succesfully built a 2.6.39.4 with all the relevant xen support and booted
my dom0 into this (previously this machine ran the RHEL5 kernel-xen with no
glitches).
> 
> DomU machines get succesfully started as far as Xen is concerned (all
devices connected, domain unpaused), but then I get the dreaded "XENBUS:
Waiting for devices to initialise: 295s...290s...285s..." for both
vbd''s assigned to the guest.
> 
> After the timeouts, the guest goes into a kernel panic. Guest worked fine
when dom0-kernel was 2.6.18 and nothing else was changed.
> 
> This is the output of xm block-list for the guest. I dont know what
"state 3" means.
> 
> (51713
>    ((virtual-device 51713)
>        (device-type disk)
>        (protocol x86_64-abi)
>        (backend-id 0)
>        (state 3)
>        (backend /local/domain/0/backend/vbd/2/51713)
>        (ring-ref 8)
>        (event-channel 8)
>    )
> )
> (51714
>    ((virtual-device 51714)
>        (device-type disk)
>        (protocol x86_64-abi)
>        (backend-id 0)
>        (state 3)
>        (backend /local/domain/0/backend/vbd/2/51714)
>        (ring-ref 9)
>        (event-channel 9)
>    )
> )
> 
> Am I missing something?
> 
> Cheers,
> Pim
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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