Xentop show the DomU’s total cpu util%, your DomU is multi-VCPU domain, right?
If “top”, you can use “1” to check each cpu’s util%.
Best Regards,
Xudong
From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-boun...@lists.xen.org]
On Behalf Of Xiaoding (B)
Sent: Monday, December 29, 2014 8:48 P
This drvier transfers any request/repond between TPM xenstubdoms
driver and Xen vTPM stubdom, and facilitates communications between
Xen vTPM stubdom domain and vTPM xenstubdoms driver. It is a glue for
the TPM xenstubdoms driver and Xen stubdom vTPM domain that provides
the actual TPM functionalit
This patch adds infrastructure for xen front drivers living in qemu,
so drivers don't need to implement common stuff on their own. It's
mostly xenbus management stuff: some functions to access XenStore,
setting up XenStore watches, callbacks on device discovery and state
changes, and handle event
make sure QEMU machine class is initialized and QEMU has registered
Xen stubdom vTPM driver when call tpm_init()
Signed-off-by: Quan Xu
---
vl.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/vl.c b/vl.c
index f6b3546..dd437e1 100644
--- a/vl.c
+++ b/vl.c
@
Signed-off-by: Quan Xu
---
configure| 14 ++
hmp.c| 7 +++
qapi-schema.json | 19 ---
qemu-options.hx | 13 +++--
tpm.c| 7 ++-
5 files changed, 54 insertions(+), 6 deletions(-)
diff --git a/configure b/configure
inde
*INTRODUCTION*
The goal of virtual Trusted Platform Module (vTPM) is to provide a TPM
functionality to virtual machines (Fedora, Ubuntu, Redhat, Windows .etc). This
allows programs to interact with a TPM in a virtual machine the same way they
interact with a TPM on the physical system. Each virt
This Patch provides the glue for the TPM_TIS(Qemu frontend) to Xen
stubdom vTPM domain that provides the actual TPM functionality. It
sends data and TPM commends with xen_vtpm_frontend. It is similar as
another two vTPM backens:
*vTPM passthrough backen Since QEMU 1.5.
*vTPM libtpms-based backe
Ok Fabio, thanks to your configure, some bits of hacking the install part
and lots of advises/support/encouragements ;) from Mark Pryor I ended up
installing 4.5RC4 with QXL support on Deb8 unstable.
So now what do you want me to test fabio?
I have win7 x64 / win 2k8R2 vms in test mode ready to
flight 32858 linux-next real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32858/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install fail REGR. vs. 32674
Regressions which are
flight 32854 qemu-mainline real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32854/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-installfail REGR. vs. 32598
test-amd64-i386-qem
branch xen-unstable
xen branch xen-unstable
job test-amd64-i386-xl-win7-amd64
test windows-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git:/
flight 32844 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32844/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-rumpuserxen-i386 3 host-install(3) broken pass in 32806
test-amd64-i386-xl-win7-amd64 5 x
flight 32834 linux-3.10 real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32834/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install fail REGR. vs. 26303
Regressions which are
flight 32830 seabios real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32830/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pvh-intel 9 guest-start fail never pass
test-amd64-i386-libvirt 9 guest-start
On 30 December 2014 at 09:06, Fabio Fantoni wrote:
> In the automatic test the qemu log contain:
>>
>> qemu-system-i386: util/qemu-option.c:387: qemu_opt_get_bool_helper:
>> Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed.
>
> Is there unexpected case in the qemu patch spotted by
Il 30/12/2014 08:52, xen.org ha scritto:
branch xen-unstable
xen branch xen-unstable
job test-amd64-amd64-xl-win7-amd64
test windows-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/sta
16 matches
Mail list logo
