[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Nikolai Lifanov lifa...@mail.lifanov.com changed: What|Removed |Added Status|Needs Triage|Issue Resolved Resolution|--- |Works As Intended --- Comment #11 from Nikolai Lifanov lifa...@mail.lifanov.com --- This issue can be closed. It's not valuable to fix, but anyone with a similar problem can find this bug report. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #2 from Nikolai Lifanov lifa...@mail.lifanov.com --- Created attachment 146376 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146376action=edit sysctl hw.vmm output of sysctl hw.vmm -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #4 from Nikolai Lifanov lifa...@mail.lifanov.com --- Created attachment 146380 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146380action=edit dmesg from CURRENT boot The boot sometimes works. Trying to boot CURRENT over and over again, I was able to boot it twice out of many tries. Here is a dmesg output from a successful boot. If FreeBSD boots, it works normally. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Peter Grehan gre...@freebsd.org changed: What|Removed |Added CC||gre...@freebsd.org --- Comment #6 from Peter Grehan gre...@freebsd.org --- Just to confirm the negative: does pinning to CPUs other than 0 result in the guest crashing ? If so, would you be able to install the cpuid port (pkg install cpuid) and run it on all cpus cpuset -l cpu cpuid .. and see if there are any differences in what is reported between CPUs, other than obvious ones such as APIC ID. later, Peter. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #7 from Nikolai Lifanov lifa...@mail.lifanov.com --- Pinning vcpu 0 on hostcpu 1 does not allow boot. It seems that all cpus other than 0 produce a similar diff. I'm about to attach it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #8 from Nikolai Lifanov lifa...@mail.lifanov.com --- Created attachment 146425 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146425action=edit cpuid difference -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #9 from Peter Grehan gre...@freebsd.org --- Comment on attachment 146425 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146425 cpuid difference Thanks - I think this explains it. -Vendor ID: GenuineIntel; CPUID level 13 +Vendor ID: GenuineIntel; CPUID level 2 The AP is coming up with a reduced number of CPU leaves compared to the BSP. FreeBSD (and bhyve) assumes that this is the same in all CPUs. FreeBSD itself pulls all information about the system from the BSP's leaf contents, and then assumes this is the same for all other CPUs. bhyve's assumption is that it can call do_cpuid() on any CPU and get the same information to pass to guests on CPUID exits. A lot of applications also assume this and will look at CPUID values to determine whether they can use SSE/SSE2/AVX libraries etc. What system is this ? Are there BIOS options to change max leaf values ? Is it running nested ? later, Peter. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Craig Rodrigues rodr...@freebsd.org changed: What|Removed |Added CC||rodr...@freebsd.org Assignee|freebsd-b...@freebsd.org|freebsd-virtualization@Free ||BSD.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
