Dong, Eddie wrote:
A minor patch to avoid heavy is_empty_shadow_page for release version.
diff --git a/drivers/kvm/mmu.c b/drivers/kvm/mmu.c
index e85b4c7..58fdd7b 100644
--- a/drivers/kvm/mmu.c
+++ b/drivers/kvm/mmu.c
@@ -52,11 +52,15 @@ static void kvm_mmu_audit(struct kvm_vcpu
Hi!
This is just a (probably silly) idea I had the other day. Currently, the
guest's memory is allocated inside the kernel and exported to userspace
via mmap(). But wouldn't it also be possible to create a file in
userspace and pass its descriptor to kvm? If we also pass file offset
and length
Hi!
Avi Kivity wrote:
Sounds like ondemand is broken.
Maybe it only switches when the load rises in user space. With KVM, it
appears in system space. Got to cross-check that on my Core Duo.
Michael.
-
Take Surveys. Earn
Hi!
Avi Kivity wrote:
Michael Riepe wrote:
Avi Kivity wrote:
This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
Well, almost. Knoppix 5.0 and 5.2 work now, but 5.1.1 still hangs with a
black framebuffer (no penguin logo) and a load of 100%.
Do you have
Avi Kivity wrote:
This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
Well, almost. Knoppix 5.0 and 5.2 work now, but 5.1.1 still hangs with a
black framebuffer (no penguin logo) and a load of 100%.
Everything else still works as fine as with kvm-17.
Great work!
--
Michael
Hi!
Carsten Emde wrote:
Avi Kivity wrote:
Michael Riepe wrote:
With respect to the Core Duo, this is the best release I've seen so far:
Unfortunately, kvm-17 was less successful here. FC6 did not boot any
longer after I upgraded from kvm-16 to kvm-17, so I was rather surprised
when I
Hi!
Carsten Emde wrote:
Actually, the above line can be preserved, if we move the previous line
down by 1: Was it a simple race?
--- kvm_main-17.c 2007-03-24 02:09:00.0 +0100
+++ kvm_main.c2007-03-24 04:10:59.0 +0100
@@ -1574,8 +1574,8 @@
if
which is the right user-space release to use the built-in kvm?
My tools from the trunk kill the Core Duo, probably due to an interface
mismatch.
--
Michael Tired Riepe [EMAIL PROTECTED]
X-Tired: Each morning I get up I die a little
Hi!
Waba wrote:
I tried to install Solaris 10 under KVM, without success, so Avi told me
to post the details here. My CPU is an AMD X2, and I am using KVM trunk
on a 2.6.19.2, started with the following command-line:
kvm -hda solaris.qcow -cdrom sol-10-u3-ga-x86-dvd.iso -boot d -m 512
Hi!
Avi Kivity wrote:
I added a page on the wiki to track the status of various guest
operating systems, and seeded it with my usual testcases.
You should add a column for the host CPU. It really makes a difference
in some cases.
--
Michael Tired Riepe [EMAIL PROTECTED]
X-Tired: Each
Hi!
Francesc wrote:
I have install 2.6.19.2 kernel in Red Hat and I have got .ko files at
last !!
But it seems if there is a problem when I try to load the module:
modprobe kvm-intel
FATAL: Error inserting kvm_intel
(/lib/modules/2.6.19.2/extra/kvm-intel.ko): Operation not supported
Hi!
Francesc wrote:
Thank's. You were absolutely right. Virtualization was disbled. I
enabled it and module seems to load.
The only thing is that I get this message:
kvm: no version for struct_module found: kernel tainted.
kvm: msrs: 2
does it mean any trouble?
Usually not. It may be
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 exception if executed via WRMSR with CPL =
0.
And there's a
Avi Kivity wrote:
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.
That doesn't help, the messages are still there.
--
Michael Tired Riepe [EMAIL PROTECTED]
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.
Guess what? It's qemu!
In
Avi Kivity wrote:
Michael Riepe wrote:
Did I mention that kvm dies a horrible death (Aiee, killing interrupt
handler!) when I configure the kernel with CONFIG_PREEMPT=y? Currently
I use CONFIG_PREEMPT_NONE.
I'll investigate this. I thought we had this fixed.
Maybe the problem
Hi!
Gerd Hoffmann wrote:
both isolinux and grub fail to switch into gfx mode, which likely is
caused by either incomplete real mode emulation or big real mode.
Workaround for grub: just turn off the eye candy, comment the gfxmenu
line in /boot/grub/menu.lst.
Yep, that did the trick :-)
Hi!
Avi Kivity wrote:
Michael Riepe wrote:
By the way: I get myriads of kvm: unhandled rdmsr: c081 messages
in my syslog, but they don't seem to cause any further harm.
Which guest does this happen with? AFAICT this should be handled well
(vmx.c:vmx_get_msr() - find_msr_entry
18 matches
Mail list logo
