bhyve problem

[Adam]

On Sun, Aug 18, 2019 at 8:39 AM Wojciech Puchar <wojtek at puchar.net> wrote:

> after updating system to
>
> FreeBSD puchar.net 11.3-PRERELEASE FreeBSD 11.3-PRERELEASE #2 r347617:
> Sat
> Jun  1 18:32:23 CEST 2019
> root at puchar.net:/h/backup1/src/sys/amd64/compile/puchar  amd64
>
> bhyve no longer works
>
> attempts to start VM that worked normally like
>
>   nice -n -20 /usr/sbin/bhyve -s 0,hostbridge -m 2048M -P -H -c 2 \
> -s 7,fbuf,rfb=10.0.1.1:5902,password=2j74uo5 \
> -s
> 3,ahci-hd,/dev/label/Windows2-C.eli,hd:/dev/label/Windows2-U.eli,hd:/dev/label/Windows2-V.eli
> \
> -s 5,virtio-net,tap5,mac=08:00:27:b7:ca:0b \
> -s 30,virtio-rnd -s 31,lpc -U dc53b3f7-7eb0-11e7-b5b8-54ee7513f26b \
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -w windows2
> /usr/sbin/bhyvectl --destroy --vm=windows2
>
>
> results in
>
>   bhyve: vm_set_topology
>
>
> on console
>
> and bhyve exits. no more messages. no VM.
>
> what's wrong?
>

I think how bhyve presents CPU to guest changed, you can try syntax like
this:

-c 4,sockets=1,cores=4


-- 
Adam