[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xen3.4.1 on Debian Lenny - network scripts bug?
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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |