Bug 662922 - [RHEL5.6]: default network doesn't take into account the host network
Summary: [RHEL5.6]: default network doesn't take into account the host network
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.6
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Laine Stump
QA Contact: Virtualization Bugs
Depends On: 235961 594494
TreeView+ depends on / blocked
Reported: 2010-12-14 08:10 UTC by Min Zhan
Modified: 2010-12-22 04:48 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 594494
Last Closed: 2010-12-22 04:48:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

Comment 1 Min Zhan 2010-12-14 08:35:04 UTC
Both KVM and Xen can reproduce this bug. Environment are below:



Detailed steps:

1.Make sure latest libvirt installed inside both host and guest

2.start the guest vm and check libvirtd is running in both host and guest

# service libvirtd status
libvirtd (pid  1255) is running...

3. check the guest network list in libivrt

#virsh net-list --all

Make sure the default net is inactive, if not please inactive manually.

4. check the network connectivity

from host  # ping guest_ip

from guest #ping host_ip   #ping www.google.com

5. try to start default network in guest

#virsh net-start default

Actual result:
 1. step 4, host can not ping guest, guest can not ping www.google.com
 2. step 5, default can start successfully

Expected result:
1.all ping successfully
2.step 5, an error display

Comment 2 Laine Stump 2010-12-21 16:00:32 UTC
I just tried this with a RHEL5 guest running libvrit-0.8.2-15.el5, and it behaves as expected. If the guest's libvirt is configured with the same default network as the host's libvirt, when you start libvirtd in the guest, /var/log/messages will show the following message:

networkCheckRouteCollision:1110 : internal error Network is already in use by interface eth0.

The default network on the guest libvirtd is not started, and the guest is still able to contact the outside. If I then run "virsh net-start default", I get the same error message from virsh, and the default network is still not started.

Can you please verify that:

1) the *guest* is running libvirtd-0.8.2-15.el5
2) "virsh net-dumpxml default" on the host and guest are the same
3) reboot the guest
4) verify the guest can reach the outside (eg "ping ftp.uu.net")
5) check for network connectivity in the guest, and look for the error message I mention above in /var/log/messages.
6) start libvirtd and check all that again.

If you still get the same results we need to investigate further.

Comment 3 Min Zhan 2010-12-22 04:48:01 UTC
(In reply to comment #2)

I tried with RHEL5.6-Server-x86_64-kvm,rc 1.0 tree. A guest running libvirt-0.8.2-15.el5. According to steps in comment 1, this bug can not be reproduced.All ping are successful in step 4, and an error will display when #virsh net-start default in guest.

So I will close this bug.

Note You need to log in before you can comment on or make changes to this bug.