Hi,
i guess this is a frequent error:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
i have created a symlink in /etc/udev/rules.d to the xen-backend.rules
If i try to create a vm without a network config, a similiar error message
comes up:
Error: Device 769 (vbd) could not be connected. Hotplug scripts not working.
I am really stuck now. I have searched quite a while to find a solution but all
tries where unsuccessful. Therefor i am asking here, maybe someone has some
ideas
what i could try. I am running debian packages from unstable.
I am adding some output of various commands for your reference and a xend.log
and
a strace log.
Any help is really appreciated, thanks
regards
--lars
uname:
Linux etc1 2.6.16-2-xen-k7 #1 SMP Mon May 22 22:20:22 UTC 2006 i686 GNU/Linux
etc1:~# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 2600+
stepping : 0
cpu MHz : 1915.041
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 mmx fxsr
sse syscall mmxext 3dnowext 3dnow ts
bogomips : 4789.15
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-===================-===================-=====================================================ii
libc6-xen 2.3.6-15 GNU C Library: Shared libraries [Xen
version]
un libxen-python <none> (no description available)
un libxen2.0 <none> (no description available)
un libxen2.0-dev <none> (no description available)
ii linux-headers-2.6-x 2.6.16-14 Header files for Linux kernel 2.6 on
AMD K7 machines
ii linux-headers-2.6.1 2.6.16-14 Common header files for Linux kernel
2.6.16
ii linux-headers-2.6.1 2.6.16-14 Header files for Linux kernel 2.6.16
on AMD K7 machine
ii linux-image-2.6-xen 2.6.16-14 Linux kernel 2.6 image on AMD K7
machines
ii linux-image-2.6.16- 2.6.16-14 Linux kernel 2.6.16 image on AMD K7
machines
ii linux-image-xen-k7 2.6.16-14 Linux kernel image on AMD K7
machines
ii linux-modules-2.6.1 2.6.16-14 Linux kernel modules 2.6.16 image on
AMD K7 machines
un xen <none> (no description available)
ii xen-docs-3.0 3.0.2+hg9697-1 documentation for XEN, a Virtual
Machine Monitor
un xen-hypervisor <none> (no description available)
un xen-hypervisor-3.0 <none> (no description available)
ii xen-hypervisor-3.0- 3.0.2+hg9697-1 The Xen Hypervisor for i386
un xen-hypervisor-i386 <none> (no description available)
ii xen-ioemu-3.0 3.0.2+hg9697-1 XEN administrative tools
ii xen-tools 2.1-1 Tools to manage debian XEN virtual
servers
un xen-utils <none> (no description available)
ii xen-utils-3.0 3.0.2+hg9697-1 XEN administrative tools
un xengine <none> (no description available)
ifconfig says:
eth0 Link encap:Ethernet HWaddr 00:0C:76:42:7B:34
inet addr:XXXX Bcast:XXXX Mask:255.255.255.224
inet6 addr: fe80::20c:76ff:fe42:7b34/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45333 errors:0 dropped:0 overruns:0 frame:0
TX packets:30024 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:41509320 (39.5 MiB) TX bytes:4180664 (3.9 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 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)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:45323 errors:0 dropped:0 overruns:0 frame:0
TX packets:30034 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41508570 (39.5 MiB) TX bytes:4181400 (3.9 MiB)
Interrupt:17 Base address:0xe000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30024 errors:0 dropped:0 overruns:0 frame:0
TX packets:45334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4180664 (3.9 MiB) TX bytes:41509410 (39.5 MiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1363 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:62788 (61.3 KiB) TX bytes:468 (468.0 b)
xm list:
etc1:~# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 96 1 r----- 142.8
etc1:~# ps -A|grep xen
8 ? 00:00:00 xenwatch
9 ? 00:00:00 xenbus
3954 ? 00:00:01 xenstored
3960 ? 00:00:00 xenconsoled
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Am Dienstag, den 27.06.2006, 13:45 +0200 schrieb Lars Wilke:> Hi,Hi,> > i guess this is a frequent error: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > i have created a symlink in /etc/udev/rules.d to the xen-backend.rules > > If i try to create a vm without a network config, a similiar error message > comes up: > > Error: Device 769 (vbd) could not be connected. Hotplug scripts not working. > > > I am really stuck now. I have searched quite a while to find a solution but all > tries where unsuccessful. Therefor i am asking here, maybe someone has some ideas > what i could try. I am running debian packages from unstable. > > I am adding some output of various commands for your reference and a xend.log and > a strace log.I first got the same error when using Debian + xen source (3.0.2-2). But i found out, that the module "loop" was not loaded. So maybe the solution for me also works for you: ----8<---- modprobe loop max_loop=256 ----8<---- I also put this line into /etc/modules.> > Any help is really appreciated, thanks > > regards > --larsRegards, Marvin Stark -- .""`. Marvin Stark <marvin.stark@credativ.de> : :" : credativ.de - The creative IT consultants `. `"` `- Debian - when you have better things to do than fix a system _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
* Marvin Stark wrote:> Am Dienstag, den 27.06.2006, 13:45 +0200 schrieb Lars Wilke: > > [hotplug errors] > > I first got the same error when using Debian + xen source (3.0.2-2). > But i found out, that the module "loop" was not loaded. > So maybe the solution for me also works for you: > > ----8<---- > modprobe loop max_loop=256 > ----8<----Tried this line but still the same problme :( lsmod says: loop 15944 0 iptable_filter 3264 0 ip_tables 12916 1 iptable_filter x_tables 12356 1 ip_tables bridge 47508 0 ipv6 231232 12 dm_mod 49748 1 sr_mod 16420 0 ide_generic 1664 0 [permanent] ide_cd 36512 0 cdrom 32880 2 sr_mod,ide_cd i2c_viapro 8468 0 i2c_core 20288 1 i2c_viapro via_ircc 24532 0 pcspkr 3780 0 shpchp 40032 0 pci_hotplug 25340 1 shpchp psmouse 35400 0 irda 170108 1 via_ircc serial_core 20288 0 serio_raw 7236 0 evdev 9280 0 via_agp 9856 1 parport_pc 32880 0 parport 33800 1 parport_pc crc_ccitt 2496 1 irda agpgart 30920 1 via_agp rtc 13748 1 floppy 55504 0 ext3 119368 1 jbd 51924 1 ext3 mbcache 8580 1 ext3 ide_disk 15488 4 ehci_hcd 28808 0 uhci_hcd 29008 0 via_rhine 23620 0 usbcore 115552 3 ehci_hcdühci_hcd via82cxxx 8516 0 [permanent] generic 4676 0 [permanent] ide_core 116364 5 ide_generic,ide_cd,ide_disk,via82cxxx,generic mii 5696 1 via_rhine thermal 13640 0 processor 23336 1 thermal fan 4996 0 sata_sil 10120 0 sata_via 8644 0 libata 55248 2 sata_silßata_via 3w_9xxx 30688 0 3w_xxxx 25632 0 scsi_mod 125420 4 sr_mod,libata,3w_9xxx,3w_xxxx reiserfs 221424 0 xfs 495096 0 exportfs 6016 1 xfs _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 27 June 2006 04:45, Lars Wilke wrote:> Hi, > > i guess this is a frequent error: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working.I got this error when the partition for the domU had been deleted. The "Hotplug" key word in the error message led me in the wrong direction trying to find the cause. David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I met the same problem on my Debian too, i did the following steps apt-get update apt-get install ifrename udev copy -dpR dist/install/etc/udev/* /etc/udev/ and it works, i don''t know which step resolve the problem. I install xen from source code, the version is 3.0.2. Lars Wilke wrote:> Hi, > > i guess this is a frequent error: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > i have created a symlink in /etc/udev/rules.d to the xen-backend.rules > > If i try to create a vm without a network config, a similiar error message > comes up: > > Error: Device 769 (vbd) could not be connected. Hotplug scripts not working. > > > I am really stuck now. I have searched quite a while to find a solution but all > tries where unsuccessful. Therefor i am asking here, maybe someone has some ideas > what i could try. I am running debian packages from unstable. > > I am adding some output of various commands for your reference and a xend.log and > a strace log. > > Any help is really appreciated, thanks > > regards > --lars > > uname: > Linux etc1 2.6.16-2-xen-k7 #1 SMP Mon May 22 22:20:22 UTC 2006 i686 GNU/Linux > > etc1:~# cat /proc/cpuinfo > processor : 0 > vendor_id : AuthenticAMD > cpu family : 6 > model : 10 > model name : AMD Athlon(tm) XP 2600+ > stepping : 0 > cpu MHz : 1915.041 > cache size : 512 KB > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 1 > wp : yes > flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow ts > bogomips : 4789.15 > > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) > ||/ Name Version Description > +++-===================-===================-=====================================================> ii libc6-xen 2.3.6-15 GNU C Library: Shared libraries [Xen version] > un libxen-python <none> (no description available) > un libxen2.0 <none> (no description available) > un libxen2.0-dev <none> (no description available) > ii linux-headers-2.6-x 2.6.16-14 Header files for Linux kernel 2.6 on AMD K7 machines > ii linux-headers-2.6.1 2.6.16-14 Common header files for Linux kernel 2.6.16 > ii linux-headers-2.6.1 2.6.16-14 Header files for Linux kernel 2.6.16 on AMD K7 machine > ii linux-image-2.6-xen 2.6.16-14 Linux kernel 2.6 image on AMD K7 machines > ii linux-image-2.6.16- 2.6.16-14 Linux kernel 2.6.16 image on AMD K7 machines > ii linux-image-xen-k7 2.6.16-14 Linux kernel image on AMD K7 machines > ii linux-modules-2.6.1 2.6.16-14 Linux kernel modules 2.6.16 image on AMD K7 machines > un xen <none> (no description available) > ii xen-docs-3.0 3.0.2+hg9697-1 documentation for XEN, a Virtual Machine Monitor > un xen-hypervisor <none> (no description available) > un xen-hypervisor-3.0 <none> (no description available) > ii xen-hypervisor-3.0- 3.0.2+hg9697-1 The Xen Hypervisor for i386 > un xen-hypervisor-i386 <none> (no description available) > ii xen-ioemu-3.0 3.0.2+hg9697-1 XEN administrative tools > ii xen-tools 2.1-1 Tools to manage debian XEN virtual servers > un xen-utils <none> (no description available) > ii xen-utils-3.0 3.0.2+hg9697-1 XEN administrative tools > un xengine <none> (no description available) > > > ifconfig says: > > eth0 Link encap:Ethernet HWaddr 00:0C:76:42:7B:34 > inet addr:XXXX Bcast:XXXX Mask:255.255.255.224 > inet6 addr: fe80::20c:76ff:fe42:7b34/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:45333 errors:0 dropped:0 overruns:0 frame:0 > TX packets:30024 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:41509320 (39.5 MiB) TX bytes:4180664 (3.9 MiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 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) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:45323 errors:0 dropped:0 overruns:0 frame:0 > TX packets:30034 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:41508570 (39.5 MiB) TX bytes:4181400 (3.9 MiB) > Interrupt:17 Base address:0xe000 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:30024 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45334 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4180664 (3.9 MiB) TX bytes:41509410 (39.5 MiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1363 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:62788 (61.3 KiB) TX bytes:468 (468.0 b) > > > xm list: > > etc1:~# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 96 1 r----- 142.8 > > etc1:~# ps -A|grep xen > 8 ? 00:00:00 xenwatch > 9 ? 00:00:00 xenbus > 3954 ? 00:00:01 xenstored > 3960 ? 00:00:00 xenconsoled > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
[vif not connected, maybe hotplug problem] * James Pan wrote:> I met the same problem on my Debian too, i did the following steps > apt-get update > apt-get install ifrename udev > copy -dpR dist/install/etc/udev/* /etc/udev/No luck, i installed ifrename and udev version is udev_0.093-1_i386 but still it does not work. A cat /proc/sys/kernel/hotplug just returns nothing. I guess i have to ditch the debian packages and use xen sources. Thanks --lars _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 27 June 2006 14:45, Lars Wilke wrote:> * Marvin Stark wrote: > > Am Dienstag, den 27.06.2006, 13:45 +0200 schrieb Lars Wilke: > > > [hotplug errors] > > > > I first got the same error when using Debian + xen source (3.0.2-2). > > But i found out, that the module "loop" was not loaded. > > So maybe the solution for me also works for you: > > > > ----8<---- > > modprobe loop max_loop=256 > > ----8<---- > > Tried this line but still the same problme :( >Ok, then you have to activate bridging in /etc/xen/xend-config.sxp. Change line: (network-script network-dummy) to (network-script network-bridge) [...] Regards, Marvin Stark -- .""`. Marvin Stark <marvin.stark@credativ.de> : :" : credativ.de - The creative IT consultants `. `"` `- Debian - when you have better things to do than fix a system _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
* Marvin Stark wrote:> On Tuesday 27 June 2006 14:45, Lars Wilke wrote: > > > > [hotplug errors] > > > > > Ok, then you have to activate bridging in /etc/xen/xend-config.sxp.Nope, already done. But i reboot the system again. This time i really powered the machine off and then on again. Now guess what *g* it works, yah. Cool. Don''t ask me what the problem was. I haven''t changed anything or updated anything before restarting the machine *shrug* So for the records, Debians xen packages from unstable are working. At least here and now. Anyway thank you very much, and everybody else, for your time and help. regards --lars _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users