On Thu, Jun 25, 2015 at 1:07 AM, John Nielsen wrote:
> Interesting. Using the same PC-BSD image I am able to reproduce on a server
> running slightly older software but I can not reproduce running bleeding
> edge. I verified enable_apicv=Y on both. In both cases I ran
> qemu-kvm -drive if=virtio
On 24/06/2015 19:07, John Nielsen wrote:
>
> Unfortunately I no longer have the test environment I used a few days
> ago to reproduce this issue so I can’t verify the software versions
> that were in use. It’s possible I was mistaken about the kernel
> version (I thought it was 4.0.4). Perhaps i
On Jun 24, 2015, at 9:50 AM, Paolo Bonzini wrote:
> On 23/06/2015 00:08, John Nielsen wrote:
I’m resurrecting an old thread since I haven’t heard anything in a
while. Has anyone looked in to the KVM+apicv bug documented above as
well as here:
https://bugs.launchpad.net/q
On 24/06/2015 17:57, Bandan Das wrote:
> Paolo Bonzini writes:
> ...
>>
>> I did this:
>>
>> 1) download
>> http://download.pcbsd.org/iso/10.1-RELEASE/amd64/PCBSD10.1.2-x64-trueos-server.raw.xz
>> and unpack it
>>
>> 2) run it with "qemu-kvm -drive
>> if=virtio,PCBSD10.1.2-x64-trueos-server.raw
Paolo Bonzini writes:
...
>
> I did this:
>
> 1) download
> http://download.pcbsd.org/iso/10.1-RELEASE/amd64/PCBSD10.1.2-x64-trueos-server.raw.xz
> and unpack it
>
> 2) run it with "qemu-kvm -drive
> if=virtio,PCBSD10.1.2-x64-trueos-server.raw -smp 2"
>
> 3) login as root/pcbsd, type "reboot"
>
>
On 23/06/2015 00:08, John Nielsen wrote:
>>> I’m resurrecting an old thread since I haven’t heard anything in a
>>> while. Has anyone looked in to the KVM+apicv bug documented above as
>>> well as here:
>>>
>>> https://bugs.launchpad.net/qemu/+bug/1329956 ?
>>>
>>> If appropriate, where should I
On 23/06/2015 00:08, John Nielsen wrote:
Thank you. This both narrows the problem considerably and provides
an acceptable workaround. It would still be nice to see it fixed, of
course. Keep me CC'ed as I'm not on the KVM list.
>>>
>>> I’m resurrecting an old thread since I haven’t
On Jun 22, 2015, at 3:48 PM, Bandan Das wrote:
> John Nielsen writes:
>
>> On Jun 17, 2014, at 10:48 AM, John Nielsen wrote:
>>
>>> On Jun 17, 2014, at 12:05 AM, Gleb Natapov wrote:
>>>
On Tue, Jun 17, 2014 at 06:21:23AM +0200, Paolo Bonzini wrote:
> Il 16/06/2014 18:47, John Niels
John Nielsen writes:
> On Jun 17, 2014, at 10:48 AM, John Nielsen wrote:
>
>> On Jun 17, 2014, at 12:05 AM, Gleb Natapov wrote:
>>
>>> On Tue, Jun 17, 2014 at 06:21:23AM +0200, Paolo Bonzini wrote:
Il 16/06/2014 18:47, John Nielsen ha scritto:
> On Jun 16, 2014, at 10:39 AM, Paolo Bon
On Jun 17, 2014, at 10:48 AM, John Nielsen wrote:
> On Jun 17, 2014, at 12:05 AM, Gleb Natapov wrote:
>
>> On Tue, Jun 17, 2014 at 06:21:23AM +0200, Paolo Bonzini wrote:
>>> Il 16/06/2014 18:47, John Nielsen ha scritto:
On Jun 16, 2014, at 10:39 AM, Paolo Bonzini wrote:
> Il 16/
On Jun 20, 2014, at 1:53 PM, Paolo Bonzini wrote:
> Il 20/06/2014 17:41, John Nielsen ha scritto:
>>> >
>>> > So we have a clue. Let me study the code more, I'll try to get back with
>>> > a suggestion.
>> Paolo, have you had an opportunity to look in to this some more?
>
> Not yet, sorry.
>
Il 20/06/2014 17:41, John Nielsen ha scritto:
>
> So we have a clue. Let me study the code more, I'll try to get back with a
suggestion.
Paolo, have you had an opportunity to look in to this some more?
Not yet, sorry.
One possibility is this though. Can you try migrating (or
saving/restor
On Jun 16, 2014, at 10:21 PM, Paolo Bonzini wrote:
> Il 16/06/2014 18:47, John Nielsen ha scritto:
>> On Jun 16, 2014, at 10:39 AM, Paolo Bonzini wrote:
>>
>>> Il 16/06/2014 18:09, John Nielsen ha scritto:
>> The only substantial difference on the hardware side is the CPU.
>> The hosts
On Jun 17, 2014, at 12:05 AM, Gleb Natapov wrote:
> On Tue, Jun 17, 2014 at 06:21:23AM +0200, Paolo Bonzini wrote:
>> Il 16/06/2014 18:47, John Nielsen ha scritto:
>>> On Jun 16, 2014, at 10:39 AM, Paolo Bonzini wrote:
>>>
Il 16/06/2014 18:09, John Nielsen ha scritto:
>>> The only subs
On Tue, Jun 17, 2014 at 06:21:23AM +0200, Paolo Bonzini wrote:
> Il 16/06/2014 18:47, John Nielsen ha scritto:
> >On Jun 16, 2014, at 10:39 AM, Paolo Bonzini wrote:
> >
> >>Il 16/06/2014 18:09, John Nielsen ha scritto:
> >The only substantial difference on the hardware side is the CPU.
> >
Il 16/06/2014 18:47, John Nielsen ha scritto:
On Jun 16, 2014, at 10:39 AM, Paolo Bonzini wrote:
Il 16/06/2014 18:09, John Nielsen ha scritto:
The only substantial difference on the hardware side is the CPU.
The hosts where the problem occurs use "Intel(R) Xeon(R) CPU
E5-2650 v2 @ 2.60GHz", w
16 matches
Mail list logo
