[Bug 241338] [bhyve] haiku fails to boot with smp (more than one virtual core)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Oct 19 06:16:32 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241338
Bug ID: 241338
Summary: [bhyve] haiku fails to boot with smp (more than one
virtual core)
Product: Base System
Version: 11.3-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bhyve
Assignee: virtualization at FreeBSD.org
Reporter: nep at packageloss.eu
Created attachment 208414
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208414&action=edit
syslog of failed haiku boot (output of bhyve)
For purposes of this bug i am mentioning a specific revision i have tested this
issue with, even though i haven't found any haiku revision this did not occur
on. haiku revision: hrev53541 with architecture x86_64
The 'haiku-nightly-anyboot.iso' can be obtained from
https://download.haiku-os.org/nightly-images/x86_64/, or more precisely what i
used:
https://s3.wasabisys.com/haiku-nightly/x86_64/haiku-master-hrev53546-x86_64-anyboot.zip
The file is in the archive.
This is my host system:
uname -a: FreeBSD sleepyprincess 11.3-RELEASE FreeBSD 11.3-RELEASE #0 r349754:
Fri Jul 5 04:45:24 UTC 2019
root at releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
Haiku will boot here with this invocation of vmrun.sh
./vmrun.sh -c 1 -E -i -I haiku-nightly-anyboot.iso haiku
But not with this one
./vmrun.sh -c 2 -E -i -I haiku-nightly-anyboot.iso haiku
I am not sure if this is all information that is required, please tell me if i
missed anything :)
sysctl:
hw.machine: amd64
hw.model: AMD FX(tm)-4300 Quad-Core Processor
hw.ncpu: 4
hw.byteorder: 1234
hw.physmem: 4237471744
hw.usermem: 1444818944
hw.pagesize: 4096
hw.floatingpoint: 1
hw.machine_arch: amd64
hw.realmem: 4294967296
hw.vmm.npt.pmap_flags: 507
hw.vmm.svm.num_asids: 65536
hw.vmm.svm.disable_npf_assist: 0
hw.vmm.svm.features: 7423
hw.vmm.svm.vmcb_clean: 1023
hw.vmm.vmx.l1d_flush_sw: 0
hw.vmm.vmx.l1d_flush: 0
hw.vmm.vmx.vpid_alloc_failed: 0
hw.vmm.vmx.posted_interrupt_vector: -1
hw.vmm.vmx.cap.posted_interrupts: 0
hw.vmm.vmx.cap.virtual_interrupt_delivery: 0
hw.vmm.vmx.cap.invpcid: 0
hw.vmm.vmx.cap.monitor_trap: 0
hw.vmm.vmx.cap.unrestricted_guest: 0
hw.vmm.vmx.cap.pause_exit: 0
hw.vmm.vmx.cap.halt_exit: 0
hw.vmm.vmx.initialized: 0
hw.vmm.vmx.cr4_zeros_mask: 0
hw.vmm.vmx.cr4_ones_mask: 0
hw.vmm.vmx.cr0_zeros_mask: 0
hw.vmm.vmx.cr0_ones_mask: 0
hw.vmm.vmx.no_flush_rsb: 0
hw.vmm.ept.pmap_flags: 0
hw.vmm.vrtc.flag_broken_time: 1
hw.vmm.ppt.devices: 0
hw.vmm.iommu.enable: 1
hw.vmm.iommu.initialized: 0
hw.vmm.bhyve_xcpuids: 8
hw.vmm.topology.cpuid_leaf_b: 1
hw.vmm.topology.cores_per_package: 1
hw.vmm.topology.threads_per_core: 1
hw.vmm.create: beavis
hw.vmm.destroy: beavis
hw.vmm.trace_guest_exceptions: 0
hw.vmm.ipinum: 251
hw.vmm.halt_detection: 1
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-virtualization
mailing list