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 <dkao@xxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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