Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Tue, Feb 23, 2010 at 01:30:12PM -0000, Ian Tobin wrote:
> Hello,
> 
> Can anyone help?
> 
> I have again installed a fresh OS Debian Lenny 64bit and done the
> following
> 
> Xen:
>         downloaded xen-3.4.2.tar.gz and extract it
>         cd xen-3.4.2
>         make xen
>         make tools
>         make stubdom
>  
> cd dist/install/
> cp -R * /
>  
> downloaded Jeremys kernel
> 
> make menuconfig
> make bzImage
> make modules
> make modules_install
> add to /etc/fstab      none /proc/xen  xenfs  defaults 0 0
> cp -a arch/x86/boot/bzImage /boot/vmlinuz-2.6.31.6
> cp -a System.map /boot/System.map-2.6.31.6
> cp -a .config /boot/config-2.6.31.6
> depmod -a
> update-initramfs -c -k 2.6.31.6
> 
> added grub line and rebooted. XEN starts but DomU just keeps coming up
> about hotplug scripts not working.
> 
> Anyone?
>

Does "xm log" have more details about the error? Do you have udev installed in 
dom0?

What's your udev version?

-- Pasi
 
> Thanks
> 
> Ian
> 
> 
> -----Original Message-----
> From: Tej [mailto:bewith.tej@xxxxxxxxx] 
> Sent: 20 February 2010 12:04
> To: Ian Tobin
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Error: Device 0 (vif) could not be connected.
> Hotplug scripts not working
> 
> On Sat, Feb 20, 2010 at 5:25 AM, Ian Tobin <itobin@xxxxxxxxxxxxx> wrote:
> > Hi guys,
> >
> >
> >
> > Familiar issue.
> >
> >
> >
> > Running pv_ops kernel 2.6.31.6 64 bit on Debian Lenny
> >
> >
> >
> > Everytime i build the server i get the same issue. The build goes well
> but
> > as soon as i try and start a DomU i get this problem.
> >
> >
> >
> > Have checked the bridge everytime which exists, checked vif config
> which is
> > fine and also have tried live configs from another server to no
> effect.
> >
> >
> >
> > Logs show nothing.
> >
> >
> >
> > Interesting i have found if i have 2 ssh windows open i can issue xm
> create
> > domu in one window and while it hangs jump to the other and issue xm
> unpause
> > domu and then jump back to the other and issue ctrl+c the and the domU
> will
> > start with networking!
> >
> >
> >
> > Im really puzzled but it sounds to me like a bug in one of the xen
> scripts.
> >
> >
> >
> > Anyone else had this issue?
> 
> I had this issue couple of time.... But I go for some quick fix for it.
> what your udev directory says:
> 
> # ls -l /etc/udev/rules.d
> 
> If not hotplug scripts exist, copy it from tools (could be some
> dependency issue e.g uuid not installed )
> 
> >
> >
> >
> > Ian
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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

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