RE: Reboot on *DOM0* while/after installing GPLPV drivers

[John Hayward <john.hayward%wheaton.edu@localhost>]

Sorry for miss info - it turned out that in earlier verisons of xen (I think 
before 4.1) one needs to have the path to qemu-dm - once that was in place I 
was able to run winxp-64bit with sp2 (which looked like win2003) and install 
the gplpv drivers - Windows seemed to be confused about the "new hardware" and 
was asking for drivers but it finally figured out it had them.

I hope tomorrow to check win7 and xp 32 bit with sp3.

This is on a dom0 5.1.2 and xen 3.3.2

Manual seemed to indicate he was successful with a dom0 6.0 version so I might 
try to see if I can replicate that.
johnh...
________________________________________
From: John Hayward
Sent: Wednesday, October 09, 2013 10:01 PM
To: Takahiro HAYASHI; Manuel Bouyer
Cc: port-xen%NetBSD.org@localhost; Mike C.
Subject: RE: Reboot on *DOM0* while/after installing GPLPV drivers

For what it is worth I tried to install winxpwithsp 3  on a dom0 5.1.2 - xen 
3.3.2 and could not even install windows.
________________________________________
From: port-xen-owner%NetBSD.org@localhost [port-xen-owner%NetBSD.org@localhost] 
on behalf of Takahiro HAYASHI [t-hash%abox3.so-net.ne.jp@localhost]
Sent: Sunday, October 06, 2013 4:13 AM
To: Manuel Bouyer
Cc: port-xen%NetBSD.org@localhost; Mike C.
Subject: Re: Reboot on *DOM0* while/after installing GPLPV drivers

The build date of kernel is Sep 19 00:16:55 UTC 2013 and
src has been checked out on Sep 18 21:34:46 UTC 2013.
Sorry.

On Sun, 6 Oct 2013 10:31:05 +0200
Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:

> > XEN console said:
> > [...]
> > (XEN) domain_crash_sync called from entry.S
> > (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> > (XEN) ----[ Xen-4.2.3  x86_64  debug=y  Not tainted ]----
> > (XEN) CPU:    0
> > (XEN) RIP:    e033:[<ffffffff802b014a>]
> > (XEN) RFLAGS: 0000000000010282   EM: 0   CONTEXT: pv guest
> > (XEN) rax: 0000000000000000   rbx: 0000000000000000   rcx: 0000000000000000
> > (XEN) rdx: 0000000000000000   rsi: ffffffff803eea98   rdi: 0000a0011f879c20
> > (XEN) rbp: ffffa000191a8a50   rsp: ffffa000191a89f0   r8:  fffffffffffffffc
> > (XEN) r9:  0000000000028004   r10: 0000000000000000   r11: 0000000000000000
> > (XEN) r12: 0000000000000000   r13: ffffa000191a8a98   r14: ffffffff805f4c40
> > (XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000426f0
> > (XEN) cr3: 000000013b916000   cr2: ffffa000191a8a98
> > (XEN) ds: 0017   es: 0017   fs: 0000   gs: 0000   ss: e02b   cs: e033
> > (XEN) Guest stack trace from rsp=ffffa000191a89f0:
> > (XEN)   Fault while accessing guest memory.
> > (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
>
> Could you see where ffffffff802b014a is in your dom0 kenrel ?

pmap_extract + 0x112

netbsd.map says:

>                0xffffffff802afd60                pmap_remove
>                0xffffffff802b0038                pmap_extract
>                0xffffffff802b01a8                vtophys


--
t-hash