4.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
imes it requires both vmm.ko *and* bhyve. At this
point there is not much more I can do for you on this issue beyond what I
have stated.
Mark
The patch is used in both.
Please read the bug I mentioned (comments #1 and #2) where the submitter
only compiled a new vmm.ko and it didn't work without the corresponding
bhyve.
Mark
ioned or 2) open a new
bug. Make sure to include information on the host system as well
(intel/amd, etc.) and how the various guest bits (.img, .fd, etc) were
download/created.
Mark
ge I need to
make before submitting it for review. Please make that change in your copy.
And per email after this one, yes, that compilation of vmm.ko looks fine.
Mark
On Mon, Dec 2, 2024 at 1:05 PM Mario Marietto
wrote:
> Hello Mark,
>
> I see that your patch is about to modify the code of the vmm.ko module.
> I've just exchanged the vmm.ko module that I'm using on the ZFS system with
> the module that I use on the UFS system (where I
out how I can fix it ?
>
This looks like a duplication of this bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282852
I need to tweak the patch (attached to the bug) before submitting for
review. Note that both the kernel and bhyve need to be recompiled after
applying the patch.
Mark
of:
http://ftp3.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/15.0-CURRENT/aarch64/20241107/FreeBSD-15.0-CURRENT-arm64-aarch64-ufs-20241107-5036d9652a57-273504.vhd.xz
(Listed with "2024-Nov-07 06:22" in the web browser.)
===
Mark Millard
marklmi at yahoo.com
On Fri, Oct 25, 2024 at 11:12:48PM +0200, Guido Falsi wrote:
> On 25/10/24 22:49, Mark Johnston wrote:
> > On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
> > > Hi,
> > >
> > > I've recently updated my current machines to git commit
> >
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
> Hi,
>
> I've recently updated my current machines to git commit
> 525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024 -0800)
> and just have Windows 10 VMs fail to start in bhyve with the error in the
> subject.
>
> I'v
root cmd bhyve-lin
>> permit nopass :wheel as root cmd /bhyve/12-Win-11-vm12
>>
>> [marietto@marietto /bhyve]==> doas 12-Win-11-vm12
>> doas: Operation not permitted
>>
>> On Mon, Jun 17, 2024 at 9:50 PM Mark Peek wrote:
>>
>>> Likely because y
n the vm like this :
>
> [marietto@marietto /bhyve]==> doas 12-Win-11-vm12
>
> it says :
>
> doas: 12-Win-11-vm12: command not found
>
> and when I do :
>
> [marietto@marietto /bhyve]==> doas ./12-Win-11-vm12
>
> it says :
>
> doas: Operation not permitted
>
Likely need to add this as it is what you are passing to doas as the
command to execute:
permit nopass :wheel as root cmd /usr/sbin/12-Win-11-vm12
Mark
On Mon, Jun 17, 2024 at 10:40 AM Mario Marietto wrote:
>
> [marietto@marietto /bhyve]==> sudo cp 12-Win-11-vm12 /usr/sbin
>
I've been working on porting bhyvectl and vmrun.sh to arm64, as the
initial arm64 bhyve port has landed in main. In the process I
discovered a problem with bhyve's handling of BARs that I'd appreciate
some help with.
Suppose I configure a VM with a virtio-blk and virtio-net device. Both
register
?
If an Amazon firecracker environment works for you, there’s
https://www.freebsd.org/status/report-2023-04-2023-06/boot-performance/ of
course, there’s more to booting than the kernel. I’d guess some of those
improvements could apply to more generic VM hypervisors too.
- Mark
Hi all, today I've learned and been reading about VETHER(4). Virtual
ethernet interface on FreeBSD, wanted to try it for my VMs networking.
My VMs currently are networking through vm-vmswitch with a set of private
IP block; 192.168.2.1/29 (PF - NAT involved);
# vm switch list
NAME TYPE
Hello,
I implemented a network backend for bhyve which uses libslirp to provide
NAT on a virtual network. This enables some of the functionality one
can get with "user" network devices in QEMU. I have a few use cases and
particularly want to be able to ssh into guests without requiring any
netwo
ners-for-freebsd-512a6df2bc85
which should get you what you need, ask podman is OCI compliant and
mostly compatible w/ docker, see:
https://soc.crashed.org/objects/2d51da12-7262-4576-bf53-0ea6a61d0da0
The last message is on the dev version of FreeBSD, I'm not sure if it
will run on 13 if you
On Wed, Feb 08, 2023 at 11:08:31AM -0800, John Baldwin wrote:
> On 2/8/23 10:05 AM, Mark Johnston wrote:
> > On Sun, Jan 15, 2023 at 10:46:21AM -0500, Mark Johnston wrote:
> >> On Wed, Nov 23, 2022 at 08:00:16AM +, Corvin Köhne wrote:
> >>> The branch ma
On Sun, Jan 15, 2023 at 10:46:21AM -0500, Mark Johnston wrote:
> On Wed, Nov 23, 2022 at 08:00:16AM +, Corvin Köhne wrote:
> > The branch main has been updated by corvink:
> >
> > URL:
> > https://cgit.FreeBSD.org/src/commit/?id=7c326ab5bb9aced8dcbc2465ac1c9
eeBSD (with NAT), it does not seem to be a viable
alternative for any kind of use without such an effort.
I'd expect Apple silicon macOS VM's to have the same sort
of properties for aarch64 FreeBSD. But I've no access to an
Apple silicon context to check with.
===
Mark Millard
marklmi at yahoo.com
On Fri, Nov 04, 2022 at 11:22:55AM +0100, Corvin Köhne wrote:
> > On 10/23/22 11:18 AM, Mark Johnston wrote:
> >> I'm going through compiler warnings in the bhyve code with the aim of
> >> bumping WARNS, since the current setting hides bugs. There's one in the
I'm going through compiler warnings in the bhyve code with the aim of
bumping WARNS, since the current setting hides bugs. There's one in the
config code that looks a bit tricky to resolve and I was hoping for some
guidance on the right way to do that.
The basic problem is _lookup_config_node() m
> > receiver
>
>
> Increasing MTU on the Virtio interface and on the TAP interface to 9000 helps
> a little bit:
> getting 8.38Gbit/s guest->host and 10.3Gbit/s host->guest.
>
> Increasing TCP windows size to 1024k only produces more retries and
Erik,
Sorry about that, teach me to respond from my phone.
How about this for the FreeBSD related code?
https://github.com/sean-/freebsd
which has a default branch of projects/VPC?
Mark
On Sun, Apr 17, 2022 at 9:10 AM Erik N wrote:
> Thank you Mark but as mentioned that’s not it.
>
Perhaps this?
https://github.com/joyent/freebsd-vpc
Mark
On Sun, Apr 17, 2022 at 6:03 AM Philip M. Gollucci
wrote:
> I may be able to get ahold of Brian Cantrill. He's likely the best PoC
> too.
>
> On Sun, Apr 17, 2022 at 2:49 AM Erik N wrote:
>
>> I was watch
just the only measure of
benchmarking, but the amount of CPU time used to get the work done..
Another option that has been discussed, but I don't think has made any
headway is only running all the VM's vCPUs at once, but that would
require a lot of scheduler work.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
On Sat, Jun 05, 2021 at 01:00:45PM +, Wei Hu via freebsd-virtualization
wrote:
> Hi Harry,
>
> Can you test if this patch fixes the problems?
>
> https://reviews.freebsd.org/D30577
Hi Wei,
Harry tested the patch before I submitted the review; it does indeed fix
the problems with vmbus on i
28 matches
Mail list logo
