Experiencing a problem with 'xm save' for a Win2k3 VM. At first we
tried using Xen-3.0.3 on a Gentoo 2006.1 box built from source. Then
thinking that we might have an easier time with a "supported" OS, we
tried going with Fedora Core 6 and the built in Xen. In both instances
we had the same errors when trying to save the state of a Win2K3 VM:
Here is the config of the VM:
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
shadow_memory = 8
name = "win2k3U"
vif = [ 'type=ioemu, bridge=xenbr0, mac=00:16:3e:00:00:aa' ]
disk = [ 'phy:/dev/xenspace/win2k3U,ioemu:hda,w',
'file:/root/win2k3.iso,hdc:cdrom,r' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="c"
sdl=0
vnc=1
stdvga=0
serial='pty'
----
Here is the error when executing the 'xm save' command:
xm save win2k3U /tmp/win2k3U.stat
Error: /usr/lib64/xen/bin/xc_save 21 2 0 0 0 failed
Usage: xm save <Domain> <CheckpointFile>
Save a domain state to restore later.
----
Here is what shows up in the xen log when read with 'xm log' after
attempting to save the VM:
[2006-12-06 14:37:15 xend 3228] DEBUG (XendCheckpoint:83) [xc_save]:
/usr/lib64/xen/bin/xc_save 20 2 0 0 0
[2006-12-06 14:37:15 xend 3228] ERROR (XendCheckpoint:236) Couldn\047t map
p2m_frame_list_list (errno 14): 14
[2006-12-06 14:37:15 xend 3228] ERROR (XendCheckpoint:236) Save exit rc=1
[2006-12-06 14:37:15 xend 3228] ERROR (XendCheckpoint:106) Save failed on
domain win2k3U (2).
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
100, in save
forkHelper(cmd, fd, saveInputHandler, False)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 227, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 20 2 0 0 0 failed
----
All of this is identical to what we experienced on the Gentoo box. I
suspect it has something to do with a Python problem. But what? In
some of my searching I found results pointing at a problem that was
identical but was fixed before Xen-3.0.3 came out. However, even after
attempting to apply the changes, we still experience this error. Is
anyone else having trouble with this? Does 'xm save' only work with
paravirtualized systems (I am successfully using the xm save with a
Xen-3.0.2 system at home that doesn't have HVM support)? Soe 'xm save'
NOT work with Windows? Any ideas at all?
Thanks,
George
--
George Lenzer
Computer and Networking Specialist
Cleveland Public Library
Automation Department
Office: (216)623-2981
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home