El 22/05/15 a les 18.11, Roman Bogorodskiy ha escrit:
> H,
> I'm observing a crash that looks similar to me:
> (XEN) ----[ Xen-4.5.0  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    0020:[<ffffffff8034a2f3>]
> (XEN) RFLAGS: 0000000000010246   CONTEXT: hvm guest
> (XEN) rax: fffff800d887c1b0   rbx: fffff8000ed85100   rcx: 0000000000000000
> (XEN) rdx: ffffffff81788560   rsi: 0000000000000008   rdi: fffff8000ed85100
> (XEN) rbp: fffffe023956a850   rsp: fffffe023956a850   r8:  ffffffff815056f8
> (XEN) r9:  ffffffff8178857c   r10: fffff8000ea9e0f0   r11: ffffffff81664200
> (XEN) r12: 0000000000000004   r13: ffffffff80ee832b   r14: fffff8000ed85118
> (XEN) r15: fffff8000ed85100   cr0: 000000008005003b   cr4: 00000000000406e0
> (XEN) cr3: 0000000002cca000   cr2: 000000080a8da140
> (XEN) ds: 003b   es: 003b   fs: 0013   gs: 001b   ss: 0028   cs: 0020
> (XEN) Guest stack trace from rsp=fffffe023956a850:
> (XEN)   Fault while accessing guest memory.
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
> I'm wondering if it's related to the same issue?

The issue mentioned in this thread has been fixed in the xen-kernel port
with the following commit:


Not sure if binary packages in pkg have been updated or not.

> It's triggered only when I try to reboot/poweroff the guest.

I'm not sure if it's the same issue.

In this case the crash happened when booting Dom0 (well even before
booting Dom0).

Can you please provide the full log (including Xen and FreeBSD boot
output)? With just this chunk it's impossible to guess what's going on.

Also, if I understand it correctly, the crash you are seeing happens
when trying to shutdown/reboot a running DomU?

freebsd-xen@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to