Bug 704091 - with the <loader> line removed from xen guest xml , the guest will be undefined from virsh list quietly
Summary: with the <loader> line removed from xen guest xml , the guest will be undefin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-12 06:57 UTC by Vivian Bian
Modified: 2011-08-15 19:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-15 19:45:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vivian Bian 2011-05-12 06:57:12 UTC 
Description of problem:
Removed the <loader> line by accident ,saved and quit the edition of the xen hvm guest xml . Try to dumpxml , but found the guest was undefined quietly . 

Version-Release number of selected component (if applicable):
libvirt-0.8.2-20.el5

How reproducible:
always

Steps to Reproduce:
1.virsh edit guest
2.remove the loader line
3.quit the edition 
4.virsh list --all
  
Actual results:
the guest disappeared 

Expected results:
if we don't support remove the loader line , should leave the xml the previous status without changing it . And also reserve the guest with the warning info . 

Additional info:
Comment 1 RHEL Program Management 2011-06-20 22:49:47 UTC 
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.
Comment 3 RHEL Program Management 2011-08-15 19:45:48 UTC 
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.