Hi,

Following daily snapshots, I have hit a bug that was introduced between
6.5-current #61 and 6.5-current #66 (not sure if it was related to the LLVM
upgrade).

Reference system is bhyve on FreeBSD 11.2 with an OpenBSD guest.  #61 boots
fine and runs as expected.  However, #66 get to the following point and the
guest terminates:

scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xbf957000 (11 entries)
bios0: vendor BHYVE version "1.00" date 03/14/2014
bios0: bhyve BHYVE
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S5
acpi0: tables DSDT FACP HPET APIC MCFG SPCR
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 16777216 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1230 v6 @ 3.50GHz, 3504.21 MHz, 06-9e-09
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,HTT,PBE,SSE3,PCLMUL,DTES64,DS-CPL,SSSE3,SDBG,FMA3,CX16,xTPR,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,BMI1,HLE,AVX2,BMI2,ERMS,INVPCID,RTM,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: CPU supports MTRRs but not enabled by BIOS

(Note:  The above was text from #61 but was all the console text (as UEFI
is graphics) I could copy/paste).

Below is output from bhyve.log:

rdmsr to register 0xc80 on vcpu 0
Failed to emulate instruction [0xf7 0x04 0x25 0x00 0xd3 0xd1 0x81 0x00 0x10
0x00 0x00 0x74 0x08 0xf3 0x90] at 0xffffffff817648f0

bhyve.log when booting with #61:

rdmsr to register 0xc80 on vcpu 0
rdmsr to register 0xc80 on vcpu 1
rdmsr to register 0xc80 on vcpu 2
rdmsr to register 0xc80 on vcpu 3
rdmsr to register 0xc80 on vcpu 4
rdmsr to register 0xc80 on vcpu 5
rdmsr to register 0xc80 on vcpu 6
rdmsr to register 0xc80 on vcpu 7

RAMDISK #62 is not showing this issue either.

Please advise if there is any further information that is needed.

Jason.

Reply via email to