Hide Forgot
+++ This bug was initially created as a clone of Bug #213166 +++ Description of problem: When I use save button on screen to save a running hvm domain. no any error messge show up, even though the save action failed. Version-Release number of selected component (if applicable): FC6GA virt-manager-0.2.3-2.fc6 How reproducible: Every time, it can be reproduced. Steps to Reproduce: 1. Start a hvm domain 2. Select the save button and input the path where image will be located with virt-manager. 3. Push "save" Actual results: Nothing show up, even though the save acction failed. The following log was got from the xend.log showing the save action failed and image was not saved. ----- [2006-10-27 14:13:43 xend 2459] DEBUG (XendCheckpoint:83) [xc_save]: /usr/lib/xen/bin/xc_save 21 6 0 0 0 [2006-10-27 14:13:43 xend 2459] ERROR (XendCheckpoint:236) Couldn't map p2m_frame_list_list (errno 14): 14 [2006-10-27 14:13:43 xend 2459] ERROR (XendCheckpoint:236) Save exit rc=1 [2006-10-27 14:13:43 xend 2459] ERROR (XendCheckpoint:106) Save failed on domain Full_FC6GA_CD (6). Traceback (most recent call last): ----- Expected results: If the save command failed, the error message should be output to user. Additional info: For the reason why save command failed, that's a different issue from virt-manager, and will be reported with different bug. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This issue still exists in RHEL-5, with virt-manager 0.2.6; basically, when an "xm save" fails, there is no error message back to the user in the GUI.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Fixing this first requires sensible error reporting in libxc (see bug 212272). Once that's done, some more work is needed in XenD to actually capture the error & feed it back to libvirt, before virt-manager stands a chance of seeing it.
Hi Chris, Though Fujitsu tested this issue, but this was reproduced on 5.1 beta, unfortunately. Internal Status set to 'Waiting on SEG' This event sent from IssueTracker by mmatsuya issue 107359
This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release.
We've rebased to virt-manager 0.5.3, which contains the fix for this bug: Build Tag Built by ---------------------------------------- -------------------- ---------------- virt-manager-0.5.3-1.el5 dist-5E-qu-candidate berrange
I've tested this on my own and it works to the full extent that virt-manager can manage. By editing the libvirt python bindings and forcing the save command to fail, an error box pops up as expected. Ex. edit /usr/lib64/python2.4/site-packages/libvirt.py and have save() return -1. Gurhan, can you check ~/.virt-manager/virt-manager.log and see if any exception was logged there? If so, virt-manager has an issue. If not (which I am suspecting), this is either a xen bug (not properly returning the error) or libvirt bug (not properly catching it).
(In reply to comment #11) > > Gurhan, can you check ~/.virt-manager/virt-manager.log and see if any exception > was logged there? If so, virt-manager has an issue. If not (which I am > suspecting), this is either a xen bug (not properly returning the error) or > libvirt bug (not properly catching it). There are no errors about this in virt-manager.log.. All I see is: [Fri, 25 Apr 2008 03:44:01 virt-manager 26251] DEBUG (console:434) Trying console login [Fri, 25 Apr 2008 03:44:01 virt-manager 26251] DEBUG (console:444) Graphics console configured at vnc://127.0.0.1:5906 [Fri, 25 Apr 2008 03:44:01 virt-manager 26251] DEBUG (console:457) Starting connect process for 127.0.0.1 5906 [Fri, 25 Apr 2008 03:44:01 virt-manager 26251] DEBUG (console:368) VNC initialized [Fri, 25 Apr 2008 03:44:25 virt-manager 26251] DEBUG (connection:580) Couldn't fetch domain id 6; it probably went away [Fri, 25 Apr 2008 03:44:26 virt-manager 26251] DEBUG (connection:580) Couldn't fetch domain id 6; it probably went away [Fri, 25 Apr 2008 03:44:26 virt-manager 26251] DEBUG (console:354) VNC disconnected [Fri, 25 Apr 2008 03:44:27 virt-manager 26251] DEBUG (console:434) Trying console login [Fri, 25 Apr 2008 03:44:27 virt-manager 26251] DEBUG (console:444) Graphics console configured at vnc://127.0.0.1:5906 [Fri, 25 Apr 2008 03:44:27 virt-manager 26251] DEBUG (console:457) Starting connect process for 127.0.0.1 5906 [Fri, 25 Apr 2008 03:44:27 virt-manager 26251] DEBUG (console:354) VNC disconnected Over and over again.. I'll verify this particular bug against virt-manager and open up another one against xend/libvirtd for not reporting/catching it properly.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0480.html