On 02/16/2011 09:54 PM, --[ UxBoD ]-- wrote:
Hello all,
I believe I am hitting a problem on one of our Windows 2003 KVM guests were I
believe it is running out of Entropy and causing SSL issues.
I see that there is a module called virtio-rng which I believe passes the HW
entropy source
On 02/16/2011 03:34 PM, Anthony Liguori wrote:
On 02/16/2011 04:24 AM, Avi Kivity wrote:
On 02/16/2011 01:13 AM, Anthony Liguori wrote:
On 02/15/2011 10:26 AM, Chris Wright wrote:
QAPI and QMP
- Anthony adding a new wiki page to describe all of this
http://wiki.qemu.org/Features/QAPI
[
On 02/16/2011 06:51 PM, Marcelo Tosatti wrote:
On Wed, Feb 16, 2011 at 11:01:47AM +0200, Avi Kivity wrote:
On 02/15/2011 10:36 PM, Marcelo Tosatti wrote:
On Mon, Feb 14, 2011 at 04:42:16PM +0200, Avi Kivity wrote:
Short-circuit an STI; HLT sequence while an interrupt is pending:
On 02/16/2011 05:17 PM, Nadav Har'El wrote:
Hi, In the recent KVM forum, Marcelo Tosatti presented some KVM performance
improvements. One of them (page 17 of the presentation) was about the MSRs
used by SYSCALL: MSR_STAR, MSR_LSTAR, MSR_CSTAR (and also MSR_SYSCALL_MASK).
He said that Guests
On Thu, 2011-02-17 at 11:11 +0200, Avi Kivity wrote:
On 02/16/2011 09:54 PM, --[ UxBoD ]-- wrote:
Hello all,
I believe I am hitting a problem on one of our Windows 2003 KVM guests were
I believe it is running out of Entropy and causing SSL issues.
I see that there is a module called
On Thu, Feb 17, 2011, Avi Kivity wrote about Re: Why exit on MSR_STAR and
friends?:
It isn't needed. The code doesn't distinguish between the read and
write bitmaps, and so far no guest issues rdmsr for these msrs with any
frequency (kvm as a guest will write those msrs, but it shouldn't
On 02/17/2011 12:09 PM, Vadim Rozenfeld wrote:
On Thu, 2011-02-17 at 11:11 +0200, Avi Kivity wrote:
On 02/16/2011 09:54 PM, --[ UxBoD ]-- wrote:
Hello all,
I believe I am hitting a problem on one of our Windows 2003 KVM guests were I
believe it is running out of Entropy and causing SSL
On 02/17/2011 12:29 PM, Nadav Har'El wrote:
I guess I should be more worried why I got all these PIOs in L2 in the
first place - the MSR reads and writes in L1 were just an odd consequence
of that. It turns out that the ping -f workload I was running in L2
insisted to get accurate timings of
Hello,
I tried to install Windows 7 Professional 64 Bit with VirtIO 1.16 on an Debian
based system using AMD64 CPUs. During the install, the system froze (progress
bar didn't advance) and kvm was slowly eating CPU cycles on the host.
$ dpkg-query -W libvirt0 qemu-kvm linux-image-`uname -r`
On Thu, 2011-02-17 at 12:37 +0200, Dor Laor wrote:
On 02/17/2011 12:09 PM, Vadim Rozenfeld wrote:
On Thu, 2011-02-17 at 11:11 +0200, Avi Kivity wrote:
On 02/16/2011 09:54 PM, --[ UxBoD ]-- wrote:
Hello all,
I believe I am hitting a problem on one of our Windows 2003 KVM guests
were I
On Thu, Feb 17, 2011 at 10:44 AM, Philipp Hahn h...@univention.de wrote:
Hello,
I tried to install Windows 7 Professional 64 Bit with VirtIO 1.16 on an Debian
based system using AMD64 CPUs. During the install, the system froze (progress
bar didn't advance) and kvm was slowly eating CPU cycles
On Thu, Feb 17, 2011 at 11:30:25AM +, Stefan Hajnoczi wrote:
On Thu, Feb 17, 2011 at 10:44 AM, Philipp Hahn h...@univention.de wrote:
Hello,
I tried to install Windows 7 Professional 64 Bit with VirtIO 1.16 on an
Debian
based system using AMD64 CPUs. During the install, the system
On 02/17/2011 03:26 AM, Avi Kivity wrote:
On 02/16/2011 03:34 PM, Anthony Liguori wrote:
On 02/16/2011 04:24 AM, Avi Kivity wrote:
On 02/16/2011 01:13 AM, Anthony Liguori wrote:
On 02/15/2011 10:26 AM, Chris Wright wrote:
QAPI and QMP
- Anthony adding a new wiki page to describe all of this
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
reject unencodable strings).
While QEMU is mostly ASCII internally, for the purposes of the JSON
parser, we always encode and decode UTF-8. We reject invalid UTF-8
sequences. But
kvm_stat currently tracks both tracepoints, and also kvm_exit by exit reason.
This is somewhat cluttered and also very expensive with the current
kernel filter implementation.
Make drilldown optional by adding a key to trigger it.
Avi Kivity (4):
kvm_stat: move groups and events into well
Signed-off-by: Avi Kivity a...@redhat.com
---
kvm/kvm_stat |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/kvm/kvm_stat b/kvm/kvm_stat
index 371e547..2e1fe73 100755
--- a/kvm/kvm_stat
+++ b/kvm/kvm_stat
@@ -245,6 +245,12 @@ class Event(object):
import
Signed-off-by: Avi Kivity a...@redhat.com
---
kvm/kvm_stat | 107 +++--
1 files changed, 66 insertions(+), 41 deletions(-)
diff --git a/kvm/kvm_stat b/kvm/kvm_stat
index f8a1399..371e547 100755
--- a/kvm/kvm_stat
+++ b/kvm/kvm_stat
@@ -201,12
Signed-off-by: Avi Kivity a...@redhat.com
---
kvm/kvm_stat | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/kvm/kvm_stat b/kvm/kvm_stat
index 2e1fe73..e3e9def 100755
--- a/kvm/kvm_stat
+++ b/kvm/kvm_stat
@@ -265,10 +265,11 @@ class TracepointProvider(object):
On (Wed) 16 Feb 2011 [08:41:27], Anthony Liguori wrote:
On 02/16/2011 08:39 AM, Amit Shah wrote:
On (Tue) 15 Feb 2011 [17:13:13], Anthony Liguori wrote:
On 02/15/2011 10:26 AM, Chris Wright wrote:
revisit new - old migration
- Amit offers virtio-serial patches and some legwork
So, to me,
Pressing 'x' enables drilldown into kvm_exit reasons. Pressing it
again reverts to normal behaviour.
Signed-off-by: Avi Kivity a...@redhat.com
---
kvm/kvm_stat | 26 ++
1 files changed, 22 insertions(+), 4 deletions(-)
diff --git a/kvm/kvm_stat b/kvm/kvm_stat
index
On Thu, 2011-02-17 at 13:41 +0200, Gleb Natapov wrote:
On Thu, Feb 17, 2011 at 11:30:25AM +, Stefan Hajnoczi wrote:
On Thu, Feb 17, 2011 at 10:44 AM, Philipp Hahn h...@univention.de wrote:
Hello,
I tried to install Windows 7 Professional 64 Bit with VirtIO 1.16 on an
Debian
On 02/17/2011 06:23 AM, Avi Kivity wrote:
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
reject unencodable strings).
While QEMU is mostly ASCII internally, for the purposes of the JSON
parser, we always encode and decode
On 02/17/2011 03:10 PM, Anthony Liguori wrote:
On 02/17/2011 06:23 AM, Avi Kivity wrote:
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
reject unencodable strings).
While QEMU is mostly ASCII internally, for the purposes of the
On 02/17/2011 07:25 AM, Avi Kivity wrote:
On 02/17/2011 03:10 PM, Anthony Liguori wrote:
On 02/17/2011 06:23 AM, Avi Kivity wrote:
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
reject unencodable strings).
While QEMU is
On 02/17/2011 07:25 AM, Avi Kivity wrote:
On 02/17/2011 03:10 PM, Anthony Liguori wrote:
On 02/17/2011 06:23 AM, Avi Kivity wrote:
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
reject unencodable strings).
While QEMU is
On 17 February 2011 13:37, Anthony Liguori anth...@codemonkey.ws wrote:
An application has to explicitly support an encoding. It is not
transparent. UCS2/UTF-16 means that strings are not 'const char *'s but
'const wchar_t *' where typedef unsigned short wchar_t;.
QEMU assumes, in lots of
On 02/17/2011 07:59 AM, Peter Maydell wrote:
On 17 February 2011 13:37, Anthony Liguorianth...@codemonkey.ws wrote:
An application has to explicitly support an encoding. It is not
transparent. UCS2/UTF-16 means that strings are not 'const char *'s but
'const wchar_t *' where typedef
On 02/17/2011 03:37 PM, Anthony Liguori wrote:
On 02/17/2011 07:25 AM, Avi Kivity wrote:
On 02/17/2011 03:10 PM, Anthony Liguori wrote:
On 02/17/2011 06:23 AM, Avi Kivity wrote:
On 02/17/2011 02:12 PM, Anthony Liguori wrote:
(btw what happens in a non-UTF-8 locale? I guess we should just
On Thu, Feb 17, 2011 at 12:45 PM, Vadim Rozenfeld vroze...@redhat.com wrote:
On Thu, 2011-02-17 at 13:41 +0200, Gleb Natapov wrote:
On Thu, Feb 17, 2011 at 11:30:25AM +, Stefan Hajnoczi wrote:
On Thu, Feb 17, 2011 at 10:44 AM, Philipp Hahn h...@univention.de wrote:
Hello,
I tried
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-stub.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/kvm-stub.c b/kvm-stub.c
index caef9b4..fc2b810 100644
--- a/kvm-stub.c
+++ b/kvm-stub.c
@@ -137,7 +137,6 @@ int kvm_set_ioeventfd_mmio_long(int fd, uint32_t
On Thu, 2011-02-17 at 14:26 +, Stefan Hajnoczi wrote:
On Thu, Feb 17, 2011 at 12:45 PM, Vadim Rozenfeld vroze...@redhat.com wrote:
On Thu, 2011-02-17 at 13:41 +0200, Gleb Natapov wrote:
On Thu, Feb 17, 2011 at 11:30:25AM +, Stefan Hajnoczi wrote:
On Thu, Feb 17, 2011 at 10:44 AM,
Hello,
Am Donnerstag 17 Februar 2011 13:45:34 schrieb Vadim Rozenfeld:
On Thu, 2011-02-17 at 13:41 +0200, Gleb Natapov wrote:
Why is is linked to virtio? Does install on ide work?
Yes, works without the VirtIO block driver using IDE.
Does install work
without -no-kvm-irqchip (which had
On Thu, 2011-02-17 at 16:27 +0100, Philipp Hahn wrote:
Hello,
Am Donnerstag 17 Februar 2011 13:45:34 schrieb Vadim Rozenfeld:
On Thu, 2011-02-17 at 13:41 +0200, Gleb Natapov wrote:
Why is is linked to virtio? Does install on ide work?
Yes, works without the VirtIO block driver using
On Thu, Feb 17, 2011 at 11:12:43AM +0200, Avi Kivity wrote:
index ee1cd1a..541da0e 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -3437,6 +3437,15 @@ static int handle_interrupt_window(struct
kvm_vcpu *vcpu)
static int handle_halt(struct kvm_vcpu
On Tue, Feb 15, 2011 at 09:23:32AM +0100, Jan Kiszka wrote:
The current way of injecting MCE events without updating of and
synchronizing with the CPUState is broken and causes spurious
corruptions of the MCE-related parts of the CPUState.
Can you explain how? The current pronlem with MCE is
On 2011-02-17 17:35, Marcelo Tosatti wrote:
On Tue, Feb 15, 2011 at 09:23:32AM +0100, Jan Kiszka wrote:
The current way of injecting MCE events without updating of and
synchronizing with the CPUState is broken and causes spurious
corruptions of the MCE-related parts of the CPUState.
Can you
Currently 'include' is only allowed when parsing a file. This patch allows it
to be used when parsing a string as well.
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_config.py |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_config.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/client/tests/kvm/kvm_config.py b/client/tests/kvm/kvm_config.py
index 27c3171..60df208 100755
--- a/client/tests/kvm/kvm_config.py
+++
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_config.py |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/client/tests/kvm/kvm_config.py b/client/tests/kvm/kvm_config.py
index 60df208..a125129 100755
--- a/client/tests/kvm/kvm_config.py
+++
This allows to quickly see the effect of some extra code, e.g.
./kvm_config.py tests.cfg only my_set no qcow2
The given strings may contain newlines.
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_config.py |7 ++-
1 files changed, 6 insertions(+), 1
On Thu, Feb 17, 2011 at 06:06:19PM +0100, Jan Kiszka wrote:
On 2011-02-17 17:35, Marcelo Tosatti wrote:
On Tue, Feb 15, 2011 at 09:23:32AM +0100, Jan Kiszka wrote:
The current way of injecting MCE events without updating of and
synchronizing with the CPUState is broken and causes spurious
On 2011-02-17 18:55, Marcelo Tosatti wrote:
@@ -1375,10 +1413,25 @@ static int kvm_put_vcpu_events(CPUState *env, int
level)
return 0;
}
-events.exception.injected = (env-exception_injected = 0);
-events.exception.nr = env-exception_injected;
-
On Tue, Feb 15, 2011 at 09:23:33AM +0100, Jan Kiszka wrote:
This switches KVM's MCE injection path to cpu_x86_inject_mce, both for
SIGBUS and monitor initiated events. This means we prepare the MCA MSRs
in the VCPUState also for KVM.
We have to drop the MSRs writeback restrictions for this
On 2011-02-17 19:08, Marcelo Tosatti wrote:
On Tue, Feb 15, 2011 at 09:23:33AM +0100, Jan Kiszka wrote:
This switches KVM's MCE injection path to cpu_x86_inject_mce, both for
SIGBUS and monitor initiated events. This means we prepare the MCA MSRs
in the VCPUState also for KVM.
We have to
On Thu, Feb 17, 2011 at 07:04:51PM +0100, Jan Kiszka wrote:
Should not manipulate mp_state of a running vcpu (should only do that
for migration when vcpu is stopped), since its managed by the kernel,
for irqchip case.
Not for asynchronously injected MCEs. The target CPU would simply
On 01/24/2011 03:02 AM, Marcelo Tosatti wrote:
The following changes since commit b646968336d4180bdd7d2e24209708dcee6ba400:
checkpatch: adjust to QEMUisms (2011-01-20 20:58:56 +)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Jan
i`ve got a question about pci passthrogh of 2 pci devices (2x DVB-S2
PCI cards with Saa7146 PCI Bridge from Technotrend: S2-3200).
I am using squeeze with a 2.6.37 selfcompiled Kernel. I want to
passthrough both devices to a virtual machine (Win7) an get problems.
If i passthrough
On 2011-02-07 12:19, Jan Kiszka wrote:
We do not check them, and the only arch with non-empty implementations
always returns 0 (this is also true for qemu-kvm).
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
CC: Alexander Graf ag...@suse.de
---
kvm.h |5 ++---
I extracted some WindowsXPpro VM PCI data with pcitree - maybe this gives you a
hint:
IRQ Mapping:
INT line 0 -
INT line 1 -
INT line 2 -
INT line 3 -
INT line 4 -
INT line 5 - 5-A(0.3.0)1000.1AF45-A(0.7.0)7146.1131
INT line 6 -
INT line 7 -
INT line 8 -
INT line 9 -
https://bugzilla.kernel.org/show_bug.cgi?id=29232
Rafael J. Wysocki r...@sisk.pl changed:
What|Removed |Added
CC||flor...@mickler.org,
The Buildbot has detected a new failure of disable_kvm_x86_64_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_debian_5_0/builds/745
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of disable_kvm_i386_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_debian_5_0/builds/746
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of disable_kvm_x86_64_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_out_of_tree/builds/694
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of disable_kvm_i386_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_out_of_tree/builds/694
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
Hello,
Some update on this issue, archive:
http://www.mail-archive.com/kvm@vger.kernel.org/msg32600.html
Seems to be that cirrus VGA is now ok (1000MB/s up to 2000MB/s). But
cirrus has only 320x200x256colors (Mode 13h) mode implemented in VESA
BIOS.
VMWare and std VGA still have the
55 matches
Mail list logo
