Peter Grehan wrote:

> Hi Roman,
> > I start a VM like that:
> >
> > sudo /usr/sbin/bhyveload -m 256 -M 0 -h /var/run/bhyve/test1/vm1 test1
> > sudo /usr/bin/cpuset -l 0-3 /usr/sbin/bhyve -m 256 -M 0 -s 
> > 1,virtio-net,tap0 test1
> >
> > The last commands give me:
> >
> > Failed to emulate instruction at 0xffffffff80594f3a
> >
> > What could be wrong with that?
>   Was this during boot or later ? Do you have a console log up to where 
> it occurred ?

Hm, I see strange things happening.

When I was seing this 'Failed to emulate instruction at
0xffffffff80594f3a', it happened right after boot loader menu (the one
with the ascii-art). At that time I had 'hw.physmem="0x180000000"' in my
host's loader.conf. Also the problem wasn't 100% reproducible, it
started to show up after creating/destroying several VMs.

I replaced the physmem value with hw.physmem="0x100000000". Now I have
100% reproducibility and it fails here:

GDB: debug ports: bvm
GDB: current port: bvm
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
(20:06) novel@kloomba:~/bhyve/vm1 %>

I can still see this VM in /dev/vmm though.

Roman Bogorodskiy

Attachment: pgpAO7U4jmgnB.pgp
Description: PGP signature

Reply via email to