All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Zhong <yang.zhong@intel.com>
To: pbonzini@redhat.com
Cc: yang.zhong@intel.com, qemu-devel@nongnu.org
Subject: unable to execute QEMU command 'qom-get': Property 'sgx-epc.unavailable-features' not found
Date: Thu, 25 Nov 2021 20:47:22 +0800	[thread overview]
Message-ID: <20211125124722.GA25401@yangzhon-Virtual> (raw)

Hello Paolo,

Our customer used the Libvirt XML to start a SGX VM, but failed.

libvirt.libvirtError: internal error: unable to execute QEMU command 'qom-get': Property 'sgx-epc.unavailable-features' not found

The XML file,
<qemu:commandline>
    <qemu:arg value="-cpu"/>
    <qemu:arg value="host,+sgx,+sgx-debug,+sgx-exinfo,+sgx-kss,+sgx-mode64,+sgx-provisionkey,+sgx-tokenkey,+sgx1,+sgx2,+sgxlc"/>
    <qemu:arg value="-object"/>
    <qemu:arg value="memory-backend-epc,id=mem1,size=16M,prealloc=on"/>
    <qemu:arg value="-M"/>
    <qemu:arg value="sgx-epc.0.memdev=mem1"/>
  </qemu:commandline>

The new compound property command should be located in /machine path,
which are different with old command '-sgx-epc id=epc1,memdev=mem1'.

I also tried this from Qemu monitor tool, 
(qemu) qom-list /machine
type (string)
kernel (string)
......
sgx-epc (SgxEPC)
......
sgx-epc[0] (child<memory-region>)
......

We can find sgx-epc from /machine list.

I am not familiar with Libvirt side, would you please suggest how to implement
this compound command in the XML file?  thanks a lot!

Regards,

Yang  




             reply	other threads:[~2021-11-25 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 12:47 Yang Zhong [this message]
2021-11-30 12:15 ` unable to execute QEMU command 'qom-get': Property 'sgx-epc.unavailable-features' not found Yang Zhong
2022-01-17  2:53   ` Jarkko Sakkinen
2022-01-17  2:53     ` Jarkko Sakkinen
2022-01-17  6:09     ` Yang Zhong
2022-01-17  6:09       ` Yang Zhong
2022-01-17  6:58       ` Jarkko Sakkinen
2022-01-17  6:58         ` Jarkko Sakkinen
2022-01-17  6:56     ` Jarkko Sakkinen
2022-01-17  6:56       ` Jarkko Sakkinen

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=20211125124722.GA25401@yangzhon-Virtual \
    --to=yang.zhong@intel.com \
    --cc=pbonzini@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.