Regarding items 3) and 4):
3) Indeed, bhyve does not explicitly forbid writing to 0x3c. I meant
the following. The interrupt line is set is pci_emul.c in bhyve:
pci_set_cfgdata8(pi, PCIR_INTLINE, pirq_irq(ii->ii_pirq_pin)); Bhyve
asserts interrupts with pci_irq_assert in amd64/pci_irq.c. We ne
1) The problem with PIT. Can be solved as you proposed or by
patching Mezzano. The bhyve patch would be the best option for that: it's
useful for
other older o/s's (DOS).
2) Mezzano assumes that Intel AHCI controllers report no more than 6
ports. Can be solved by patching Mezzano or defining M
I suspect PCI interrupts are not functioning correctly.
Look at this code:
;; Attach interrupt handler.
(sup:debug-print-line "Handler: " (ahci-irq-handler ahci))
(sup:irq-attach (sup:platform-irq (pci:pci-intr-line location))
(ahci-irq-handler-function ahci)
Turns out, panic always happens in the same place when Mezzano is trying
to initialize an AHCI controller. Qemu uses an old PATA controller
by default, which works. When forcing SATA, it fails just like bhyve.
Virtio block devices are also claimed to work, but using virtio-blk
option in bhyve a
Hi! Mezzano is an operating system written in Common lisp. I would like
to test it in bhyve. When I launch it, it spins infinitely in a loop
measuring how many CPU cycles it makes in a unit of time (I understood
it by adding various debug messages).
The timer it uses is something called a PIT:
wrmsr to register 0xc0011029(0x3) on vcpu 0
The -w option is needed so that bhyve won't exit on accessing an
unimplemented MSR (that particular one is harmless).
later,
Peter.
I don't know why bhyve validates the BAR size. The commit adding this
check is old [1] and doesn't explain it. What bhyve could do is
rounding up the BAR size to a full page size when allocating memory for
the BAR.
[1] https://github.com/freebsd/freebsd-
src/commit/7a902ec0eccc752c9c38533ed123121
Hi Chuck,
I'm getting conflicting information and thought I'd ask here about
guest disk images without UEFI.
1. If bhyve can boot the image with uefi-csm, should I be able to get
a graphical console? I tried:
-s 6:0,fbuf,tcp=0.0.0.0:5900,vga=io
VNC connects, but the screen is blank. I saw s
Hi Thomas,
I have 2 production servers that I want to upgrade to FreeBSD 14.0 that
use Bhyve to run OpenBSD 7.3 packet packet filters and a few other
instances. Since this is an operating system upgrade to FreeBSD 14.0, I
wanted to also upgrade the OpenBSD 7.3 instance to OpenBSD 7.4 that was
Hi Corvin,
this is the next patch stack for EDKII. Bhyve is able to pass ACPI
tables to the guest by FwCfg. This is more flexible and less space
limited than our current approach of placing ACPI tables into memory.
So, this patch stack modifes the guest firmware to pick up ACPI tables
from FwCfg
Using the qemu fwcfg has one big disadvantage:
Bhyve's fwctl and qemu's fwcfg can't be used at the same time. Due to
backward compatibility reasons, bhyve uses fwctl as default. So, using
qemu's fwcfg to locate the rsdp only works, if the user changes his
bhyve call.
I don't want to use fwctl to l
Hi Corvin,
I would like to send the following patch to the EDKII project.
Therefore, I'd like to get some feedback from the bhyve community before
sending them to EDKII.
Thanks for giving a heads-up.
The patch looks fine to me. The only minor suggestion I have is to use
the qemu fwcfg inte
Managed to "fix" it :D - the tl;dr version is "select GPT and not MBR"
because if GPT isn't selected, an msdos efi partition isn't created and
that's why my previous attempts (apart from the vm where I made a msdos
partition manually before installation) failed.
This part in the initial installat
Hi,
Hello, I'm trying to attach another disk to an openbsd72 guest like so:
[snip]
bhyve -c 4 -m 16G -wuH \
-s 0,amd_hostbridge \
-s 3,virtio-blk,/dev/zvol/vms/openbsd64g \
-s 4,ahci-hd,/dev/zvol/vms/openbsd-externalfs0 \ <=== here
-s 5,virtio-net,tap14 \
-s 30,xhci,tablet \
-s 31,lpc -l com1,s
message?
Acked-by: Peter Grehan
[re-posting from my personal email account, since my mail to > freebsd-virtualization got rejected]> > I seem to remember seeing
previous feedback that Bhyve developers > strongly preferred the
BhyveFwCtl mechanism. I've been out of the loop > though (busy with
$dayjob) so I don't know if thing
Hi Corvin Köhne wrote:,
It's much easier to create configuration dependend ACPI tables for
bhyve than for OVMF. For this reason, don't use the statically
created ACPI tables provided by OVMF. Instead use the dynamically
created ACPI tables of bhyve. If bhyve provides no ACPI tables or
we are un
Hi Bjoern,
I grabbed an external USB drive from an Intel machine and put it to an
AMD host
using it to boot directly from it like:
-s 3,ahci-hd,/dev/da0,sectorsize=512 \
...
On the AMD machine this doesn't work and I get a lot of:
ivhd0: EVT INTR 45 Status:0x1a EVT Head:0xfb0 Tail:
Hi Corvin,
As far as I know, QEMU uses OVMF with bus enumeration enabled. How
does QEMU solve such issues?
Full-time corp Linux staff working on Qemu, KVM and EFI.
- there is no need for EFI to perform a slow scan via PCI bus
operations, resulting in VM-exits, where bhyve can perform all th
Hi Corvin,
Thanks for posting these here.
GPU-Passthrough for bhyve requires a few patches to work properly.
These patches will allow GPU-Passthrough for bhyve.
It will work for dedicated AMD GPUs and integrated Intel GPUs.
Nvidia GPUs are untested.
I have no issue with patches 3/4 and 4/4.
20 matches
Mail list logo
