Anil
2008-Jul-16 05:24 UTC
[Xen-users] Communicating with VM before Network is configured.
Hi All, I am facing an issue regarding communicating a value from outside to a Guest OS (linux, solaris and windows) launched on Xen Server. I did went through this thread, but It was not completely clear. http://lists.xensource.com/archives/html/xen-users/2006-07/msg00473.html My question is - Is there a way in Xen, through which I can communicate a value from outside to a Guest OS (linux, solaris and windows)? One of the posts said we can pass the foollowing parameters to kernel by making entry in the xen config file - vif = [ ''ip=192.168.1.61'' ] netmask = "255.255.255.0" gateway = "192.168.1.1" hostname = "ds-1" In the first place, I could not find any Xen config file in /etc/xen. Where can I find it? Does this solution work with windows as well? Thanks in Advance, Anil Katti. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Kao
2008-Jul-18 09:45 UTC
[Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working. (CentOS 5.2 x86_64, Xen 3.2.1)
Hi All,
I for the life of me cannot get bridging to work with Xen on an HVM in
CentOS 5.2 x86_64 and Xen 3.2.1. I''ve searched the old threads but
nothing seems to cover what I''m running into. When I comment out the
respective "vif =" line in the python configuration file, the HVM
boots
up fine. (Windows XP SP3 in this case).
The error in xend.log shows the following error:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Here is my ifconfig upon boot of the system:
eth0 Link encap:Ethernet HWaddr 00:1C:C0:2F:97:89
inet addr:192.168.3.39 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::21c:c0ff:fe2f:9789/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10473 errors:0 dropped:0 overruns:0 frame:0
TX packets:11410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:628152 (613.4 KiB) TX bytes:9652259 (9.2 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:2397 errors:0 dropped:0 overruns:0 frame:0
TX packets:2397 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3258838 (3.1 MiB) TX bytes:3258838 (3.1 MiB)
peth0 Link encap:Ethernet HWaddr 00:1C:C0:2F:97:89
inet6 addr: fe80::21c:c0ff:fe2f:9789/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10608 errors:0 dropped:0 overruns:0 frame:0
TX packets:14062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:804062 (785.2 KiB) TX bytes:9828573 (9.3 MiB)
Memory:e0580000-e05a0000
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:17355 (16.9 KiB)
Here is my "brctl show" after boot:
Bridge name bridge id STP enabled interfaces
eth0 8000.001cc02f9789 no peth0
virbr0 8000.000000000000 yes
Not sure where to start looking. I''ve tried "virbr0",
"peth0" and
"eth0" under the vif line with the same error message. I must be
missing something. Help! Thanks in advance!
Cheers,
Daniel
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Daniel Kao
2008-Jul-18 10:18 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working. (CentOS 5.2 x86_64, Xen 3.2.1)
Update: I just noticed my peth0 has the same MAC address as eth0 which seems to be wrong. The mac address for peth0 should be FE:FF:FF:FF:FF:FF and the inet6 address should be fe80::fcff:ffff:feff:ffff/64... ... but I''m not sure what''s causing that or how to fix it or it might be the result of incorrect brctl settings. :/ Cheers, Daniel Daniel Kao wrote:> Hi All, > > I for the life of me cannot get bridging to work with Xen on an HVM in > CentOS 5.2 x86_64 and Xen 3.2.1. I''ve searched the old threads but > nothing seems to cover what I''m running into. When I comment out the > respective "vif =" line in the python configuration file, the HVM > boots up fine. (Windows XP SP3 in this case). > > The error in xend.log shows the following error: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not > working. > > Here is my ifconfig upon boot of the system: > > eth0 Link encap:Ethernet HWaddr 00:1C:C0:2F:97:89 inet > addr:192.168.3.39 Bcast:192.168.3.255 Mask:255.255.255.0 > inet6 addr: fe80::21c:c0ff:fe2f:9789/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10473 errors:0 dropped:0 overruns:0 frame:0 > TX packets:11410 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:628152 (613.4 KiB) TX bytes:9652259 (9.2 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:2397 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2397 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3258838 (3.1 MiB) TX bytes:3258838 (3.1 MiB) > > peth0 Link encap:Ethernet HWaddr 00:1C:C0:2F:97:89 inet6 > addr: fe80::21c:c0ff:fe2f:9789/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:10608 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14062 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:804062 (785.2 KiB) TX bytes:9828573 (9.3 MiB) > Memory:e0580000-e05a0000 > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet > addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:94 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:17355 (16.9 KiB) > > Here is my "brctl show" after boot: > > Bridge name bridge id STP enabled interfaces > eth0 8000.001cc02f9789 no peth0 > virbr0 8000.000000000000 yes > > Not sure where to start looking. I''ve tried "virbr0", "peth0" and > "eth0" under the vif line with the same error message. I must be > missing something. Help! Thanks in advance! > > Cheers, > Daniel > > _______________________________________________ > 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
Stefan de Konink
2008-Jul-18 10:19 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working. (CentOS 5.2 x86_64, Xen 3.2.1)
On Fri, 18 Jul 2008, Daniel Kao wrote:> Bridge name bridge id STP enabled interfaces > eth0 8000.001cc02f9789 no peth0 > virbr0 8000.000000000000 yes > > Not sure where to start looking. I''ve tried "virbr0", "peth0" and > "eth0" under the vif line with the same error message. I must be > missing something. Help! Thanks in advance!I debugged this problem yesterday. Some nice people (Yes Daniel YOU!) have added a stateful configuration together with libvirt. To get your xen config working again do the following: - go to /etc/libvirt/qemu/networks - rm default.xml; rm autostart/default.xml - cd /var/lib/xend/state/ - edit: network.xml, and remove the complete section of virbr0 (The last thing must be possible by some obscure xenstore-rm command, I don''t know it...) Now if you got this far, reboot your pc, your virbr0 should be gone, and everything works again. File your complaints to libvirt for automatic screwups. Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Kao
2008-Jul-18 10:43 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working. (CentOS 5.2 x86_64, Xen 3.2.1)
Hi Stefan! Thanks for the help! That got rid of the virbr0 interface, but I''m still having the same issue. :( When I try to start the HVM, I see "tap0" created when I run ifconfig and added to the eth0 bridge. But still ends up with the same error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2008-07-18 03:34:26 6737] DEBUG (DevController:151) Waiting for devices vif. [2008-07-18 03:34:26 6737] DEBUG (DevController:156) Waiting for 0. [2008-07-18 03:34:26 6737] DEBUG (DevController:595) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. On a CentOS 5.1 & Xen 3.2.0 I''m running, this is what it looks like when it''s working right: ifconfig: eth0 Link encap:Ethernet HWaddr 00:1E:8C:5A:CE:1E inet addr:192.168.3.16 Bcast:192.168.3.255 Mask:255.255.255.0 inet6 addr: fe80::21e:8cff:fe5a:ce1e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:89801631 errors:0 dropped:0 overruns:0 frame:0 TX packets:48367585 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:107987884550 (100.5 GiB) TX bytes:22648000223 (21.0 GiB) eth1 Link encap:Ethernet HWaddr 00:1E:8C:5A:CE:E6 inet addr:10.254.254.3 Bcast:10.254.254.255 Mask:255.255.255.0 inet6 addr: fe80::21e:8cff:fe5a:cee6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1173855 errors:0 dropped:0 overruns:0 frame:0 TX packets:25756 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:181321741 (172.9 MiB) TX bytes:6915621 (6.5 MiB) ham0 Link encap:Ethernet HWaddr 46:40:5B:DC:B4:37 inet addr:5.193.248.18 Bcast:5.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1200 Metric:1 RX packets:590174 errors:0 dropped:0 overruns:0 frame:0 TX packets:305834 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:148139465 (141.2 MiB) TX bytes:138973972 (132.5 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:544826 errors:0 dropped:0 overruns:0 frame:0 TX packets:544826 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2912972895 (2.7 GiB) TX bytes:2912972895 (2.7 GiB) 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 MTU:1500 Metric:1 RX packets:124401793 errors:0 dropped:0 overruns:0 frame:0 TX packets:76822772 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:134910124947 (125.6 GiB) TX bytes:29326162577 (27.3 GiB) Interrupt:16 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:684389019 errors:0 dropped:0 overruns:0 frame:0 TX packets:662927215 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:177088549355 (164.9 GiB) TX bytes:603713436163 (562.2 GiB) Interrupt:17 tap0 Link encap:Ethernet HWaddr F6:D4:E9:03:88:B2 inet6 addr: fe80::f4d4:e9ff:fe03:88b2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3514937 errors:0 dropped:0 overruns:0 frame:0 TX packets:6331816 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:473395798 (451.4 MiB) TX bytes:913334754 (871.0 MiB) tap1 Link encap:Ethernet HWaddr 26:16:9C:0E:97:76 inet6 addr: fe80::2416:9cff:fe0e:9776/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10072349 errors:0 dropped:0 overruns:0 frame:0 TX packets:13542011 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:1687445151 (1.5 GiB) TX bytes:2703951944 (2.5 GiB) tap2 Link encap:Ethernet HWaddr 3E:2A:26:BF:30:94 inet6 addr: fe80::3c2a:26ff:febf:3094/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2134156 errors:0 dropped:0 overruns:0 frame:0 TX packets:7612878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:521599721 (497.4 MiB) TX bytes:1867840298 (1.7 GiB) tap3 Link encap:Ethernet HWaddr 96:29:0B:DB:45:25 inet6 addr: fe80::9429:bff:fedb:4525/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3272720 errors:0 dropped:0 overruns:0 frame:0 TX packets:5033965 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:806332179 (768.9 MiB) TX bytes:1028432571 (980.7 MiB) tap4 Link encap:Ethernet HWaddr 2A:2C:07:ED:FB:A4 inet6 addr: fe80::282c:7ff:feed:fba4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:355805 errors:0 dropped:0 overruns:0 frame:0 TX packets:5861491 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:27714044 (26.4 MiB) TX bytes:1424159084 (1.3 GiB) tap5 Link encap:Ethernet HWaddr 66:16:49:F4:07:E7 inet6 addr: fe80::6416:49ff:fef4:7e7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34397689 errors:0 dropped:0 overruns:0 frame:0 TX packets:35585838 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:7766294045 (7.2 GiB) TX bytes:7785144017 (7.2 GiB) tap6 Link encap:Ethernet HWaddr 8A:BD:30:C5:90:B2 inet6 addr: fe80::88bd:30ff:fec5:90b2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41221 errors:0 dropped:0 overruns:0 frame:0 TX packets:653903 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:5413977 (5.1 MiB) TX bytes:147652857 (140.8 MiB) tap7 Link encap:Ethernet HWaddr 02:FF:0F:10:A3:13 inet6 addr: fe80::ff:fff:fe10:a313/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:432434 errors:0 dropped:0 overruns:0 frame:0 TX packets:327821 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:49865086 (47.5 MiB) TX bytes:31784864 (30.3 MiB) 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 NOARP MTU:1500 Metric:1 RX packets:48367750 errors:0 dropped:0 overruns:0 frame:0 TX packets:89801683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22648021600 (21.0 GiB) TX bytes:107987887670 (100.5 GiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:25756 errors:0 dropped:0 overruns:0 frame:0 TX packets:1173856 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6915621 (6.5 MiB) TX bytes:181321805 (172.9 MiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:16076180 errors:0 dropped:0 overruns:0 frame:0 TX packets:16115388 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:34647855193 (32.2 GiB) TX bytes:2887651426 (2.6 GiB) vif1.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:427589833 errors:0 dropped:0 overruns:0 frame:0 TX packets:625321639 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:562030355389 (523.4 GiB) TX bytes:160980148996 (149.9 GiB) vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif7.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif12.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif12.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif14.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif14.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif53.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:13490693 errors:0 dropped:0 overruns:0 frame:0 TX packets:31190508 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:2175625788 (2.0 GiB) TX bytes:50096353028 (46.6 GiB) vif53.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:4564408 errors:0 dropped:0 overruns:0 frame:0 TX packets:6776410 errors:0 dropped:341 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:10239939880 (9.5 GiB) TX bytes:1110147146 (1.0 GiB) vif69.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:329036 errors:0 dropped:0 overruns:0 frame:0 TX packets:3586139 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:31335171 (29.8 MiB) TX bytes:836161390 (797.4 MiB) vif69.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:433781 errors:0 dropped:0 overruns:0 frame:0 TX packets:980377 errors:0 dropped:4698 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:71859366 (68.5 MiB) TX bytes:106141999 (101.2 MiB) vif74.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif74.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:699515 errors:0 dropped:0 overruns:0 frame:0 TX packets:1807181 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:37236709 (35.5 MiB) TX bytes:2460034461 (2.2 GiB) xenbr0 Link encap:Ethernet HWaddr 2A:2C:07:ED:FB:A4 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:5457477 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:1254824351 (1.1 GiB) TX bytes:0 (0.0 b) xenbr1 Link encap:Ethernet HWaddr 02:FF:0F:10:A3:13 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1057758 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:77989508 (74.3 MiB) TX bytes:0 (0.0 b) And the brctl show: (notice virbr0 is in there but it doesn''t affect my networking) bridge name bridge id STP enabled interfaces virbr0 8000.000000000000 no xenbr0 8000.2a2c07edfba4 no tap6 vif74.0 vif69.0 vif53.0 vif14.0 tap4 vif12.0 tap2 vif1.0 peth0 vif0.0 xenbr1 8000.02ff0f10a313 no tap7 vif74.1 vif69.1 vif53.1 vif14.1 tap5 vif12.1 tap3 vif7.0 tap0 vif4.0 tap1 vif1.1 peth1 vif0.1 I''m stumped :/ Thanks for your help again! Cheers, Daniel Stefan de Konink wrote: On Fri, 18 Jul 2008, Daniel Kao wrote: Bridge name bridge id STP enabled interfaces eth0 8000.001cc02f9789 no peth0 virbr0 8000.000000000000 yes Not sure where to start looking. I''ve tried "virbr0", "peth0" and "eth0" under the vif line with the same error message. I must be missing something. Help! Thanks in advance! I debugged this problem yesterday. Some nice people (Yes Daniel YOU!) have added a stateful configuration together with libvirt. To get your xen config working again do the following: - go to /etc/libvirt/qemu/networks - rm default.xml; rm autostart/default.xml - cd /var/lib/xend/state/ - edit: network.xml, and remove the complete section of virbr0 (The last thing must be possible by some obscure xenstore-rm command, I don''t know it...) Now if you got this far, reboot your pc, your virbr0 should be gone, and everything works again. File your complaints to libvirt for automatic screwups. Stefan _______________________________________________ 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
Stefan de Konink
2008-Jul-18 10:50 UTC
Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working. (CentOS 5.2 x86_64, Xen 3.2.1)
Daniel Kao schreef:> Thanks for the help! That got rid of the virbr0 interface, but I''m > still having the same issue. :( > > When I try to start the HVM, I see "tap0" created when I run ifconfig > and added to the eth0 bridge. But still ends up with the same error: > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > [2008-07-18 03:34:26 6737] DEBUG (DevController:151) Waiting for devices > vif. > [2008-07-18 03:34:26 6737] DEBUG (DevController:156) Waiting for 0. > [2008-07-18 03:34:26 6737] DEBUG (DevController:595) > hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.What I saw specifically was the relation to a bridge name.> On a CentOS 5.1 & Xen 3.2.0 I''m running, this is what it looks like when > it''s working right:I see that you have a xenbr0 and xenbr1 is this right? To debug the problem: find the macaddress of your HVM, now try by typing: brctl xenbr0 showmacs [yourhvmmac] brctl xenbr1 showmacs [yourhvmmac] To identify where the HVM is connected to. It might be that it is connected to the second bridge that might not have outside connectivity. To remove the second bridge (if required) take the same approach as for the virbr0. Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users