ymed wrote:
> Hello!
>
> I have recently tried to install XP 64 bit SP1 on KVM 16.
> But Windows setup buzzed on text mode and screen: "Setup is starting
> Windows". Xp 32 bit runs on KVM 16 without any problems.
> Does KVM support XP 64 bit?
>
> Thank you very much!
>
64-bit Windows is not ye
Anthony Liguori wrote:
> Attached patch implements lazy FPU save/restore for SVM. It's much
> more conservative than my previous patch. We can now mark the guest
> FPU as inactive whenever we want which will trigger CR0.TS to be set
> in the guest's shadowed CR0.
>
> Right now, we only mark th
Hi all,
I've been toying around with a benchmark suite for virtualization, and
I've just added kvm support. You can download the source tarball
straight from the mercurial repo:
http://ozlabs.org/~rusty/virtbench/
http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2
R
Hello!
I have recently tried to install XP 64 bit SP1 on KVM 16.
But Windows setup buzzed on text mode and screen: "Setup is starting Windows".
Xp 32 bit runs on KVM 16 without any problems.
Does KVM support XP 64 bit?
Thank you very much!
---
Hi all,
I note that Linux under kvm 20 doesn't use sysenter, while it did under
kvm 19. There's no "sep" in /proc/cpuinfo and the vendor id looks kinda
random too: this looks like a cpuid problem?
Cheers,
Rusty.
-
Howdy,
I had an idea for improving VMEXIT time by only saving/restoring
sys{enter,call,ret} MSRs when exiting from kernel space code since as
long as these instructions aren't executed on the host, everything
should be fine.
This worked fine for MSR_IA32_SYSENTER* msrs, but not so much for the
Attached patch implements lazy FPU save/restore for SVM. It's much more
conservative than my previous patch. We can now mark the guest FPU as
inactive whenever we want which will trigger CR0.TS to be set in the
guest's shadowed CR0.
Right now, we only mark the FPU as inactive when the guest
On Sun, Apr 22, 2007 at 12:21:40PM +0100, Andrew Walrond wrote:
> Latest Feisty kernel but using kvm-19 modules No idea about CONFIG_HZ.
> The Kubuntu kernel doesn't seem to expose the .config in /proc. Any
> other way I can find out?
grep CONFIG_HZ /boot/config-`uname -r`
> [ 3949.793179] rtc
Fabian Deutsch wrote:
> Hey,
>
> I just updated kvm to the latest head revision (userland and
> kernelspace) on a 32bit host runnig fedora 6.
>
> First my Ubuntu Lts guest panicked because of some acpi thing. I added
> the -no-acpi option and my guest is running fine again.
>
> Just wanted to note
...and I then see only the top left part of the XP screen, min/maximise/close
widgets are missing from the right end of the main window grab bar.
This only seems to happen occasionally. If I use XP's display properties to
change resolution, the window resizes and everything works properly again
Interestingly, I still get the lost interrupts messages if I leave the
max-user-freq at the bootup default of 64. Running XP under kvm fresh after a
reboot:
$ cat /proc/sys/dev/rtc/max-user-freq
64
$ dmesg | tail -n 3
[ 362.567318] rtc: lost some interrupts at 1024Hz.
[ 362.569987] rtc: lost s
On Sunday 22 April 2007 11:25:21 Avi Kivity wrote:
>
> Anything in dmesg?
Ok, so running as root allows qemu to ignore /proc/sys/dev/rtc/max-user-freq
and increase the frequency to 1024Hz anyway.
Running as a user means I get this message from qemu again:
Could not configure '/dev/rtc' to have
On Sunday 22 April 2007 11:25:21 Avi Kivity wrote:
> Andrew Walrond wrote:
> > On all kvm versions I have tried (16 - 19) running windows XP, with the
> > XP window having captured the mouse, I have to make my mouse clicks slow
> > and deliberate else XP does notice them. It makes double clicks
> >
Hey,
I just updated kvm to the latest head revision (userland and
kernelspace) on a 32bit host runnig fedora 6.
First my Ubuntu Lts guest panicked because of some acpi thing. I added
the -no-acpi option and my guest is running fine again.
Just wanted to note this ..
- fabian
-
Bugs item #1705253, was opened at 2007-04-22 14:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1705253&group_id=180599
Please note that this message will contain a full copy
Andrew Walrond wrote:
>
>> Anything in dmesg?
>>
>
> Ah... A load of these
>
> [ 3949.793179] rtc: lost some interrupts at 1024Hz.
> [ 3949.813162] rtc: lost some interrupts at 1024Hz.
> [ 3949.833150] rtc: lost some interrupts at 1024Hz.
> [ 3949.853139] rtc: lost some interrupts at 1024Hz
Andrew Walrond wrote:
> On Sunday 22 April 2007 11:40:32 Avi Kivity wrote:
>> Carsten Emde wrote:
>>> Andrew,
On all kvm versions I have tried (16 - 19) running windows XP, with the
XP window having captured the mouse, I have to make my mouse clicks slow
and deliberate else XP does n
Jon wrote:
> On Sun, Apr 22, 2007 at 12:08:33PM +0300, Avi Kivity wrote:
>
>
>> Is this the reboot that's part of the install? If so, it's
>> kind-of-expected. Otherwise reboots should work.
>>
>
> I've been having the same error as Troy, with both Windows XP and Linux
> guests. I'm usi
On Sun, Apr 22, 2007 at 12:08:33PM +0300, Avi Kivity wrote:
> Is this the reboot that's part of the install? If so, it's
> kind-of-expected. Otherwise reboots should work.
I've been having the same error as Troy, with both Windows XP and Linux
guests. I'm using a Core Duo cpu.
But I just tri
On Sunday 22 April 2007 11:40:32 Avi Kivity wrote:
> Carsten Emde wrote:
> > Andrew,
> >
> >> On all kvm versions I have tried (16 - 19) running windows XP, with the
> >> XP window having captured the mouse, I have to make my mouse clicks slow
> >> and deliberate else XP does notice them. It makes
Carsten Emde wrote:
> Andrew,
>
>> On all kvm versions I have tried (16 - 19) running windows XP, with the XP
>> window having captured the mouse, I have to make my mouse clicks slow and
>> deliberate else XP does notice them. It makes double clicks especially hard.
>>
> I had the same pr
Andrew,
> On all kvm versions I have tried (16 - 19) running windows XP, with the XP
> window having captured the mouse, I have to make my mouse clicks slow and
> deliberate else XP does notice them. It makes double clicks especially hard.
I had the same problem, it went away immediately after I
Andrew Walrond wrote:
> On all kvm versions I have tried (16 - 19) running windows XP, with the XP
> window having captured the mouse, I have to make my mouse clicks slow and
> deliberate else XP does notice them. It makes double clicks especially hard.
>
> I am running Kubuntu Feisty 64bit on a
Significant cpu performance improvements (esp. for 32-bit guests on
64-bit hosts), as well as Windows 2000 support (without acpi).
Changes from kvm-19:
- Windows 2000 support
- performance enhancements
- patch against latest kernel tree included in tarball
- fix oops with 32-bit nonpae guests
No
On all kvm versions I have tried (16 - 19) running windows XP, with the XP
window having captured the mouse, I have to make my mouse clicks slow and
deliberate else XP does notice them. It makes double clicks especially hard.
I am running Kubuntu Feisty 64bit on a core 2 duo dell laptop, and the
PAGE_MASK is an unsigned long, so using it to mask physical addresses on
i386 (which are 64-bit wide) leads to truncation. This can result in
page->private of unrelated memory pages being modified, with disasterous
results.
Fix by not using PAGE_MASK for physical addresses; instead calculate
the
KVM shadow page tables are always in pae mode, regardless of the guest
setting. This means that a guest pde (mapping 4MB of memory) is mapped
to two shadow pdes (mapping 2MB each).
When the guest writes to a pte or pde, we intercept the write and emulate it.
We also remove any shadowed mappings c
Troy Benjegerdes wrote:
> I have a windows XP guest that when the guest attempts to restart does
> this:
>
> [EMAIL PROTECTED]:/extra$ kvm -m 512 -usbdevice tablet
> XP-2007-4-19-new.img.raw
> exception 13 (0)
>
Is this the reboot that's part of the install? If so, it's
kind-of-expected. Ot
Benjamin Budts wrote:
> Hi,
>
> I made an mknod myself now, did a cat of /sys/class/misc/kvm/dev
> 18 64
>
> and did a
> mknod /dev/kvm c 18 64
>
> everything OK now
>
> how come I dont have the /dev automatically ?
>
> udevtrigger didn't help, pgrep udevd showed the pid of udevd... so it
> was al
Gregory Haskins wrote:
> The following is my patch series for adding in-kernel APIC support. It
> supports three "levels" of dynamic configuration (via a new ioctl):
>
> * level 0 = (default) compatiblity mode (everything in userspace)
> * level 1 = LAPIC in kernel, IOAPIC/i8259 in userspace
>
Gregory Haskins wrote:
> Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
> ---
>
> drivers/kvm/Makefile |2
> drivers/kvm/kernint.c | 168 +
> drivers/kvm/kvm.h | 14
> drivers/kvm/kvm_main.c | 142 +
> drivers/kvm/lapic.c| 1472
> +
Gregory Haskins wrote:
> Adds an abstraction to the LAPIC logic so that we can later substitute it
> for an in-kernel model.
>
>
This is overly abstracted. It's not like you can (on real hardware)
wire your own lapic and plug it into the processor. It's well defined,
and there are just thre
Gregory Haskins wrote:
> The VCPU executes synchronously w.r.t. userspace today, and therefore
> interrupt injection is pretty straight forward. However, we will soon need
> to be able to inject interrupts asynchronous to the execution of the VCPU
> due to the introduction of SMP, paravirtualized
Gregory Haskins wrote:
> The current code is geared towards using a user-mode (A)PIC. This patch adds
> an "irqdevice" abstraction, and implements a "userint" model to handle the
> duties of the original code. Later, we can develop other irqdevice models
> to handle objects like LAPIC, IOAPIC, i
34 matches
Mail list logo
