From: Ian Campbell <ian.campbell@citrix.com>
To: Kristoffer Egefelt <kristoffer@itoc.dk>
Cc: Anthony Perard <anthony.perard@citrix.com>, Xen-devel@lists.xen.org
Subject: Re: pvhvm cpu hotplug not working in xen 4.4
Date: Thu, 6 Mar 2014 14:32:48 +0000 [thread overview]
Message-ID: <1394116368.13270.6.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <A1A13819-3359-47C7-B50F-68659DA8C4B2@itoc.dk>
On Thu, 2014-03-06 at 15:16 +0100, Kristoffer Egefelt wrote:
> Is xl vcpu-set supposed to work with pvhvm in xen 4.4?
>
> I’m trying with xen 4.4 rc-6 from git, getting libxl: error:
> libxl_qmp.c:287:qmp_handle_error_response: received an error message
> from QMP server: Not supported
>
> Is some specific version of qemu needed?
Are you using the version tagged/shipped with 4.4-rc6 or one of your own
devising? ISTR Anthony fixing this not so long ago -- which would
suggest a fairly recent qemu was needed -- Anthony???
Ian
>
> Full output:
>
> $ xl list
> Name ID Mem VCPUs State Time(s)
> pvhvm-template-vm101 175 7744 4 -b—— 9.9
>
> $ xl vcpu-set 175 5
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-175
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "qmp_capabilities",
> "id": 1
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "cpu-add",
> "id": 2,
> "arguments": {
> "id": 0
> }
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: error
> libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an error message from QMP server: Not supported
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-175
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "qmp_capabilities",
> "id": 1
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "cpu-add",
> "id": 2,
> "arguments": {
> "id": 1
> }
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: error
> libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an error message from QMP server: Not supported
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-175
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "qmp_capabilities",
> "id": 1
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "cpu-add",
> "id": 2,
> "arguments": {
> "id": 2
> }
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: error
> libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an error message from QMP server: Not supported
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-175
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "qmp_capabilities",
> "id": 1
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "cpu-add",
> "id": 2,
> "arguments": {
> "id": 3
> }
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: error
> libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an error message from QMP server: Not supported
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-175
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "qmp_capabilities",
> "id": 1
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{
> "execute": "cpu-add",
> "id": 2,
> "arguments": {
> "id": 4
> }
> }
> '
> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: error
> libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an error message from QMP server: Not supported
> xc: debug: hypercall buffer: total allocations:9 total releases:9
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:7 misses:2 toobig:0
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-06 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 14:16 pvhvm cpu hotplug not working in xen 4.4 Kristoffer Egefelt
2014-03-06 14:32 ` Ian Campbell [this message]
2014-03-06 14:59 ` Anthony PERARD
2014-03-07 10:02 ` Kristoffer Egefelt
2014-03-10 16:33 ` Pasi Kärkkäinen
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=1394116368.13270.6.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=anthony.perard@citrix.com \
--cc=kristoffer@itoc.dk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).