On Wed, Apr 23, 2008 at 10:40 AM, [EMAIL PROTECTED] wrote:
Hi,
I'm trying libvirt-0.4.2, it should support initiating guest shutdown for
KVM domains. But for some reason it doesn't work for me, I'm using linux
guests with external kernel, if I run poweroff from within the domain, it
On Tue, Apr 22, 2008 at 1:10 PM, Avi Kivity [EMAIL PROTECTED] wrote:
Damjan wrote:
I have some questions for the FAQ, about the configuration of Linux guests:
a) is swap needed in the guest (I'd say no, but..)
b) what filesystem is best for a guest
c) what io scheduler in the guest
On Tue, Apr 22, 2008 at 4:15 PM, Anthony Liguori [EMAIL PROTECTED] wrote:
This patch changes virtio devices to be multi-function devices whenever
possible. This increases the number of virtio devices we can support now by
a factor of 8.
[...]
diff --git a/qemu/hw/virtio.c
On Dec 7, 2007 7:38 PM, Anthony Liguori [EMAIL PROTECTED] wrote:
Izik Eidus wrote:
Anthony Liguori wrote:
Glauber de Oliveira Costa wrote:
Currently, the -kernel option is not working.
Reason is, because we're registering chunks for regions 0-0xa and
0x10-ram_size, the
On Nov 13, 2007 11:42 PM, Dor Laor [EMAIL PROTECTED] wrote:
Anthony Liguori wrote:
I've been experimenting with creating IO threads for the PV device
drivers. Unfortunately, my experiments haven't gotten very far as QEMU
tends to hang up a bit into booting the guest whenever I spawn a
On 11/5/07, Elmar Haneke [EMAIL PROTECTED] wrote:
What problems are the cause for recommending to emulate NE2K hardware?
Vista expects that the correct frame checksum is calculated for
inbound packets; the emulated card didn't do that.
Is this still valid fpr KVM-50?
It was fixed in QEMU CVS
On 10/29/07, Denys Duchier [EMAIL PROTECTED] wrote:
qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests
(confirmed
by danieldg on irc), but it works for 64bit guests and it works for linux
2.6.22
x86 guests. I tried kvm-45 and kvm-49. -no-kvm does not help.
Try acpi=force
Il Sun, Sep 09, 2007 at 03:51:20PM +0300, Avi Kivity ha scritto:
Luca Tettamanti wrote:
Actually 0xfff2 is in the middle of an instruction.
I'm guessing an 'out' instruction triggered the reboot, and
skip_emulated_instruction() added 2 to rip.
I think you're right; the reset
Hi,
while debugging a program with GDB I got a GPF which seems related to
KVM. Note that I was *not* using the debugger inside the guest nor on
the virtual machine. The target was an unrelated userspace program.
This is the GPF:
general protection fault: [#1]
PREEMPT SMP
Modules linked in:
Il Mon, Aug 20, 2007 at 10:58:57AM +0300, Avi Kivity ha scritto:
Luca Tettamanti wrote:
In order to reactivate the CPU after the reset. When the guest reboots I
get an unhandled vm exit:
unhandled vm exit: 0x8021
rax rbx rcx rdx
Hi,
I just got this warning when doing a 'rmmod kvm-intel':
=
[ INFO: inconsistent lock state ]
2.6.23-rc3-libata-g28e8351a-dirty #93
-
inconsistent {hardirq-on-W} - {in-hardirq-W} usage.
udevd/2800 [HC1[1]:SC0[0]:HE0:SE1] takes:
Mark Bidewell ha scritto:
On 8/24/07, Luca [EMAIL PROTECTED] wrote:
On 8/25/07, Mark Bidewell [EMAIL PROTECTED] wrote:
When building kvm-36 with the latest Fedora kernel I get the error:
kvmctl.c: In function 'kvm_run':
kvmctl.c:1046: error: 'KVM_EXIT_SET_TPR' undeclared (first
Avi Kivity ha scritto:
Luca Tettamanti wrote:
At 1000Hz:
QEMU
hpet5.5%
dynticks 11.7%
KVM
hpet3.4%
dynticks7.3%
No surprises here, you can see the additional 1k syscalls per second.
This is very surprising to me. The 6.2% difference
Il Sun, Aug 19, 2007 at 10:31:26PM +0300, Avi Kivity ha scritto:
Luca wrote:
On 8/19/07, Luca Tettamanti [EMAIL PROTECTED] wrote:
+static uint64_t qemu_next_deadline(void) {
+uint64_t nearest_delta_us = ULLONG_MAX;
+uint64_t vmdelta_us;
Hum, I introduced a bug
Il Sun, Aug 19, 2007 at 10:36:06AM +0300, Avi Kivity ha scritto:
Luca wrote:
On 8/13/07, Avi Kivity [EMAIL PROTECTED] wrote:
Luca Tettamanti wrote:
The patch stops the unhandled wrmsr, but reboot is still not working
(guest is stuck using 100% of the CPU). The last working
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and
expands the alarm timer handling in QEMU. Patches have been rebased on QEMU
CVS.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
#ifdefs to handle different timers scattered all over the
in the
same way as the RTC timer.
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
vl.c | 57 -
1 file changed, 56 insertions(+), 1 deletion(-)
Index: qemu/vl.c
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
vl.c | 72 +++
1 file changed, 72 insertions
]
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
configure |5 ++
vl.c | 149 +++---
2 files changed, 148 insertions(+), 6 deletions(-)
Index: qemu/vl.c
in the
same way as the RTC timer.
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
qemu/vl.c | 57 ++-
1 files changed, 56 insertions(+), 1 deletions(-)
diff --git a/qemu/vl.c b/qemu/vl.c
index f0b4896..0373beb 100644
--- a/qemu/vl.c
+++ b/qemu
]
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
qemu/configure |5 ++
qemu/vl.c | 149 --
2 files changed, 148 insertions(+), 6 deletions(-)
diff --git a/qemu/configure b/qemu/configure
index 365b7fb..38373db 100755
--- a/qemu/configure
Make the alarm code modular, removing #ifdef from the generic code and
abstract a common interface for all the timer. The result is functionally
equivalent to the old code.
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
qemu/vl.c | 292
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and
expands
the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree,
but I think I can rebase it to QEMU svn if desired.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
---
qemu/vl.c | 90 --
1 files changed, 72 insertions(+), 18
Fix a few trivial warnings:
- use %zu when printing size_t arguments in printf
- include qemu-kvm.h where appropriate
- change the return type of kvm_eat_signals
Signed-Off-By: Luca Tettamanti [EMAIL PROTECTED]
---
qemu/hw/apic.c |4
qemu/migration.c |8
Il Mon, Aug 13, 2007 at 05:42:55PM +0300, Dan Kenigsberg ha scritto:
Dynamic ticks in Qemu: have a SIGALRM generated only when it is
needed, instead of every 1 millisecond. This patch requires that the
host supports high resolution timers, since it arms a POSIX timer to the
nearest Qemu
Il Sun, Aug 12, 2007 at 12:26:15PM -0700, Izik Eidus ha scritto:
this is a request for comment for patchs that allow kvm to run with more than
2 giga.
there are 4 patchs.
the first patch(biospatch): is for the bios:now the bios know how to map
memory about the 0xf000-0x hole.
(sorry for the double post - I mistyped the address of the list)
Hi Uri, Avi,
I think I debugged the
kvm: unhandled wrmsr: 0xc083
on guest reboot with recent KVM userspace.
The root cause is this commit from Uri:
commit 5e1accfc9e7a7d79244c862c04621f7ba23c6d38
Author: Uri Lublin [EMAIL
Il Tue, Aug 07, 2007 at 02:08:08PM +0200, Luca ha scritto:
On 8/7/07, Dor Laor [EMAIL PROTECTED] wrote:
Luca claims the HPET intefer the RTC. Can it be disabled? ( I know some
new chipsets implement rtc using HPET).
Basically HPET can operate in legacy mode - where it uses the same IRQ
(don't top post)
Il Thu, Jul 12, 2007 at 03:56:07PM +0300, David Shwatrz ha scritto:
Hello,
And I just want to add some info :
running :
brctl show
gives:
bridge name bridge id STP enabled interfaces
virbr0 8000. no
which means that
and perform the writeback stage in the emulation unless
it's explicitly disabled (currently push and some 2 bytes instructions
may disable the writeback).
Signed-Off-By: Luca Tettamanti [EMAIL PROTECTED]
---
Tested with Fedora7, Solaris10 and WinXP on a 32 bit host with Intel
CPU.
drivers/kvm
Il Mon, Jun 18, 2007 at 02:32:39PM +0300, Avi Kivity ha scritto:
Unfortunately, this kills Windows XP (first run with a guest crash,
second with a host oops), so I reverted it. I'd guess some operation
which doesn't need writeback ends up in the modified code.
Previously, the check
Il Sat, Jun 16, 2007 at 10:43:23AM +0300, Avi Kivity ha scritto:
Luca Tettamanti wrote:
Il Fri, Jun 15, 2007 at 12:06:50PM +0300, Avi Kivity ha scritto:
After a bit of thinking: it's correct but removes an optimization;
furthermore it may miss other instructions that write to memory
and always perform the writeback stage in the
emulation.
Signed-Off-By: Luca Tettamanti [EMAIL PROTECTED]
---
drivers/kvm/x86_emulate.c | 60 +++-
1 file changed, 29 insertions(+), 31 deletions(-)
diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm
When writing to normal memory and the memory area is unchanged the write
can be safely skipped, avoiding the costly kvm_mmu_pte_write.
Signed-Off-By: Luca Tettamanti [EMAIL PROTECTED]
---
drivers/kvm/kvm_main.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Il Fri, Jun 15, 2007 at 12:06:50PM +0300, Avi Kivity ha scritto:
After a bit of thinking: it's correct but removes an optimization;
furthermore it may miss other instructions that write to memory mapped
areas.
A more proper fix should be force the writeback if dst.ptr is in some
kind of
Il Thu, Jun 14, 2007 at 11:26:29AM +0300, Avi Kivity ha scritto:
Luca Tettamanti wrote:
With GOOD_APIC apic_read_around is a nop, while apic_write_around is a
normal write. With !GOOD_APIC apic_write_around writes to the APIC reg
using xchg. With !GOOD_APIC and this patch:
--- include/asm
Il Fri, Jun 15, 2007 at 12:53:24AM +0200, Luca Tettamanti ha scritto:
Il Thu, Jun 14, 2007 at 11:26:29AM +0300, Avi Kivity ha scritto:
Luca Tettamanti wrote:
With GOOD_APIC apic_read_around is a nop, while apic_write_around is a
normal write. With !GOOD_APIC apic_write_around writes
Il Mon, Jun 11, 2007 at 10:44:45AM +0300, Avi Kivity ha scritto:
Luca wrote:
I've managed to reproduce this on kvm-21 (it takes many boots for this
to happen, but it does eventually).
Hum, any clue on the cause?
From what I've seen, it's the new Linux clocksource code.
Should I
Hi,
Il Mon, Jun 04, 2007 at 12:35:37PM +0300, Avi Kivity ha scritto:
Luca Tettamanti wrote:
Hello,
my kernel just exploded :)
The host is running 2.6-git-current, with KVM modules from KVM-27
package. kernel is 32bit, SMP, with PREEMPT enabled, no HIGHMEM (but I'm
using
Hello,
I'm testing the new Fedora7 under KVM. As you may know Fedora has
migrated to the new libata drivers.
ata_piix is unhappy with the PIIX IDE controller provided by QEmu/KVM:
libata version 2.20 loaded.
ata_piix :00:01.1: version 2.10ac1
PCI: Setting latency timer of device :00:01.1
Il Mon, Jun 04, 2007 at 11:51:10PM +0300, Avi Kivity ha scritto:
While doing repeated tests with the installer I ran into another
(unrelated) problem. Sometimes the guest kernel hangs at boot at:
NET: Registered protocol family 2
with any kind of networking options (except for -net
Hello,
my kernel just exploded :)
The host is running 2.6-git-current, with KVM modules from KVM-27
package. kernel is 32bit, SMP, with PREEMPT enabled, no HIGHMEM (but I'm
using CONFIG_VMSPLIT_3G_OPT=y). The CPU is a Core2 (hence I'm using
kvm-intel).
Guest was a Fedora7 setup DVD, which died
be actually on a
differnt node, no?
Singed-Off-By: Luca Tettamanti [EMAIL PROTECTED]
---
drivers/kvm/vmx.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index d0a2c2d..4d088a0 100644
--- a/drivers/kvm/vmx.c
+++ b/drivers/kvm
44 matches
Mail list logo
