On 07/06/2010 06:58 PM, BuraphaLinux Server wrote:
I spent the day getting things ready for you to log in, but was amazed
to find you already had a patch ready for testing, which was good
news. I wasn't sure which kernel that was for. I applied it by hand
to 2.6.34.1 and then regenerated the p
On 7/6/10, Avi Kivity wrote:
> On 07/06/2010 10:46 AM, Avi Kivity wrote:
>>
>> I'll investigate further.
>>
>
> Patch posted.
Hello Avi Kitty,
I spent the day getting things ready for you to log in, but was amazed
to find you already had a patch ready for testing, which was good
news. I wasn't
On 07/06/2010 10:46 AM, Avi Kivity wrote:
I'll investigate further.
Patch posted.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at ht
On 07/05/2010 10:42 AM, Avi Kivity wrote:
Please don't top-post.
On 07/03/2010 05:23 PM, BuraphaLinux Server wrote:
Ok, I kept going like you said. Here is what it said:
$git bisect good
44ea2b1758d88ad822e65b1c4c21ca6164494e27 is the first bad commit
commit 44ea2b1758d88ad822e65b1c4c21ca616
On 07/05/2010 11:52 AM, BuraphaLinux Server wrote:
Hello,
Software:
We use a 32bit userland with a 64bit kernel. In the qemu-kvm I
run the same distribution (using 64bit kernel with 32bit userland).
The userland is compiled with gcc-4.4.4, binutils-2.20.51.0.9,
glibc-2.11.2. The kernels
Hello,
Software:
We use a 32bit userland with a 64bit kernel. In the qemu-kvm I
run the same distribution (using 64bit kernel with 32bit userland).
The userland is compiled with gcc-4.4.4, binutils-2.20.51.0.9,
glibc-2.11.2. The kernels are compiled using a crosstool-ng toolchain
generated
Please don't top-post.
On 07/03/2010 05:23 PM, BuraphaLinux Server wrote:
Ok, I kept going like you said. Here is what it said:
$git bisect good
44ea2b1758d88ad822e65b1c4c21ca6164494e27 is the first bad commit
commit 44ea2b1758d88ad822e65b1c4c21ca6164494e27
Author: Avi Kivity
Date: Sun Sep
Ok, I kept going like you said. Here is what it said:
$git bisect good
44ea2b1758d88ad822e65b1c4c21ca6164494e27 is the first bad commit
commit 44ea2b1758d88ad822e65b1c4c21ca6164494e27
Author: Avi Kivity
Date: Sun Sep 6 15:55:37 2009 +0300
KVM: VMX: Move MSR_KERNEL_GS_BASE out of the vmx
On 07/02/2010 10:08 PM, BuraphaLinux Server wrote:
Hello,
I tried my best to do the bisection, and the result after many kernels was:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[3ce672d48400e0112fec7a3cb6bb2120493c6e11] KVM: SVM: init_vmcb():
remove redundant save->cr0 ini
Hello,
I tried my best to do the bisection, and the result after many kernels was:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[3ce672d48400e0112fec7a3cb6bb2120493c6e11] KVM: SVM: init_vmcb():
remove redundant save->cr0 initialization
So what do I do next? I did not 'make m
On 06/30/2010 09:25 PM, BuraphaLinux Server wrote:
Can you downgrade the kernel to a known good one to see which component
causes the failure?
Thank you for your suggestion. Changing only the kernel back to
2.6.32.14 and changing nothing else, the qemu/kvm works well.
However, I want to
On 7/1/10, Anthony Liguori wrote:
> On 06/28/2010 12:28 PM, BuraphaLinux Server wrote:
>> Hello,
>>
>> I have tried qemu_kvm 0.12.4 release and also git from about 1/2
>> an hour ago. In both cases, I crash in the post_kvm_run() function on
>> the line about:
>>
>> pthread_mutex_lock(&qemu_m
On 6/29/10, Avi Kivity wrote:
> On 06/28/2010 08:28 PM, BuraphaLinux Server wrote:
>> Hello,
>>
>> I have tried qemu_kvm 0.12.4 release and also git from about 1/2
>> an hour ago. In both cases, I crash in the post_kvm_run() function on
>> the line about:
>>
>> pthread_mutex_lock(&qemu_mutex
On 06/28/2010 12:28 PM, BuraphaLinux Server wrote:
Hello,
I have tried qemu_kvm 0.12.4 release and also git from about 1/2
an hour ago. In both cases, I crash in the post_kvm_run() function on
the line about:
pthread_mutex_lock(&qemu_mutex);
The command I use to run qemu worked great wit
Reply inline.
On 6/29/10, Brian Jackson wrote:
> On Monday, June 28, 2010 12:28:52 pm BuraphaLinux Server wrote:
>> Hello,
>>
>> I have tried qemu_kvm 0.12.4 release and also git from about 1/2
>> an hour ago. In both cases, I crash in the post_kvm_run() function on
>> the line about:
>>
>>
On 06/28/2010 08:28 PM, BuraphaLinux Server wrote:
Hello,
I have tried qemu_kvm 0.12.4 release and also git from about 1/2
an hour ago. In both cases, I crash in the post_kvm_run() function on
the line about:
pthread_mutex_lock(&qemu_mutex);
The command I use to run qemu worked great wit
On Monday, June 28, 2010 12:28:52 pm BuraphaLinux Server wrote:
> Hello,
>
> I have tried qemu_kvm 0.12.4 release and also git from about 1/2
> an hour ago. In both cases, I crash in the post_kvm_run() function on
> the line about:
>
> pthread_mutex_lock(&qemu_mutex);
>
> The command I use
Hello,
I have tried qemu_kvm 0.12.4 release and also git from about 1/2
an hour ago. In both cases, I crash in the post_kvm_run() function on
the line about:
pthread_mutex_lock(&qemu_mutex);
The command I use to run qemu worked great with
glibc-2.11.1,linux-2.6.32.14,and gcc-4.4.3,
but I ha
18 matches
Mail list logo