Leslie Mann wrote:
> kvm-18 has broken use of Cisco VPN client on WinXP SP1 running on a FC6
> 2.6.19-1.2911 client, Intel Core Duo system. I have been running
> successfully from kvm-11 thru kvm-17 without issue. After upgrading to
> kvm-18 any attempts to connect the VPN client result in an
Hollis Blanchard wrote:
> Hi Avi, I was wondering what you think is the right abstraction layer to
> target for porting KVM to non-x86 architectures? To me it looks like
> libkvm is the answer.
>
> The kernel/userland interface is heavily x86-specific, including things
> like struct kvm_run. So it
Li, Shaohua wrote:
> How about take cpu hotplug lock for kvm_vm_ioctl and kvm_vcpu_ioctl?
>
>
That will serialize calls to these functions, and we want parallel
execution of kvm_vcpu_ioctl(). We could make it a reader-writer lock,
but...
I think that adding a
raw_notifier_call_chain(&c
kvm-18 has broken use of Cisco VPN client on WinXP SP1 running on a FC6
2.6.19-1.2911 client, Intel Core Duo system. I have been running
successfully from kvm-11 thru kvm-17 without issue. After upgrading to
kvm-18 any attempts to connect the VPN client result in an unresponsive
X11 session (
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: Monday, March 26, 2007 6:58 PM
>To: Li, Shaohua
>Cc: kvm-devel; Andrew Morton
>Subject: Re: [PATCH] KVM breaks CPU hotplug
>
>Avi Kivity wrote:
>> Shaohua Li wrote:
>>> When testing CPU hotplug, I found cpu can't be on
Hi Avi, I was wondering what you think is the right abstraction layer to
target for porting KVM to non-x86 architectures? To me it looks like
libkvm is the answer.
The kernel/userland interface is heavily x86-specific, including things
like struct kvm_run. So it looks like the higher-level API of
Hi!
Avi Kivity wrote:
> Michael Riepe wrote:
>
>> Avi Kivity wrote:
>>
>>
>>> This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
>>>
>>
>>
>> Well, almost. Knoppix 5.0 and 5.2 work now, but 5.1.1 still hangs with a
>> black framebuffer (no penguin logo) and a load of 100%.
>>
Avi Kivity wrote:
> Shaohua Li wrote:
>> When testing CPU hotplug, I found cpu can't be onlined with kvm enabled
>> sometimes. The reason is smp_call_function_single is a nop if the thread
>> is running on the target cpu. I think CPU_ONLINE case doesn't require
>> the fix as the online CPU isn't pl
BELLEGUEULLE Damien wrote:
>
> ./configure --prefix=/usr --qemu-cc="/usr/bin/gcc-3.3.6"
>
> er -I. -I.. -I/home/bellegueulle/kvm-18/qemu/target-i386
> -I/home/bellegueulle/kvm-18/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D__user= -I/home/bellegueulle/kvm-18/qemu/fpu
> -DHA
./configure --prefix=/usr --qemu-cc="/usr/bin/gcc-3.3.6"
er -I. -I.. -I/home/bellegueulle/kvm-18/qemu/target-i386
-I/home/bellegueulle/kvm-18/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D__user= -I/home/bellegueulle/kvm-18/qemu/fpu -DHAS_AUDIO
-I/home/bellegueulle/kvm-18/qem
Kiselev, Sergey wrote:
> Following patch adds back this functionality:
>
> Signed-off-by: Sergey Kiselev <[EMAIL PROTECTED]>
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
Shaohua Li wrote:
> When testing CPU hotplug, I found cpu can't be onlined with kvm enabled
> sometimes. The reason is smp_call_function_single is a nop if the thread
> is running on the target cpu. I think CPU_ONLINE case doesn't require
> the fix as the online CPU isn't plugged into sheduler yet.
When testing CPU hotplug, I found cpu can't be onlined with kvm enabled
sometimes. The reason is smp_call_function_single is a nop if the thread
is running on the target cpu. I think CPU_ONLINE case doesn't require
the fix as the online CPU isn't plugged into sheduler yet.
Signed-off-by: Shaohua L
13 matches
Mail list logo