esource base to 1
It seems that when using dom0 qemu, the PCI configuration instructions are
intercepted by xen hypervisor, while when using qemu stub domain, these
instructions are not intercepted.
Why? Thanks:-)
On 13 August 2015 at 15:04, Xuehan Xu wrote:
> Hi, everyone.
>
>
Hi, Thanks for your reply:-)
Now, I know that the windows VM is crashed due to a not fully booted stub
domain. But why did the stub domain crash?
Thanks:-)
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Hi, everyone.
I'm trying to run a Windows HVM vm with stub domain in xenserver-6.5, whose
internal xen version is xen-4.4-xs88306. After I started the vm, both the
vm and its corresponding stub domain crashed. Here is the related content
in hypervisor.log. The domain ID of the windows vm is 1, and
Hi, everyone.
Is there any way to run a stub domain on linux not mini-os?
Thanks:-)
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Hi, everyone.
I don't quite follow the design philosophy of blktap. Since every virtual
disk is backed by a tapdisk process, when there are hundreds of domU
running and doing I/O operation simultaneously, which means that hundreds
of tapdisk process are doing I/O read/write simulataneously in dom0
-- Forwarded message --
From: "Xuehan Xu"
Date: May 4, 2015 2:35 PM
Subject: How to probe io related operation in dom0 kernel?
To:
Cc:
Hi, everyone
Recently, I tested the disk io latency on dom0 by running the following
instruction:
dd if=/dev/zero of=test_
-- Forwarded message --
From: "Xuehan Xu"
Date: Apr 29, 2015 10:11 AM
Subject: How to get real time in a xen vm?
To:
Cc:
Hi, everyone
Recently, I got a need to measure the latency of the I/O operation of
TAPDISK on dom0, in comparison with that latency on a phyisic
