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_vc
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 par
Hi!
David Abrahams wrote:
[...]
>>What happens if you hide the qemu window below another one, e.g. your
>>favorite web browser?
>
>
> It seems to make progress. I can play internet radio in the VM and I
> keep hearing it (glitchy, but it doesn't stop).
What about the load?
By the way, how is
Hi!
David Abrahams wrote:
[...]
>>More data: it definitely seems to make a difference whether the VM's
>>desktop is showing. If I switch Gnome workspaces so it's not visible,
>>it doesn't seem to drive the frequency up.
Because it doesn't have to redraw the window?
What happens if you hide the
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 wit
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 "Ti
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 (k
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 upgrad
Hi!
With respect to the Core Duo, this is the best release I've seen so far:
- FreeBSD 6.1: works.
- NetBSD 3.1: works.
- OpenSuse 10.2 (sans gfxmenu): works.
- Qemu-Puppy 2.01-3: works.
- Qemu-Puppy 2.13-1: works.
- Solaris 10.1: works.
- XP Pro: works.
Unfortunately, Knoppix (both 5.0 and 5.1.
Hi!
Benjamin Prosnitz wrote:
> I ran some benchmarks inside of KVM-12 on my system and outside of KVM
> (no virtualization on my system). I found that floating point
> performance when running both with and without KVM was approximately the
> same, but integer performance in KVM was about 25% of
Hi!
>>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.
>
>
> The KVM_API_VERSION in the kernel tree is 2 while the one in the trunk
> is 3.
> When have you updated your sources?
Too often to r
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!
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 m
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 51
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. I
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 suppor
Kamble, Nitin A wrote:
> Hi Guys,
>
>I was wondering if SuSE Linux 10.1 and 10.2 can boot on top of KVM?
>
> Xen is getting into real mode emulation issues with these distributions
> for Fully virtualized Guests.
I guess that means you're using an Intel host.
Install with -no-kvm, then un
Fine. :-)
But at the same time, the SVN repository has vanished.
Avi Kivity wrote:
> The long promised kvm wiki has arrived: please stroll to
> http://kvm.qumranet.com to see it.
>
> I will update the sourceforge site to redirect to the wiki later.
>
> Thanks to Yaniv Ferszt at Qumranet for se
Hi!
When happening on Intel processors, this usually means that the
bootloader has tried to use big real mode. The workaround is probably
the same as for (Open)Suse: Install with -no-kvm, then disable the
graphical boot menu.
Uri Lublin wrote:
> Hi Vineet,
>
> What guest OS are you trying to run
different from the behaviour on a Core Duo, maybe
because the Xeon is running in 64-bit mode.
Uri Lublin wrote:
> O.K.
> I'll try to reproduce it with netbsd, and investigate a little.
> Uri.
>
> --------
> *From:
s on it. :-)
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Michael Riepe
> Sent: Sun 14/01/2007 19:09
> To: kvm-devel@lists.sourceforge.net
> Subject: [kvm-devel] Talking about regressions...
>
> When I did a couple of tests the other day, I noticed that o
When I did a couple of tests the other day, I noticed that one or more
bugs must have been introduced at least into the vmx part in kvm-10:
- netbsd 3.1 used to work with kvm-9. In kvm-10, the system hangs during
boot. One of the last things I can see is that a shell process dies with
a SIGSEGV. T
Hi!
Avi Kivity wrote:
>>on a related note, i also got:
>>
>> vmwrite error: reg 6802 value cfd3c4a4 (err 17408)
>
> This is already fixed on the trunk (which now has mmu merged).
Actually not. Now it reads:
vmwrite error: reg 6802 value 6802 (err 17408)
(trunk revision 4236)
--
Mich
Hi!
Parag Warudkar wrote:
> I am using kvm-8 plus all 8 kernel side updates for 2.6.20-rc2.
> If I start a XP SP2 install using qemu and KVM it dies with a BSOD.
> If KVM is disabled, the installation proceeds as expected.
That's a known problem. XP SP2 doesn't work with the current ACPI
imple
Hi!
Avi Kivity wrote:
> Windows crashes immediately with this patch (STOP: 0x7E (0xc005
> 0xF724879C 0xF7A168DC 0xF7A165D8) for those who know how to decode
> BSODs), so either it's doing too much or not enough.
>
> Note that we support migration from Intel to AMD and vice versa, so it
>
Hi there!
Avi Kivity wrote:
> 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
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 be fine for msr 1.
Yep.
But that doesn't help with Plan9 (just checked
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
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 qemu-kvm.c
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 PROTEC
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
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 :-
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 inv
Hi!
Dor Laor wrote:
>>Hi!
>>
>>I immediately tried the latest version (SVN release 4064) on my
>
> Thinkpad
>
>>(Core Duo T2400, Linux 2.6.19) but I still have the same problems I
>
> had
>
>>with release 5.
>>
>>Suse 10.1 (the German version) dies with:
>>
>>
>>>exception 13 (0)
>>>Aborted
>>
Hi!
I immediately tried the latest version (SVN release 4064) on my Thinkpad
(Core Duo T2400, Linux 2.6.19) but I still have the same problems I had
with release 5.
Suse 10.1 (the German version) dies with:
> exception 13 (0)
> Aborted
no matter if I boot from DVD or disk.
OpenSolaris XXL gets
36 matches
Mail list logo
