Hello Kamil,

We will try to look into that but probably from September. Now we are
engaged with reviewing save/restore and live migration.

Thank you for testing,
Mihai

On Mon, Jul 15, 2019 at 1:41 PM Alexandru Elisei
<[email protected]> wrote:
>
> Hello,
>
> From the error message and the symptoms you described, it looks like
> something is broken with the world switch code.
>
> Thank you for testing bhyve.
>
> Regards,
> Alex
>
> On Mon, Jul 15, 2019 at 11:17 AM Kamil Koczurek <[email protected]> wrote:
>
> > Hello,
> > I'm testing bhyve on an arm64 board, and it fails on a basic use case.
> >
> > Setup:
> >   - board: EspressoBin
> >   - FreeBSD 13.0
> > (https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyvearm64-refactor)
> >
> > Steps to reproduce:
> >   $ kldload vmm
> >   $ cd /boot/kernel
> >   $ bhyveload -k kernel guest
> >   $ bhyve guest
> >
> > The following error appears almost instantly:
> >   `arm64_handle_world_switch:534 Unknown exception type: 1514243680`
> >
> > After this, the board stops responding and requires a hard reset.
> > Debugger doesn't kick in either. It's not completely frozen though: I
> > can see new kernel messages regarding the attached usb drive.
> >
> > I believe this might be interesting to people working on bhyve.
> >
> > Ps. I can collect additional information if needed, feel free to
> > contact me either here or privately.
> >
> > Respectfully,
> > Kamil Koczurek
> > _______________________________________________
> > [email protected] mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to "
> > [email protected]"
> >
> _______________________________________________
> [email protected] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "[email protected]"
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"[email protected]"

Reply via email to