Bug 506797 - virt-manager drops vifname
Summary: virt-manager drops vifname
Keywords:
Status: CLOSED DUPLICATE of bug 465593
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.3
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-18 17:11 UTC by Brian Buchanan
Modified: 2009-12-14 21:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-18 17:56:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brian Buchanan 2009-06-18 17:11:33 UTC
Description of problem:
Manually added vif option vifname to a xen domu config file is truncated by virt-manager

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

How reproducible:
100%
Create a Virtual Machine. Close virt-manager.  Manually edit the /etc/xen/xxx config file, adding the option vifname to the nic definition on the vif line.  Start the vm with `xm create` and check with ifconfig in dom0 that the specified device name is used.  Now use virt-manager to configure an additional disk file and note that the vifname option has been removed.

Steps to Reproduce:
1. Create a Virtual Machine with virt-manager
2. Manually add the vifname option to the NIC defintion on the vif line in the config file
3. Add another storage device via virt-manager
  
Actual results:
vifname has been removed from the vif line in config file.

Expected results:
vifname should be preserved.

Additional info:
virt-manager has no way of setting vifname, so this must be done manually.

Comment 1 Cole Robinson 2009-06-18 17:30:48 UTC
The issue is that libvirt probably didn't support the vifname parameter, so when converting the xm file to XML and back, it loses the changes you made. This may be supported in the libvirt version pending for 5.4.

Reassigning to libvirt.

Comment 2 Daniel Berrangé 2009-06-18 17:56:56 UTC

*** This bug has been marked as a duplicate of bug 465593 ***


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