Re: [Xen-devel] HVM crash system on AMD APU A8-6600K

[Vitaliy Tomin <highwaystar.ru@xxxxxxxxx>]

>You might want to add 'sync_console' on your Xen line. That should
give you a bit more of data (I hope?)

Here is  log captured with sync_console and empty hvm config.

On Mon, Feb 3, 2014 at 11:55 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Mon, Feb 03, 2014 at 11:36:23PM +0900, Vitaliy Tomin wrote:
>> >What about without PCI passthrough?  In all cases you appear to be
>> passing the embedded graphics through to an HVM domain
>>
>> Next log captured with following hvm domain config:
>>
>> name = 'blank'
>> builder = 'hvm'
>> memory = 1024
>>
>> Only 3 lines. It takes longer to crash, about 5-10 minutes, with OS in
>> hvm it takes less than a minute.
>
> You might want to add 'sync_console' on your Xen line. That should
> give you a bit more of data (I hope?)
>>
>> Now trying to make log with watchdog added
>>
>> On Mon, Feb 3, 2014 at 11:32 PM, Andrew Cooper
>> <andrew.cooper3@xxxxxxxxxx> wrote:
>> > Can you please reply-to-all to keep this on the list.
>> >
>> > On 03/02/14 14:21, Vitaliy Tomin 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)
>> >
>> > What about without PCI passthrough?  In all cases you appear to be
>> > passing the embedded graphics through to an HVM domain
>> >
>> >>
>> >>> 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.
>> >
>> > Ok - so something forced a system reset.  Even more curious that debug
>> > mode is fine while non-debug is fatal.
>> >
>> > ~Andrew
>> >
>> >
>
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-devel
>

Attachment: screenlog.0
Description: Binary data

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