Hide Forgot
Description of problem: cbad352 XenD: Fix setName() code to store new domain name introduced a regression, now save a windows guest will fail, RHEL guests works well. Version-Release number of selected component (if applicable): xen-3.0.3-122.el5 How reproducible: 100% Steps to Reproduce: 1. boot up a windows guest 2. perform xm save when windows boot up (can't reproduce at the beginning of windows boot) $ xm save winxp winxp.save Error: unknown device type: savedstate Usage: xm save <Domain> <CheckpointFile> Save a domain state to restore later. $ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 4825 2 r----- 1347.8 migrating-winxp 18 1031 1 -b---- 106.1 3. domain name is change as step 2 show, but guest is running actually, and no log found in xend.log Actual results: save windows guests failed Expected results: save windows guest should work Additional info: save RHEL guests works well
I'll investigate this further for the Windows guests. Michal
This bug is reproduced in xen-3.0.3-124.el5 and verified to be fixed in xen-3.0.3-125.el5. How to reproduce|verify 1- Update the xen to the specific version and restart xend service 2- start a Windows guest(such as WinXP 32bit HVM guest) 3- #xm save $Domain_ID|$Domain_name $savefile Result: 1- In xen-3.0.3-124.el5, failed to save windows guests 2- In xen-3.0.3-125.el5, succeed to save windows guests Plus, #xm restore $savefile The restored guest works well.
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 therefore 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-2011-1070.html