From 3b65fbe4d12039cce61ba8d0d90f06d42356ae6a Mon Sep 17 00:00:00 2001 From: Tycho Nightingale Date: Wed, 15 Apr 2015 18:49:03 +0000 Subject: [PATCH] Prior to aborting due to an ioport error, it is always interesting to see what the guest's %rip is. Reviewed by: grehan --- usr.sbin/bhyve/bhyverun.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/usr.sbin/bhyve/bhyverun.c b/usr.sbin/bhyve/bhyverun.c index 271f67c4d05..d2e3d3c7a66 100644 --- a/usr.sbin/bhyve/bhyverun.c +++ b/usr.sbin/bhyve/bhyverun.c @@ -325,8 +325,10 @@ vmexit_inout(struct vmctx *ctx, struct vm_exit *vme, int *pvcpu) error = emulate_inout(ctx, vcpu, vme, strictio); if (error) { - fprintf(stderr, "Unhandled %s%c 0x%04x\n", in ? "in" : "out", - bytes == 1 ? 'b' : (bytes == 2 ? 'w' : 'l'), port); + fprintf(stderr, "Unhandled %s%c 0x%04x at 0x%lx\n", + in ? "in" : "out", + bytes == 1 ? 'b' : (bytes == 2 ? 'w' : 'l'), + port, vmexit->rip); return (VMEXIT_ABORT); } else { return (VMEXIT_CONTINUE);