Re: DOMU problem with vif

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Thu, Jan 29, 2015 at 05:54:30PM +0100, Roger Pau Monné wrote:
> El 29/01/15 a les 9.58, Manuel Bouyer ha escrit:
> > On Thu, Jan 29, 2015 at 12:05:08AM -0800, Phil Nelson wrote:
> >> Hello,
> >>
> >>     I've finally had time to start using xen ... and have been setting
> >> up a set of 4 machines with xen.   I'm using NetBSD/amd64, 6.1.5
> >> as DOM0 and using xen 4.1.   On three of the 4 machines, I have
> >> successfully set up a couple of DOMU domains.   Using an identical
> >> setup (except MAC address) I've been having problems getting
> >> the 4th machine to run any DOMU domains.     It continues to return
> >> the error:
> >>
> >> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> >>
> >> I have a bridge created the same way as on the three working machines.
> >>
> >> I have no clue where to go from here.   The machine has two real
> >> ethernet ports and have tried both of them with identical results.
> >>
> >> I have finally checked the dmesg of all the DOM0 kernels and have 
> >> found that the three working ones are essentially identical, but there
> >> the non-working one has some more interesting differences.   Following
> >> is a unified diff from a working kernel and the non-working.  I'm
> >> wondering if there is anything here that could explain why I can't
> >> start a DOMU on the mc2 machine.
> > 
> > I don't think the problem is there. what do you have in 
> > /var/log/xenbackend.log (or /var/log/xen/xenbackend.log) ?
> 
> xenbackendd should not be running if you are using xl, libxl will
> already take care of launching the necessary hotplug scripts:

He his running Xen 4.1, where xm is the only safe way.

> 
> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/libxl/libxl_device.c;h=0f50d0475d2e3604f2c9e960d315e19ac9cbfde7;hb=HEAD#l971
> 
> Upstream xencommons rc.d script doesn't launch xenbackendd any more:
> 
> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/hotplug/NetBSD/rc.d/xencommons.in;h=db03f22ff23ccb3b071d23c1e298275eb436c8c2;hb=HEAD
> 
> I will send a patch next week (if no one else beats me to it) to remove
> xenbackendd from the Xen source since now xm/xend is also gone (which

Also, libxl can lauch the scripts, but can also leave this job to xenbackendd
(run_hotplug_scripts=0 in xl.conf). 
So please  leave xenbackendd for now, it can still be usefull.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--