Our virus detector has just been triggered by a message you sent:-
To: go...@erg.abdn.ac.uk
Subject: Mail System Error - Returned Mail
Date: Mon Oct 18 07:27:58 2010
One or more of the attachments are on the list of unacceptable attachments
for this site and will not have been delivered to t
Hello guys:
Any further suggestion which I need to improve those patches?
I agree that there's no much tests need to be run is this way except for
migration. In order to validate the function of migration, many tests need to be
run in parallel with migration and this series is just aimed at this.
On Sun, Oct 17, 2010 at 8:15 PM, Avi Kivity wrote:
> On 10/17/2010 12:14 PM, Dave Young wrote:
>>
>> On Sun, Oct 17, 2010 at 5:34 PM, Avi Kivity wrote:
>> > On 10/17/2010 10:54 AM, Dave Young wrote:
>> >>
>> >> linux guest can not startup normally, qemu keep rebooting.
>> >>
>> >> host&
I am running Ubuntu 10.04 in a VM and the mouse appears frozen. The
keyboard works and CentOS work with both keyboard and mouse. Any
suggestions on how to debug this?
Thanks.
--
Mark Bidewell
http://www.linkedin.com/in/markbidewell
--
To unsubscribe from this list: send the line "unsubscribe k
Ordering by reason makes it easy to group failures and
easily identifying them.
Signed-off-by: Lucas Meneghel Rodrigues
---
scheduler/scheduler_models.py |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/scheduler/scheduler_models.py b/scheduler/scheduler_models.py
index f
This patch creates a convenience KojiDownloader class, that
downloads rpm packages from either brew or koji (the RHEL/Fedora
build systems). This way other parts of the code can benefit
from downloading rpm packages from the build system, such
as the host kernel install code on the control file.
S
When page is swapped in it is mapped into guest memory only after guest
tries to access it again and generate another fault. To save this fault
we can map it immediately since we know that guest is going to access
the page. Do it only when tdp is enabled for now. Shadow paging case is
more complica
On 10/17/2010 12:13 PM, Nadav Har'El wrote:
This patch implements nested_vmx_vmexit(), called when the nested L2 guest
exits and we want to run its L1 parent and let it handle this exit.
Note that this will not necessarily be called on every L2 exit. L0 may decide
to handle a particular exit on
On 10/17/2010 12:12 PM, Nadav Har'El wrote:
Implement the VMLAUNCH and VMRESUME instructions, allowing a guest
hypervisor to run its own guests.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 221 ++-
1 file changed, 218 insertions(+), 3 deletio
On Sun, Oct 17, 2010 at 04:12:35PM +0200, Avi Kivity wrote:
> On 10/17/2010 03:37 PM, Nadav Har'El wrote:
> >On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 10/27] nVMX:
> >Implement VMCLEAR":
> >> Is something preventing you from changing all kmap()s to kmap_atomic()s
> >> (like guest
On 10/17/2010 03:37 PM, Nadav Har'El wrote:
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 10/27] nVMX: Implement
VMCLEAR":
> Is something preventing you from changing all kmap()s to kmap_atomic()s
> (like guest memory access in the mapped section)?
Yes. We've discussed this before
On 10/17/2010 12:11 PM, Nadav Har'El wrote:
This patch contains code to prepare the VMCS which can be used to actually
run the L2 guest, vmcs02. prepare_vmcs02 appropriately merges the information
in vmcs12 (the vmcs that L1 built for L2) and in vmcs01 (the vmcs that we
built for L1).
VMREAD/WR
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 10/27] nVMX: Implement
VMCLEAR":
> Is something preventing you from changing all kmap()s to kmap_atomic()s
> (like guest memory access in the mapped section)?
Yes. We've discussed this before, and I know you suggested other alternatives,
b
On 10/17/2010 02:39 PM, Nadav Har'El wrote:
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 0/24] Nested VMX, v5":
> >patch. In short, try running the L0 kernel with the "nosmp" option,
> What are the problems with smp?
Unfortunately, there appears to be a bug which causes KVM with n
On 10/17/2010 03:18 PM, Nadav Har'El wrote:
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 05/27] nVMX: Introduce
vmcs12: a VMCS structure for L1":
> >+ if(to_vmx(vcpu)->nested.current_vmptr != -1ull){
>
> Missing whitespace after if and before {.
Sorry about that - I forgot to
On 10/17/2010 03:25 PM, Nadav Har'El wrote:
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 10/27] nVMX: Implement
VMCLEAR":
> >+ vmcs12 = kmap(page);
>
> kmap_atomic() please (better, kvm_write_guest(), but can defer that for
> later)
Sorry about my ignorance, but why is kmap_
On 10/17/2010 12:10 PM, Nadav Har'El wrote:
Implement the VMREAD and VMWRITE instructions. With these instructions, L1
can read and write to the VMCS it is holding. The values are read or written
to the fields of the vmcs_fields structure introduced in the previous patch.
+
+static inline bool
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 10/27] nVMX: Implement
VMCLEAR":
> >+vmcs12 = kmap(page);
>
> kmap_atomic() please (better, kvm_write_guest(), but can defer that for
> later)
Sorry about my ignorance, but why is kmap_atomic() better here than kmap()?
While handling
Hi,
when using dmix as an ALSA output, the output cannot be polled and
ALSA (snd_pcm_poll_descriptors) returns the event mask set to POLLIN
instead. As this event mask is passed to the main loop, the select()
in main_loop_wait() never waits, because the output file descriptor is
never read. So, qe
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 05/27] nVMX: Introduce
vmcs12: a VMCS structure for L1":
> >+if(to_vmx(vcpu)->nested.current_vmptr != -1ull){
>
> Missing whitespace after if and before {.
Sorry about that - I forgot to run checkpatch.pl on this iteration.
I now fixed
On 10/17/2010 12:10 PM, Nadav Har'El wrote:
In this patch we add to vmcs12 (the VMCS that L1 keeps for L2) all the
standard VMCS fields. These fields are encapsulated in a struct vmcs_fields.
Later patches will enable L1 to read and write these fields using VMREAD/
VMWRITE, and they will be use
On 10/17/2010 12:05 PM, Nadav Har'El wrote:
This patch allows a guest to use the VMXON and VMXOFF instructions, and
emulates them accordingly. Basically this amounts to checking some
prerequisites, and then remembering whether the guest has enabled or disabled
VMX operation.
Please add a TODO
On 10/17/2010 12:08 PM, Nadav Har'El wrote:
This patch implements the VMCLEAR instruction.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 62 ++-
1 file changed, 61 insertions(+), 1 deletion(-)
--- .before/arch/x86/kvm/vmx.c 2010-10-17 11:52:
On 10/17/2010 12:07 PM, Nadav Har'El wrote:
In this patch we add a list of L0 (hardware) VMCSs, which we'll use to hold a
hardware VMCS for each active vmcs12 (i.e., for each L2 guest).
We call each of these L0 VMCSs a "vmcs02", as it is the VMCS that L0 uses
to run its nested guest L2.
+
+/*
On 10/17/2010 12:06 PM, Nadav Har'El wrote:
When the guest can use VMX instructions (when the "nested" module option is
on), it should also be able to read and write VMX MSRs, e.g., to query about
VMX capabilities. This patch adds this support.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 03/27] nVMX: Implement
VMXON and VMXOFF":
> >+static int handle_vmon(struct kvm_vcpu *vcpu)
>..
> >+if (!nested ||
>
> Is the !nested case needed? Presumably cr4.vmxe will be clear is !nested.
Right - I just added this as a redundant
On Sun, Oct 17, 2010, Avi Kivity wrote about "Re: [PATCH 0/24] Nested VMX, v5":
> >patch. In short, try running the L0 kernel with the "nosmp" option,
> What are the problems with smp?
Unfortunately, there appears to be a bug which causes KVM with nested VMX to
hang when SMP is enabled, even if yo
On 10/17/2010 12:06 PM, Nadav Har'El wrote:
An implementation of VMX needs to define a VMCS structure. This structure
is kept in guest memory, but is opaque to the guest (who can only read or
write it with VMX instructions).
This patch starts to define the VMCS structure which our nested VMX
im
On 10/17/2010 12:05 PM, Nadav Har'El wrote:
This patch allows the guest to enable the VMXE bit in CR4, which is a
prerequisite to running VMXON.
Whether to allow setting the VMXE bit now depends on the architecture (svm
or vmx), so its checking has moved to kvm_x86_ops->set_cr4(). This function
On 10/17/2010 12:05 PM, Nadav Har'El wrote:
This patch allows a guest to use the VMXON and VMXOFF instructions, and
emulates them accordingly. Basically this amounts to checking some
prerequisites, and then remembering whether the guest has enabled or disabled
VMX operation.
+/*
+ * Emulate th
On 10/17/2010 12:14 PM, Dave Young wrote:
On Sun, Oct 17, 2010 at 5:34 PM, Avi Kivity wrote:
>On 10/17/2010 10:54 AM, Dave Young wrote:
>>
>> linux guest can not startup normally, qemu keep rebooting.
>>
>> host&guest both use linux-2.6.36-rc8+ kernel
>>
>> Add a dump_stack in x86.c
On 10/17/2010 02:03 PM, Nadav Har'El wrote:
On Tue, Jun 15, 2010, Avi Kivity wrote about "Re: [PATCH 0/24] Nested VMX, v5":
> I've tried to test the patches, but I see a vm-entry failure code 7 on
> the very first vmentry. Guest is Fedora 12 x86-64 (2.6.32.9-70.fc12).
Hi, as you can see, I p
On Tue, Jun 15, 2010, Avi Kivity wrote about "Re: [PATCH 0/24] Nested VMX, v5":
> I've tried to test the patches, but I see a vm-entry failure code 7 on
> the very first vmentry. Guest is Fedora 12 x86-64 (2.6.32.9-70.fc12).
Hi, as you can see, I posted a new set of patches, which apply to the c
On 10/17/2010 12:33 PM, Avi Kivity wrote:
On 10/14/2010 11:22 AM, Gleb Natapov wrote:
When page is swapped in it is mapped into guest memory only after guest
tries to access it again and generate another fault. To save this fault
we can map it immediately since we know that guest is going to a
On 10/14/2010 11:22 AM, Gleb Natapov wrote:
When page is swapped in it is mapped into guest memory only after guest
tries to access it again and generate another fault. To save this fault
we can map it immediately since we know that guest is going to access
the page. Do it only when tdp is enabl
This patch includes a brief introduction to the nested vmx feature in the
Documentation/kvm directory. The document also includes a copy of the
vmcs12 structure, as requested by Avi Kivity.
Signed-off-by: Nadav Har'El
---
Documentation/kvm/nested-vmx.txt | 237 +
1 f
Small corrections of KVM (spelling, etc.) not directly related to nested VMX.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- .before/arch/x86/kvm/vmx.c 2010-10-17 11:52:03.0 +0200
+++ .after/arch/x86/kvm/vmx.c 2010-10-1
In the unlikely case that L1 does not capture MSR_IA32_TSC, L0 needs to
emulate this MSR write by L2 by modifying vmcs02.tsc_offset.
We also need to set vmcs12.tsc_offset, for this change to survive the next
nested entry (see prepare_vmcs02()).
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c
KVM's "Lazy FPU loading" means that sometimes L0 needs to set CR0.TS, even
if a guest didn't set it. Moreover, L0 must also trap CR0.TS changes and
NM exceptions, even if we have a guest hypervisor (L1) who didn't want these
traps. And of course, conversely: If L1 wanted to trap these events, we
mu
This patch adds correct handling of IDT_VECTORING_INFO_FIELD for the nested
case.
When a guest exits while handling an interrupt or exception, we get this
information in IDT_VECTORING_INFO_FIELD in the VMCS. When L2 exits to L1,
there's nothing we need to do, because L1 will see this field in vmcs
When KVM wants to inject an interrupt, the guest should think a real interrupt
has happened. Normally (in the non-nested case) this means checking that the
guest doesn't block interrupts (and if it does, inject when it doesn't - using
the "interrupt window" VMX mechanism), and setting up the approp
Similar to the previous patch, but concerning injection of exceptions rather
than external interrupts.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 26 ++
1 file changed, 26 insertions(+)
--- .before/arch/x86/kvm/vmx.c 2010-10-17 11:52:02.0 +0200
+++ .
On Sun, Oct 17, 2010 at 5:34 PM, Avi Kivity wrote:
> On 10/17/2010 10:54 AM, Dave Young wrote:
>>
>> linux guest can not startup normally, qemu keep rebooting.
>>
>> host& guest both use linux-2.6.36-rc8+ kernel
>>
>> Add a dump_stack in x86.c around EXIT_SHUTDOWN code, I got:
>> [ 3924.503041]
This patch contains the logic of whether an L2 exit should be handled by L0
and then L2 should be resumed, or whether L1 should be run to handle this
exit (using the nested_vmx_vmexit() function of the previous patch).
The basic idea is to let L1 handle the exit only if it actually asked to
trap t
This patch implements nested_vmx_vmexit(), called when the nested L2 guest
exits and we want to run its L1 parent and let it handle this exit.
Note that this will not necessarily be called on every L2 exit. L0 may decide
to handle a particular exit on its own, without L1's involvement; In that
cas
Before nested VMX support, the exit handler for a guest executing a VMX
instruction (vmclear, vmlaunch, vmptrld, vmptrst, vmread, vmread, vmresume,
vmwrite, vmon, vmoff), was handle_vmx_insn(). This handler simply threw a #UD
exception. Now that all these exit reasons are properly handled (and emul
Implement the VMLAUNCH and VMRESUME instructions, allowing a guest
hypervisor to run its own guests.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 221 ++-
1 file changed, 218 insertions(+), 3 deletions(-)
--- .before/arch/x86/kvm/vmx.c 2010-10-1
Move code that syncs dirty RSP and RIP registers back to the VMCS, into a
function. We will need to call this function from additional places in the
next patch.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
--- .befor
This patch contains code to prepare the VMCS which can be used to actually
run the L2 guest, vmcs02. prepare_vmcs02 appropriately merges the information
in vmcs12 (the vmcs that L1 built for L2) and in vmcs01 (the vmcs that we
built for L1).
VMREAD/WRITE can only access one VMCS at a time (the "cu
Implement the VMREAD and VMWRITE instructions. With these instructions, L1
can read and write to the VMCS it is holding. The values are read or written
to the fields of the vmcs_fields structure introduced in the previous patch.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 171 +
In this patch we add to vmcs12 (the VMCS that L1 keeps for L2) all the
standard VMCS fields. These fields are encapsulated in a struct vmcs_fields.
Later patches will enable L1 to read and write these fields using VMREAD/
VMWRITE, and they will be used during a VMLAUNCH/VMRESUME in preparing vmcs0
This patch implements the VMPTRST instruction.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 27 ++-
arch/x86/kvm/x86.c |3 ++-
arch/x86/kvm/x86.h |3 +++
3 files changed, 31 insertions(+), 2 deletions(-)
--- .before/arch/x86/kvm/x86.c 2010-10-17 11:52
This patch implements the VMPTRLD instruction.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 64 ++-
1 file changed, 63 insertions(+), 1 deletion(-)
--- .before/arch/x86/kvm/vmx.c 2010-10-17 11:52:01.0 +0200
+++ .after/arch/x86/kvm/vmx.c
This patch implements the VMCLEAR instruction.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 62 ++-
1 file changed, 61 insertions(+), 1 deletion(-)
--- .before/arch/x86/kvm/vmx.c 2010-10-17 11:52:01.0 +0200
+++ .after/arch/x86/kvm/vmx.c
VMX instructions specify success or failure by setting certain RFLAGS bits.
This patch contains common functions to do this, and they will be used in
the following patches which emulate the various VMX instructions.
Signed-off-by: Nadav Har'El
---
arch/x86/include/asm/vmx.h | 31 ++
In this patch we add a list of L0 (hardware) VMCSs, which we'll use to hold a
hardware VMCS for each active vmcs12 (i.e., for each L2 guest).
We call each of these L0 VMCSs a "vmcs02", as it is the VMCS that L0 uses
to run its nested guest L2.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c
This patch includes a utility function for decoding pointer operands of VMX
instructions issued by L1 (a guest hypervisor)
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 59 +++
arch/x86/kvm/x86.c |3 +-
arch/x86/kvm/x86.h |3 ++
3 files ch
When the guest can use VMX instructions (when the "nested" module option is
on), it should also be able to read and write VMX MSRs, e.g., to query about
VMX capabilities. This patch adds this support.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 117 +
This patch allows the guest to enable the VMXE bit in CR4, which is a
prerequisite to running VMXON.
Whether to allow setting the VMXE bit now depends on the architecture (svm
or vmx), so its checking has moved to kvm_x86_ops->set_cr4(). This function
now returns an int: If kvm_x86_ops->set_cr4()
An implementation of VMX needs to define a VMCS structure. This structure
is kept in guest memory, but is opaque to the guest (who can only read or
write it with VMX instructions).
This patch starts to define the VMCS structure which our nested VMX
implementation will present to L1. We call it "vm
This patch allows a guest to use the VMXON and VMXOFF instructions, and
emulates them accordingly. Basically this amounts to checking some
prerequisites, and then remembering whether the guest has enabled or disabled
VMX operation.
Signed-off-by: Nadav Har'El
---
arch/x86/kvm/vmx.c | 102 ++
If the "nested" module option is enabled, add the "VMX" CPU feature to the
list of CPU features KVM advertises with the KVM_GET_SUPPORTED_CPUID ioctl.
Qemu uses this ioctl, and intersects KVM's list with its own list of desired
cpu features (depending on the -cpu option given to qemu) to determine
This patch adds a module option "nested" to vmx.c, which controls whether
the guest can use VMX instructions, i.e., whether we allow nested
virtualization. A similar, but separate, option already exists for the
SVM module.
This option currently defaults to 0, meaning that nested VMX must be
explic
Hi,
About three months have passed since my previous (v5) nested VMX patch set,
and it can no longer be applied cleanly to the current KVM trunk.
This version of the patches can be applied to the current trunk, and addresses
dozens of concerns that have been raised by Avi Kivity, Marcelo Tosatti,
On 10/17/2010 10:54 AM, Dave Young wrote:
linux guest can not startup normally, qemu keep rebooting.
host& guest both use linux-2.6.36-rc8+ kernel
Add a dump_stack in x86.c around EXIT_SHUTDOWN code, I got:
[ 3924.503041] Pid: 1685, comm: qemu-system-x86 Not tainted 2.6.36-rc8+ #62
[ 3924.503
On 10/11/2010 08:31 PM, Marcelo Tosatti wrote:
Port qemu-kvm's KVM MCE (Machine Check Exception) handling to qemu. It
allows qemu to propagate MCEs to the guest.
v2:
- rename do_qemu_ram_addr_from_host.
- fix kvm_on_sigbus/kvm_on_sigbus_vcpu naming.
- fix bank register restoration (Dean Nelson)
On Sun, Oct 17, 2010 at 4:54 PM, Dave Young wrote:
> linux guest can not startup normally, qemu keep rebooting.
>
> host & guest both use linux-2.6.36-rc8+ kernel
BTW, qemu cmdline with -kernel will more likely trigger this bug
>
> Add a dump_stack in x86.c around EXIT_SHUTDOWN code, I got:
> [
linux guest can not startup normally, qemu keep rebooting.
host & guest both use linux-2.6.36-rc8+ kernel
Add a dump_stack in x86.c around EXIT_SHUTDOWN code, I got:
[ 3924.503041] Pid: 1685, comm: qemu-system-x86 Not tainted 2.6.36-rc8+ #62
[ 3924.503045] Call Trace:
[ 3924.503055] [] handle_tr
68 matches
Mail list logo
