From nobody Sun Dec 08 18:41:05 2024 X-Original-To: freebsd-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 4Y5v3317ycz5f1L0 for ; Sun, 08 Dec 2024 18:41:19 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y5v314NYsz4Cl4 for ; Sun, 8 Dec 2024 18:41:17 +0000 (UTC) (envelope-from mp@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1733683277; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3JH36ILS7CbRSogBAIG8/cZS2CYQd1k9vwZNu0rY8Zk=; b=U8BVSi8hY3RmisGqooq4Vcgjzot1XPxBSkxpmLhl9Vs2M/Jfh3eWUpvQGC9OCXk1dy+big Fb/zMH5xwP4hJpkTNDRqLmVH4LfXLHG+iLptIpNzmsPjA65mh6n3ZGmwCsbzj9GuJ2VME+ +f/ARWKQhhwT0RKbqi4L7QK6rI4yM1GpPuHozvRCNu6El3hwjwM+IM7avpZ4mi+yxdvn+x 5SsTE4d0AlsbTUMQPmEDUqe/SB0JzYuWSxbIkhu6ggFajzJmosTQBNM2llgnJc7CIblB4O ewSjIcZ2LWgBGHST5XGw/P1mBdY9RrZBHhcq6vBKirJ/leLevRS36M8ScEORdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1733683277; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3JH36ILS7CbRSogBAIG8/cZS2CYQd1k9vwZNu0rY8Zk=; b=l7Zbsthf6CUOmLqj6X8YtFe0sUXKHpdpL9TygXp/6SSuvWcWlC/l1y14inySbvj1yzzuDl AWFTf359K3PFNnz1SUySp/AXSVNviPTXWrBp3rurraMuMxvtPSf0NRRJ9uyi7xHu+TNQJV TmDwbhe5FL/LRFwt72jNLM4DlujOvmFDD09VmuVbSL7xDnBg6uogKwqFjDh2hpNLwowhGX xSEEKA7vlSegatYOBH2BArJHcOzg5vhmRkFIpYlGWu49SCzqYmGLLSnYS5Jpd5i2U+P74U FTuRt8CQlXCEv66jjrGzp1Nep+Kh3AzIJozzVImWPNhXpKDnWc1CKrC71jyipw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1733683277; a=rsa-sha256; cv=none; b=IWwSgFhRR37v4+jsor6mbpaUTgR2laQDpqtSnrkUVFdTSr/4tB5o+6jawvU1Warl8opGCB QTrtjUUFuhVFcmO90xKluXXCdQO09C6qMmm906eaRO8tqDhcqF0/hQu/4cvdiGO9D7cyAB FEHzfMLbzVV1LhZh2TmK0HjAYWmNJFyvG/DCA+C5AusRNUdFVGQ+CNcMosmrHlh8Hf5+DH JFL4DCa3K57/O/OokI2ZE1h9MeXRfrHjl/qo3lGmvoQsRMn/sfB3wUchwZcVXBKl6MR2wO BXHJliJH8THAddOPQ1c8juarbe3bSHZYKQeq55ywI978SjWULWnzrA0KbF/5cA== Received: from mail-qt1-f179.google.com (mail-qt1-f179.google.com [209.85.160.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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.gmail.com", Issuer "WR4" (verified OK)) (Authenticated sender: mp) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Y5v313mKKz1K5F for ; Sun, 8 Dec 2024 18:41:17 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mail-qt1-f179.google.com with SMTP id d75a77b69052e-4674ce290aaso18788701cf.3 for ; Sun, 08 Dec 2024 10:41:17 -0800 (PST) X-Forwarded-Encrypted: i=1; AJvYcCWqkQjftCFDCa5QIWEwYHVDVeqXKoyxAazqger1xI/3kqpXDRFrQPemBTBw7SixWWAJF2IKB1qnf88/BpfzRSiGNU+6vwOC@freebsd.org X-Gm-Message-State: AOJu0Yzqwvd3PvMWy6Bu++KvuAIYAIH09CCsKo/dv8gXjORS+WsCFlvE d7CRWXWgAEWhtDpUn8QK9k0OQZCXUmkev/mhAuKhhCxiP/ebpNzpmpc86SxVUpadYDoujxhuMAe bjC2KI7QhuLOlCAWjyiUCYkYSBTI7FSV2xEMvHw== X-Google-Smtp-Source: AGHT+IHbZ2QcPB1w45jkHAOApSSFOu2lH3AsZ5ADnj/rLn+KAhsz+NrozNk6Slib05my8jVcs/FzyUmM7ZIU9MeHTqA= X-Received: by 2002:a05:622a:7414:b0:467:48f3:3452 with SMTP id d75a77b69052e-46748f339a0mr108799611cf.56.1733683277164; Sun, 08 Dec 2024 10:41:17 -0800 (PST) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 References: <6B19A54E-78B2-4BDA-94FA-F7558F26DA87@iitbombay.org> In-Reply-To: From: Mark Peek Date: Sun, 8 Dec 2024 10:41:05 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Struggle with bhyve and Kali. To: Zaphod Beeblebrox Cc: Bakul Shah , freebsd-virtualization@freebsd.org, Chris Moerz Content-Type: multipart/alternative; boundary="000000000000e391910628c6978b" --000000000000e391910628c6978b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Dec 8, 2024 at 1:51=E2=80=AFAM Chris Moerz = wrote: > > > On Sat, 7 Dec 2024, Zaphod Beeblebrox wrote: > > > That doesn't seem to help for kali. I found the binary, and I think it > boots... but it goes from the 1080p > > that I select for it down to some 4x3 resolution that is tiny. Then I > think X is up, but I don't get a > > login or any other response to input other than a mouse cursor. > > > > Really, this should be documented (the uefi boot variables thing). I > suppose I'll keep messing with it --- > > maybe booting with the full resolution and the correct file will work > --- which will likely require me to > > mount the efi partition on the host and mess around. > > I believe this actually is documented - at least in the Handbook: > > https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization= -bhyve-uefi > > I remember we added that note in the blue box particularly because of the > behavior you're describing. > > If you have any recommandation or suggestion how to make it clearer, I'm > certainly open to hear it! > > If using vm-bhyve and uefi, make sure these are set in the vm-bhyve config file prior to installing: loader=3D"uefi" uefi_vars=3D"yes" In other words: # vm create kali Now edit kali/kali.conf to add the above and other tweaks to the settings # vm install kali kali-linux-2024.3-installer-amd64.iso Install kali and it reboots. Login and shut it down # vm start kali kali should boot fine now You should now see a kali/uefi-vars.fd file in the virtual machine directory. Mark --000000000000e391910628c6978b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Dec 8, 2024 at 1:51=E2=80=AFAM Ch= ris Moerz <freebsd@ny-central.= org> wrote:


On Sat, 7 Dec 2024, Zaphod Beeblebrox wrote:

> That doesn't seem to help for kali.=C2=A0 I found the binary, and = I think it boots... but it goes from the 1080p
> that I select for it down to some 4x3 resolution that is tiny.=C2=A0 T= hen I think X is up, but I don't get a
> login or any other response to input other than a mouse cursor.
>
> Really, this should be documented (the uefi boot variables thing).=C2= =A0 I suppose I'll keep messing with it ---
> maybe booting with the full resolution and the correct file will work = --- which will likely require me to
> mount the efi partition on the host and mess around.

I believe this actually is documented - at least in the Handbook:
https://docs.fre= ebsd.org/en/books/handbook/virtualization/#virtualization-bhyve-uefi
I remember we added that note in the blue box particularly because of the behavior you're describing.

If you have any recommandation or suggestion how to make it clearer, I'= m
certainly open to hear it!


If using= vm-bhyve and uefi, make sure these are set in the vm-bhyve config file pri= or to installing:
loader=3D"uefi&qu= ot;
uefi_vars=3D"yes"

In other= words:
# vm create kali
Now edit kali/kali.conf to add= the above and other tweaks to the settings
# vm install kali=C2= =A0kali-linux-2024.3-installer-amd64.iso
Install kali and it rebo= ots. Login and shut it down
# vm start kali
kali should= boot fine now

You should now see a kali/uefi-vars= .fd file in the virtual machine directory.

Mark

--000000000000e391910628c6978b--