Re: [Xen-devel] Debugging Windows HVM crashes on Ryzen 3xxx series CPUs.

[Steven Haigh <netwiz@xxxxxxxxx>]

Further to my last, I downloaded the latest Windows Server 2016 ISO from 
Microsoft.
Filename: Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO

Have attached as much of the log as I could get attempting to boot from 
the ISO and having a blank LV as the install target.
The Windows error message (shown via VNC) is HAL MEMORY ALLOCATION.

On 2019-10-25 16:26, Steven Haigh wrote:
> Just to make things annoying, I also get the following message in the
> logs for correctly operating Linux PVH DomU's:
>
> (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x2600, fault
> address = 0xfffffffdf8000000, flags = 0x8
>
> As such, I think we're back to zero clues at the moment as to what is 
> going on.
> Suggestions welcome :)
>
> On 2019-10-25 01:45, Paul Durrant wrote:
> > Not much clue in the logs. The crash params are weird though...
> > certainly not matching the doc.
> > (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xac--hal-memory-allocation)
> > but then again they are not always to be believed.
> > There are some odd looking IOMMU faults in there too.
> >
> >  Paul
> >
> > On Thu, 24 Oct 2019 at 13:01, Steven Haigh <netwiz@xxxxxxxxx> wrote:
> >
> > > Hi all,
> > >
> > > I've managed to get the git master version of Xen on this affected
> > > system and tries to boot a Windows Server 2016 system. It crashes as
> > >
> > > per normal.
> > >
> > > I managed to get these logs, but I'm not quite sure what else to do
> > > to
> > > debug this issue further.
> > >
> > > Suggestions welcome.
> > >
> > > The boot log in /var/log/xen/ shows:
> > > Waiting for domain soti.vm (domid 4) to die [pid 9174]
> > > Domain 4 has shut down, reason code 3 0x3
> > > Action for shutdown reason code 3 is destroy
> > > Domain 4 needs to be cleaned up: destroying the domain
> > > Done. Exiting now
> > >
> > > For some reason I'm not getting any serial output - so I'll have to
> > > take a look at that tomorrow - but if you need anything further,
> > > please
> > > let me know and I'll see what I can turn up.
> > >
> > > Windows config file:
> > >
> > > type = "hvm"
> > > name = "$vmname.vm"
> > > viridian = 1
> > > #viridian = ['base']
> > > memory = 8192
> > > vcpus = 4
> > > vif = ['bridge=br51, mac=00:16:3E:64:CC:A0']
> > > #disk = [ '/dev/vg_hosting/$vmname.vm,raw,xvda,rw',
> > 'file:/root/SW_DVD9_NTRL_Windows_Svrs_2016_English_2_Std_DC_FPP_OEM_X21-22567.ISO,hdc:cdrom,r'
> > > ]
> > > disk = [ '/dev/vg_hosting/$vmname.vm,raw,hda,rw' ]
> > > boot = 'cd'
> > > vnc = 2
> > > vnclisten = "0.0.0.0"
> > > #vncpasswd = ''
> > >
> > > ## Set the clock to localtime - not UTC...
> > > localtime = 1
> > >
> > > ## Fix the mouse cursor for VNC usage
> > > usbdevice = 'tablet'
> > >
> > > ## Lower CPU prio that other VMs...
> > > cpu_weight = 128
> > >
> > > on_poweroff = 'destroy'
> > > on_reboot = 'destroy'
> > > on_crash = 'destroy'
> > >
> > > Steven Haigh
> > >
> > > 📧 netwiz@xxxxxxxxx     💻 https://www.crc.id.au
> > > 📞 +613 9001 6090       📱 +614 1293 5897
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > https://lists.xenproject.org/mailman/listinfo/xen-devel
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxx
> > https://lists.xenproject.org/mailman/listinfo/xen-devel
--
Steven Haigh

? netwiz@xxxxxxxxx     ? http://www.crc.id.au
? +61 (3) 9001 6090    ? 0412 935 897

Attachment: windows-boot-cd-crash.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel