This incremental patch fixes the macbook issue for real.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Tested-by: Alex Larsson (sometimes testing helps)
Index: linux-2.6/drivers/kvm
No serious changes from the last release, but a couple of
shoot-self-in-foot bugs have been fixed. After the recent increase in
exposure, it's best to have a stable release out there.
- prevent loading arch module on wrong hardware
- fix for macbooks
- other minor fixes
--
error compiling com
Michael Riepe wrote:
> vmx_get_msr() actually works fine. The problem is in vmx_vcpu_setup(),
> in the loop starting at line 1142. It tries to read all the MSRs listed
> in vmx_msr_index, but it fails for MSR_K6_STAR. With earlier releases, I
> also used to see the kernel message "kvm: msrs: 1" - t
James Morris wrote:
> Consolidate the logic for checking whether a vcpu index is valid. Also,
> use likely(), as a valid value should be the overwhelmingly common case.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
Franco Spinelli wrote:
> I am testing kvm on my new PC
> MB is Asus M2NPV-VM with AMD CPU X2.
> Installed OS is Ubuntu Edgy
>
> I get kvm tarball and compiled it.
>
> After installing gcc 3.4 I begin compile step
>
> On Ubuntu Edgy there is no uuid/uuid.h file so I have grab it from tar
> file at
Franco Spinelli wrote:
Using dmesg command I geta lot of this error:
[17192500.496000] kvm: unhandled rdmsr: 0xc081
The attached patch should fix it (we didn't handle MSR_STAR on 32-bit
AMD hosts)
--
error compiling committee.c: too many arguments to function
Index: kernel/svm.c
==
If you've experienced this problem, please test the attached patch (to
qemu, not the kernel module) and report back. The patch basically tells
the guest that the msr doesn't exist.
--
error compiling committee.c: too many arguments to function
Index: qemu/qemu-kvm.c
==
A cleanup and two AMD SVM fixes (the STAR MSR on 32-bit hosts, and the
floating point unit state on all AMD hosts).
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash. Influence the Fu
From: James Morris <[EMAIL PROTECTED]>
Consolidate the logic for checking whether a vcpu index is valid. Also,
use likely(), as a valid value should be the overwhelmingly common case.
Signed-off-by: James Morris <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]
They're not on speaking terms.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux-2.6.orig/drivers/kvm/svm.c
+++ linux-2.6/drivers/kvm/svm.c
@@ -377,6 +377,7 @@ static
Avi Kivity wrote:
> They're not on speaking terms.
>
>
Please disregard - this patch was already sent. Slippery fingers.
--
error compiling committee.c: too many arguments to function
-
Take Surv
This is necessary for linux guests.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux-2.6.orig/drivers/kvm/svm.c
+++ linux-2.6/drivers/kvm/svm.c
@@ -402,11 +402,11 @@ static __in
Fixes sf bug 1614113 (segfaults in nbench).
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux-2.6.orig/drivers/kvm/svm.c
+++ linux-2.6/drivers/kvm/svm.c
@@ -575,6 +575,8 @@ stat
Michael Riepe wrote:
> Oh well...
>
> I was wondering which stupid piece of sh^H^Hcode generated so many wrong
> rdmsr instructions without looking at the CPU feature flags. So I
> grepped through the linux kernel and glibc sources as well as some other
> likely suspects and found - nothing.
>
> Gu
[EMAIL PROTECTED] wrote:
> Good moorning, I changed the -boot option in 'c' but when my Windows Xp boot
> to complete the installation I got the following errors:
>
> unhandled vm exit: 0x8022
> rax 0800 rbx ffdff120 rcx c080 rdx
>
> rsi 00
Avi Kivity wrote:
Michael Riepe wrote:
Oh well...
I was wondering which stupid piece of sh^H^Hcode generated so many wrong
rdmsr instructions without looking at the CPU feature flags. So I
grepped through the linux kernel and glibc sources as well as some other
likely suspects and found
[EMAIL PROTECTED] wrote:
>
> My cpu model is :
> Intel(R) Pentium(R) D CPU 3.60GHz
>
I have a Intel(R) Pentium(R) D CPU 3.00GHz on one of my boxes. Strange.
--
error compiling committee.c: too many arguments to function
-
[EMAIL PROTECTED] wrote:
I applyed the patch.
Attacched here there is the dmesg output.
Please run the attached program and report output.
Before you run it, run 'modprobe msr' and check you have a /dev/cpu/0/msr.
--
error compiling committee.c: too many arguments to function
#define _FILE_O
[EMAIL PROTECTED] wrote:
>
> I did not understand ... sorry.
> Let me to explain what I am doing...
>
> modprobe -r kvm-intel
> cd kvm-7
> patch kernel/vmx.c your_first_patch_file
> pacth kernel/vmx.c your_second_patch_file
> make
> make install
> modprobe -r kvm-intel
>
> Then I lauch the winxp bo
[EMAIL PROTECTED] wrote:
> OK
> I restored the original vmx.c file and I applyed the second patch but
> wueh I boot winxp no lines are addes in /var/log/messages and dmesg
> produces the following :
>
> kvm: msrs: 6
>
>
How does it crash now?
--
Do not meddle in the internals of kernels, for t
[EMAIL PROTECTED] wrote:
> Now I execute:
>
>
> /usr/local/bin/qemu-system-x86_64 -no-acpi -hda
> /root/winXP/windows_kvm.disk -boot c -m 512
>
>
> On the terminal where I execute the command the following appears:
>
> unhandled vm exit: 0x8022
> rax 0800 rbx ffdff120 rcx
Michael Riepe wrote:
> Hi!
>
> I found this footnote in my Intel docs (22.4):
>
>
>> Processing of an entry fails in any of the following cases:
>>
> [...]
>
>> • An attempt to write bits 127:64 to the MSR indexed by bits 31:0 of the
>> entry
>> would cause a general-protection exceptio
Dmitry Melekhov wrote:
> Hello!
> v7 with 2.6.19.1 works OK.
>
>
>
Excellent! Thanks for the feedback.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
Take Surveys. Earn Cash.
Stuart Johnson wrote:
> I have two Windows boxes for my day job (Win2K and WinXP). I will be
> working from home soon, and I don't want more computers in my house. I
> really want to run everything on Linux if possible.
> I plan to get a Core 2 Duo, with Gentoo Linux 64, and at least 2Gb of RAM
James Morris wrote:
> I just tried installing Plan 9 from the current CD ISO (see
> http://plan9.bell-labs.com/plan9/download.html) under KVM and didn't get
> very far.
>
> It boots, then hangs after some initialization. Screenshot of the guest
> at this point: http://namei.org/images/p9-kvm.pn
user01 wrote:
> hi list
>
> just started playing a little with kvm & qemu. i discovered,
> that resetting the guest actually resets the host. tested
> on amd/pacifica with kvm-7 (svn revision 4115) with debian
> as host and an openbsd install-cd (4.0) as guest. typing
> "halt" in the guests shell s
Michael Riepe wrote:
> Hi!
>
> Avi Kivity wrote:
>
>
>> The way to fix is to add handling to {svm,vmx}_get_msr() for msr 1 (and
>> any other pointless msrs the guest reads or writes). From a cursory
>> reading of the machine check docs, returning 0 should b
[EMAIL PROTECTED] wrote:
> Shalom Avi,
>
> are there any plans to have MAC OS X running under KVM??
>
> I have KVM running under Edgy.
>
>
I think that Mac OS X requires different firmware than that provided by
the qemu bios which we use.
If you can run Mac OS X under regular qemu, then kvm s
Michael Riepe wrote:
> OpenSolaris runs on Intel with a simple modification: force the CS limit
> to 0x in real mode (I wonder why that didn't happen already).
>
> Plan9, on the other hand, seems to execute code outside the 64K range.
> With cs-limit.patch, it dies at RIP 0x100212. I'm afraid w
user01 wrote:
>
Can you set up a serial console and capture dmesg?
>>> sure. but which machine? host or guest?
>>>
>>>
>> the host please. do an
>>
>>echo 9 > /proc/sysrq-trigger
>>
>> before so we get to see anything interesting.
>>
>
> the only
Dmitry Melekhov wrote:
> Hello!
>
> I tested linux x86 and windows xp with v7.
> Linux can't get ip address from dhcp server, but if I set it manually
> all works OK.
> Windows can't get address from dhcp server too and even manual
> assignment doesn't help :-(
> Is this known problem?
>
What
Mark Clarkson wrote:
> Hi,
> When using WinXP I get a completely white screen whenever I change the
> resolution and just before the Windows GUI comes up, which lasts for
> around 20 seconds.
That is a known issue. Windows is clearing the screen using mmio
writes. We have hacks to convert the
Anthony Liguori wrote:
> I spent some time this weekend trying to port the KVM changes to the
> latest QEMU CVS. I got snagged on a certain changeset though.
> Specifically, the changeset on Sep 24th that added SMM support (and
> moved ACPI init to the BIOS) is where my patch stops working.
>
[EMAIL PROTECTED] wrote:
>
> Hi, modifing the patch and launching windows boot it reports the
> following:
>
> kvm: msrs: 6
> VMentry guest msr[0] index=c084 data=3700
> VMentry guest msr[1] index=c082 data=8025be90
> VMentry guest msr[2] index=c083 data=8025efa0
> VMen
Dmitry Melekhov wrote:
> Avi Kivity пишет:
>> Dmitry Melekhov wrote:
>>> Hello!
>>>
>>> I tested linux x86 and windows xp with v7.
>>> Linux can't get ip address from dhcp server, but if I set it
>>> manually all works OK.
>>
Dmitry Melekhov wrote:
> Avi Kivity пишет:
>> Dmitry Melekhov wrote:
>>>
>>>> The defaults are to use a qemu internal dhcp server.
>>>>
>>> Looks like it doesn't work :-(
>>>
>>>
>>
>> Can you test with the -n
[EMAIL PROTECTED] wrote:
Hi, modified NR_BAD_MSRS, dmesg reports:
ok, please revert all patches an apply the attached.
--
error compiling committee.c: too many arguments to function
Index: vmx.c
===
--- vmx.c (revision 4120)
+++
James Jacobsson wrote:
> Is KVM supposed to be a generic VT-x/SVM abstraction layer, or is it
> supposed to be yet-another Qemu backend?
>
>
kvm is intended to be a generic hardware virtualization abstraction
layer (not limited to VT-x/SVM -- if the ppc folk want in, they're welcome).
That sa
[EMAIL PROTECTED] wrote:
>
> Hi, I reverted all patched and applied last one.
> How when windows XP start the qemu windows remains frozen . No
> warnings o messages are displayed.
> The host cannot be reachable from network.
>
Please send the host .config.
--
error compiling committee.c: too m
James Jacobsson wrote:
> Attached is a patch to allow KVM to build without gcc 3.x (by skipping
> building QEmu).
>
> The only changes are to the top-level configure script and Makefile.
>
> To build without QEmu, there is a new argument to configure, --no-qemu
>
> This patch applies to KVM release
[EMAIL PROTECTED] wrote:
>
> Hu,
> where is .config file ?
> I did not find it in kvm directory .
>
The .config file used to compile the kernel. If you didn't compile it
yourself, it can probably be found in /boot/config-2.6.18.x.y.z for
something similar.
What distribution are you using?
--
Mark Clarkson wrote:
> Unfortunately the slow network performance and the fact that, on my
> setup at least, network io takes 100% of a single core means that kvm is
> not currently useful for server use.
>
>
Certainly, kvm is slow right now for server use. This will improve
quickly though.
[EMAIL PROTECTED] wrote:
Dec 19 12:10:10 timb194083 kernel: Process qemu-system-x86 (pid: 2947,
threadinfo 81005ccd8000, task Dec 19 12:10:10 timb194083 kernel:
Dec 19 12:10:10 timb194083 kernel: Dec 19 12:10:10 timb194083 kernel:
Code: 0f 30 41 ff c0 48 83 c7 10 41 39 f0 7c e4 c3 45 31 c0
rongeens7 wrote:
> All,
>
> I am experimenting somewhat with kvm on an
> ubuntu edgy system, and am now trying to install
> a plain ubuntu dapper from CD into a VM.
> The problem is that I cannot get past the lilo prompt,
> in fact the Qemu process craches immediately after doing
> starting up its
[EMAIL PROTECTED] wrote:
>
> Applayed patch.
> Now qemu and host are frozen e nothing is reported in /var/log/messages.
>
Please try with serial console or netconsole.
--
error compiling committee.c: too many arguments to function
--
rongeens7 wrote:
>
>> This is due to a problem kvm has in processing real mode code on intel
>> processors. If you can disable the lilo splashscreen, this may help.
>>
>
> I wouldn't now how to tackle this, the qemu window dissapears before I
> can do anything. Anyone knows a way around thi
[EMAIL PROTECTED] wrote:
>
> I tried with the -vnc option.
> My host frozen.
>
Ok. I sure don't know what's wrong on that machine then.
I'll try to come up with a better patch.
--
error compiling committee.c: too many arguments to function
James Jacobsson wrote:
> Attached is a patch to add some API documentation for libkvm to the
> source-tree (applies to the trunk).
> Also attached is the Doxyfile and a separate document which I use to
> generate documentation on my machine, just for reference.
>
> This is the first suggestion of h
Commits to the kvm subversion repository are now sent to a mailing list,
[EMAIL PROTECTED] If you wish to track development
closely, you can subscribe to the mailing list.
Please note that development occurs on several branches; not every
commit will be available in the next release.
http://k
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>> Any thoughts?
>>
>> SMM continues the tradition of making each x86 generation hackier
>> than before.
>>
>> What happens (probably) is that the virtual hardware unmaps the
Anthony Liguori wrote:
> Howdy,
>
> The attached patch forward ports the KVM patch to QEMU's CVS. The
> only significant change needed was hacking the Bochs BIOS to
> dynamically disable SMM support if KVM is enabled. This was done by
> using one of the Bochs DEBUG ports. Probably not the bes
Jeremy Katz wrote:
> Currently, kvm ends up just using the standard qemu cpu initialization.
> This means that all x86_64 virtual machines appear to have an
> AuthenticAMD (AMD64) processor. This ends up causing a problem when
> booting some x86_64 Linux kernels as they attempt to do AMD64 specifi
Various minor fixes to support more guest OSes, fix a bug in exporting
MSRs to userspace, and version the API.
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash. Influence the Future
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/mmu.c
===
--- linux-2.6.orig/drivers/kvm/mmu.c
+++ linux-2.6/drivers/kvm/mmu.c
@@ -647,14 +647,20 @@ int kvm_mmu_init(struct kvm_vcpu *vcpu)
From: Michael Riepe <[EMAIL PROTECTED]>
Some msrs, such as MSR_STAR, are not available on all processors. Exporting
them causes qemu to try to fetch them, which will fail.
So, check all msrs for validity at module load time.
Signed-off-by: Michael Riepe <[EMAIL PROTECTED]>
Signed
From: Michael Riepe <[EMAIL PROTECTED]>
this allows opensolaris to boot on kvm/intel.
Signed-off-by: Michael Riepe <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/vmx.c
===
From: Michael Riepe <[EMAIL PROTECTED]>
This allows plan9 to get a little further booting.
Signed-off-by: Michael Riepe <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6
Add compile-time and run-time API versioning.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ linux-2.6/drivers/kvm/kvm_main.c
@@ -
James Jacobsson wrote:
> I've revised the documentation patch,
Applied; thanks.
> and I've also created a new
> version of the "building KVM without gcc 3.x" patch.
>
I'll take a closer look at this later.
--
error compiling committee.c: too many arguments to function
--
Jeremy Katz wrote:
> On Thu, 2006-12-21 at 11:20 +0200, Avi Kivity wrote:
>
>> Jeremy Katz wrote:
>>
>>> Currently, kvm ends up just using the standard qemu cpu initialization.
>>> This means that all x86_64 virtual machines appear to have an
>>&g
Emil Tantilov wrote:
> Also getting the following panic on init 6:
>
>
I presume (from the module list) that this is on the guest, right?
Guest shutdown/restart is not a well supported area at the moment.
> Restarting system.
> divide error: [#1]
> SMP
> Modules linked in: ne2k_pci 8390
Not much is happening on the trunk, as most of the work is on branches.
That is not an excuse not to make a release, so I tagged kvm-8:
- msr fixes (Michael Riepe)
- more guest support (Michael Riepe)
- random fixes
- fpu state corruption fix on AMD hosts
--
error compiling committee.c: too ma
Avi Kivity wrote:
> Not much is happening on the trunk, as most of the work is on
> branches. That is not an excuse not to make a release, so I tagged
> kvm-8:
>
> - msr fixes (Michael Riepe)
> - more guest support (Michael Riepe)
> - random fixes
> - fpu state corruptio
Emil Tantilov wrote:
> Yep - that is corect. init 0 works OK, but init 6
> panics.
>
> EIP points to delay_tsc, so I think it might be
> related to the issue with the clock (TSC running
> slow).
>
>
Well, the EIP points at a sub instruction, which has no business
generating divide exceptions.
Jeremy Katz wrote:
>> What do you mean by "current state of migration"? How to run it for
>> testing?
>>
>
> Yep
>
I've asked Uri to add a section to the web site.
--
error compiling committee.c: too many arguments to function
-
Anthony Liguori wrote:
> Avi Kivity wrote:
>> There are four issues I can see:
>>
>> - if there are multiple sources of kvm userspace, there are bound to
>> be problems with incompatible kernel API and userspace, especially as
>> I have plans for extensive
Xu Nakajima wrote:
> Hello,
> I have an AMD machine with 3800+ Dual Core Processor
>
> Athlon(tm) processor (x86_64).
> FC6 (x86_64) is installed on this machine.
>
> This processor DOES support SVM
> (cat /proc/cpuinfo | grep flags shows a line which
> includes "svm").
> I had built kvm-7 on th
Diwaker Gupta wrote:
> $ lsmod | grep kvm
> kvm41120 0
>
>
You need to modprobe kvm-intel as well.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
Take Surve
Xu Nakajima wrote:
> Hello,
>
> Thanks for your answer.
>
>> Are you using a Xen kernel? If so, please
>> try again without Xen.
>>
>
> Indeed , I am trying it with FC6, where the kernel is
> Xen kernel.
>
> The thing is that with FC6 , the default installation
>
> has a Xen kernel; Do
James Jacobsson wrote:
> I've started writing a simulation environment based on KVM, and so far
> everything is working as expected.
> However, I've reached a point where I need to start simulating the
> 8259A PIC, and I can't really seem to grasp how the interrupts are to
> be simulated in KVM.
>
Franco Spinelli wrote:
> After installing XP on my AMD X2 machine using "fast formatting" tip, I
> am now using it for some test.
>
> Some network questions:
>
> - without any "-net" option I get a "user" config, I can see my physical
>gateway and browse internet but I can't see my LAN share -
Avi Kivity wrote:
> Jeremy Katz wrote:
>>> What do you mean by "current state of migration"? How to run it for
>>> testing?
>>>
>>
>> Yep
>>
>
> I've asked Uri to add a section to the web site.
>
This is now htt
Haw-Yuan Yang wrote:
> I have installed two WinXP pro guests on kvm8+FC5+VT
> machine and experienced serious task scheduling problem (guest stop
> and go) when two guests are running at the same time. Is it known
> issue or I did some thing wrong during the installation?
It is not a known prob
Haw-Yuan Yang wrote:
>
> Host PC configuration:
> CPU: Intel Pentium D 925 Dual Core.
> RAM: 2GByte
> Kernel version: 2.6.15 smp
>
> Problem: After two WinXP pro guest start, mouse response in guest
> window is kind of up and down sometimes good and sometimes have no
> response at all .
C
Yoshimi Ichiyanagi wrote:
> The latest version of kvm doesn't initialize kvm_arch_ops in kvm_init(),
> which causes an error with the following sequence.
>
> 1. Load the supported arch's module.
> 2. Load the unsupported arch's module. (loading error)
> 3. Unload the unsupported arch's module.
>
>
Jun Koi wrote:
> Hi,
>
> I got the infamous exception 13 problem when trying to run guest by
> booting from a Debian iso (debian-31r4-i386-netinst.iso).
>
> Syslog file has only one line, like this:
>
> kvm: msrs: 6
>
> My machine has Pentium D 930 processor.
>
> I grepped through the mailing list,
[EMAIL PROTECTED] wrote:
Good moorning, I changed the -boot option in 'c' but when my Windows Xp boot
to complete the installation I got the following errors:
unhandled vm exit: 0x8022
rax 0800 rbx ffdff120 rcx c080 rdx
rsi
Nguyen Anh Quynh wrote:
> Hi,
>
> This patch renames few MSR registers in vmx.h and did few trivial
> cleanups.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash.
Ingo Molnar wrote:
> btw., we've got a problem with KVM in -rt:
>
> BUG: scheduling while atomic: qemu/0x0001/11445, CPU#0
> [] dump_trace+0x63/0x1e8
> [] show_trace_log_lvl+0x19/0x2e
> [] show_trace+0x12/0x14
> [] dump_stack+0x14/0x16
> [] __schedule+0xae/0xd9f
> [] schedule+0xec/
Compatibility and stabilization fixes, many centered around msrs, but a
few other corner cases as well.
--
error compiling committee.c: too many arguments to function
-
Take Surveys. Earn Cash. Influence the Future of IT
J
current_cpu_data invokes smp_processor_id(), which is inadvisable when
preemption is enabled. Switch to boot_cpu_data instead.
Resolves sourceforge bug 1621401.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm
Instead of doing tricky stuff with the arch dependent virtualization registers,
take a peek at the guest's efer.
This simlifies some code, and fixes some confusion in the mmu branch.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/driver
ch's module at step 2.
This patch initializes kvm_arch_ops upon loading architecture specific
kvm module, and prevents overwriting kvm_arch_ops when kvm_arch_ops is
already set correctly.
Signed-off-by: Avi Kivity <[EMAI
Resolves sourceforge bug 169 (guest crashes running benchmark software).
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/svm.c
===
--- linux-2.6.orig/drivers/kvm/svm.c
+++ linux-2.6/drivers/kvm
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ linux-2.6/drivers/kvm/kvm_main.c
@@ -1103,6 +1103,47 @@ void realmode_set_cr(struct kvm_vc
These msrs are referenced by benchmarking software when pretending to be
an Intel cpu.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ lin
From: Nguyen Anh Quynh <[EMAIL PROTECTED]>
No need to append _MSR to msr names, a prefix should suffice.
Signed-off-by: Nguyen Anh Quynh <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6
__free_page() doesn't like a NULL argument, so check before calling it. A
NULL can only happen if memory is exhausted during allocation of a memory
slot.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm
Ingo Molnar wrote:
> * Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>>> NOTE: this is not a worry for upstream kernel, it is caused by
>>> PREEMPT_RT scheduling in previously atomic APIs like kunmap(). But
>>> KVM used to work pretty nicely in -rt a
Ingo Molnar wrote:
> * Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>> Talking about the scheduler (and to the scheduler's author :), it
>> would be nice to hook the migration weight algorithm too. kvm guests
>> are considerably more expensive to migrate,
Ingo Molnar wrote:
> * Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>>> I'll commit the previous patch (which is correct, even if no guest
>>> actually uses syscall), and teach qemu not to read MSR_STAR when it
>>> isn't available.
>>>
Yoshimi Ichiyanagi wrote:
>> This bit is unnecessary, no? I think kvm_init() will only be called
>> after the module is loaded, at which point kvm_arch_ops is initialized
>>
> >from the .bss section.
>
>
> Logically it's not required, however it's better to initialize
> explicitly in gener
Ingo Molnar wrote:
> * Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>> 3. The most expensive vmx context switch involves cpu migration:
>>
>> cpu 0: vmclear vm1 /* decache vmx context into memory */
>> cpu 1: vmptrld vm1
>>... vm register
Ingo Molnar wrote:
> Subject: [patch] kvm: fix GFP_KERNEL alloc in atomic section bug
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> KVM does kmalloc() in an atomic section while having preemption disabled
> via vcpu_load(). Fix this by moving the ->*_msr setup from the
> vcpu_setup method to the vc
Ingo Molnar wrote:
> Subject: [patch] kvm: fix GFP_KERNEL allocation in atomic section in
> kvm_dev_ioctl_create_vcpu()
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> fix a GFP_KERNEL allocation in atomic section bug:
> kvm_dev_ioctl_create_vcpu() called kvm_mmu_init(), which calls
> alloc_pages(),
Ingo Molnar wrote:
> Subject: [patch] kvm: fix GFP_KERNEL allocation in atomic section in
> kvm_dev_ioctl_create_vcpu()
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> fix an GFP_KERNEL allocation in atomic section:
> kvm_dev_ioctl_create_vcpu() called kvm_mmu_init(), which calls
> alloc_pages(), wh
Ingo Molnar wrote:
> I've got a security related question as well: vcpu_load() sets up a
> physical CPU's VM registers/state, and vcpu_put() drops that. But
> vcpu_put() only does a put_cpu() call - it does not tear down any VM
> state that has been loaded into the CPU. Is it guaranteed that (ho
Ingo Molnar wrote:
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
>
>> I'll do a full qemu rebuild, just to make sure it picked up the new
>> library ...
>>
>
> that did the trick. The only messages remaining are:
>
> kvm: unhandled wrmsr: 0xc1
> inject_general_protection: rip 0xc011b8ae
>
Ingo Molnar wrote:
> * Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>>> As SVN has shown it, we can rely on VMX state save/load to become
>>> faster in the future. So we definitely shouldnt design for a
>>> small-scale overhead in first-generation silic
Ingo Molnar wrote:
> * Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>>> that did the trick. The only messages remaining are:
>>>
>>> kvm: unhandled wrmsr: 0xc1
>>> inject_general_protection: rip 0xc011b8ae
>>>
>>>
>>>
201 - 300 of 1103 matches
Mail list logo
