>>> On 02.08.16 at 15:13, <li...@ssl-mail.com> wrote:
> On Mon, Aug 1, 2016, at 11:36 PM, Jan Beulich wrote:
>> yet without a full log thereof I can't judge
>
> I've asked what that 'full log' should be
>
>>>> Hmmm.... Could you provide full console dump from Xen and Linux kernel?
>>
>>Will serial console output with these options
>>
>> kernel: earlyprintk=xen,keep debug loglevel=8
>> hypervisor: loglvl=all guest_loglvl=all sync_console console_to_ring
>
> got an ack, then provided the serial console output with that set of log
> options.
Well, without going through the _full_ thread again, what I could
easily find is
"So full console output from boot -> crash now doesn't look any different than
https://lists.xen.org/archives/html/xen-devel/2016-07/msg02814.html
"
which doesn't tell me at all which combination of /mapbs and/or
/noexitboot was used. Certainly in that run "efi=attr=uc" wasn't
used. It in particular seems highly questionable to me that the
reboot crash would look _exactly_ the same with /mapbs.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
