[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Re: Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |