Am 10.02.2015 um 11:50 schrieb Marcelo Tosatti:
On Tue, Feb 10, 2015 at 10:26:33AM +0100, Peter Lieven wrote:
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion that
seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in
On 10/02/2015 14:58, Peter Lieven wrote:
Yes, but it is still not ready. It only works with 3.18 and 3.16.
Okay, but for testing I will use 3.19 with the patch for testing if the
assertion disappears?!
If you use 3.19 in the host, you don't need kvm-kmod.
If you use 3.19 with kvm-kmod,
On 10/02/2015 11:03, Peter Lieven wrote:
My hope was that anyone has observed this post 2.2.0 already and there
is a fix available ;-)
Can you indicate what info would be helpful debugging this?
Cmdline is:
/usr/bin/qemu-2.2.0 -enable-kvm -M pc-i440fx-2.1 -nodefaults -netdev
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion that
seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in a serious
amount of cases. In most cases it works flawlessly on the second attempt to
migrate the vServer
(same
On 10/02/2015 10:26, Peter Lieven wrote:
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following
assertion that seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in a serious
amount of cases. In most cases it works flawlessly on
Am 10.02.2015 um 11:17 schrieb Paolo Bonzini:
On 10/02/2015 11:03, Peter Lieven wrote:
My hope was that anyone has observed this post 2.2.0 already and there
is a fix available ;-)
Can you indicate what info would be helpful debugging this?
Cmdline is:
/usr/bin/qemu-2.2.0 -enable-kvm -M
On 10/02/2015 11:24, Peter Lieven wrote:
First of all (but unrelated to the bug) do not use -cpu qemu64 with
KVM.
I remember there was an issue with kvm64 anytime in the past, but this
is ages ago I think. I will change that for new vserver starts. What
(which flag) is the exact issue
Am 10.02.2015 um 11:25 schrieb Paolo Bonzini:
On 10/02/2015 11:24, Peter Lieven wrote:
First of all (but unrelated to the bug) do not use -cpu qemu64 with
KVM.
I remember there was an issue with kvm64 anytime in the past, but this
is ages ago I think. I will change that for new vserver
On Tue, Feb 10, 2015 at 10:26:33AM +0100, Peter Lieven wrote:
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion
that seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in a serious
amount of cases. In most cases it
Am 10.02.2015 um 10:49 schrieb Paolo Bonzini:
On 10/02/2015 10:26, Peter Lieven wrote:
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following
assertion that seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in a serious
amount of
Am 10.02.2015 um 11:17 schrieb Paolo Bonzini:
On 10/02/2015 11:03, Peter Lieven wrote:
My hope was that anyone has observed this post 2.2.0 already and there
is a fix available ;-)
Can you indicate what info would be helpful debugging this?
Cmdline is:
/usr/bin/qemu-2.2.0 -enable-kvm -M
On 10/02/2015 11:30, Peter Lieven wrote:
QEMU64 does not resemble any actual processor. You want the lowest
denominator of your cluster, probably Nehalem.
Ah okay. Normally, I compare the available cpu flags of my cluster
and pass those flags individually. Maybe I have to revisit that
Am 10.02.2015 um 14:15 schrieb Paolo Bonzini:
On 10/02/2015 13:56, Peter Lieven wrote:
Ahem, 3.19 was released last Sunday. Give us some breathing room...
I missed the next branch. I checked that out and updated the submodule
to commit bfa76d49576599a4b9f9b7a71f23d73d6dcff735.
Does that
On 10/02/2015 14:31, Peter Lieven wrote:
Yes, but it is still not ready. It only works with 3.18 and 3.16.
Okay, but for testing I will use 3.19 with the patch for testing if the
assertion disappears?!
If you use 3.19 in the host, you don't need kvm-kmod.
If you use 3.19 with kvm-kmod,
Am 10.02.2015 um 14:40 schrieb Paolo Bonzini:
On 10/02/2015 14:31, Peter Lieven wrote:
Yes, but it is still not ready. It only works with 3.18 and 3.16.
Okay, but for testing I will use 3.19 with the patch for testing if the
assertion disappears?!
If you use 3.19 in the host, you don't need
On 10/02/2015 13:56, Peter Lieven wrote:
Ahem, 3.19 was released last Sunday. Give us some breathing room...
I missed the next branch. I checked that out and updated the submodule
to commit bfa76d49576599a4b9f9b7a71f23d73d6dcff735.
Does that make sense?
Yes, but it is still not ready.
Am 10.02.2015 um 11:50 schrieb Marcelo Tosatti:
On Tue, Feb 10, 2015 at 10:26:33AM +0100, Peter Lieven wrote:
Hi,
while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion that
seems to have
been introduced between 2.1.0 and 2.2.0 trigger on the destination. This
happens in
On 10/02/2015 13:17, Peter Lieven wrote:
I have build my kvm module from
http://git.kiszka.org/?p=kvm-kmod.git
but it seems not to have been updates since October.
The patch is not in there.
Is that repository not up to date anymore?
Ahem, 3.19 was released last Sunday. Give us
Am 10.02.2015 um 13:35 schrieb Paolo Bonzini:
On 10/02/2015 13:17, Peter Lieven wrote:
I have build my kvm module from
http://git.kiszka.org/?p=kvm-kmod.git
but it seems not to have been updates since October.
The patch is not in there.
Is that repository not up to date anymore?
Ahem, 3.19
19 matches
Mail list logo
