Date: Mon, 19 Aug 2019 08:29:04 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Warner Losh <imp@bsdimp.com> Cc: Wojciech Puchar <wojtek@puchar.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Subject: Re: bhyve problem Message-ID: <201908191529.x7JFT4lN045007@gndrsh.dnsmgr.net> In-Reply-To: <CANCZdfqrMkhdF4jDGSz%2Be=7szictQ5MMY5Wg9oXmXCotL2Ehtw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I wonder which kernel interface changed in an incompatible way... The fact that he had a new user land with an ioctl that does not exist in his kernel would be the "incompatible way". The ioctl didnt exist so an error was returned. Nothing more in the name of compatibility could be done. > Warner > > On Mon, Aug 19, 2019, 1:05 AM Wojciech Puchar <wojtek@puchar.net> wrote: > > > the problem was that i upgraded userland, compiled kernel but forgot to > > install kernel. > > > > > > On Sun, 18 Aug 2019, Rodney W. Grimes 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 \ > > > ^^^^ > > > This is the topology, it looks fine. Hummm... > > > You could try "-c cpus=2" but that should make no difference at all. > > > > > > Are you by any chance having syctl's for cpu topology set? > > > hw.vmm.topology.cores_per_package > > > hw.vmm.topology.threads_per_core > > > > > > Can you show me the output of: > > > sysctl -a hw.vmm.topology > > > > > > > > >> -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 > > > > > > Humm.. you have 2 commands above, which one produced this error? > > > I think you actually only ran the first command which failed, and > > > you never actually ran the second command. > > > > > > If it is the first command that is failing can you do a > > > ls -lag /dev/vmm/windows2 > > > BEFORE you run that command, I want to see if this might > > > be a reinit attempt. > > > > > >> on console > > >> > > >> and bhyve exits. no more messages. no VM. > > >> > > >> what's wrong? > > > > > > -- > > > Rod Grimes > > rgrimes@freebsd.org > > > _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to " > > freebsd-hackers-unsubscribe@freebsd.org" > > > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201908191529.x7JFT4lN045007>