From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: live migrating hvm from 4.4 to 4.7 fails in ioreq server
Date: Wed, 11 May 2016 14:18:16 +0200 [thread overview]
Message-ID: <20160511121816.GA2789@aepfle.de> (raw)
Migrating a HVM guest from staging-4.4 to staging fails:
# cat /var/log/xen/qemu-dm-fv-x64-sles12sp1-clean--incoming.log
char device redirected to /dev/pts/3 (label serial0)
xen: ioreq server create: Cannot allocate memory
qemu-system-x86_64: xen hardware virtual machine initialisation failed
Looks like hvm_alloc_ioreq_gmfn finds no bit in
d->arch.hvm_domain.ioreq_gmfn.mask. Is there a slim change that 4.4 does not
know about HVM_PARAM_NR_IOREQ_SERVER_PAGES, and as a result 4.7 fails to
configure the guest properly?
domU.cfg looks like this:
name="x"
memory=256
serial="pty"
builder="hvm"
boot="cd"
disk=[
'file:/disk0.raw,hda,w',
'file:/some.iso,hdc:cdrom,r',
]
vif=[
'bridge=br0'
]
keymap="de"
vfb = [
'type=vnc,vncunused=1,keymap=de'
]
usb=1
usbdevice='tablet'
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-05-11 12:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 12:18 Olaf Hering [this message]
2016-05-11 12:22 ` live migrating hvm from 4.4 to 4.7 fails in ioreq server Andrew Cooper
2016-05-11 12:30 ` Olaf Hering
2016-05-11 13:07 ` Olaf Hering
2016-05-12 10:53 ` Wei Liu
2016-05-11 12:38 ` Paul Durrant
2016-05-12 10:55 ` Wei Liu
2016-05-12 12:39 ` Paul Durrant
2016-05-12 13:01 ` Wei Liu
2016-05-12 13:03 ` Paul Durrant
2016-05-12 13:18 ` Olaf Hering
2016-05-12 14:10 ` Wei Liu
2016-05-12 14:13 ` Paul Durrant
2016-05-25 20:57 ` Konrad Rzeszutek Wilk
2016-05-26 8:30 ` Paul Durrant
2016-06-03 20:07 ` Konrad Rzeszutek Wilk
2016-07-26 15:45 ` Olaf Hering
2016-07-26 15:48 ` Paul Durrant
2016-07-29 10:11 ` Paul Durrant
2016-07-29 10:34 ` Paul Durrant
2016-07-29 13:10 ` Olaf Hering
2016-07-29 13:22 ` Paul Durrant
2016-05-12 13:38 ` Stefano Stabellini
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=20160511121816.GA2789@aepfle.de \
--to=olaf@aepfle.de \
--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.