John Mok
2011-Mar-16 15:30 UTC
[Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working
Hi, I used the kernel config on Ubuntu Xen documentation and succeeded to compile Xen 4.0.1 on Ubuntu 10.04.02 LTS :- https://help.ubuntu.com/community/Xen#Lucid%20%20Notes%20(Xen%204.0.1%20with%20a%20pv-ops%20Dom0%20kernel%20on%20Ubuntu%2010.04) However, when I tried to use HVM to install Windows 2003 R2, it failed to create the domU :- >xm create smlxsv1 A blank console screen appeared for 1 min and then returned an error "Error: Device 0 (vif) could not be connected. Hotplug scripts not working". I hope someone could point me what went wrong. Thanks a lot. John Mok === begin of /etc/xen/smlxsv1 == # -*- mode: python; -*- import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' memory = 1024 shadow_memory = 8 name = "smlxsv1" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [ ''phy:/dev/volgroup1/smlxsv1-disk0,ioemu:hda,w'', ''phy:/dev/volgroup1/smlxsv1-disk1,ioemu:hdb,w'', ''file:/var/tmp/win2k3-x64-cd1.iso,ioemu:hdc:cdrom,r'' ] boot = "d" device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' sdl=1 vnc=0 vncpasswd = '''' === end of /etc/xen/smlxsv1 == === begin of xend-debug == Xend started at Wed Mar 16 18:25:49 2011. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:32/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:32/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:32/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:32/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:32/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:2:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:2:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:2:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:2:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:2:0/scsi_level: No such file or directory /usr/local/lib/python2.6/dist-packages/xen/xend/XendAPI.py:548: DeprecationWarning: object.__new__() takes no parameters return object.__new__(cls, *args, **kwds) === begin of xend-debug == _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-16 22:19 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working
On Wed, Mar 16, 2011 at 10:30 PM, John Mok <jmok@attglobal.net> wrote:> I used the kernel config on Ubuntu Xen documentation and succeeded to > compile Xen 4.0.1 on Ubuntu 10.04.02 LTS :-> A blank console screen appeared for 1 min and then returned an error "Error: > Device 0 (vif) could not be connected. Hotplug scripts not working".> vif = [ ''type=ioemu, bridge=xenbr0'' ]Some simple checks: - do you have udevd running? - do you have a bridge called xenbr0 (try running "brctl show") -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John/SML
2011-Mar-17 01:21 UTC
[Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working
Dear Fajar, Thank you for your prompt reply.>> I used the kernel config on Ubuntu Xen documentation and succeeded to >> compile Xen 4.0.1 on Ubuntu 10.04.02 LTS :- >> A blank console screen appeared for 1 min and then returned an error"Error:>> Device 0 (vif) could not be connected. Hotplug scripts not working". >> vif = [ ''type=ioemu, bridge=xenbr0'' ]>Some simple checks: >- do you have udevd running? >- do you have a bridge called xenbr0 (try running "brctl show")Yes, the vdevd is running and the bridge xenbr0 is available :- bridge name bridge id STP enabled interfaces xenbr0 8000.782bcb0892e9 no peth0 I see no clue from the xen logs (see below). I hope someone could point me what went wrong. Thanks a lot. John Mok === begin of smlxsv1 config == # -*- mode: python; -*- import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' memory = 1024 shadow_memory = 8 name = "smlxsv1" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [ ''phy:/dev/volgroup1/smlxsv1-disk0,ioemu:hda,w'', ''phy:/dev/volgroup1/smlxsv1-disk1,ioemu:hdb,w'', ''file:/var/tmp/win2k3-x64-cd1.iso,ioemu:hdc:cdrom,r'' ] boot = "d" device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' sdl=1 vnc=0 vncpasswd = '''' === end of smlxsv1 config == === begin of qemu log == domid: 3 config qemu network with xen bridge for tap3.0 xenbr0 Using file /dev/volgroup1/smlxsv1-disk0 in read-write mode Using file /dev/volgroup1/smlxsv1-disk1 in read-write mode Using file /var/tmp/win2k3-x64-cd1.iso in read-only mode Watching /local/domain/0/device-model/3/logdirty/cmd Watching /local/domain/0/device-model/3/command qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = c55e71c1-928c-5cd5-394d-eff39479e4ba Time offset set 0 populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error medium change watch on `hdc'' (index: 2): /var/tmp/win2k3-x64-cd1.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. xs_read(/local/domain/3/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/3/log-throttling'' medium change watch on `/local/domain/3/log-throttling'' - unknown device, ignored === end of qemu log == ========================Sunciti Manufacturers Ltd. Direct: +852 27976403 Mobile (HK): +852 81011325 Mobile (CN): +86 15018974476 Facsmile: +852 22601701 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Gareth Glaccum
2011-Mar-17 09:15 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working
On Thu, 2011-03-17 at 09:21 +0800, John/SML wrote:>> >> I used the kernel config on Ubuntu Xen documentation and succeeded > to > >> compile Xen 4.0.1 on Ubuntu 10.04.02 LTS :-> >Some simple checks: > >- do you have udevd running? > >- do you have a bridge called xenbr0 (try running "brctl show") > > Yes, the vdevd is running and the bridge xenbr0 is available :- >Which version of udevd is your system running? I had a similar issue (different OS, and my problem was bridge wasn''t being started correctly), but whilst researching I came across a lot of ubuntu posts about versions of the default udevd above 151 were not working properly with xen. The work-around was to downgrade to udevd 151. I didn''t see any ''resolution'' posts that said upgrading the version solved the problem. Gareth _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users