lost ability to run FreeBSD on bhyve on CURRENT
Nikolai Lifanov
lifanov at mail.lifanov.com
Wed Aug 27 16:00:53 UTC 2014
On 08/27/14 11:53, Nikolai Lifanov wrote:
> On 08/27/14 09:40, Nikolai Lifanov wrote:
>> On 08/27/14 08:00, freebsd-virtualization-request at freebsd.org wrote:
>>> Hi Nikolai,
>>>>> Can someone look at Bugzilla 192470 please?
>>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
>>> We've not been able to repro this on E3-1220 v3, E5-2650, or E5-2609
>>> v2 systems :(
>>>
>>> Do you have any xsave-related tunables set in loader.conf ?
>>>
>>> Do CURRENT guests work ? If so, would you be able to send a dmesg from
>>> one ?
>>>
>>> later,
>>>
>>> Peter.
>>
>> Hello.
>>
>> I don't have anything exotic in my loader.conf:
>> vmm_load="YES"
>> nmdm_load="YES"
>> pptdevs="10/0/0"
>> zfs_load="YES"
>> vfs.root.mountfrom="zfs:tank/ROOT/270660"
>>
>> Disabling ppt doesn't help either. CURRENT panics and drops me in ddb
>> when booting. I attached "sysctl hw.vmm" and the panic message when
>> trying to boot CURRENT to the bug.
>>
>
> Interestingly, boot works 1/many times. By repeatedly trying to boot it
> over and over again, I was able to get it to boot twice total. Once
> FreeBSD is able to boot, it works as expected.
>
> I'm about to attach the dmesg from this to Bugzilla.
>
Update: if I pin vcpu 0 to hostcpu 0, boot works every time.
- Nikolai Lifanov
More information about the freebsd-virtualization
mailing list