[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Bisected Xen-unstable: "Segment register inaccessible for d1v0" when starting HVM guest on intel

>>> On 28.06.14 at 22:21, <linux@xxxxxxxxxxxxxx> wrote:
> On intel machines when starting a HVM guest with qemu upstream i get:
> (d2) [2014-06-27 20:07:46] Booting from Hard Disk...
> (d2) [2014-06-27 20:07:46] Booting from 0000:7c00
> (XEN) [2014-06-27 20:08:00] irq.c:380: Dom1 callback via changed to Direct 
> Vector 0xf3
> (XEN) [2014-06-27 20:08:00] irq.c:380: Dom2 callback via changed to Direct 
> Vector 0xf3
> (XEN) [2014-06-27 20:08:03] Segment register inaccessible for d1v0
> (XEN) [2014-06-27 20:08:03] (If you see this outside of debugging activity, 
> please report to xen-devel@xxxxxxxxxxxxxxxxxxxx)

Could you put a dump_execution_state() alongside the respective
printk(), so we can see one what path(s) this is actually happening?

Thanks, Jan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.