On 09/10/2009 02:10 AM, Daniel Gollub wrote:
qemu-kvm --disable-kvm build regression of commit 8c7d4cb spotted by
qemu-kvm buildbot:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_debian_5_0/builds/44
The Buildbot has detected a new failure of disable_kvm_i386_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_debian_5_0/builds/47
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
Fix warnings with USE_KVM_DEVICE_ASSIGNMENT disabled, spotted by buildbot:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_debian_5_0/builds/55/steps/compile/logs/warnings
Signed-off-by: Daniel Gollub gol...@b1-systems.de
--
qemu-kvm.c |4
1 files changed, 4
On (Wed) Sep 09 2009 [13:41:59], Amit Shah wrote:
Hello all,
Here is a new iteration of the patch series that implements a
transport for guest and host communications.
I've tested for compatibility (old qemu new kernel, new qemu old
kernel, new qemu new kernel) and it all works
Fixes warning about missing kvm_arch_do_ioperm prototype with
USE_KVM_DEVICE_ASSIGNMENT disabled.
/var/lib/buildbot/qemu-kvm/default_x86_64_debian_5_0/build/qemu-kvm-x86.c:1635:
warning: no previous prototype for 'kvm_arch_do_ioperm'
Patch only build-tested with i386 and x86_64 - not ia64!
In order to prepare for the subsequent changes, made
some cleanups on the kvm source files: I've noticed
that the top level docstrings were going before the
imports block, and that does not follow the pattern
found on other files (my fault). This patch fixes
that problem and fixed some places on
That is no longer necessary since we handle cd keys on
a separate configuration file.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/fix_cdkeys.py | 76
1 files changed, 0 insertions(+), 76 deletions(-)
delete mode 100755
* Renamed BEFORE_YOU_START to README, and point
to the online documentation in there (it's
pointless to duplicate procedures).
* The control file docstring points to the
top level KVM testing documentation.
* The kvm class docstring points to the getting
started guide.
Don't strip binaries on all supported build methods.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/kvm_install.py |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/client/tests/kvm/kvm_install.py b/client/tests/kvm/kvm_install.py
index
Hi,
The following seires add ksm support to the kvm mmu.
Thanks.
--
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 http://vger.kernel.org/majordomo-info.html
this flag notify that the host physical page we are pointing to from
the spte is write protected, and therefore we cant change its access
to be write unless we run get_user_pages(write = 1).
(this is needed for change_pte support in kvm)
Signed-off-by: Izik Eidus iei...@redhat.com
---
this is needed for kvm if it want ksm to directly map pages into its
shadow page tables.
Signed-off-by: Izik Eidus iei...@redhat.com
---
arch/x86/include/asm/kvm_host.h |1 +
arch/x86/kvm/mmu.c | 70 ++
virt/kvm/kvm_main.c | 14
On Fri, Aug 28, 2009 at 09:50:36AM +0300, Avi Kivity wrote:
On 08/28/2009 01:59 AM, Marcelo Tosatti wrote:
On Thu, Aug 27, 2009 at 07:27:48PM +0300, Avi Kivity wrote:
On 08/27/2009 06:54 PM, Marcelo Tosatti wrote:
perf report shows heavy overhead from down/up of slots_lock.
Use random.SystemRandom() (which uses /dev/urandom) in
kvm_utils.generate_random_string().
Currently, when running multiple jobs in parallel, the generated strings
occasionally collide, and this is very bad.
Also, don't seed the random number generator in kvm.py. This is not necessary
and is
used_cpus denotes the number of CPUs required for a test.
used_mem denotes the amount of RAM required for a test.
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_tests.cfg.sample |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git
This patch adds a control.parallel file that runs several test execution queues
in parallel.
The number of queues is set to the number of CPUs reported by /proc/cpuinfo.
It can be changed by modifying the control file.
The total amount of RAM defaults to 3/4 times what 'free -m' reports.
The
16 matches
Mail list logo