Michael Walker
2005-Dec-21 17:48 UTC
[Xen-users] Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
All,
I am attempting to install Xen3.0 following the WiKi howto''s
for ''Xen 3.0.x on Debian Sarge'' (Dom0) and
''Debian Sarge on Xen'' (DomU):
Dom0: http://mark.foster.cc/wiki/index.php/Xen_3.0.x_on_Debian_Sarge
DomU: http://mark.foster.cc/wiki/index.php/Debian_Sarge_on_Xen
I''ve got Debian installed just fine and Domain0 up and running.
When I try to create my first DomainU domain - it fails with the following
error message:
xen1:~# xm create vm01.cfg -c
Using config file "/etc/xen/vm01.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
xen:!#
I''ve seen another thread with a similiar problem - but I
didn''t
see a resolution to this problem. Any ideas what''s gone wrong?
Here''s a snippet from the xend.log if it helps:
...
[2005-12-21 01:30:17 xend] DEBUG (DevController:133) Waiting for devices vif.
[2005-12-21 01:30:17 xend] DEBUG (DevController:139) Waiting for 0.
[2005-12-21 01:30:17 xend] DEBUG (DevController:409)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2005-12-21 01:30:27 xend] ERROR (SrvBase:87) Request wait_for_devices failed.
Traceback (most recent call last):
File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
return op_method(op, req)
File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 72, in
op_wait_for_devices
return self.dom.waitForDevices()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1343, in
waitForDevices
self.waitForDevices_(c)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 971, in
waitForDevices_
return self.getDeviceController(deviceClass).waitForDevices()
File "/usr/lib/python/xen/xend/server/DevController.py", line 135,
in waitForDevices
return map(self.waitForDevice, self.deviceIDs())
File "/usr/lib/python/xen/xend/server/DevController.py", line 145,
in waitForDevice
raise VmError("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.
...
I''ve attached both the xend.log and the xend.debug.log and the
vm01.cfg file as defined in the above WiKi.
Any insights into what''s gone wrong would be appreciated. If more
info is required - just let me know what will help diagnoset he problem.
Thanx,
_Mike_
--
Michael Walker
mwalker@fins.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Michael Walker
2005-Dec-29 18:40 UTC
Re: [Xen-users] Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
Mark,
Thanx for the reply.
Here''s the diagnostic info - not sure what the problem is yet though, I
appear to have at least some information bridge setup, so it
may be a different issue. Also - this session is after a complete
re-install of the base system and then xen on top - still the same
problem.
The only thing that looks ''interesting'' is the following at
the tail
of ''xm dmesg'':
...
(XEN) mtrr: base(0xe8020000) is not aligned on a size(0x800000) boundary
...
Not sure if that is a fatal error or not...
Here''s the full diagnostic info you requested:
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.
debian:~#
debian:~# xm dmesg
__ __ _____ ___ ___
\ \/ /___ _ __ |___ / / _ \ / _ \
\ // _ \ ''_ \ |_ \| | | | | | |
/ \ __/ | | | ___) | |_| | |_| |
/_/\_\___|_| |_| |____(_)___(_)___/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.0 (root@) (gcc version 4.0.3 20051201 (prerelease)
(Debian 4.0.2-5)) Thu Dec 29 01:56:30 PST 2005
Latest ChangeSet: Sun Dec 4 17:24:24 2005 +0100 8240:64cd054aa143
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000001fe70000 (usable)
(XEN) 000000001fe70000 - 000000001fe72000 (ACPI NVS)
(XEN) 000000001fe72000 - 000000001fe93000 (ACPI data)
(XEN) 000000001fe93000 - 000000001ff00000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fecf0000 - 00000000fecf1000 (reserved)
(XEN) 00000000fed20000 - 00000000fed90000 (reserved)
(XEN) 00000000fee00000 - 00000000fee10000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 510MB (522304kB)
(XEN) Xen heap: 10MB (10644kB)
(XEN) PAE disabled.
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 DELL ) @ 0x000feb90
(XEN) ACPI: RSDT (v001 DELL 3000 0x00000007 ASL 0x00000061) @ 0x000fd28b
(XEN) ACPI: FADT (v001 DELL 3000 0x00000007 ASL 0x00000061) @ 0x000fd2bf
(XEN) ACPI: SSDT (v001 DELL st_ex 0x00001000 MSFT 0x0100000d) @ 0xfffd1496
(XEN) ACPI: MADT (v001 DELL 3000 0x00000007 ASL 0x00000061) @ 0x000fd333
(XEN) ACPI: BOOT (v001 DELL 3000 0x00000007 ASL 0x00000061) @ 0x000fd39f
(XEN) ACPI: DSDT (v001 DELL dt_ex 0x00001000 MSFT 0x0100000d) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:3 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:3 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2992.621 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=xen-3.0,VIRT_BASE=0xC0000000,PAE=no,LOADER=generic''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 01800000->02000000 (29952 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c05fd904
(XEN) Init. ramdisk: c05fe000->c05fe000
(XEN) Phys-Mach map: c05fe000->c061d400
(XEN) Start info: c061e000->c061f000
(XEN) Page tables: c061f000->c0622000
(XEN) Boot stack: c0622000->c0623000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing Free RAM: ......done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
(XEN) mtrr: base(0xe8020000) is not aligned on a size(0x800000) boundary
debian:~# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 125 1 r----- 126.9
vm01 1 96 1 --p--- 0.0
debian:~#
debian:~# xm info
system : Linux
host : debian
release : 2.6.12.6-xen0
version : #1 Wed Dec 28 02:12:31 PST 2005
machine : i686
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 2
cpu_mhz : 2992
hw_caps : bfebfbff:00000000:00000000:00000080:0000441d
total_memory : 511
free_memory : 271
xen_major : 3
xen_minor : 0
xen_extra : .0
xen_caps : xen-3.0-x86_32
platform_params : virt_start=0xfc000000
xen_changeset : Sun Dec 4 17:24:24 2005 +0100 8240:64cd054aa143
cc_compiler : gcc version 4.0.3 20051201 (prerelease)
(Debian 4.0.2-5)
cc_compile_by : root
cc_compile_domain : (none)
cc_compile_date : Thu Dec 29 01:56:30 PST 2005
debian:~# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
debian:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:11:22:48:19
inet addr:192.168.1.35 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27366 errors:0 dropped:0 overruns:0 frame:0
TX packets:16648 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39922381 (38.0 MiB) TX bytes:1180509 (1.1 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6640 (6.4 KiB) TX bytes:6640 (6.4 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:27499 errors:0 dropped:0 overruns:0 frame:0
TX packets:16788 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:40040429 (38.1 MiB) TX bytes:1200860 (1.1 MiB)
veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth4 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth5 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth6 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth7 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16648 errors:0 dropped:0 overruns:0 frame:0
TX packets:27366 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1180509 (1.1 MiB) TX bytes:39922381 (38.0 MiB)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.4 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.5 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.6 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.7 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:57 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7059 (6.8 KiB) TX bytes:0 (0.0 b)
debian:~#
Any other thoughts on what could be going wrong?
Thanx!
_Mike_
On 12/27/05, Mark Foster <mark@foster.cc> wrote:> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> You might want to send output from these commands:
> xm dmesg
> xm list
> xm info
> brctl show
> ifconfig -a
>
> I had a similar issue on one of my boxes, the bridge was not getting
> setup correctly (output from brctl show was empty)... ended up
> uninstalling and reinstalling xen 3.0.0 and even then, the xend
> doesn''t want to start at boot -- I have to start it by hand.
>
> Michael Walker wrote:
>
> > All,
> >
> > I am attempting to install Xen3.0 following the WiKi howto''s
for
> > ''Xen 3.0.x on Debian Sarge'' (Dom0) and
''Debian Sarge on Xen''
> > (DomU):
> >
> > Dom0:
> > http://mark.foster.cc/wiki/index.php/Xen_3.0.x_on_Debian_Sarge
> > DomU: http://mark.foster.cc/wiki/index.php/Debian_Sarge_on_Xen
> >
> > I''ve got Debian installed just fine and Domain0 up and
running.
> >
> > When I try to create my first DomainU domain - it fails with the
> > following error message:
> >
> > xen1:~# xm create vm01.cfg -c Using config file
> > "/etc/xen/vm01.cfg". Error: Device 0 (vif) could not be
connected.
> > Hotplug scripts not working. xen:!#
> >
> > I''ve seen another thread with a similiar problem - but I
didn''t see
> > a resolution to this problem. Any ideas what''s gone wrong?
> >
> > Here''s a snippet from the xend.log if it helps:
> >
> > ... [2005-12-21 01:30:17 xend] DEBUG (DevController:133) Waiting
> > for devices vif. [2005-12-21 01:30:17 xend] DEBUG
> > (DevController:139) Waiting for 0. [2005-12-21 01:30:17 xend] DEBUG
> > (DevController:409) hotplugStatusCallback
> > /local/domain/0/backend/vif/1/0/hotplug-status. [2005-12-21
> > 01:30:27 xend] ERROR (SrvBase:87) Request wait_for_devices failed.
> > Traceback (most recent call last): File
> > "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
return
> > op_method(op, req) File
> > "/usr/lib/python/xen/xend/server/SrvDomain.py", line 72, in
> > op_wait_for_devices return self.dom.waitForDevices() File
> > "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1343, in
> > waitForDevices self.waitForDevices_(c) File
> > "/usr/lib/python/xen/xend/XendDomainInfo.py", line 971, in
> > waitForDevices_ return
> > self.getDeviceController(deviceClass).waitForDevices() File
> > "/usr/lib/python/xen/xend/server/DevController.py", line
135, in
> > waitForDevices return map(self.waitForDevice, self.deviceIDs())
> > File "/usr/lib/python/xen/xend/server/DevController.py",
line 145,
> > in waitForDevice raise VmError("Device %s (%s) could not be
> > connected. " VmError: Device 0 (vif) could not be connected.
> > Hotplug scripts not working. ...
> >
> > I''ve attached both the xend.log and the xend.debug.log and
the
> > vm01.cfg file as defined in the above WiKi.
> >
> > Any insights into what''s gone wrong would be appreciated. If
more
> > info is required - just let me know what will help diagnoset he
> > problem.
> >
> > Thanx, _Mike_
> >
> > -- Michael Walker mwalker@fins.com
> >
> >
> > ----------------------------------------------------------------------
> >
> >
> > [2005-12-21 01:30:11 xend] INFO (SrvDaemon:268) Xend Daemon started
> > [2005-12-21 01:30:11 xend] INFO (SrvDaemon:272) Xend changeset:
> > Sun Dec 4 17:24:24 2005 +0100 8240:64cd054aa143. [2005-12-21
> > 01:30:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:198)
> > XendDomainInfo.recreate({''paused'': 0,
''cpu_time'': 16092068622L,
> > ''ssidref'': 0, ''handle'': [0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> > 0, 0], ''shutdown_reason'': 0,
''dying'': 0, ''dom'': 0,
''mem_kb'':
> > 471788, ''maxmem_kb'': -4,
''max_vcpu_id'': 1, ''crashed'': 0,
''running'':
> > 1, ''shutdown'': 0, ''online_vcpus'':
1, ''blocked'': 0}) [2005-12-21
> > 01:30:11 xend.XendDomainInfo] INFO (XendDomainInfo:210) Recreating
> > domain 0, UUID 00000000-00000000-00000000-00000000. [2005-12-21
> > 01:30:11 xend.XendDomainInfo] WARNING (XendDomainInfo:232) No vm
> > path in store for existing domain 0 [2005-12-21 01:30:11
> > xend.XendDomainInfo] DEBUG (XendDomainInfo:655) Storing VM details:
> > {''ssidref'': ''0'',
''uuid'':
''00000000-00000000-00000000-00000000'',
> > ''on_reboot'': ''restart'',
''on_poweroff'': ''destroy'',
''name'':
> > ''Domain-0'', ''vcpus'':
''2'', ''vcpu_avail'': ''3'',
''memory'': ''461'',
> > ''on_crash'': ''restart'',
''maxmem'': ''461''} [2005-12-21 01:30:11
> > xend.XendDomainInfo] DEBUG (XendDomainInfo:680) Storing domain
> > details: {''cpu/0/availability'':
''online'', ''memory/target'':
> > ''472064'', ''cpu/1/availability'':
''online'', ''name'':
''Domain-0'',
> > ''console/limit'': ''1048576'',
''vm'':
> > ''/vm/00000000-00000000-00000000-00000000'',
''domid'': ''0''}
> > [2005-12-21 01:30:11 xend] DEBUG (XendDomain:151) number of vcpus
> > to use is 0 [2005-12-21 01:30:11 xend] INFO (SrvServer:112) unix
> > path=/var/lib/xend/xend-socket [2005-12-21 01:30:16
> > xend.XendDomainInfo] DEBUG (XendDomainInfo:176)
> > XendDomainInfo.create([''vm'',
[''name'', ''vm01''],
[''memory'', ''96''],
> > [''image'', [''linux'',
[''kernel'', ''/boot/vmlinuz-2.6.12-xenU''],
[''ip'',
> > '':1.2.3.4::::eth0:dhcp''], [''root'',
''/dev/hda1 ro''], [''vcpus'',
''1''],
> > [''vcpus'', ''1''],
[''boot'', ''c''], [''nics'',
''1'']]], [''device'', [''vbd'',
> > [''uname'',
''file:/opt/xen/domains/vm01/diskimage''],
[''dev'', ''hda1''],
> > [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'',
> > ''file:/opt/xen/domains/vm01/swapimage''],
[''dev'', ''hda2''], [''mode'',
> > ''w'']]], [''device'',
[''vif'']]]) [2005-12-21 01:30:16
> > xend.XendDomainInfo] DEBUG (XendDomainInfo:281) parseConfig: config
> > is [''vm'', [''name'',
''vm01''], [''memory'', ''96''],
[''image'', [''linux'',
> > [''kernel'',
''/boot/vmlinuz-2.6.12-xenU''], [''ip'',
> > '':1.2.3.4::::eth0:dhcp''], [''root'',
''/dev/hda1 ro''], [''vcpus'',
''1''],
> > [''vcpus'', ''1''],
[''boot'', ''c''], [''nics'',
''1'']]], [''device'', [''vbd'',
> > [''uname'',
''file:/opt/xen/domains/vm01/diskimage''],
[''dev'', ''hda1''],
> > [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'',
> > ''file:/opt/xen/domains/vm01/swapimage''],
[''dev'', ''hda2''], [''mode'',
> > ''w'']]], [''device'',
[''vif'']]] [2005-12-21 01:30:16
> > xend.XendDomainInfo] DEBUG (XendDomainInfo:373) parseConfig: result
> > is {''ssidref'': None, ''uuid'': None,
''on_crash'': None, ''on_reboot'':
> > None, ''image'': [''linux'',
[''kernel'', ''/boot/vmlinuz-2.6.12-xenU''],
> > [''ip'', '':1.2.3.4::::eth0:dhcp''],
[''root'', ''/dev/hda1 ro''],
> > [''vcpus'', ''1''],
[''vcpus'', ''1''], [''boot'',
''c''], [''nics'', ''1'']],
> > ''on_poweroff'': None, ''cpus'': None,
''name'': ''vm01'', ''backend'':
[],
> > ''vcpus'': 1, ''cpu_weight'': None,
''vcpu_avail'': None, ''memory'': 96,
> > ''device'': [(''vbd'',
[''vbd'', [''uname'',
> > ''file:/opt/xen/domains/vm01/diskimage''],
[''dev'', ''hda1''], [''mode'',
> > ''w'']]), (''vbd'',
[''vbd'', [''uname'',
> > ''file:/opt/xen/domains/vm01/swapimage''],
[''dev'', ''hda2''], [''mode'',
> > ''w'']]), (''vif'',
[''vif''])], ''bootloader'': None,
''cpu'': None,
> > ''maxmem'': None} [2005-12-21 01:30:16
xend.XendDomainInfo] DEBUG
> > (XendDomainInfo:1123) XendDomainInfo.construct: None 0 [2005-12-21
> > 01:30:16 xend.XendDomainInfo] DEBUG (XendDomainInfo:1155)
> > XendDomainInfo.initDomain: 1 1.0 [2005-12-21 01:30:16 xend] DEBUG
> > (balloon:47) Balloon: free 31; need 97. [2005-12-21 01:30:16
> > xend.XendDomainInfo] DEBUG (XendDomainInfo:903) Setting memory
> > target of domain Domain-0 (0) to 395 MiB. [2005-12-21 01:30:16
> > xend] INFO (image:132) buildDomain os=linux dom=1 vcpus=1
> > [2005-12-21 01:30:16 xend] DEBUG (image:170) dom = 1
> > [2005-12-21 01:30:16 xend] DEBUG (image:171) image > >
/boot/vmlinuz-2.6.12-xenU [2005-12-21 01:30:16 xend] DEBUG
> > (image:172) store_evtchn = 1 [2005-12-21 01:30:16 xend] DEBUG
> > (image:173) console_evtchn = 2 [2005-12-21 01:30:16 xend] DEBUG
> > (image:174) cmdline = ip=:1.2.3.4::::eth0:dhcp
> > root=/dev/hda1 ro [2005-12-21 01:30:16 xend] DEBUG (image:175)
> > ramdisk = [2005-12-21 01:30:16 xend] DEBUG (image:176) vcpus
> > = 1 [2005-12-21 01:30:17 xend] DEBUG (DevController:104)
> > DevController: writing {''virtual-device'':
''769'', ''backend-id'': ''0'',
> > ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/1/769''} to
> > /local/domain/1/device/vbd/769. [2005-12-21 01:30:17 xend] DEBUG
> > (DevController:106) DevController: writing
{''domain'': ''vm01'',
> > ''frontend'':
''/local/domain/1/device/vbd/769'', ''dev'':
''hda1'',
> > ''state'': ''1'',
''params'': ''/opt/xen/domains/vm01/diskimage'',
''mode'':
> > ''w'', ''frontend-id'':
''1'', ''type'': ''file''} to
> > /local/domain/0/backend/vbd/1/769. [2005-12-21 01:30:17 xend] DEBUG
> > (DevController:104) DevController: writing
{''virtual-device'':
> > ''770'', ''backend-id'':
''0'', ''state'': ''1'',
''backend'':
> > ''/local/domain/0/backend/vbd/1/770''} to
> > /local/domain/1/device/vbd/770. [2005-12-21 01:30:17 xend] DEBUG
> > (DevController:106) DevController: writing
{''domain'': ''vm01'',
> > ''frontend'':
''/local/domain/1/device/vbd/770'', ''dev'':
''hda2'',
> > ''state'': ''1'',
''params'': ''/opt/xen/domains/vm01/swapimage'',
''mode'':
> > ''w'', ''frontend-id'':
''1'', ''type'': ''file''} to
> > /local/domain/0/backend/vbd/1/770. [2005-12-21 01:30:17 xend] DEBUG
> > (DevController:104) DevController: writing
{''backend-id'': ''0'',
> > ''mac'': ''00:16:3e:50:88:e8'',
''handle'': ''0'', ''state'':
''1'', ''backend'':
> > ''/local/domain/0/backend/vif/1/0''} to
/local/domain/1/device/vif/0.
> > [2005-12-21 01:30:17 xend] DEBUG (DevController:106)
> > DevController: writing {''mac'':
''00:16:3e:50:88:e8'', ''state'':
''1'',
> > ''handle'': ''0'',
''script'': ''/etc/xen/scripts/vif-bridge'',
> > ''frontend-id'': ''1'',
''domain'': ''vm01'',
''frontend'':
> > ''/local/domain/1/device/vif/0''} to
/local/domain/0/backend/vif/1/0.
> > [2005-12-21 01:30:17 xend.XendDomainInfo] DEBUG
> > (XendDomainInfo:655) Storing VM details: {''ssidref'':
''0'', ''uuid'':
> > ''19d0e670-31a9234a-73c39835-0a58f6b7'',
''on_reboot'': ''restart'',
> > ''image'': "(linux (kernel
/boot/vmlinuz-2.6.12-xenU) (ip
> > :1.2.3.4::::eth0:dhcp) (root ''/dev/hda1 ro'') (vcpus
1) (vcpus 1)
> > (boot c) (nics 1))", ''on_poweroff'':
''destroy'', ''name'': ''vm01'',
> > ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''96'',
''on_crash'':
> > ''restart'', ''start_time'':
''1135157417.12'', ''maxmem'':
''96''}
> > [2005-12-21 01:30:17 xend.XendDomainInfo] DEBUG
> > (XendDomainInfo:680) Storing domain details:
{''console/ring-ref'':
> > ''73417'', ''console/port'':
''2'', ''name'': ''vm01'',
''console/limit'':
> > ''1048576'', ''vm'':
''/vm/19d0e670-31a9234a-73c39835-0a58f6b7'',
> > ''domid'': ''1'',
''cpu/0/availability'': ''online'',
''memory/target'':
> > ''98304'', ''store/ring-ref'':
''73418'', ''store/port'':
''1''} [2005-12-21
> > 01:30:17 xend] DEBUG (DevController:133) Waiting for devices vif.
> > [2005-12-21 01:30:17 xend] DEBUG (DevController:139) Waiting for 0.
> > [2005-12-21 01:30:17 xend] DEBUG (DevController:409)
> > hotplugStatusCallback
> > /local/domain/0/backend/vif/1/0/hotplug-status. [2005-12-21
> > 01:30:27 xend] ERROR (SrvBase:87) Request wait_for_devices failed.
> > Traceback (most recent call last): File
> > "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
return
> > op_method(op, req) File
> > "/usr/lib/python/xen/xend/server/SrvDomain.py", line 72, in
> > op_wait_for_devices return self.dom.waitForDevices() File
> > "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1343, in
> > waitForDevices self.waitForDevices_(c) File
> > "/usr/lib/python/xen/xend/XendDomainInfo.py", line 971, in
> > waitForDevices_ return
> > self.getDeviceController(deviceClass).waitForDevices() File
> > "/usr/lib/python/xen/xend/server/DevController.py", line
135, in
> > waitForDevices return map(self.waitForDevice, self.deviceIDs())
> > File "/usr/lib/python/xen/xend/server/DevController.py",
line 145,
> > in waitForDevice raise VmError("Device %s (%s) could not be
> > connected. " VmError: Device 0 (vif) could not be connected.
> > Hotplug scripts not working.
> >
> >
> > ----------------------------------------------------------------------
> >
> >
> > Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995,
> > 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights
> > reserved.
> >
> > Please contribute if you find this software useful. For info,
> > please visit http://www.isc.org/dhcp-contrib.html
> >
> > Listening on LPF/eth0/00:11:11:22:48:19 Sending on
> > LPF/eth0/00:11:11:22:48:19 Sending on
> > Socket/fallback/fallback-net DHCPREQUEST on eth0 to 255.255.255.255
> > port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.29 -- renewal
> > in 10800 seconds.
> >
> >
> > ----------------------------------------------------------------------
> >
> >
> > _______________________________________________ Xen-users mailing
> > list Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
>
>
>
> - --
> Some days it''s just not worth chewing through the restraints...
> Mark D. Foster, CISSP <mark@foster.cc> http://mark.foster.cc/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFDsZpbPyOrEOyoEfsRAvaCAKCTz5wrZuG58ltjOO6m8CRW77U5lACgqU3X
> 1Xbo+Kgn1xOzNdvH/CS5qMg> =Wb+W
> -----END PGP SIGNATURE-----
>
>
--
Michael Walker
mwalker@fins.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Matthew Palmer
2005-Dec-29 21:33 UTC
[Xen-users] Re: Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Foster
2005-Dec-30 00:21 UTC
Re: [Xen-users] Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
Michael Walker wrote:> debian:~# xm info > system : Linux > host : debian > release : 2.6.12.6-xen0 > version : #1 Wed Dec 28 02:12:31 PST 2005 > machine : i686 > nr_cpus : 2 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 2992 > hw_caps : bfebfbff:00000000:00000000:00000080:0000441d > total_memory : 511 > free_memory : 271The difference here (240) is not very close to what is indicated by xm list (221)> xen_major : 3 > xen_minor : 0 > xen_extra : .0 > xen_caps : xen-3.0-x86_32Mine has xen-3.0-x86_32p - dunno what the difference is.> platform_params : virt_start=0xfc000000 > xen_changeset : Sun Dec 4 17:24:24 2005 +0100 8240:64cd054aa143 > cc_compiler : gcc version 4.0.3 20051201 (prerelease) > (Debian 4.0.2-5)Mine has cc_compiler : gcc version 3.3.5 (Debian 1:3.3.5-13) I suggest you start over with gcc 3.3.5. Also what version of hotplug is installed? I have 0.0.20040329-2 -- Some days it''s just not worth chewing through the restraints... Mark D. Foster, CISSP <mark@foster.cc> http://mark.foster.cc/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Walker
2005-Dec-30 02:49 UTC
Re: [Xen-users] Re: Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
On 12/29/05, Matthew Palmer <mpalmer@hezmatt.org> 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? 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# _Mike_> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- Michael Walker mwalker@fins.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Walker
2005-Dec-30 02:51 UTC
Re: [Xen-users] Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
On 12/29/05, Mark Foster <mark@foster.cc> wrote:> Michael Walker wrote: > > cc_compiler : gcc version 4.0.3 20051201 (prerelease) > > (Debian 4.0.2-5) > Mine has cc_compiler : gcc version 3.3.5 (Debian 1:3.3.5-13) > I suggest you start over with gcc 3.3.5. >ok - I''ll give it a go with gcc 3.3 tomorrow. Thanx.> Also what version of hotplug is installed? I have 0.0.20040329-2I have the following: rc hotplug 0.0.20040329-2 Linux Hotplug Scripts same version. I''ll report back what happens with the new compiler, thanx. _Mike_> > -- > Some days it''s just not worth chewing through the restraints... > Mark D. Foster, CISSP <mark@foster.cc> http://mark.foster.cc/ > >-- Michael Walker mwalker@fins.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matthew Palmer
2005-Dec-30 19:39 UTC
[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@hezmatt.org> 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@lists.xensource.com http://lists.xensource.com/xen-users
Michael Walker
2005-Dec-31 01:35 UTC
Re: [Xen-users] Re: Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
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@hezmatt.org> wrote:> On Thu, Dec 29, 2005 at 06:49:23PM -0800, Michael Walker wrote: > > On 12/29/05, Matthew Palmer <mpalmer@hezmatt.org> 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@lists.xensource.com > http://lists.xensource.com/xen-users > >-- Michael Walker mwalker@fins.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Walker
2005-Dec-31 01:38 UTC
Re: [Xen-users] Debian DomainU failing with: Error: Device 0 (vif) could not be connected.
just to follow up on this thread. The problem turned out to be related to the fact that I did not have the proper files in /etc/udev/rules.d (as discussed later in this thread). I am still using the 4.03 gcc (which is default in Debian etch) and everything is working fine with that. Thanx for the help Mark. Cheers, _Mike_ On 12/29/05, Michael Walker <mwalker@fins.com> wrote:> On 12/29/05, Mark Foster <mark@foster.cc> wrote: > > Michael Walker wrote: > > > cc_compiler : gcc version 4.0.3 20051201 (prerelease) > > > (Debian 4.0.2-5) > > Mine has cc_compiler : gcc version 3.3.5 (Debian 1:3.3.5-13) > > I suggest you start over with gcc 3.3.5. > > > > ok - I''ll give it a go with gcc 3.3 tomorrow. Thanx. > > > Also what version of hotplug is installed? I have 0.0.20040329-2 > > I have the following: > rc hotplug 0.0.20040329-2 Linux Hotplug Scripts > > same version. > > I''ll report back what happens with the new compiler, thanx. > > _Mike_ > > > > > > -- > > Some days it''s just not worth chewing through the restraints... > > Mark D. Foster, CISSP <mark@foster.cc> http://mark.foster.cc/ > > > > > > > -- > Michael Walker > mwalker@fins.com >-- Michael Walker mwalker@fins.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users