From nobody Sat Mar 02 09:31:17 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Tn07F2gbxz5CPMv for ; Sat, 2 Mar 2024 09:30:33 +0000 (UTC) (envelope-from Stephan.Althaus@Duedinghausen.eu) Received: from mo4-p05-ob.smtp.rzone.de (mo4-p05-ob.smtp.rzone.de [81.169.146.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tn07D1l0dz4Md6 for ; Sat, 2 Mar 2024 09:30:31 +0000 (UTC) (envelope-from Stephan.Althaus@Duedinghausen.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hoewweken.de header.s=strato-dkim-0002 header.b=GsxkavCR; dkim=pass header.d=hoewweken.de header.s=strato-dkim-0003 header.b=VHRZEefZ; dmarc=none; spf=none (mx1.freebsd.org: domain of Stephan.Althaus@Duedinghausen.eu has no SPF policy when checking 81.169.146.181) smtp.mailfrom=Stephan.Althaus@Duedinghausen.eu; arc=pass ("strato.com:s=strato-dkim-0002:i=1") ARC-Seal: i=1; a=rsa-sha256; t=1709371829; cv=none; d=strato.com; s=strato-dkim-0002; b=R3XfFIE4XWUULO5M+QM+uybJiM41DQa+rp3jnnTPqixXElfKEoHm6Z0fhenkpKm98r 8SWI/EgzH7DGxG/SfbNVEPwX3m1U+Pprcc8FybC68Ppy/dMdOuoNXunh9ZUjqh5pGePW KZbTIcrpY6bJ1vquG6u7w8kXXHdYhHCgNn8LTqbfBp5GNumhcqqE95s3iaHS0TOt77W0 KlxHyO7kRMTsDidkUK3smnE94suDJ1Zu3ICLKov4YYnvFLrBQptJPEHGW6jAOLMqWtfo s/ahYM7GUAEG5B9N9m7b7J3RGZYABSXa99yDnJYtBneoPO1T3RBzluHOI8sdcMZ5FsB/ HjzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1709371829; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=utr9DgeUpMAbco5AiNRoOhFpmJhUBCQt49GPgJfu/NU=; b=ZsYJGW/H2THpK/xoQCokEc00cQbPLlrHr4ji32gsUEMMkS/PpkCbioQSqJshsSFxhb 0zsPfB7bkcF/dnuiVEmNIxbMtG0BScxO227qsu8UH2Xral2mMIR+Co33nnYQzisIw7ZO rj0cgkaexV03qiDrXbWEwQWHnhrccFcYlxYTQDU/kPlNGDx3t5GELDzKQKuSEfPFYHRb W9w/zLeMQZ6KSN+573pblAxt+6424XGoghWyD4xxmD+nWfHIAz8PRI+GWLDhII/8E5NP IS1cmg12Gh89uSgn4PvmutVWzWQmvoe9kbnoII3wbAn+mBmiu5hw2eZOchwoJv3UflgF D2mA== ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1709371828; s=strato-dkim-0002; d=hoewweken.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=utr9DgeUpMAbco5AiNRoOhFpmJhUBCQt49GPgJfu/NU=; b=GsxkavCRHaz/QFDTK5ZTOXdBm2cHssyn5AsRM7mChledRgouqOaRKA45J+2RsLVKs9 dOsGTkA7/JOoZDpA4rOyrohSRPNSJTVy/EK/2p+pcOPH6Bm+tk1y0ZXADMrcABN+noFl oZBQevws3ByK29XatdKLA0PpCunqZiXMkj8bGaSryYnnb//f+lmDHj0T6tCQ5/vSvs8u hOqsspH4A+EJKurApr3xWzZ0UhPHyCHULXyOHEv/+F4TsG/W+/1Mqsk3sl1/9YVRDdP7 aRxNKJfnXx3P4l7c3qKB7HlI2e1Cy3A0p4KojzhtD6P2nQgOH+9uQtBC1xImDQb5SgAV 6NTw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1709371828; s=strato-dkim-0003; d=hoewweken.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=utr9DgeUpMAbco5AiNRoOhFpmJhUBCQt49GPgJfu/NU=; b=VHRZEefZ0RaNGbqoInx8tVI5LpBwLXCI4+b5wPEWU/P7hlgBBCz3E4iO0R3KhU6jtk ZhtONzhvIxwXG0RQUPCQ== X-RZG-AUTH: ":O2kGeEG7b/pS1EW2TmikjLDsYYueHLp2aWg0q38nsxN1mOntnRORP93PLpfReKNjbyctOge9YThV7Q==" X-RZG-CLASS-ID: mo05 Received: from www.duedinghausen.eu by smtp.strato.de (RZmta 50.2.0 DYNA|AUTH) with ESMTPSA id R5eff80229USDE6 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Sat, 2 Mar 2024 10:30:28 +0100 (CET) Received: from [192.168.2.63] (speedport.ip [192.168.1.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) (Authenticated sender: steven) by www.duedinghausen.eu (Postfix) with ESMTPSA id 6CF4A11A199 for ; Sat, 2 Mar 2024 10:28:38 +0100 (CET) Message-ID: <054b7368-ff59-41c0-aafc-f489d6643acf@Duedinghausen.eu> Date: Sat, 2 Mar 2024 10:31:17 +0100 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Bhyve Boot Question To: virtualization@freebsd.org References: Content-Language: en-US From: Stephan Althaus In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.39 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; ARC_ALLOW(-1.00)[strato.com:s=strato-dkim-0002:i=1]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[hoewweken.de:s=strato-dkim-0002,hoewweken.de:s=strato-dkim-0003]; RCVD_IN_DNSWL_LOW(-0.10)[81.169.146.181:from]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:6724, ipnet:81.169.144.0/22, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[duedinghausen.eu]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[virtualization@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[hoewweken.de:+] X-Rspamd-Queue-Id: 4Tn07D1l0dz4Md6 On 3/1/24 23:29, Pete Wright wrote: > Hello, > > I was hoping someone could help me diagnose an issue I'm having > porting some FreeBSD VM's that are currently running on FreeBSD+Bhyve > to a SmartOS+Bhyve configuration. > > The VM's I'd like to port over use a file back VM raw disk image, this > works fine on my FreeBSD hypervisor but SmartOS would prefer zvols.  > One thing I should note is I'm using bhyveload(8) to boot my VMs.  The > guest instances in question are all FreeBSD as well. > > To test migrating these VM's to SmartOS I've done the following: > > 1. copy the VM image file to the SmartOS hypervisor > > 2. use quemu-img convert to convert the raw disk image to a zvol > > I did this with one of the official memdisk USB images, and things > worked great.  I used the UEFI bootrom flag to bhyve.  Yet when I try > to take one of the VM's I want to port things don't work as expected.  > When I start the VM the console (and VNC display output) just hang on > a blank screen.  I suspect its related to the fact that I use > bhyveload(8). > > Here is what the disk looks like for one of the VM's in question: > $ gpart  show nda0 > =>      40  41942960  nda0  GPT  (20G) >        40       216        - free -  (108K) >       256      1024     1  freebsd-boot  (512K) >      1280  39844608     2  freebsd-ufs  (19G) >  39845888   2097112     3  freebsd-swap  (1.0G) > > So my question is this - if I am reading the gpart output correctly, I > should be able to use the "bios" bootrom option for Bhyve under > SmartOS right and it'd find the "freebsd-boot" partition?  Or is > something special happening to my VM when I use bhyveload(8) that > would cause problems porting it over to a zvol under SmartOS? > > Thanks in advance for any insights! > > -pete > Hello! If you have a vm with BIOS boot, you have to use an other bootrom file.. UEFI looks like bootrom,/usr/share/bhyve/firmware/BHYVE_RELEASE.fd BIOS would be bootrom,/usr/share/bhyve/firmware/BHYVE_RELEASE_CSM.fd Alas i am on OpenIndiana, on SmartOs it may differ.. You can get your infos via pkg commands like this: # pkg list|grep bhy system/bhyve 0.5.11-2024.0.0.22024      i-- system/bhyve/firmware 20230801-2024.0.0.0        i-- system/library/bhyve 0.5.11-2024.0.0.22024      i-- system/zones/brand/bhyve 0.5.11-2024.0.0.5618       i-- # pkg contents system/bhyve/firmware PATH usr/share/bhyve usr/share/bhyve/firmware usr/share/bhyve/firmware/BHYVE.fd usr/share/bhyve/firmware/BHYVE_CSM.fd usr/share/bhyve/firmware/BHYVE_DEBUG.fd usr/share/bhyve/firmware/BHYVE_DEBUG_CSM.fd usr/share/bhyve/firmware/BHYVE_RELEASE.fd usr/share/bhyve/firmware/BHYVE_RELEASE_CSM.fd usr/share/bhyve/firmware/BHYVE_VARS.fd HTH Regards, Stephan