This patch sets up multiple TSS for real mode emulation on Intel vmx,
one for each vcpu. This is a preparation patch for full SMP real mode
support.
Signed-off-by: Qing He <[EMAIL PROTECTED]>
kvm.h |1 +
kvm_main.c |1 +
vmx.c | 31 +--
3 files change
He, Qing wrote:
> This patch sets up multiple TSS for real mode emulation on Intel vmx,
> one for each vcpu. This is a preparation patch for full SMP real mode
> support.
>
>
Why are separate tss's needed? Can't all vcpus use the same tss?
> Signed-off-by: Qing He <[EMAIL PROTECTED]>
>
>
> kv
Hello,
I have kvm on FC7. I had installed an FC6 guest on it according to the
kvm howto. I can launch the FC6 guest (using kvm) perfectly ok.
During installation, I set the IP address of the guest to be
192.168.0.11/24 and defualt gw to 192.168.0.1.
These definitions are OK (I simply run "ifconfi
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年7月12日 16:16
>To: He, Qing
>Cc: kvm-devel
>Subject: Re: [kvm-devel] [PATCH] SMP: Setup multiple tss for real mode
>emulation
>
>He, Qing wrote:
>> This patch sets up multiple TSS for real mode emulation on Intel v
This patch adds a `vcpu_id' field in `struct vcpu', so we can
differentiate BSP and APs without pointer comparison or arithmetic.
Signed-off-by: Qing He <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 65ab268..0f7a4d9 100644
--- a/drivers/kvm/kvm.h
+++ b/drivers/kvm
On Thu, 2007-07-12 at 13:33 +0800, Dong, Eddie wrote:
> Here is the update with adding HLT cap.
Thats a good start, but you probably need to make the decision to use
the halt predicated on a halt-specific boolean set by userspace in order
to actually function as we've discussed. This is in contra
He, Qing wrote:
> This patch adds a `vcpu_id' field in `struct vcpu', so we can
> differentiate BSP and APs without pointer comparison or arithmetic.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
Dong, Eddie wrote:
> Here is the update with adding HLT cap.
>
>
> diff --git a/drivers/kvm/i8259.c b/drivers/kvm/i8259.c
> index f4ae5f7..e84e665 100644
> --- a/drivers/kvm/i8259.c
> +++ b/drivers/kvm/i8259.c
> @@ -411,8 +411,13 @@ static void picdev_read(struct kvm_io_device *this,
> static void
Gregory Haskins wrote:
> On Thu, 2007-07-12 at 13:33 +0800, Dong, Eddie wrote:
>
>> Here is the update with adding HLT cap.
>>
>
> Thats a good start, but you probably need to make the decision to use
> the halt predicated on a halt-specific boolean set by userspace in order
> to actually f
Well, I really wanted to have guest smp in the release, but alas, it was
not to be. It still doesn't like starting X, for example.
Note: on i386 the qemu binary is now named qemu-system-x86_64. This is
to allow migration from 32-bit hosts to 64-bit hosts, and to allow
32-bit userspace on a 64
On 7/12/07, David Shwatrz <[EMAIL PROTECTED]> wrote:
> I have kvm on FC7. I had installed an FC6 guest on it according to the
> kvm howto. I can launch the FC6 guest (using kvm) perfectly ok.
> During installation, I set the IP address of the guest to be
> 192.168.0.11/24 and defualt gw to 192.168
I just tried out the latest release but it won't compile. The compiler
complains first:
WARNING: "sigprocmask" [/root/kvm/kvm-29/kernel/kvm.ko] undefined!
and after several other messages:
make[3]: *** [/root/kvm/kvm-29/kernel/kvm-amd.mod.o] Error 1
make[2]: *** [modules] Error 2
make[1]: *** [
Adrian Lambeck wrote:
> I just tried out the latest release but it won't compile. The compiler
> complains first:
>
> WARNING: "sigprocmask" [/root/kvm/kvm-29/kernel/kvm.ko] undefined!
>
>
What kernel are you compiling against?
--
error compiling committee.c: too many arguments to function
Hello,
I know this is not probably the place, but as I haven't found a
kvm-users list and probably some of you have encountered the same problem I feel
it's the best place to post my problem. I have a macbook pro running Feisty
with a Radeon Mobility X1600 and VMX cpu support and I was qui
Víctor Abeytua García wrote:
> Hello,
> I know this is not probably the place, but as I haven't found a
> kvm-users list and probably some of you have encountered the same problem I
> feel
> it's the best place to post my problem. I have a macbook pro running Feisty
> with a Radeon Mobility
Thanks;
I am not sure I got you !
running "ifconfig -a " on the host shows the following:
eth0 Link encap:Ethernet HWaddr 00:1B:24:1D:EC:C0
inet addr:192.168.0.31 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:24ff:fe1d:ecc0/64 Scope:Link
UP BROAD
Thanks a lot,
I was looking at the wrong place. I was trying to launch the
installation as root after sudoing. And as root I didn't have the DISPLAY
variable. Now the installation is proceeding smoothly.
Best regards,
Víctor
Thu, Jul 12, 2007 at 03:03:05PM +0300, Avi Kivit
Hello,
And I just want to add some info :
running :
"brctl show"
gives:
bridge name bridge id STP enabled interfaces
virbr0 8000. no
which means that there is no interface enslaved to this bridge.
Regards,
DS
On 7/12/07, David Shwatrz <[EMAI
I had the same problem, I missed couple of SDL packages...
here is my package list under debian :
ii libsdl1.2-dev
1.2.11-8Simple DirectMedia Layer development
files
ii libsdl1.2debian
1.2.11-8Sim
Avi Kivity wrote:
> Dong, Eddie wrote:
>> Here is the update with adding HLT cap.
>>
>>
>> diff --git a/drivers/kvm/i8259.c b/drivers/kvm/i8259.c index
>> f4ae5f7..e84e665 100644 --- a/drivers/kvm/i8259.c
>> +++ b/drivers/kvm/i8259.c
>> @@ -411,8 +411,13 @@ static void picdev_read(struct kvm_io_d
On Thu, 2007-07-12 at 22:20 +0800, Dong, Eddie wrote:
> Apply to current kvm.git? Then we need to define false for
> irqchip_in_kernel() which makes the patch quit stranger.
I think what Avi is saying is this can be generalized as a separate
feature independent of in-kernel-PIC. Since Avi and I
Dong, Eddie wrote:
> Gregory Haskins wrote:
>
>> On Thu, 2007-07-12 at 22:20 +0800, Dong, Eddie wrote:
>>
>>
>>
>>> Apply to current kvm.git? Then we need to define false for
>>> irqchip_in_kernel() which makes the patch quit stranger.
>>>
>> I think what Avi is saying is this can be
QEMU-KVM has a bug where the interruptibility of the CPU is predicated on
pending interrupts. If the reason that a CPU is interrupted is because we
need to inject interrupts, the current code will just keep looping and miss
the event window.
This doesnt seem to cause problems with in-trunk KVM.
Gregory Haskins wrote:
> On Thu, 2007-07-12 at 22:20 +0800, Dong, Eddie wrote:
>
>
>> Apply to current kvm.git? Then we need to define false for
>> irqchip_in_kernel() which makes the patch quit stranger.
>
> I think what Avi is saying is this can be generalized as a separate
> feature independe
Avi Kivity wrote:
> Dong, Eddie wrote:
>> Gregory Haskins wrote:
>>
>>> On Thu, 2007-07-12 at 22:20 +0800, Dong, Eddie wrote:
>>>
>>>
>>>
Apply to current kvm.git? Then we need to define false for
irqchip_in_kernel() which makes the patch quit stranger.
>>> I think what Avi is s
On Thu, 2007-07-12 at 23:39 +0800, Dong, Eddie wrote:
> Greg:
> I think you need to do the whole patch for this including kernel
> side. Will u ?
Ya, I can do that. But I probably wont be able to look at it until this
RT stuff I am working on is done.
-Greg
---
Greg:
I think you need to do the whole patch for this including kernel
side. Will u ?
eddie
Gregory Haskins wrote:
> QEMU-KVM has a bug where the interruptibility of the CPU is
> predicated on pending interrupts. If the reason that a CPU is
> interrupted
> is because we
> need to inject
Gregory Haskins wrote:
> On Thu, 2007-07-12 at 23:39 +0800, Dong, Eddie wrote:
>> Greg:
>> I think you need to do the whole patch for this including kernel
>> side. Will u ?
>
> Ya, I can do that. But I probably wont be able to look at it until
> this RT stuff I am working on is done.
>
The
On Thu, 2007-07-12 at 08:37 +0300, Avi Kivity wrote:
> Can you confirm it by backing out that one patch?
Do you know the git commit id by chance?
-- Dave
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express
(don't top post)
Il Thu, Jul 12, 2007 at 03:56:07PM +0300, David Shwatrz ha scritto:
> Hello,
> And I just want to add some info :
>
> running :
> "brctl show"
>
> gives:
> bridge name bridge id STP enabled interfaces
> virbr0 8000. no
>
> which
Avi,
A couple of months back, we had a discussion about PMU virtualization
and the difficulty I encountered trying to catch the PMU interrupt
vector in kvm on VM-exit. KVM does not set ack_intr_on_intr. Would
you mind reminding me of the reason for this?
On the topic of scheduler hooks for use by
The same error happens on linux-2.6.21.4:
I am using the same config as on 2.6.20 which worked well with kvm-28...
#
Output when compiling:
WARNING: "sigprocmask" [/root/kvm/kvm-29/kernel/kvm.ko] undefined!
WARNING: "kmem_cache_destroy" [/root/kvm/kvm-29/kernel/kv
[EMAIL PROTECTED] wrote:
> Avi,
>
> A couple of months back, we had a discussion about PMU virtualization
> and the difficulty I encountered trying to catch the PMU interrupt
> vector in kvm on VM-exit. KVM does not set ack_intr_on_intr. Would
> you mind reminding me of the reason for this?
>
> O
On 7/12/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
repository: /home/avi/kvm
branch: master
commit ebad9f20e60405fbf01beea7521c8a764391dece
Author: Avi Kivity <[EMAIL PROTECTED]>
Date: Thu Jul 12 13:20:47 2007 +0300
kvm: external module: rename original kernel's modules when installing
Eddie,
On Fri, Jul 13, 2007 at 08:46:06AM +0800, Dong, Eddie wrote:
> [EMAIL PROTECTED] wrote:
> > Avi,
> >
> > A couple of months back, we had a discussion about PMU virtualization
> > and the difficulty I encountered trying to catch the PMU interrupt
> > vector in kvm on VM-exit. KVM does not s
Stephane Eranian wrote:
> Eddie,
>
> On Fri, Jul 13, 2007 at 08:46:06AM +0800, Dong, Eddie wrote:
>> [EMAIL PROTECTED] wrote:
>>> Avi,
>>>
>>> A couple of months back, we had a discussion about PMU
>>> virtualization and the difficulty I encountered trying to catch the
>>> PMU interrupt vector in
Stephane Eranian wrote:
> Avi,
>
> A couple of months back, we had a discussion about PMU virtualization
> and the difficulty I encountered trying to catch the PMU interrupt
> vector in kvm on VM-exit. KVM does not set ack_intr_on_intr. Would
> you mind reminding me of the reason for this?
>
>
37 matches
Mail list logo
