PCI configuration space is not emulated by the hypervisor. There must be an
external emulator to handle config cycles which, in the general case, is either
QEMU or a stub domain. Either one of these must be running *before* the guest
is unpaused and hence allowed to generate I/O emulation reques
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
On Thu, Aug 13, 2015 at 10:52:14AM +0100, Andrew Cooper wrote:
> On 13/08/15 08:04, Xuehan Xu wrote:
> > 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 cor
On 13/08/15 10:52, Andrew Cooper wrote:
> On 13/08/15 08:04, Xuehan Xu wrote:
>> 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 crash
On 13/08/15 08:04, Xuehan Xu wrote:
> 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
