Bug 650543 - target device info is not in dumpxml
Summary: target device info is not in dumpxml
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-07 00:02 UTC by Steven Wagner
Modified: 2010-11-12 01:31 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-10 23:15:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Steven Wagner 2010-11-07 00:02:36 UTC
Description of problem:

Missing target device info makes it impossible to retrieve network usage information about a guest from libvirt.

Reproduce:
Trigger of issue unknown.

Workaround:
Restart the guest, and the network device info reappears again.

Detect:
Use virsh with the dumpxml command to view information about a running guest.

Good result:
virsh # dumpxml myhost1
    ...
    <interface type='bridge'>
      <mac address='52:54:00:11:a6:2c'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
    </interface>
    ...

Bad result:
virsh # dumpxml myhost2
    ...
    <interface type='bridge'>
      <mac address='52:54:14:79:32:6d'/>
      <source bridge='br0'/>
      <model type='virtio'/>
    </interface>
    ...

Version-Release number of selected component (if applicable):
libvirt 0.7.5

Comment 1 Daniel Berrangé 2010-11-10 23:15:31 UTC
Fixed several releases ago by this commit

commit 362bc09a4d9441f9abd14956546777f86d8b9d79
Author: Jiri Denemark <jdenemar>
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.


You need to update to something newer than 0.7.5, or pull in that patch to your build

Comment 2 Steven Wagner 2010-11-12 01:31:02 UTC
THANK YOU!


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