[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-09-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Nikolai Lifanov changed: What|Removed |Added Status|Needs Triage|Issue Resolved Resolutio

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #10 from Nikolai Lifanov --- This is exactly it! I had a BIOS setting called "Limit Max CPUID". After I turned it off, every core shows the same features and bhyve works reliably. It's still interesting that bhyve works despit

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #9 from Peter Grehan --- 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:

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #8 from Nikolai Lifanov --- Created attachment 146425 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146425&action=edit cpuid difference -- You are receiving this mail because: You are the assignee for the bug.

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #7 from Nikolai Lifanov --- 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

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Peter Grehan changed: What|Removed |Added CC||gre...@freebsd.org --- Comment #6 f

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #5 from Nikolai Lifanov --- Since booting actually works once in a while, I tried pinning vcpu 0 to hostcpu 0. If I pin vcpu 0 to hostcpu 0, boot works every time. -- You are receiving this mail because: You are the assignee f

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #4 from Nikolai Lifanov --- Created attachment 146380 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146380&action=edit dmesg from CURRENT boot The boot sometimes works. Trying to boot CURRENT over and over again, I

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #3 from Nikolai Lifanov --- Created attachment 146377 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146377&action=edit panic booting CURRENT This is trying to boot CURRENT snapshot, r270458 -- You are receiving th

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 --- Comment #2 from Nikolai Lifanov --- Created attachment 146376 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146376&action=edit sysctl hw.vmm output of "sysctl hw.vmm" -- You are receiving this mail because: You are the as

[Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT

2014-08-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Craig Rodrigues changed: What|Removed |Added CC||rodr...@freebsd.org As