On 28.10.2019 12:18, Andrew Cooper wrote:
> One option which was experimented with was clearing HTT using the cpuid=
> control, but that didn't work. I think a user HTT setting gets
> clobbered by the later CPUID logic. Perhaps that is something we could
> bodge in a less bad way.
Right - that's
On 28/10/2019 09:21, Jan Beulich wrote:
> On 25.10.2019 19:01, Andrew Cooper wrote:
>> On 24/10/2019 12:57, Steven Haigh 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 nor
Hello All,
https://www.reddit.com/r/Amd/comments/ckr5f4/amd_ryzen_3000_series_linux_support_and/
is concerning KVM, but it identified that the TOPOEXT feature was
important to getting windows to boot.
I just tried qemu 3.1.1 with KVM (kernel 5.1.21) on a Ryzen 3700X and
started qemu with "-cp
On Mon, 28 Oct 2019 at 09:21, Jan Beulich wrote:
>
> On 25.10.2019 19:01, Andrew Cooper wrote:
> > On 24/10/2019 12:57, Steven Haigh 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 crash
On 26.10.2019 07:22, Jürgen Groß wrote:
> On 25.10.19 19:01, Andrew Cooper wrote:
>> On 24/10/2019 12:57, Steven Haigh 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 norma
On 25.10.2019 19:01, Andrew Cooper wrote:
> On 24/10/2019 12:57, Steven Haigh 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
On 25.10.19 19:01, Andrew Cooper wrote:
On 24/10/2019 12:57, Steven Haigh 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
On 24/10/2019 12:57, Steven Haigh 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 issu
# patch -p1 < ../000-debug-patch-0.patch
patching file xen/arch/x86/hvm/hvm.c
Hunk #1 succeeded at 3373 (offset 1 line).
patching file xen/arch/x86/hvm/svm/svm.c
Hunk #1 succeeded at 2159 (offset -64 lines).
I've attached the output from around boot all the way until after the
Windows HVM DomU c
On 25.10.2019 09:00, Steven Haigh wrote:
> 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 ha
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 e
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 = 0xfffdf800, flags = 0x8
As such, I think we're back to zero clues at the moment as to what
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 t
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
14 matches
Mail list logo
