[Pkg-xen-devel] Bug#385934: Fixed by using xen-hypervisor-3.0-unstable-1-i386

[Thomas Stewart]

On Thu, Sep 07, 2006 at 03:54:12PM +0200, Thomas Schwinge wrote:
> Hello!
> 
> Indeed I can confirm that `xen-hypervisor-3.0-unstable-1-i386' together
> with `linux-image-2.6.17-2-xen-686' gets the Dom0 going again.  So far, I
> had no luck to get a DomU running, however:
> 
> #v+
> thomas at taylor:~ $ sudo /etc/init.d/xendomains restart
> Shutting down Xen domains:Starting auto Xen domains: riemannError: Device 0 (vif) could not be connected. Hotplug scripts not working.
> #v-

I got the same messsage, however if you create a dom without networking or
disable networking, I found that the a dom will start and run fine.

I think this networking issue has something todo with kernel module that
creates the devices.

It's somethign todo with:
/lib/modules/2.6.17-2-xen-686/kernel/drivers/xen/netback/netloop.ko

I found that if I added netloop to /etc/modules, everything works ok.

I have a feeling that its named changed and whatever was auto loading
it before is not now. (Thow I have no idea)

Regards
--
Tom