WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] xen 4.1.1 - Error: Device 0 (vif) could not be connected. Ho

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen 4.1.1 - Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
From: Mark Schneider <ms@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 03 Aug 2011 01:29:31 +0200
Delivery-date: Tue, 02 Aug 2011 16:31:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E387EBA.4090503@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110728132300.248098023@xxxxxxxxx> <20110728132303.745606789@xxxxxxxxx> <alpine.DEB.2.00.1107291539380.12963@kaball-desktop> <20110801125810.GA9956@xxxxxxxxx> <alpine.DEB.2.00.1108022159260.12963@kaball-desktop> <4E387820.7080100@xxxxxxxxxxxxxxxxxxxxxx> <4E387D3E.9070006@xxxxxxxxxxxxxxxxxxxxxx> <4E387EBA.4090503@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110307 Icedove/3.0.11
Hello,

I need your kindly help. I am getting an error message when trying create an HVM on xen 4.1.1 (debian wheezy with kernel 3.0.0-rc7) (s. more details below and attached log files). The same config works as expected on xen 4.0 (debian sqeueeze). In both cases dom0 runs in live mode from an USB-stick.

# ---
root@xen41dom0:/etc/xen# xm create /etc/xen/hvm-wheezyD.born2b3.net.cfg
Using config file "/etc/xen/hvm-wheezyD.born2b3.net.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
# ---

Some details:
# ---
root@xen41dom0:/var/log/xen# ln -s /usr/lib/xen-4.1 /usr/lib/xen

root@xen41dom0:/var/log/xen# modprobe -l | grep xen-gnt
kernel/drivers/xen/xen-gntdev.ko
kernel/drivers/xen/xen-gntalloc.ko

xenfs on /proc/xen type xenfs (rw)
/dev/mapper/vg_depos-ftp on /ftp type ext4 (rw)
# ---

# ---
root@xen41dom0:/etc/xen/scripts# xm list
Name ID Mem VCPUs State Time(s) Domain-0 0 1536 24 r----- 456.3 wheezyhvm.born2b3.net 1 8192 1 --p--- 0.0

root@xen41dom0:/etc/xen/scripts# xm list
Name ID Mem VCPUs State Time(s) Domain-0 0 1536 24 r----- 465.6
# ---

# ---
root@xen41dom0:/etc/xen# sed -n '/^[a-z]/p' hvm-wheezyD.born2b3.net.cfg
kernel      = '/usr/lib64/xen-default/boot/hvmloader'
builder     = 'hvm'
device_model= '/usr/lib64/xen-4.1/bin/qemu-dm'
name        = 'wheezyhvm.born2b3.net'
acpi        = 1
apic        = 1
vif         = ['bridge=eth0']
disk = [ 'phy:/dev/vg_wheezy/wheezy,ioemu:hda,w','file:/ftp/debian-testing-amd64-DVD-1.iso,ioemu:hdc:cdrom,r']
vcpus       = '8'
memory      = '8192'
boot        = 'cd'
vnc         = 1
vncviewer   = 1
vncdisplay  = 9
serial      = 'pty'
usb         = 1
usbdevice   = 'tablet'
# ---

# ---
root@xen41dom0:/# tar cvpf var-log-xen-logs-before-first-xm-create.tar var/log/xen/
var/log/xen/
var/log/xen/xend.log
var/log/xen/xend-debug.log
var/log/xen/qemu-dm-wheezyhvm.born2b3.net.log
var/log/xen/xen-hotplug.log
# ---

modprobe xen-gntdev

root@xen41dom0:/etc/xen# xm create /etc/xen/hvm-wheezyD.born2b3.net.cfg
Using config file "/etc/xen/hvm-wheezyD.born2b3.net.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

# ---
root@xen41dom0:/# tar cvpf var-log-xen-logs-AFTER-first-xm-create.tar 
var/log/xen/
var/log/xen/
var/log/xen/qemu-dm-wheezyhvm.born2b3.net.log
var/log/xen/qemu-dm-wheezyhvm.born2b3.net.log.1
var/log/xen/xend.log
var/log/xen/xend-debug.log
var/log/xen/xen-hotplug.log
# ---


What do I miss? Thank you in advance for any hints.

regards, Mark

--
ms@xxxxxxxxxxxxxxxxxxxxxx

# ---
root@xen41dom0:/var/log/xen# xm info
host                   : xen41dom0
release                : 3.0.0-rc7
version                : #3 SMP Sat Jul 16 00:01:14 CEST 2011
machine                : x86_64
nr_cpus                : 24
nr_nodes               : 4
cores_per_socket       : 12
threads_per_core       : 1
cpu_mhz                : 2500
hw_caps                : 
178bf3ff:efd3fbff:00000000:00001710:00802001:00000000:000837ff:00000000
virt_caps              : hvm
total_memory           : 32763
free_memory            : 30868
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : dom0_mem=1536M iommu=1
cc_compiler            : gcc version 4.6.1 (Debian 4.6.1-4)
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Mon Jul 18 17:41:10 UTC 2011
xend_config_format     : 4


Attachment: var-log-xen-logs-before-first-xm-create.tar.gz
Description: application/gzip

Attachment: var-log-xen-logs-AFTER-first-xm-create.tar.gz
Description: application/gzip

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