Issue

VM won't start. Error: Device 0 (vif)

posted in Hypervisor
Monday, September 09 2013, 10:18 AM
boospy
boospy
Offline
0
Hello,

This day i reboot an xenguest, and this vm did not start anymore. The outeput of the CMD is:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

For Hypervisor and the guest there run a Gentoo with xenversion 4.2.0-r3. Here are the configfile of the vm:
# general
name = "gleivs01-xstyriondns02";
memory = 1024;

# booting
kernel = "/vserver/kernel/xen-3.8.6";

# virtual harddisk
disk = [ "phy:/dev/mapper/vg-xdns2--ng,xvda,w" ];
root = "/dev/xvda ro";

# virtual network
#vif = [ "bridge=xenbr0" ];
#dhcp = "dhcp"
#hostname = "gleivs01-xstyriondns02"

vcpus = 2

#extra = "TERM=xterm xencons=tty console=tty1"


The bridges are there and working fine. An other guest uses the same bridge. I also can't start the vm with the other bridge (xenbr1), and i can't start without network. Same errormessage.
Xendlog says:
[2013-09-09 11:59:52 3035] DEBUG (XendDomainInfo:1882) XendDomainInfo.handleShutdownWatch
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices tap2.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices vif.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices vkbd.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices ioports.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices tap.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices vif2.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices console.
[2013-09-09 11:59:52 3035] DEBUG (DevController:144) Waiting for 0.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices vscsi.
[2013-09-09 11:59:52 3035] DEBUG (DevController:139) Waiting for devices vbd.
[2013-09-09 11:59:52 3035] DEBUG (DevController:144) Waiting for 51712.
[2013-09-09 11:59:52 3035] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/19/51712/hotplug-status.
[2013-09-09 12:01:32 3035] DEBUG (XendDomainInfo:3077) XendDomainInfo.destroy: domid=19
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2402) Destroying device model
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2409) Releasing devices
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2415) Removing console/0
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2415) Removing vbd/51712
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2407) No device model
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2409) Releasing devices
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:2415) Removing vbd/51712
[2013-09-09 12:01:33 3035] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712

My knowledge over xen is not the best, so i don't know what the problem should be.

Thank for help and
Regrads
boospy

At the Gentooforum i postet the same: http://forums.gentoo.org/viewtopic-p-7391532.html#7391532
Responses (1)
  • Accepted Answer

    Lars Kurth
    Lars Kurth
    Offline
    Monday, September 09 2013, 04:17 PM - #permalink
    0
    Hi, wondering whether this entry in the Common Problems Section on the wiki, will solve your problem. Also, if you google for "Error: Device 0 (vif) could not be connected. Hotplug scripts not working" quite a few different threads come up. I could not find one for Gentoo though. If you don't get any further, you may want to try the ##xen IRC channel for a quick answer.
    The reply is currently minimized Show
Your Reply