On Fri, 2007-08-31 at 09:54 +0200, Christian Ehrhardt wrote:
> (XEN) (GUEST: 353) Detected Xen v3.0.3-1
I was unable to reproduce this problem on Xen 3.1.0 although I can't
immediately see a particular changeset which obviously fixed it. There
have been plenty of fixes to the emulator since 3.0.3
Christian Ehrhardt wrote:
I took the trouble to bisect (manually) exactly which change in the new
boot code triggers this problem.
The problem is with the lgdt instruction. Apparently XEN does not keep
the contents of the 48-bit gdt_48 data structure that is passed to lgdt
in the XEN machine st
Hi,
On Thu, Aug 30, 2007 at 07:49:26AM -0700, H. Peter Anvin wrote:
> Christian Ehrhardt wrote:
> >
> >Note the the xm console command terminates on its own, i.e. the guest
> >machine seems to halt and not hang somewhere.
> >
> >I could verify that the real mode code up to the assembly code in
>
Christian Ehrhardt wrote:
(XEN) Failed vm entry (exit reason 0x8021) caused by invalid guest state
(0).
(XEN) * VMCS Area **
(XEN)16-bit Guest-State Fields
(XEN) 0x0800: 0x0018 0x0010 0x0018 0x0018
(XEN) 0x0808: 0x0018 0x0018 0x 0x0008
(XEN) 16
On Thu, Aug 30, 2007 at 12:04:09PM -0700, Jeremy Fitzhardinge wrote:
> Are there any messages on the xen console ("xm dmesg")? Or logs ("xm
> log")? What version of Xen are you using? What does your domain config
> file look like?
Domain Config:
| kernel = "hvmloader"
| builder='hvm'
| memory =
5 matches
Mail list logo
