|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] RHEL5 & Xen 3.2.1; Not creating tap0 in dom0 for domU's
Hi All,
I have a weird issue I'm not sure how to solve. I've got Xen 3.2.1
working under RHEL 5.2 x86_64 just fine. I fired off a CentOS 5.2 PV
install and everything went smoothly... except that when I fire up the
PV, the tap0 for bridging isn't being created. This results in the
CentOS 5.2 domU's bridged eth0 only being able to ping the RHEL5 dom0's
IP address... but nothing else on the same physical NIC/subnet.
Everything else is properly set in my dom0 in the sense that eth0,
peth0 and vifX.0 are all there along with a "brctl show" which shows
vifX.0 and peth0 bridged under eth0, but missing tap0 for the
peth0/eth0.
Anyone have any ideas? Thanks!
--
Daniel Kao
Übermind, Inc.
Seattle, WA, U.S.A.
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] RHEL5 & Xen 3.2.1; Not creating tap0 in dom0 for domU's,
Daniel Kao <=
|
|
|
|
|