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:
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.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
Peter Grehan changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment #6 f
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-requ...@freebsd.org wrote:
>>> Hi Nikolai,
> Can someone look at Bugzilla 192470 please?
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
>>> We've
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
On 08/27/14 09:40, Nikolai Lifanov wrote:
> On 08/27/14 08:00, freebsd-virtualization-requ...@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-26
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
On 08/27/14 08:00, freebsd-virtualization-requ...@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
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
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
11 matches
Mail list logo