Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=591438.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2010-05-12T09:14:50+00:00 M wrote:

Description of problem:
If I have QEMU/KVM guest started in libvirtd and then restart libvirtd, 
libvirtd no longer knows mapping between guests and tun devices on host and 
quering virDomainInterfaceStats do not work.


Version-Release number of selected component (if applicable):
libvirt version 0.7.1 (Fedora 12 rpm: libvirt-0.7.1-15.fc12.x86_64)

also tested with Centos 5.4 and libvirt 0.6.3

How reproducible:
every time

Steps to Reproduce:
1. Start QEMU/KVM guest with: virsh start vm01
2. restart libvirtd: /sbin/service libvrtd restart
3. Get statistics with virsh domifstat vm01 vnet0
  
Actual results:
[root@kvm01 ~]# virsh domifstat vm01 vnet0
error: Failed to get interface stats vm01 vnet0
error: invalid argument in invalid path, 'vnet0' is not a known interface


Expected results:
[root@kvm01 ~]# virsh domifstat vm01 vnet0
vnet0 rx_bytes 83980
vnet0 rx_packets 1612
vnet0 rx_errs 0
vnet0 rx_drop 0
vnet0 tx_bytes 3546
vnet0 tx_packets 15
vnet0 tx_errs 0
vnet0 tx_drop 0


Additional info:
I found out that after libvirtd forgets mapping for virtual interfaces. Here 
are the output from virsh dumpxml vm01 before restart:
    <interface type='network'>
      <mac address='52:54:00:28:59:5c'/>
      <source network='default'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
    </interface>

and after restart of libvirtd:
    <interface type='network'>
      <mac address='52:54:00:28:59:5c'/>
      <source network='default'/>
      <model type='virtio'/>
    </interface>

the <target dev='vnet0'/>  is missing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/0

------------------------------------------------------------------------
On 2010-05-21T17:45:26+00:00 Cole wrote:

Thanks for the report, sounds like a real bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/1

------------------------------------------------------------------------
On 2010-07-12T17:16:31+00:00 Fedora wrote:

libvirt-0.8.2-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc13

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/2

------------------------------------------------------------------------
On 2010-07-12T17:22:20+00:00 Fedora wrote:

libvirt-0.8.2-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/3

------------------------------------------------------------------------
On 2010-07-13T07:43:51+00:00 Fedora wrote:

libvirt-0.8.2-1.fc12 has been pushed to the Fedora 12 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libvirt'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/4

------------------------------------------------------------------------
On 2010-07-13T12:40:35+00:00 Cole wrote:

Danpb, has this really been fixed? I don't remember an upstream patch
addressing it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/5

------------------------------------------------------------------------
On 2010-07-13T12:54:56+00:00 Daniel wrote:

Yep, in this patch:

commit 362bc09a4d9441f9abd14956546777f86d8b9d79
Author: Jiri Denemark <[email protected]>
Date:   Tue May 4 15:16:29 2010 +0200

    Don't wipe generated iface target in active domains
    
    Wipe generated interface target only when reading configuration of
    inactive domains.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/6

------------------------------------------------------------------------
On 2010-07-27T02:48:21+00:00 Fedora wrote:

libvirt-0.8.2-1.fc12 has been pushed to the Fedora 12 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/comments/7


** Changed in: libvirt (Fedora)
       Status: Unknown => Fix Released

** Changed in: libvirt (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/668042

Title:
  If Libvirtd is restarted, libvirt drops active domains lose network
  interface info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668042/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to