Wednesday, June 15, 2016, 10:57:03 AM, you wrote: > Wednesday, June 15, 2016, 10:29:37 AM, you wrote:
>>>>> On 15.06.16 at 01:49, <li...@eikelenboom.it> wrote: >>> Just tested latest xen-unstable 4.8 (xen_changeset git:d337764), >>> but one of the latest commits seems to have broken boot of HVM guests >>> (using qemu-xen) previous build with xen_changeset git:6e908ee worked >>> fine. >> Primary suspects would seem to be 67fc274bbe and bfa84968b2, >> but (obviously) I didn't see any issues with them in my own >> testing, so could you >> - instead of doing a full bisect, revert just those two > Will give reverting that a shot. Reverting bfa84968b2 is sufficient. >> - clarify what specific things you're having your guest(s) do that >> I may not have done with just "ordinary" guests? > That was what i was also wondering about, but it is an ordinary guest, no pci > passthrough or something funky. > Perhaps an Intel vs AMD (this machine has a AMD phenom X6) issue ? > -- > Sander >> And then of course this domain_crash() could of course be >> accompanied by some helpful printk() ... Do you have a debug patch of what you are interested in ? >> Thanks, Jan -- Sander _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
