Bug 602493 - VM description text not saved
Summary: VM description text not saved
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-10 00:14 UTC by kevin
Modified: 2010-06-11 14:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-11 14:11:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description kevin 2010-06-10 00:14:44 UTC
Description of problem:
virt-manager 0.8.4 introduced a text description field for VM's. That description is not being saved.

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

How reproducible:
Every time

Steps to Reproduce:
1. Enter some text into the description field
2. Click "Apply"
3. Navigate to, say, "Performance" window
4. Navigate back to the "Overview" window
5. The text is not displayed

Also, it is not saved in /etc/libvirt/qemu/<vm_name>.xml

Actual results:
No text

Expected results:
Text saved in config file

Additional info:

Comment 1 Cole Robinson 2010-06-10 14:33:05 UTC
What libvirt version are you using? Description requires at least libvirt 0.7.2. Are you making sure to hit the 'Apply' button after updating the desc? Is this Xen or KVM?

Comment 2 kevin 2010-06-10 20:58:43 UTC
Doh!! Was using 0.7.1, now upgraded to latest 0.8.1 and all is OK.

But, perhaps, virt-manager could check for a compatible libvirt in the same way as it checks for virtinst - no prizes for guessing how I know it performs that check. ;)

Thanks for your (prompt) help.

Comment 3 Cole Robinson 2010-06-11 14:11:52 UTC
In order to check for proper support, we really need libvirt to give us fine grained info about what it supports for each driver. There are other bugs floating around that are basically tracking that. Closing this as NOTABUG.


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