Gregory Haskins wrote:
Signed-off-by: Gregory Haskins [EMAIL PROTECTED]
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping
Gregory Haskins wrote:
Signed-off-by: Gregory Haskins [EMAIL PROTECTED]
---
Dropped - I don't see a problem with the current code.
--
error compiling committee.c: too many arguments to function
-
This SF.net email
Rusty Russell wrote:
Dynamically allocate vcpus
This patch converts the vcpus array in struct kvm to a pointer
array, and changes the vcpu_create and vcpu_setup hooks into one
vcpu_create call which does the allocation and initialization of the
vcpu (calling back into the kvm_vcpu_init core
Alistair John Strachan wrote:
Hi,
I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a digital
photo of the oops. Alarmingly, a lot of the time it triple faults the machine
and I don't get a chance to grab it. This time I was lucky, though.
Yang, Sheng wrote:
Put cpu feature detecting part in hardware_setup, and stored the vmcs
condition in global variable for further check.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
Ben Budts wrote:
Hi,
I've been running kvm21 for a long time (just upgraded to kvm-33 with
2.6.22.1)
I have a 60GB qcow2 image, I noticed the image was growing without me
installing software on the guest os...(WIN XP)
When I select all my files and take properties (in win xp that is),
On Sunday 29 July 2007 09:16:43 Avi Kivity wrote:
Alistair John Strachan wrote:
Hi,
I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a
digital photo of the oops. Alarmingly, a lot of the time it triple faults
the machine and I don't get a chance to grab it. This time I
Alistair John Strachan wrote:
On Sunday 29 July 2007 09:16:43 Avi Kivity wrote:
Alistair John Strachan wrote:
Hi,
I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a
digital photo of the oops. Alarmingly, a lot of the time it triple faults
the machine and I don't
On 7/26/07, Ben Budts [EMAIL PROTECTED] wrote:
When I select all my files and take properties (in win xp that is), it says
3.7GB, as expected...
The image is allmost the double though (6.4GB) when i look at the qcow2 image,
when taking the properties of the HD in win xp it also indictates
Alistair John Strachan wrote:
On Sunday 29 July 2007 12:34:28 you wrote:
[snip]
Doesn't help, I still get the same crashes. I tried 2.6.22 again and it's
rock solid by comparison.
Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
Please describe your
On Sunday 29 July 2007 12:34:28 you wrote:
[snip]
Doesn't help, I still get the same crashes. I tried 2.6.22 again and it's
rock solid by comparison.
Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
Please describe your configuration *exactly*.
I'm using the kvm-33
On Sunday 29 July 2007 14:47:57 you wrote:
Alistair John Strachan wrote:
On Sunday 29 July 2007 12:34:28 you wrote:
[snip]
Doesn't help, I still get the same crashes. I tried 2.6.22 again and
it's rock solid by comparison.
Do you mean, kvm-33 on top of 2.6.22, or the kvm modules
All the physical CPUs on the board should support the same VMX feature
set.
The hardware_enable() do the per-cpu check now.
In case of vmx/svm enabling failure, transfer a variable in
hardware_enable()
for error report.
Signed-off-by: Sheng Yang [EMAIL PROTECTED]
---
drivers/kvm/kvm_main.c |
Hi Avi, hi all,
I've started some (very minor) groundwork for this task. My idea was
to add an extra annotation field in qcow2 snapshots. In this way, a
snapshot can hold abitrary information; for example, command line
arguments.
Before going any further, I wanted to validate the general idea
14 matches
Mail list logo
