I'm on 32-bit Linux, kernel 2.6.27.7-smp. When I moved from kvm-83 to
kvm-87 plus kvm-kmod-devel-87, my Linux host VMs ran fine. But my XP0 host
simply ran too slowly to be useable at all, and my Windows 7 host wouldn't
boot -- just crashed and restarted early in the boot process.
Seeing the m
On 01.07.2009, at 05:28, Christoffer Dall wrote:
Hi all.
We are still working on our ARM port of KVM and we are managing to let
the guest decompress the kernel image and run from relocated address
and we can support enabling MMU before this.
Howver, to debug relocated micro-hypervisor for exc
The big change here is handling of enabling/disabling of hpet legacy mode. When
hpet enters
legacy mode, the spec says that the pit stops generating interrupts. In
practice, we want to
stop the pit periodic timer from running because it is wasteful in a virtual
environment.
We also have to worr
When kvm is in hpet_legacy_mode, the hpet is providing the
timer interrupt and the pit should not be. So in legacy mode, the pit timer is
destroyed, but the *state* of the pit is maintained. So if kvm or the guest
tries to modify the state of the pit, this modification is accepted, *except*
that
Advertise HPET in ACPI HPET table
Signed-off-by: Beth Kon
Signed-off-by: Avi Kivity
---
kvm/bios/acpi-dsdt.dsl |2 --
kvm/bios/rombios32.c | 11 +++
2 files changed, 3 insertions(+), 10 deletions(-)
diff --git a/kvm/bios/acpi-dsdt.dsl b/kvm/bios/acpi-dsdt.dsl
index
Select irq0->irq2 override based on kernel gsi routing availability
If the kernel does not support gsi routing, we cannot do the irq0->irq2
override, so disable it in that case.
Signed-off-by: Beth Kon
Signed-off-by: Avi Kivity
---
hw/ioapic.c|6 +++---
hw/pc.c
bios: allow qemu to configure irq0->inti2 override
Win2k8 expects the HPET interrupt on inti2, regardless of whether
an override exists in the BIOS. And the HPET spec states that in legacy
mode,
timer interrupt is on inti2.
The irq0->inti2 override will always be used unless
Hi all.
We are still working on our ARM port of KVM and we are managing to let
the guest decompress the kernel image and run from relocated address
and we can support enabling MMU before this.
Howver, to debug relocated micro-hypervisor for exception handling, we
are trying to implement some NOT_
Applied, with minimum changes
On Thu, 2009-06-25 at 23:54 +0800, Yolkfull Chow wrote:
> diff --git a/client/tests/kvm/kvm.py b/client/tests/kvm/kvm.py
> index 4c7bae4..26ae46f 100644
> --- a/client/tests/kvm/kvm.py
> +++ b/client/tests/kvm/kvm.py
> @@ -73,7 +73,7 @@ class kvm(test.test):
>
Bugs item #2804562, was opened at 2009-06-10 20:06
Message generated for change (Settings changed) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2804562&group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2804562, was opened at 2009-06-10 20:06
Message generated for change (Settings changed) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2804562&group_id=180599
Please note that this message will contain a full copy of the comment
On 06/30/2009 09:58 PM, Dor Laor wrote:
On 06/30/2009 02:11 PM, Yolkfull Chow wrote:
Signed-off-by: Yolkfull Chow
---
client/tests/kvm/kvm.py |1 +
client/tests/kvm/kvm_tests.cfg.sample | 56
client/tests/kvm/kvm_tests.py | 93
+
On Tuesday 30 June 2009 20:28:08 Markus Armbruster wrote:
> Sheng Yang writes:
> > On Friday 26 June 2009 01:24:03 Avi Kivity wrote:
> >> The impact of the hotplug changes on device assignment were too
> >> difficult for me to fix up during the merge, so I disabled it
> >> temporarily. Please tak
Hi, Anthony,
On Wed, 2009-07-01 at 02:12 +0800, Anthony Liguori wrote:
> Hi Huang,
>
> Huang Ying wrote:
> > - MCE features are initialized when VCPU is intialized according to CPUID.
> > - A monitor command "mce" is added to inject a MCE.
> > - A new interrupt mask: CPU_INTERRUPT_MCE is added to
Add kprobes-based event tracer on ftrace.
This tracer is similar to the events tracer which is based on Tracepoint
infrastructure. Instead of Tracepoint, this tracer is based on kprobes(kprobe
and kretprobe). It probes anywhere where kprobes can probe(this means, all
functions body except for __kp
Add x86 instruction decoder to arch-specific libraries. This decoder
can decode x86 instructions used in kernel into prefix, opcode, modrm,
sib, displacement and immediates. This can also show the length of
instructions.
This version introduces instruction attributes for decoding instructions.
The
Hi,
Here are the v10 patches. I just updated for the latest -tip and
fixed typos and Kconfig dependency.
Here are the patches of kprobe-based event tracer for x86, version 10,
which allows you to probe various kernel events through ftrace interface.
The tracer supports per-probe filtering which a
Cleanup fix_riprel() in arch/x86/kernel/kprobes.c by using x86 instruction
decoder.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Jim Keniston
Cc: Ingo Molnar
---
arch/x86/kernel/kprobes.c | 128 -
1 files changed, 23 insertio
Ensure safeness of inserting kprobes by checking whether the specified
address is at the first byte of a instruction on x86.
This is done by decoding probed function from its head to the probe point.
Signed-off-by: Masami Hiramatsu
Acked-by: Ananth N Mavinakayanahalli
Cc: Jim Keniston
Cc: Ingo
Add dynamic ftrace_event_call support to ftrace. Trace engines can adds new
ftrace_event_call to ftrace on the fly. Each operator functions of the call
takes a ftrace_event_call data structure as an argument, because these
functions may be shared among several ftrace_event_calls.
Signed-off-by: Ma
Add following APIs for accessing registers and stack entries from pt_regs.
- regs_query_register_offset(const char *name)
Query the offset of "name" register.
- regs_query_register_name(unsigned offset)
Query the name of register by its offset.
- regs_get_register(struct pt_regs *regs, uns
Add a user-space selftest of x86 instruction decoder at kernel build time.
When CONFIG_X86_DECODER_SELFTEST=y, Kbuild builds a test harness of x86
instruction decoder and performs it after building vmlinux.
The test compares the results of objdump and x86 instruction decoder
code and check there ar
On Tue, 2009-06-30 at 14:22 +0530, sudhir kumar wrote:
> On Wed, Jun 17, 2009 at 2:59 AM, Lucas Meneghel Rodrigues
> wrote:
> > Adding iperf network performance test. Basically it tests
> > networking functionality, stability and performance of guest OSes.
> > This test is cross-platform -- i.e. i
On Tue, 2009-06-30 at 19:11 +0800, Yolkfull Chow wrote:
> Signed-off-by: Yolkfull Chow
> ---
> client/tests/kvm/kvm.py |1 +
> client/tests/kvm/kvm_tests.cfg.sample | 56
> client/tests/kvm/kvm_tests.py | 93
> +
>
Linux wants to enable I/O port access to the PCI extended config space and
thus writes a 1 into an AMD Fam10h MSR. Since we don't handle extended
config space (yet?), we simply ignore this write (and return 0 on reads).
Windows on the other hands checks whether the BIOS has setup MMI/O for
config s
Michael Jinks wrote:
Given the way qemu and screen interact, using the same keystrokes to
initiate commands, it would be really useful to have some other way to
detach and re-attach to a kvm guest on the fly.
It's pretty easy to configure screen to use a different set of
keystrokes. I find tha
Gleb Natapov writes:
> Considering that interrupt remapping is fairly new feature
> are you saying that hotplug (pci and cpu) on x86 is a horrible
> hack on Linux?
Just the current cpu hotplug path.
>> It is better than nothing but it certainly is not something
>> I would expect to work all of
Avi Kivity writes:
> On 06/30/2009 10:08 PM, Eric W. Biederman wrote:
>>> Can you elaborate? For kvm guests, the hardware is reasonably will
>>> implemented
>>> and if not we will fix it. We need not cripple a feature just because some
>>> hardware is broken.
>>>
>>
>> The short version
Avi Kivity writes:
> So the jump-to-vector reset code cannot work on real hardware? It works in
> qemu, but of course that's easy.
In general yes. Nothing regularly uses that path so there is little
point adding a new users if we can avoid it.
Heck there are machines with unreliable cmos.
>>
On 06/30/2009 10:08 PM, Eric W. Biederman wrote:
Can you elaborate? For kvm guests, the hardware is reasonably will implemented
and if not we will fix it. We need not cripple a feature just because some
hardware is broken.
The short version is I don't know what work arounds we will ulti
On Tue, Jun 30, 2009 at 10:00:46AM -0700, Eric W. Biederman wrote:
> Gleb Natapov writes:
>
> > On Tue, Jun 30, 2009 at 12:18:19AM -0700, Yinghai Lu wrote:
> >> how about kexec second kernel in KVM ?
> >>
> >> x2apic_preenabled will be set in second kernel.
> >>
> > By the way anybody knows why
Avi Kivity writes:
> On 06/30/2009 07:44 PM, Eric W. Biederman wrote:
To support that seriously you need interrupt remapping.
>>> Can you explain why?
>>>
>>
>> Because ioapics don't fully function according to spec,
>> and the interrupt code on the hotplug path is a
On Tue, Jun 30, 2009 at 09:44:54AM -0700, Eric W. Biederman wrote:
> Gleb Natapov writes:
>
> > On Tue, Jun 30, 2009 at 02:24:05AM -0700, Eric W. Biederman wrote:
> >> Gleb Natapov writes:
> >>
> >> > KVM would like to provide x2APIC interface to a guest without emulating
> >> > interrupt remap
Antoine Martin wrote:
[]
LINK x86_64-softmmu/qemu-system-x86_64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lpci
What gives?
Is it your system or who's? Why the system does not have a
usable libpci.a is a question for you, not for kvm... I g
On Tue, Jun 30, 2009 at 11:43:41AM -0700, Yinghai Lu wrote:
> 2009/6/30 Gleb Natapov :
>
> >>
> >> how about kexec second kernel in KVM ?
> >>
> >> x2apic_preenabled will be set in second kernel.
> >>
> > Yes, bummer. But the similar problem exist now and without KVM. After
> > running x2apic enab
2009/6/30 Gleb Natapov :
>>
>> how about kexec second kernel in KVM ?
>>
>> x2apic_preenabled will be set in second kernel.
>>
> Yes, bummer. But the similar problem exist now and without KVM. After
> running x2apic enabled kernel you can't kexec kernel without x2apic
> support.
if the first kern
In an attempt to get past unrelated interference I just set up an X
session with only an xterm, used that to launch VNC connecting to my
KVM test host, and tried to launch my test guest again. Same
behavior: Ctl-Alt patterns are ignored, as are any other keystrokes I
try to send to the qemu consol
Hi Huang,
Huang Ying wrote:
- MCE features are initialized when VCPU is intialized according to CPUID.
- A monitor command "mce" is added to inject a MCE.
- A new interrupt mask: CPU_INTERRUPT_MCE is added to inject the MCE.
Can you post some instructions on how to test this functionality?
On Tue, Jun 30, 2009 at 12:11 PM, Michael Jinks wrote:
> I'm rebuilding libsdl with aalib switched off now, will see what happens next.
Small differences:
Over ssh, the console boots with an SDL display, and my xterm window
title set to "caca for ncurses", but it's printing garbage and my
keystr
Gleb Natapov writes:
> On Tue, Jun 30, 2009 at 12:18:19AM -0700, Yinghai Lu wrote:
>> how about kexec second kernel in KVM ?
>>
>> x2apic_preenabled will be set in second kernel.
>>
> By the way anybody knows why kexec does not use BIOS reset code
> (cmos 0xf offset) to jump into new kernel aft
On 06/30/2009 08:00 PM, Eric W. Biederman wrote:
Gleb Natapov writes:
On Tue, Jun 30, 2009 at 12:18:19AM -0700, Yinghai Lu wrote:
how about kexec second kernel in KVM ?
x2apic_preenabled will be set in second kernel.
By the way anybody knows why kexec does not use BIOS re
On 06/30/2009 07:44 PM, Eric W. Biederman wrote:
To support that seriously you need interrupt remapping.
Can you explain why?
Because ioapics don't fully function according to spec,
and the interrupt code on the hotplug path is a horrible
terrible broken hack for ioapics.
It is
On Tue, Jun 30, 2009 at 11:44 AM, Anthony Liguori wrote:
> Avi Kivity wrote:
>>
>
> Sounds like you have SDL configured to use libaa and are running qemu
> without DISPLAY set.
Sure enough, libsdl was built with aalib support...
I could swear I'd tried SDL from a VNC session but when I tried agai
Gleb Natapov writes:
> On Tue, Jun 30, 2009 at 12:18:19AM -0700, Yinghai Lu wrote:
>> how about kexec second kernel in KVM ?
>>
>> x2apic_preenabled will be set in second kernel.
>>
> By the way anybody knows why kexec does not use BIOS reset code
> (cmos 0xf offset) to jump into new kernel aft
On Tue, Jun 30, 2009 at 11:18 AM, Avi Kivity wrote:
> On 06/30/2009 06:35 PM, Michael Jinks wrote:
>>
>> My first hitch was that apparently SDL isn't working properly on my
>> system, because running a console with SDL enabled just prints garbage
>> characters to my xterm.
> I'd start fixing this
Gleb Natapov writes:
> On Tue, Jun 30, 2009 at 02:24:05AM -0700, Eric W. Biederman wrote:
>> Gleb Natapov writes:
>>
>> > KVM would like to provide x2APIC interface to a guest without emulating
>> > interrupt remapping device. The reason KVM prefers guest to use x2APIC
>> > is that x2APIC inter
Avi Kivity wrote:
On 06/30/2009 06:35 PM, Michael Jinks wrote:
Hi List.
I'm taking my first look at KVM, using version 85, on a Gentoo system
with kernel release 2.6.29.
The gist of my problem right now is that I can't figure out how to
access the monitor, and I've tried various things with no
Paul Brook wrote:
IMHO there's little value in just printing a warning. Until it actually goes
away, people are liable to assume we're just being paranoid/awkward and keep
using it anyway.
I suggest crippling it now and, assuming noone steps up to fix+maintain it,
ripping out the write suppor
On 06/30/2009 06:35 PM, Michael Jinks wrote:
Hi List.
I'm taking my first look at KVM, using version 85, on a Gentoo system
with kernel release 2.6.29.
The gist of my problem right now is that I can't figure out how to
access the monitor, and I've tried various things with no luck so far.
My f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
./configure --kerneldir=/usr/src/linux-2.6.29.4 --static
[...]
make
[...]
CCx86_64-softmmu/i386-dis.o
ARx86_64-softmmu/libqemu.a
LINK x86_64-softmmu/qemu-system-x86_64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../../../x86_64-pc-l
On Tue, Jun 30, 2009 at 12:18:19AM -0700, Yinghai Lu wrote:
> how about kexec second kernel in KVM ?
>
> x2apic_preenabled will be set in second kernel.
>
By the way anybody knows why kexec does not use BIOS reset code
(cmos 0xf offset) to jump into new kernel after hard reset?
--
Hi List.
I'm taking my first look at KVM, using version 85, on a Gentoo system
with kernel release 2.6.29.
The gist of my problem right now is that I can't figure out how to
access the monitor, and I've tried various things with no luck so far.
My first hitch was that apparently SDL isn't workin
On Tue, Jun 30, 2009 at 03:21:24PM +0100, Paul Brook wrote:
> > >>> The qcow block driver format is no longer maintained and likely
> > >>> contains
> > >>> serious data corruptors. Urge users to stay away for it, and advertise
> > >>> the new and improved replacement.
> > >
> > > I'm not sure how
> >>> The qcow block driver format is no longer maintained and likely
> >>> contains
> >>> serious data corruptors. Urge users to stay away for it, and advertise
> >>> the new and improved replacement.
> >
> > I'm not sure how I feel about this. Can we prove qcow is broken? Is
> > it only broken
Thanks for all the replies.
I do have the extra hardware, but I am right now not able to put both
together on the guest (i.e. I have to use -vga none while passing
through the nvidia card that I have) because the VGA I am trying to pass
through has an option rom and hw/device-assignment.c complai
On 06/30/2009 02:11 PM, Yolkfull Chow wrote:
Signed-off-by: Yolkfull Chow
---
client/tests/kvm/kvm.py |1 +
client/tests/kvm/kvm_tests.cfg.sample | 56
client/tests/kvm/kvm_tests.py | 93 +
client/tests/kvm/kv
On 06/30/2009 04:32 PM, Anthony Liguori wrote:
Kevin Wolf wrote:
Avi Kivity schrieb:
The qcow block driver format is no longer maintained and likely
contains
serious data corruptors. Urge users to stay away for it, and advertise
the new and improved replacement.
Signed-off-by: Avi Kivity
Anthony Liguori schrieb:
> Kevin Wolf wrote:
>> Avi Kivity schrieb:
>>
>>> The qcow block driver format is no longer maintained and likely contains
>>> serious data corruptors. Urge users to stay away for it, and advertise
>>> the new and improved replacement.
>>>
>>> Signed-off-by: Avi Kivity
Han, Weidong wrote:
Michael Tokarev wrote:
Han, Weidong wrote:
Michael Tokarev wrote:
[]
But how about using it as a "secondary" video card? Like, I can
plug another add-on vga card into a free PCI slot and tell X to
use that one instead of "default" card. Can kvm work like this?
"secondar
Kevin Wolf wrote:
Avi Kivity schrieb:
The qcow block driver format is no longer maintained and likely contains
serious data corruptors. Urge users to stay away for it, and advertise
the new and improved replacement.
Signed-off-by: Avi Kivity
vvfat is using qcow internally, so the wa
On 06/30/2009 03:54 PM, Andre Przywara wrote:
Signed-off-by: Andre Przywara
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index d77fbd8..097ea9f 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -57,6 +5
Amit Shah schrieb:
> On (Mon) Jun 29 2009 [17:04:49], Avi Kivity wrote:
>> The qcow block driver format is no longer maintained and likely contains
>> serious data corruptors. Urge users to stay away for it, and advertise
>> the new and improved replacement.
>
> Does this also print the message a
Signed-off-by: Andre Przywara
---
Documentation/kernel-parameters.txt | 38 +++
1 files changed, 38 insertions(+), 0 deletions(-)
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index d77fbd8..097ea9f 100644
--- a/Document
Michael Tokarev wrote:
> Han, Weidong wrote:
>> Michael Tokarev wrote:
> []
>>> But how about using it as a "secondary" video card? Like, I can
>>> plug another add-on vga card into a free PCI slot and tell X to
>>> use that one instead of "default" card. Can kvm work like this?
>>
>> "secondary
Sheng Yang writes:
> On Friday 26 June 2009 01:24:03 Avi Kivity wrote:
>> The impact of the hotplug changes on device assignment were too
>> difficult for me to fix up during the merge, so I disabled it
>> temporarily. Please take a look at qemu-kvm.git commit a3b371477e3.
>
> When the device as
Han, Weidong wrote:
Michael Tokarev wrote:
[]
But how about using it as a "secondary" video card? Like, I can
plug another add-on vga card into a free PCI slot and tell X to
use that one instead of "default" card. Can kvm work like this?
"secondary" means secondary video card in host, and w
On (Mon) Jun 29 2009 [17:04:49], Avi Kivity wrote:
> The qcow block driver format is no longer maintained and likely contains
> serious data corruptors. Urge users to stay away for it, and advertise
> the new and improved replacement.
Does this also print the message at the time of creating the i
Signed-off-by: Yolkfull Chow
---
client/tests/kvm/kvm.py |1 +
client/tests/kvm/kvm_tests.cfg.sample | 56
client/tests/kvm/kvm_tests.py | 93 +
client/tests/kvm/kvm_vm.py|2 +
4 files changed, 152
We ignore writes to the perfctr msrs. Ignore reads as well.
Kaspersky antivirus crashes Windows guests if it can't read
these MSRs.
Signed-off-by: Amit Shah
---
arch/x86/kvm/x86.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
So, now MSI-X is in upstream qemu. The issue here is that irqchip in
kernel is still unsupported. So here's the plan for qemu-kvm:
1. on next merge from qemu.git to qemu.kvm, virtio net will be broken
2. a quick work-around is to replace this line in hw/apic.c:
msix_supported = 1;
with
Michael Tokarev wrote:
> Han, Weidong wrote:
> []
Currently VGA pass-through is not supported in KVM. It needs much
work to support it.
>>> What does it need?
>>>
>>> Here's what I know of:
>>>
>>> - load the vga bios at 0xc
>>> - implement whatever main bios interfaces the v
On Tue, Jun 30, 2009 at 02:24:05AM -0700, Eric W. Biederman wrote:
> Gleb Natapov writes:
>
> > KVM would like to provide x2APIC interface to a guest without emulating
> > interrupt remapping device. The reason KVM prefers guest to use x2APIC
> > is that x2APIC interface is better virtualizable a
Gleb Natapov writes:
> KVM would like to provide x2APIC interface to a guest without emulating
> interrupt remapping device. The reason KVM prefers guest to use x2APIC
> is that x2APIC interface is better virtualizable and provides better
> performance than mmio xAPIC interface:
>
> - msr exits a
Han, Weidong wrote:
[]
Currently VGA pass-through is not supported in KVM. It needs much
work to support it.
What does it need?
Here's what I know of:
- load the vga bios at 0xc
- implement whatever main bios interfaces the vga vios expects
- pass through the vga I/O ports
Anything else
On Wed, Jun 17, 2009 at 2:59 AM, Lucas Meneghel Rodrigues
wrote:
> Adding iperf network performance test. Basically it tests
> networking functionality, stability and performance of guest OSes.
> This test is cross-platform -- i.e. it works on both Linux and
> Windows VMs.
>
I have a question her
Avi Kivity schrieb:
> The qcow block driver format is no longer maintained and likely contains
> serious data corruptors. Urge users to stay away for it, and advertise
> the new and improved replacement.
>
> Signed-off-by: Avi Kivity
vvfat is using qcow internally, so the warning will appear th
On Tue, Jun 30, 2009 at 12:18:19AM -0700, Yinghai Lu wrote:
> On Mon, Jun 29, 2009 at 11:45 PM, Gleb Natapov wrote:
> > KVM would like to provide x2APIC interface to a guest without emulating
> > interrupt remapping device. The reason KVM prefers guest to use x2APIC
> > is that x2APIC interface is
Avi Kivity redhat.com> writes:
> 2.6.27 has kvmclock.
>
Thanks a lot!
Will try the kvmclock
Eran
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Avi Kivity wrote:
> On 06/30/2009 09:16 AM, Han, Weidong wrote:
>> Subash Kalbarga wrote:
>>
>>> Hi
>>>
>>> I am using kvm-86 on 2.6.28 and I am able to pass through most of my
>>> PCI devices successfully. However, I do not see even the KVM BIOS
>>> output if I pass through my VGA adapter. I am
On Mon, Jun 29, 2009 at 11:45 PM, Gleb Natapov wrote:
> KVM would like to provide x2APIC interface to a guest without emulating
> interrupt remapping device. The reason KVM prefers guest to use x2APIC
> is that x2APIC interface is better virtualizable and provides better
> performance than mmio xAP
80 matches
Mail list logo
