From: rwxybh <rwxybh@126.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: [BUG REPORT] Xen 4.3 xl failed to save domu with -c param
Date: Mon, 29 Jul 2013 17:57:32 +0800 [thread overview]
Message-ID: <2013072917573134671829@126.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1167 bytes --]
Hi all!
I think there is a bug in liibxl_dom.c
for this function -> libxl__domain_resume_device_model
976 int libxl__domain_resume_device_model(libxl__gc *gc, uint32_t domid)
977 {
978
979 switch (libxl__device_model_version_running(gc, domid)) {
980 case LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN_TRADITIONAL: {
981 libxl__qemu_traditional_cmd(gc, domid, "continue");
982 libxl__wait_for_device_model(gc, domid, "running", NULL, NULL, NULL);
983 break;
984 }
985 case LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN:
986 if (libxl__qmp_resume(gc, domid))
987 return ERROR_FAIL;
break;
988 default:
989 return ERROR_INVAL;
990 }
991
992 return 0;
993 }
we should add "break" between line 987 & 988
Another problem:
The guest hung after cmd "xl save -c domid /fpath" with PV driver
if we remove/disable the pv driver, the function works well
Test ENV:
host: xen 4.3 + upstream qemu dm
dom0: Oracle UEK kernel
guest: win2k3 SP2 & centos 6.4
Additional
There is no valuable debug info in xl dmesg, /var/log/xen*
Any Suggestion??
rwxybh
[-- Attachment #1.2: Type: text/html, Size: 3544 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2013-07-29 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 9:57 rwxybh [this message]
2013-07-31 16:36 ` [BUG REPORT] Xen 4.3 xl failed to save domu with -c param George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2013072917573134671829@126.com \
--to=rwxybh@126.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.