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] xen3.4.1 on Debian Lenny - network scripts bug?

To: Rick McNeal <rick.mcneal@xxxxxxx>
Subject: Re: [Xen-users] xen3.4.1 on Debian Lenny - network scripts bug?
From: Peter Braun <xenware@xxxxxxxxx>
Date: Fri, 7 Aug 2009 06:00:57 +0200
Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 06 Aug 2009 21:02:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uZyWQ0+2S4Jkaw32BwE4bBd48puCJimSk6fRqtuwPV8=; b=PhV6FD3iSaFIhMck35xQvXSjdoGqaF+wYFBGQqQGOtTAZqVH6OJ7NEUwCKw09wnBMp EhlQQCHGO/8C9GOZwkM99jND9xRHhPn0UU90Pbl249yIeg97EOa8MzXuU0vkPLE6xHPn Lx2i01YmKtx14IGSv7gNmCC6drXvrqoAw3Ev0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=W9MsKFfnTirWFFy2GhdDtUgG9kXJrGWNTJf+3KKOTr0delLmOnM+CsdUejbdlRwsC5 BQ0o54it1jH3tLKg2PvJV7Onzwsc6ded22Qkr7/HVnqLuz10DrlEHGaE3wA9dxbYV7ov tuhxaTDK1SR5XAnF0AAoNzwgZvtycrsiEI3FI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <acbf498f0908061646u4df437f2i8b323805296c6499@xxxxxxxxxxxxxx>
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: <acbf498f0908061546k1518982fi5108bdac62752f7f@xxxxxxxxxxxxxx> <104B8A9E-9AD3-4929-AEC4-1D60B91C062D@xxxxxxx> <acbf498f0908061646u4df437f2i8b323805296c6499@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Stock 2.6.18.8 -  xenified kernel --- works OK
reboot
2.6.30.2 - xenified kernel custom config --- problem

Maybe some problem kernel config missing?


Peter


2009/8/7 Peter Braun <xenware@xxxxxxxxx>:
> Unfortunately xend-config.sxp in correct state.
> So problem somewhere else.
>
> Peter
>
> 2009/8/7 Rick McNeal <rick.mcneal@xxxxxxx>:
>>
>> On Aug 6, 2009, at 4:46 PM, Peter Braun wrote:
>>
>>> Hi,
>>>
>>> running xen3.4.1 on Debian Lenny x64
>>>
>>> Xend startup without problems.
>>>
>>> Problem to startup any domU. The guest domain stalls in PAUSED state.
>>> When I try to unpause it - it runs with networking but after a while
>>> the domu is destroyed by some timeout from xm command.
>>>
>>> Than there is error to the console
>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
>>>
>>
>> I had the same problem. In my case at least this was caused by not
>> configuring Xen correctly. I had to modify /etc/xen/xend-config.sxp and
>> change the following line from:
>>
>> (network-script network-system)
>>
>> to
>>
>> (network-script network-bridge)
>>
>> Hope this change works for you.
>>
>>>
>>> xend.log:
>>>
>>> [2009-08-07 00:33:20 3423] DEBUG (DevController:139) Waiting for devices
>>> vif.
>>> [2009-08-07 00:33:20 3423] DEBUG (DevController:144) Waiting for 0.
>>> [2009-08-07 00:33:20 3423] DEBUG (DevController:629)
>>> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-s
>>> tatus.
>>> [2009-08-07 00:33:52 3423] INFO (XendDomain:1180) Domain
>>> debian.5-0.x86 (1) unpaused.
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2724)
>>> XendDomainInfo.destroy: domid=1
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2199) Destroying device
>>> model
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2206) Releasing devices
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2219) Removing vif/0
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:1134)
>>> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif
>>> /0
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2219) Removing vbd/2049
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:1134)
>>> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd
>>> /2049
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2219) Removing console/0
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:1134)
>>> XendDomainInfo.destroyDevice: deviceClass = console, device =
>>> console/0
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2204) No device model
>>> [2009-08-07 00:35:00 3423] DEBUG (XendDomainInfo:2206) Releasing devices
>>> [2009-08-07 00:36:35 3423] DEBUG (DevController:629)
>>> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-s
>>> tatus.
>>> [2009-08-07 00:36:35 3423] DEBUG (DevController:629)
>>> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-s
>>> tatus.
>>> [2009-08-07 00:36:35 3423] DEBUG (DevController:629)
>>> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-s
>>> tatus.
>>> [2009-08-07 00:36:35 3423] DEBUG (DevController:629)
>>> hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-s
>>> tatus.
>>>
>>>
>>>
>>>
>>>
>>> Any idea?
>>>
>>>
>>> Petr
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>
>> ----
>> Rick McNeal
>> rick.mcneal@xxxxxxx
>>
>> “Never blame a legislative body for not doing something. When they do
>> nothing, they don’t hurt anybody. When they do something is when they become
>> dangerous.” —Will Rogers
>>
>>
>>
>

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