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
Of Xuehan Xu
Sent: 14 August 2015 09:05
To: xs-de...@lists.xenserver.org; xen-devel@lists.xen.org
Subject: Re: [xs-devel] Trying to bring up stub domain in xen-4.4-xs88306
Hi, I compared the hvm domain start log when using device model stub domain
with that when using dom0 qemu:
the former log:
[2015
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 corresponding
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.log.
