Re: HVM crash system on AMD APU A8-6600K

[Vitaliy Tomin <highwaystar.ru@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]

>Does it start with debug=n, but without trying to passthrough the pci device (the graphics core of the apu?) to the hvm ?

No it crashes even with empty HVM domain (no os, no disk images no network)

>Can you explain "=== whole system crashed ===" a little more.

II means system instantly rebooted. Black screen, no messages, no
image on screen next what I see is POST of my real hardware.

Log of xen runned with debug=y attached,hvm dom runned and no crash.


On Mon, Feb 3, 2014 at 11:21 PM, Vitaliy Tomin <highwaystar.ru@gmail.com> wrote:
>>Does it start with debug=n, but without trying to passthrough the pci device (the graphics core of the apu?) to the hvm ?
>
> No it crashes even with empty HVM domain (no os, no disk images no network)
>
>>Can you explain "=== whole system crashed ===" a little more.
>
> II means system instantly rebooted. Black screen, no messages, no
> image on screen next what I see is POST of my real hardware.
>
> Log of xen runned with debug=y attached,hvm dom runned and no crash.
>
>
> On Mon, Feb 3, 2014 at 11:09 PM, Andrew Cooper
> <andrew.cooper3@citrix.com> wrote:
>> On 03/02/14 13:58, Vitaliy Tomin wrote:
>>> lspci output attached.
>>>
>>> I have never managed to crash system with debug=y, but I can provide
>>> serial log captured with debug=y and HVM domain running up.
>>
>> That is a curious data point - it would imply that debug mode is doing
>> something which non-debug mode fails to do.
>>
>> Could you provide the log please?
>>
>> Can you explain "=== whole system crashed ===" a little more.
>>
>> Given the lack of stack trace or any hint of a problem from Xen, is it a
>> system hang?  Does adding "watchdog" to the Xen command line cause the
>> failure to change?
>>
>>
>> Looking back at the debug=n serial log in combination with the PCI topology,
>>
>> (XEN) AMD-Vi: No iommu for device 0000:00:00.2
>> (XEN) setup 0000:00:00.2 for d0 failed (-19)
>>
>> Device 00:00.2 is the IOMMU itself.  I would have thought applying IOMMU
>> translation to the IOMMU is going to end in tears. Suravee; Can you
>> comment about this?  is the IOMMU expected to have an IVRS entry?
>>
>> ~Andrew

[-- Attachment #2: screenlog.0 --]
[-- Type: application/octet-stream, Size: 26197 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel