From: Thomas Parrott <thomas.parrott@canonical.com>
To: qemu-devel@nongnu.org
Cc: marcel@redhat.com, jusual@redhat.com
Subject: Adding pcie-root-port devices via QMP apparently isn't possible
Date: Tue, 18 May 2021 13:28:57 +0100 [thread overview]
Message-ID: <CADNu6esr-fzfP8pug+Rfv+yJrEjDJaGy3EO+O-oLb_nMm7qLDg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
Due to QEMU moving towards a QMP configuration mechanism and away from
config file support, the LXD team are currently in the process of migrating
to using QMP to add devices to VMs (so that we can support the use of QEMU
6.0).
Currently we are using the `-S` flag to freeze CPU at startup, then using
QMP to add NIC devices via the `device_add` command, and then using the
`cont` command to start the VM guest.
However we have found that it is apparently not possible to add a
pcie-root-port device via QMP.
Initially we tried using something like:
device_add
{"id":"qemu_pcie5","driver":"pcie-root-port","bus":"pcie.0","addr":"1.5","chassis":5,"multifunction":"on"}
Which was a straight conversion from the current config file we use.
However this gave the error:
Error: Bus 'pcie.0' does not support hotplugging
Then I found the `--preconfig` flag which sounded interesting, so we
removed the use of `-daemonize` which prevents the use of --preconfig` and
then tried adding the pcie-root-port devices in the preconfig stage.
But this resulted in the error:
The command 'device_add' isn't permitted in 'preconfig' state
So we wondered is this a bug, or if not, what is the correct way to be
adding pcie-root-ports going forward?
Thanks
Tom Parrott
[-- Attachment #2: Type: text/html, Size: 1781 bytes --]
next reply other threads:[~2021-05-18 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 12:28 Thomas Parrott [this message]
2021-05-18 12:29 ` Adding pcie-root-port devices via QMP apparently isn't possible Thomas Parrott
2021-05-18 14:39 ` Marcel Apfelbaum
2021-05-18 14:43 ` Thomas Parrott
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=CADNu6esr-fzfP8pug+Rfv+yJrEjDJaGy3EO+O-oLb_nMm7qLDg@mail.gmail.com \
--to=thomas.parrott@canonical.com \
--cc=jusual@redhat.com \
--cc=marcel@redhat.com \
--cc=qemu-devel@nongnu.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.