[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] Xen save problem


  • To: <xen-api@xxxxxxxxxxxxxxxxxxx>
  • From: "Nathan" <nath.perry@xxxxxxxxx>
  • Date: Sun, 9 Aug 2009 15:57:06 -0600
  • Delivery-date: Sun, 09 Aug 2009 14:57:16 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=sb4/lExIaULdUBzGfJNZg4rkrCJikU9NKVCWPKREopOMP1eo5ZYMIHYiIswoxZTA7V ejmdr/5aJu/W7ejDbJBCWQz0KCskky0TWQsTZjuWcGk/jV31nP7A6lWItuEuEkWiuk4I ziZXr7cM+z4gtlZ+E5Lpr+EpKFEtxXpm8KISU=
  • Importance: Normal
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Hi, everyone,

Thanks for your attention, I'm new to xen-devel and now have a weird problem. I implemented a very easy live save/migration program, which works OK for PV-domains. But for HVM domains, it only works for the first time.

So if I run the program for the first time:
myxm save vm-name test.dat
everything is OK. then after I restore the domain using:
xm restore test.dat

and run the program again:
myxm save vm-name test.dat

the program will output an error message : timed out waiting for qemu to switch buffers
which is due to line 218 in function qemu_flip_buffer, file xc_save.c

I debuged the program, and found that at first, xs_read function returns NULL but variable len is set to 7, then it tries to read again and timeout. I compared my own program with xen built-in xc_save.c, xc_domain_save.c files and found nothing. Do you have any idea why this happens, or is there any difference between a new HVM domain and a restored HVM domain ? I'm using xen-3.3 on ubuntu 8.10.

Thanks very much
Nathan Perry
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.