[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Re: Debian DomainU failing with: Error: Device 0 (vif) could not be connected.


  • To: Matthew Palmer <mpalmer@xxxxxxxxxxx>
  • From: Michael Walker <mwalker@xxxxxxxx>
  • Date: Fri, 30 Dec 2005 17:35:40 -0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 31 Dec 2005 01:40:18 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=homw7EpjYZ4nDd9cLseHlML3KODz3N8opa4YojbBCwdVw+Xtl5R//VlV4cyFSjDQ8y9PcdP/1eMxaZUlgRNIRHfMyTT93nQ9Eo/DgqLCyMynXG4BJYFKbXr8RUyPZVSl+xha3iQLWOnJHtkRZgmFfrbpNBgMe5B6VGMjZ//zgL0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Mathew - thank you very much, this solved my problem.

It appears that my 'make install' did not install these scripts as they
should but instead installed scripts in '/etc/hotplug'.

When I copied the files in by hand as you sugest - I can now boot and run
my first xenU domain.

Good stuff and thanx for the help.


_Mike_


On 12/30/05, Matthew Palmer <mpalmer@xxxxxxxxxxx> wrote:
> On Thu, Dec 29, 2005 at 06:49:23PM -0800, Michael Walker wrote:
> > On 12/29/05, Matthew Palmer <mpalmer@xxxxxxxxxxx> wrote:
> > > On Thu, Dec 29, 2005 at 10:40:38AM -0800, Michael Walker wrote:
> > > > debian:~# xm list
> > > > Name                              ID Mem(MiB) VCPUs State  Time(s)
> > > > Domain-0                           0      125     1 r-----   116.8
> > > > debian:~# xm create vm01.cfg -c
> > > > Using config file "/etc/xen/vm01.cfg".
> > > > Error: Device 0 (vif) could not be connected. Hotplug scripts not 
> > > > working.
> > >
> > > I got this error message because I didn't have the udev rules script in
> > > /etc/udev/rules.d.
> > >
> > > - Matt
> > >
> >
> > I haven't done anything in this directory - was there something required?
>
> Yes, absolutely.  You need to copy tools/examples/xen-backend.rules to
> /etc/udev, and then symlink /etc/udev/rules.d/xen-backend.rules to that
> file.
>
> I had exactly the same error message as you're getting, and doing that fixed
> me right up.
>
> > At the moment I have:
> > debian:/etc/udev/rules.d# pwd
> > /etc/udev/rules.d
> > debian:/etc/udev/rules.d# ls
> > 020_permissions.rules  udev.rules            z55_hotplug.rules
> > 050_hal-plugdev.rules  z20_persistent.rules  z70_hotplugd.rules
> > cd-aliases.rules       z50_run.rules
> > debian:/etc/udev/rules.d#
>
> On the relevant machine, I've got:
>
> $ ls -l /etc/udev/*xen*
> -rw-r--r--  1 root root 682 2005-12-28 13:59 /etc/udev/xen-backend.rules
>
> $ ls -l /etc/udev/rules.d/*xen*
> lrwxrwxrwx  1 root root 20 2005-12-28 14:01 
> /etc/udev/rules.d/xen-backend.rules -> ../xen-backend.rules
>
> - Matt
>
> --
> <liw> hut.fi has or used to have two nfs servers not-responding and
> still-trying... don't know if their dns server was not-found... 4o4 would be
> then a good name for the web server... endless hours of fun
> <aj> "did you get a response from 4o4?" "nah, it just 404ed"
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>


--
Michael Walker
mwalker@xxxxxxxx

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.