Date: Sun, 18 Aug 2019 10:07:31 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Adam <amvandemore@gmail.com> Cc: Wojciech Puchar <wojtek@puchar.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: bhyve problem Message-ID: <201908181707.x7IH7Vrm040865@gndrsh.dnsmgr.net> In-Reply-To: <CA%2BtpaK3tXOFQeyWKGRYuK48_-js_UG-pgKJpfFPLS98V8LNa_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, Aug 18, 2019 at 8:39 AM Wojciech Puchar <wojtek@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@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 A raw -c 2 should still work just fine, the new code was written to be fully backwards compatible in that respect. BUT there may be a bug, or there may also be other things at play like topology sysctl's might be interfering with this. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201908181707.x7IH7Vrm040865>