From owner-freebsd-hackers@freebsd.org Mon Aug 19 07:05:09 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 270AAAAD57 for ; Mon, 19 Aug 2019 07:05:09 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46BlLD01Jnz4Pjv for ; Mon, 19 Aug 2019 07:05:06 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.15.2) with ESMTPS id x7J75rup080173 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Aug 2019 09:05:53 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Received: from localhost (puchar-wojtek@localhost) by puchar.net (8.15.2/8.15.2/Submit) with ESMTP id x7J75rJP080169; Mon, 19 Aug 2019 09:05:53 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Date: Mon, 19 Aug 2019 09:05:53 +0200 (CEST) From: Wojciech Puchar To: "Rodney W. Grimes" cc: Wojciech Puchar , freebsd-hackers@freebsd.org Subject: Re: bhyve problem In-Reply-To: <201908181706.x7IH6ASf040850@gndrsh.dnsmgr.net> Message-ID: References: <201908181706.x7IH6ASf040850@gndrsh.dnsmgr.net> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Rspamd-Queue-Id: 46BlLD01Jnz4Pjv X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of wojtek@puchar.net designates 194.1.144.90 as permitted sender) smtp.mailfrom=wojtek@puchar.net X-Spamd-Result: default: False [-6.77 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[puchar.net]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; RCVD_IN_DNSWL_NONE(0.00)[90.144.1.194.list.dnswl.org : 127.0.10.0]; IP_SCORE(-3.48)[ip: (-9.19), ipnet: 194.1.144.0/24(-4.59), asn: 43476(-3.68), country: PL(0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:43476, ipnet:194.1.144.0/24, country:PL]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 07:05:09 -0000 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" > >