From: Heiko Carstens heiko.carst...@de.ibm.com
arch/s390/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_create_vm':
arch/s390/kvm/../../../virt/kvm/kvm_main.c:409: warning: label 'out_err'
defined but not used
Signed-off-by: Heiko Carstens heiko.carst...@de.ibm.com
---
Adds even more
--
regards
Yang, Sheng
arch/x86/include/asm/kvm_host.h |2 +
arch/x86/include/asm/msr-index.h |1 +
arch/x86/include/asm/msr.h |4 +-
arch/x86/include/asm/vmx.h |1 +
arch/x86/kernel/vsyscall_64.c|3 +-
arch/x86/kvm/svm.c | 13 +++
It's no longer necessary.
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
arch/x86/kvm/vmx.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 9a0a2cf..5c464ed 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@
Also replaced the hardcode value in write_tsc() and write_tscp_aux().
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
(Already applied by Ingo)
arch/x86/include/asm/msr-index.h |1 +
arch/x86/include/asm/msr.h |4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff
shared_msr_global saved host value of relevant MSRs, but it have an
assumption that all MSRs it tracked shared the value across the different
CPUs. It's not true with some MSRs, e.g. MSR_TSC_AUX.
Extend it to per CPU to provide the support of MSR_TSC_AUX, and more
alike MSRs.
Notice now the
KVM need vsyscall_init() to initialize MSR_TSC_AUX before it read the value.
Per Avi's suggestion, this patch raised vsyscall priority on hotplug notifier
chain, to 30.
CC: Ingo Molnar mi...@elte.hu
CC: linux-ker...@vger.kernel.org
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
Sometime, we need to adjust some state in order to reflect guest CPUID
setting, e.g. if we don't expose rdtscp to guest, we won't want to enable
it on hardware. cpuid_update() is introduced for this purpose.
Also export kvm_find_cpuid_entry() for later use.
Signed-off-by: Sheng Yang
Before enabling, execution of rdtscp in guest would result in #UD.
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
arch/x86/include/asm/kvm_host.h |1 +
arch/x86/include/asm/vmx.h |1 +
arch/x86/kvm/svm.c |7
arch/x86/kvm/vmx.c | 60
2009/12/17 Kevin Wolf kw...@redhat.com:
Am 17.12.2009 11:23, schrieb Avi Kivity:
On 12/17/2009 11:38 AM, Kenni Lund wrote:
2009/12/17 Avi Kivitya...@redhat.com:
On 12/17/2009 02:52 AM, Kenni Lund wrote:
Yesterday I entered an invalid boot device as an argument to my
qemu-kvm command for my
On 12/18/2009 04:13 PM, Kenni Lund wrote:
Huh? Backing file? Is that the same as a base image? Eg. a write
protected image on which other images can be based?
Yes.
If so, I'm quite confused...this should be a standalone image created
with a command like qemu-img create -f WindowsXP.img
Am 18.12.2009 15:22, schrieb Avi Kivity:
If so, I'm quite confused...this should be a standalone image created
with a command like qemu-img create -f WindowsXP.img 50G half a year
ago on kvm 8x. I don't use libvirt/virt-manager etc. I start qemu-kvm
directly from a homemade bash script. I
2009/12/18 Avi Kivity a...@redhat.com:
On 12/18/2009 04:13 PM, Kenni Lund wrote:
The '/tmp' was prefixed by qemu-img, the actual path is
'WindowsXP.img.backup', so on your setup qemu-img would look for it in
/data/virtualization/.
If the image needs another image in /tmp/WindowsXP.img.backup
Hello ppl,
as we promised there is a new version with modifications you wanted us
to do. It's complete package based on the newest GIT version.
[Changelog]
- new structure (tests_base.cfg, ...)
- improved log
- function get_stat() raise an error when access death VM
- get_stat() splitted into
* Yolkfull Chow yz...@redhat.com [2009-12-17 22:51]:
Signed-off-by: Yolkfull Chow yz...@redhat.com
---
client/tests/kvm/tests/vnc.py | 24
client/tests/kvm/tests_base.cfg.sample |3 +++
2 files changed, 27 insertions(+), 0 deletions(-)
create mode
* Gregory Haskins gregory.hask...@gmail.com wrote:
Hi Linus,
Please pull AlacrityVM guest support for 2.6.33 from:
git://git.kernel.org/pub/scm/linux/kernel/git/ghaskins/alacrityvm/linux-2.6.git
for-linus
All of these patches have stewed in linux-next for quite a while now:
Gregory
The Buildbot has detected a new failure of default_x86_64_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_debian_5_0/builds/208
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_1
The Buildbot has detected a new failure of default_i386_debian_5_0 on qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_i386_debian_5_0/builds/210
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_2
The Buildbot has detected a new failure of default_x86_64_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_out_of_tree/builds/149
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of default_i386_out_of_tree on qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_i386_out_of_tree/builds/147
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_2
19 matches
Mail list logo
