Wednesday, January 17, 2018

Re: vmd: VMs are stopping with: vcpu 0 run ioctl failed: Invalid argument

On Wed, Jan 17, 2018 at 01:45:15PM +0000, Olivier Cherrier wrote:
> On Wed, Jan 17, 2018 at 09:30:18AM +0000, oc@symacx.com wrote:
> > > This looks like a custom kernel, can you run the latest snapshot, as-is?
> >
> > The only change I made is related to /sys/dev/ic/pckbc.c in order to
> > have a working trackpad.
> >
> > > Might want to either comment out the interface for "uplink" or remove it
> > > altogether.
> >
> > OK, commented out.
> > I am upgrading the physical machine with VMM_DEBUG.
>
>
> Now, everything is running current.
> After reboot, vmd started the am-azure VM. It worked fine for a few
> hours and it just stopped. Here are the kernel messages:
>
> Jan 17 14:35:29 stanislas /bsd: vmx_handle_exit: unhandled exit 0x31 (EPT misconfiguration)
> Jan 17 14:35:29 stanislas vmd[86737]: vcpu_run_loop: vm 1 / vcpu 0 run ioctl failed: Invalid argument
> Jan 17 14:35:30 stanislas /bsd: vmm_free_vpid: freed VPID/ASID 1
>
> I hope it helps.
> Thanks
>
> --
> Olivier Cherrier
> Phone: +352691754777
> mailto:oc@symacx.com
>

There seems to be a regression in the last few weeks or so. mpi@ is seeing this,
Olivier is seeing this, and now I'm seeing it too. I'll see if I can track it
down.

-ml

No comments:

Post a Comment