WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen 4.1.1 DomU vbd timeouts under pvops dom0-kernel

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 4.1.1 DomU vbd timeouts under pvops dom0-kernel
From: Pim van Riezen <pi+lists@xxxxxxxxxxxx>
Date: Thu, 11 Aug 2011 11:48:17 +0200
Delivery-date: Thu, 11 Aug 2011 02:49:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EF9D8C00-4A3B-4F97-B73C-4B41694A99CE@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <EF9D8C00-4A3B-4F97-B73C-4B41694A99CE@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


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

<Prev in Thread] Current Thread [Next in Thread>