On Wed, Feb 8, 2017 at 8:44 PM, Jan Beulich <jbeul...@suse.com> wrote: >>>> On 07.02.17 at 16:44, <firemet...@users.sourceforge.net> wrote: >> On Mon, Feb 6, 2017 at 8:40 PM, Jan Beulich <jbeul...@suse.com> wrote: >>>>>> On 05.02.17 at 06:51, <firemet...@users.sourceforge.net> wrote: >>>> I finally get some spare time to collect the debug info. >>> >>> As I continue to be puzzled, best I could come up with is an >>> extension to the debug patch. Please use the attached one >>> in place of the earlier one, ideally on top of >>> https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00448.html >>> to reduce the overall amount of output (and help readability). >> >> Please see attached... > > So can you please give > https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00602.html > a try? > Hmm, it does not help. But I'll need to double check if I was misleading you. I used attempt dom0pvh=1 but it was too unstable and I was only able to disable it through hacking grub.cfg through sshfs remotely. I forgot to touch the /etc/default/grub so the dom0pvh=1 may have come back when I was generating the log yesterday.
Going to do it once again now. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
