This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] GPLPV save/restore/migrate Issues

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] GPLPV save/restore/migrate Issues
From: Joshua West <jwest@xxxxxxxxxxxx>
Date: Sun, 02 Aug 2009 15:46:10 -0400
Delivery-date: Sun, 02 Aug 2009 12:49:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090605)
Hey all,

I'm having issues with the GPLPV drivers upon initiating a "xm restore"
or "xm migrate".  The details of the configuration are as follows:

  * Xen 3.4.1-rc10 64-bit Hypervisor & dom0
  * Windows Server 2003 32-bit HVM domU
  * gplpv-fre-wnet-x86_0.10.0.86.msi package
  * RHEL 5.3 x86_64; custom built Xen packages

I performed the installation of Windows Server 2003 r2 and tested
save/restore/migrate... no issues noticed.  I upgraded the OS to have
the latest and greatest Windows patches (SP2, IE8, etc etc) -- still no
issues with save/restore/migrate.

Following confirmation that HVM save/restore/migrate domU functions
properly, I installed the GPLPV drivers (I selected Complete
Installation), walked through the Windows "New Hardware Detected --
install drivers?" prompt, rebooted.  The GPLPV drivers are definitely in
use, as I see the "Xen PV DISK SCSI Disk Device" under the Hardware tab
of the C: drive.

On the dom0 I initiated a "xm save" of the VM.  No problems here, but
when I initiate an "xm restore", I receive the following error:

Error: /usr/lib64/xen/bin/xc_restore 56 103 2 3 1 1 1 failed

And in /var/log/xen/xend.log, I see (pertaining to this event):

[2009-08-02 15:12:44 4839] INFO (image:745) Need to create platform
[2009-08-02 15:12:44 4839] DEBUG (XendCheckpoint:261)
restore:shadow=0x9, _static_max=0x40000000, _static_min=0x0,
[2009-08-02 15:12:44 4839] DEBUG (balloon:166) Balloon: 31589116 KiB
free; need 1061888; done.
[2009-08-02 15:12:44 4839] DEBUG (XendCheckpoint:278) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 56 103 2 3 1 1 1
[2009-08-02 15:12:44 4839] INFO (XendCheckpoint:417) xc_domain_restore
start: p2m_size = 100000
[2009-08-02 15:12:44 4839] INFO (XendCheckpoint:417) Reloading memory
pages:   0%
[2009-08-02 15:12:52 4839] INFO (XendCheckpoint:417) Failed allocation
for dom 103: 1024 extents of order 0
[2009-08-02 15:12:52 4839] INFO (XendCheckpoint:417) ERROR Internal
error: Failed to allocate memory for batch.!
[2009-08-02 15:12:52 4839] INFO (XendCheckpoint:417)
[2009-08-02 15:12:52 4839] INFO (XendCheckpoint:417) Restore exit with rc=1
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:2724)
XendDomainInfo.destroy: domid=103
[2009-08-02 15:12:52 4839] ERROR (XendDomainInfo:2738)
XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 2731, in destroy
Error: (3, 'No such process')
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:2204) No device model
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:2206) Releasing devices
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:2219) Removing vbd/768
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:2219) Removing vfb/0
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:2219) Removing console/0
[2009-08-02 15:12:52 4839] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2009-08-02 15:12:52 4839] ERROR (XendDomain:1149) Restore failed
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line
1147, in domain_restore_fd
    return XendCheckpoint.restore(self, fd, paused=paused,
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 282, in restore
    forkHelper(cmd, fd, handler.handler, True)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 405, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 56 103 2 3 1 1 1 failed

Looks like when I have the GPLPL installed/used, I am no longer able to
restore a VM.  Additionally, even when I boot with the /NOGPLPV option
in boot.ini, I still cannot restore the VM.  For those familiar with "xm
migrate", this doesn't work either... because migrate is essentially a
save/restore over the network.

Perhaps of interest is a note in the logs which appeared during the "xm
save" process; I'm not sure if it affects things, but here is the entry:

[2009-08-02 14:58:07 4839] INFO (XendDomain:1180) Domain winxen (102)
[2009-08-02 15:11:49 4839] DEBUG (XendCheckpoint:110) [xc_save]:
/usr/lib64/xen/bin/xc_save 58 102 0 0 4
[2009-08-02 15:11:49 4839] INFO (XendCheckpoint:417) xc_save: failed to
get the suspend evtchn port
[2009-08-02 15:11:49 4839] INFO (XendCheckpoint:417)

Any help would be greatly appreciated.  I'd like to be able to properly
migrate HVM domU's which make use if the GPLPV enhancements.

The VM configuration file is as follows:

import os, re
arch_libdir = 'lib'
arch = os.uname()[4]
if os.uname()[0] == 'Linux' and re.search('64', arch):
    arch_libdir = 'lib64'
kernel = "/usr/lib/xen/boot/hvmloader"
memory = 1024
name = "winxen"
disk = [ 'phy:/dev/drbd/by-res/vm_winxen,hda,w' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'

If you need anything else, such as how I've built Xen itself, kernel
configs, or the actual "xm save" image, just let me know and I'll make
it available.


Joshua West
Senior Systems Engineer
Brandeis University

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>