KIRIYAMA Kazuhiko wrote:
Hi, all
Yesterday, I've updated 14.0-CURRENT and tried to start VM,
filed to start with "loader returned error 139". VM log is
as follows :
root@vm:~ # tail -20 /vm/msrvkxb/vm-bhyve.log
Feb 05 09:50:18: initialising
Feb 05 09:50:18: [loader: bhyveload]
Feb 05 09:50:18:
Christian Barthel wrote:
Hello,
I switched my notebook from a ThinkPad X230 to ThinkPad T480
(each running 12.1). I noticed that one of my OpenBSD (6.3)
bhyve VMs is not booting anymore. It stops with a debugger
prompt:
acpi0: sleep states S5
acpi0: tables DSDT FACP HPET APIC MCFG SPCR
acpi0:
Steve Wills wrote:
Hmm, I think I saw this when using the -W flag to bhyve and removing
that avoided it.
Yes, I should have provided the flags I'm running bhyve with, no -W:
bhyve -DHSuw -c 4 -m 4G ...
On 8/31/20 8:38 AM, Peter Grehan wrote:
This appears to be an MP issue: if the number of v
Yuri Pankov wrote:
I'm getting the following periodically when Windows 10 (2004) guest is
booting:
Assertion failed: (dtype == ntype), function e82545_transmit, file
/usr/src/usr.sbin/bhyve/pci_e82545.c, line 1139.
Abort trap
It's especially unhelpful when booting the guest first
I'm getting the following periodically when Windows 10 (2004) guest is
booting:
Assertion failed: (dtype == ntype), function e82545_transmit, file
/usr/src/usr.sbin/bhyve/pci_e82545.c, line 1139.
Abort trap
It's especially unhelpful when booting the guest first time after
installation as it
Michael Reifenberger wrote:
> Hi,
> first I tried to install windows10 ltsc 2019 onto a nvme disk.
> This failed, the windows installer did not find a disk to install.
>
> Then I tried the following setup:
> ...
> disk0_type="ahci-hd"
> disk0_dev="zvol"
> disk0_name="disk0"
> disk1_type="nvme"
> d
tech-lists wrote:
> Hi,
>
> As subject - how can I pin a VM that used 4x cpu (-c 4) to realcpu?
> I know that it's the -p option but am unclear on the syntax.
>
> vmrun.sh gives the following for -p
>
> -p: pass-through a host PCI device at bus/slot/func (e.g. 10/0/0)
>
> but how to express thi
Matt Churchyard wrote:
>> Hi,
>
>> I'm taking my first steps in using bhyve, and the first showstopper seems to
>> be that using '-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd' gets
>> me immediate vm exit with >exit_reason being 48 (EPT violation).
>
>> Relevant part of dmesg:
>
> F
Hi,
I'm taking my first steps in using bhyve, and the first showstopper
seems to be that using '-l
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd' gets me immediate
vm exit with exit_reason being 48 (EPT violation).
Relevant part of dmesg:
FreeBSD 12.0-ALPHA9 r339291 GENERIC amd64
FreeBSD
