From: Avi Kivity a...@redhat.com
Conflicts:
qemu/Makefile.target
qemu/hw/cirrus_vga.c
qemu/hw/ide.c
qemu/pc-bios/bios.bin
qemu/vl.c
Signed-off-by: Avi Kivity a...@redhat.com
--
To unsubscribe from this list: send the line unsubscribe kvm-commits in
the
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/kernel/external-module-compat-comm.h
b/kernel/external-module-compat-comm.h
index 5cb70b0..981dc96 100644
--- a/kernel/external-module-compat-comm.h
+++ b/kernel/external-module-compat-comm.h
@@ -613,6
From: Sheng Yang sh...@linux.intel.com
The vtd.c has renamed to iommu.c, and config option has changed to
CONFIG_IOMMU_API.
Notice now the host kernel before 2.6.29 can't work with VT-d due to API
changed... At least this patch enabled building with host kernel before 2.6.29
with CONFIG_DMAR.
Bugs item #2528121, was opened at 2009-01-22 10:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2528121group_id=180599
Please note that this message will contain a full copy of
Hello Avi,
here are small fixes for KVM on s390:
1. Fix printk on SIGP set arch
2. Fix problem state check for b2 intercepts
3. Fix SIGP set prefix ioctl
I dont think any of the fixes is critical, but patch 1 allows a malicious
guest to flood the host dmesg. Therefore, I want to push patch 1
From: Christian Borntraeger borntrae...@de.ibm.com
The kernel handles some priviledged instruction exits. While I was
unable to trigger such an exit from guest userspace, the code should
check for supervisor state before emulating a priviledged instruction.
I also renamed kvm_s390_handle_priv to
From: Christian Borntraeger borntrae...@de.ibm.com
This patch fixes the SET PREFIX interrupt if triggered by userspace.
Until now, it was not necessary, but life migration will need it. In
addition, it helped me creating SMP support for my kvm_crashme tool
(lets kvm execute random guest memory
From: Christian Borntraeger borntrae...@de.ibm.com
KVM on s390 does not support the ESA/390 architecture. We refuse to
change the architecture mode and print a warning. While testing a
crashme for kvm, I spotted two problems with the printk:
o A malicious can flood host dmesg
o There was no
On Thu, 22 Jan 2009 10:27:38 +0100
Christian Borntraeger borntrae...@de.ibm.com wrote:
KVM on s390 does not support the ESA/390 architecture. We refuse to
change the architecture mode and print a warning. While testing a
crashme for kvm, I spotted two problems with the printk:
o A
Am Thu, 22 Jan 2009 12:17:07 +0100
schrieb heica...@linux.vnet.ibm.com:
Why don't you just remove the printk? IMHO it's rather pointless.
It is'nt: It infoms the user why his guest is going to crash
even though it has performed an operation that is perfectly
legal according to the spec.
--
To
On (Thu) Jan 22 2009 [10:27:38], Christian Borntraeger wrote:
From: Christian Borntraeger borntrae...@de.ibm.com
KVM on s390 does not support the ESA/390 architecture. We refuse to
change the architecture mode and print a warning. While testing a
crashme for kvm, I spotted two problems with
On Thu, 22 Jan 2009 12:26:11 +0100
Carsten Otte co...@de.ibm.com wrote:
Am Thu, 22 Jan 2009 12:17:07 +0100
schrieb heica...@linux.vnet.ibm.com:
Why don't you just remove the printk? IMHO it's rather pointless.
It is'nt: It infoms the user why his guest is going to crash
even though it has
Heiko Carstens wrote:
On Thu, 22 Jan 2009 12:26:11 +0100
Carsten Otte co...@de.ibm.com wrote:
Am Thu, 22 Jan 2009 12:17:07 +0100
schrieb heica...@linux.vnet.ibm.com:
Why don't you just remove the printk? IMHO it's rather pointless.
It is'nt: It infoms the user why his guest is
Sheng Yang wrote:
The vtd.c has renamed to iommu.c, and config option has changed to
CONFIG_IOMMU_API.
Notice now the host kernel before 2.6.29 can't work with VT-d due to API
changed... At least this patch enabled building with host kernel before 2.6.29
with CONFIG_DMAR.
Applied, thanks.
Alex Williamson wrote:
This is an attempt to improve the latency of virtio-net while not hurting
throughput. I wanted to try moving packet TX into a different thread
so we can quickly return to the guest after it kicks us to send packets
out. I also switched the order of when the tx_timer
Am Thu, 22 Jan 2009 13:58:57 +0200
schrieb Avi Kivity a...@redhat.com:
Right, either inject an exception to the guest (if appropriate for the
arch), or return -ESOMETHING from ioctl(KVM_RUN).
Yea that's what we do. We let userland handle the intercept,
and there we let the guest die gracefully
On Thu, 2009-01-22 at 14:12 +0200, Avi Kivity wrote:
My worry with this change is that increases cpu utilization even more
than it increases bandwidth, so that our bits/cycle measure decreases.
Yep, agreed it's important to watch out for this.
The descriptors (and perhaps data) are
Marcelo Tosatti wrote:
On Wed, Jan 21, 2009 at 01:11:23PM +0800, Sheng Yang wrote:
Use ktime_to_ns() macro is better.
The remaining parts are fine with me. But please do more test. :)
Thanks for work!
Alexander, can you please confirm this works for you, thanks.
KVM: x86: fix
Am Thursday 22 January 2009 12:58:57 schrieb Avi Kivity:
Right, either inject an exception to the guest (if appropriate for the
arch), or return -ESOMETHING from ioctl(KVM_RUN).
Ok. What about:
[PATCH] kvm-s390: fix printk on SIGP set arch
From: Christian Borntraeger borntrae...@de.ibm.com
Hello Iam using kvm83 on CentOS5.2
my system has 2x dual Core intel CPU
Intel(R) Xeon(R) CPU5110 @ 1.60GHz
asdetected by Centos.
If I start kvm-qemu with no CPU option everythign works and hte guest
machine detects cpu as
QEMU Virtual CPU version 0.9.1
iv I run qemu-kvm -cpu
Mark McLoughlin wrote:
Hi Alex,
On Wed, 2009-01-21 at 16:08 -0700, Alex Williamson wrote:
This is an attempt to improve the latency of virtio-net while not hurting
throughput. I wanted to try moving packet TX into a different thread
so we can quickly return to the guest after it kicks us
(copying Anthony this time)
Mark McLoughlin wrote:
Hi Alex,
On Wed, 2009-01-21 at 16:08 -0700, Alex Williamson wrote:
This is an attempt to improve the latency of virtio-net while not hurting
throughput. I wanted to try moving packet TX into a different thread
so we can quickly return to
Bugs item #2528121, was opened at 2009-01-22 11:02
Message generated for change (Comment added) made by thekozmo
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2528121group_id=180599
Please note that this message will contain a full copy of the comment
Jamie Kirkpatrick wrote:
All
This is my first post to the list but this seems to be the only place
I can get this problem to be looked at by hopefully the correct
people: I've bounced it around in #kvm on freenode and we've all
agreed its a development issue / bug that needs looking at.
Simon Gao wrote:
Nikola Ciprich wrote:
Hi,
enable KVM support on kernel against which You're compiling..
n.
That did it. So from 2.6.27 and on, we need to enable KVM module in
kernel no matter we want to use a separate outside module or not. This
is a little strange.
While we
Hello everyone,
I'm using
kvm-83 on vanilla kernel 2.6.27.8
but I have some problems,
since guest freezes at boot time
(at very early stage since it does not print any message on the attached vnc)
and /var/log/messages sports the following error message:
kvm: 4982: cpu0 unhandled wrmsr:
On (Thu) Jan 22 2009 [14:16:15], Riccardo Veraldi wrote:
Hello Iam using kvm83 on CentOS5.2
my system has 2x dual Core intel CPU
Intel(R) Xeon(R) CPU5110 @ 1.60GHz
asdetected by Centos.
If I start kvm-qemu with no CPU option everythign works and hte guest
machine detects
On Thu, 2009-01-22 at 12:48 +, Mark McLoughlin wrote:
On Thu, 2009-01-22 at 14:12 +0200, Avi Kivity wrote:
My worry with this change is that increases cpu utilization even more
than it increases bandwidth, so that our bits/cycle measure decreases.
Yep, agreed it's important to
Avi Kivity wrote:
Mark McLoughlin wrote:
Avi and I went back and forth on this one in great detail before:
http://www.mail-archive.com/kvm@vger.kernel.org/msg06431.html
Avi's arguments make a lot of sense, but looking over those patches
again now, I still think that applying them would be a
Due to Marcelo's APIC fix we now depend on hrtimer_expires_remaining,
which is not available on my 2.6.27 kernel.
This patch adds a backwards compatibility layer for it.
Signed-off-by: Alexander Graf ag...@suse.de
---
kernel/external-module-compat-comm.h | 11 +++
1 files changed, 11
Alexander Graf wrote:
Alexander Graf wrote:
[...]
Also after two days of permanent stress testing I also got the Intel
machine w/ current git down:
+ sudo -u contain1 env -i /usr/local/bin/qemu-system-x86_64 -localtime
-kernel virtio-kernel -initrd virtio-initrd -nographic -append
Alexander Graf wrote:
Due to Marcelo's APIC fix we now depend on hrtimer_expires_remaining,
which is not available on my 2.6.27 kernel.
This patch adds a backwards compatibility layer for it.
Signed-off-by: Alexander Graf ag...@suse.de
I just saw that you did one yourself that doesn't
Bugs item #2528121, was opened at 2009-01-22 02:02
Message generated for change (Comment added) made by alex_williamson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2528121group_id=180599
Please note that this message will contain a full copy of the
Hi list
I've been wondering about something for a while: How does the version of the
kernel module and the version of the KVM userspace relate? Eg. if you run with
a newer 2.6.27-2.6.28 kernel with the modules included, will you then benefit
from using the modules from the latest KVM release
On Friday 23 January 2009 07:47:23 Kenni Lund wrote:
Hi list
Hi Kenni
I've been wondering about something for a while: How does the version of
the kernel module and the version of the KVM userspace relate? Eg. if you
run with a newer 2.6.27-2.6.28 kernel with the modules included, will you
- add hpet to BIOS
- add disable/enable of kernel pit when hpet enters/leaves legacy mode
Signed-off-by: Beth Kon e...@us.ibm.com
diff --git a/bios/acpi-dsdt.dsl b/bios/acpi-dsdt.dsl
index d67616d..9981a1f 100755
--- a/bios/acpi-dsdt.dsl
+++ b/bios/acpi-dsdt.dsl
@@ -233,6 +233,24 @@
This series of patches (nearly) resolves the irq0-inti2 override issue, and
gets the hpet working on kvm with and
without the in-kernel irqchip (i.e., it disables userspace and in-kernel pit as
needed).
- irq0-inti2
The resolution was to always use the override unless the kernel cannot do irq
This patch set enable another KVM PowerPC platform E500.
Like the 440 core, the MMU and a few other bits are not currently
emulated in Qemu itself,
so right now it's only functional in conjunction with KVM.
The emulation of MPC85xx boards (which use E500 as its core)
can be run on any MPC85xx
This patch add MPIC support for MPC85xx platform.
MPIC and OpenPIC have very similar design.
So a lot of code can be reused.
Since no other TCG and KVM platforms uses OpenPIC for now,
the modification makes the code only support MPIC.
Signed-off-by: Liu Yu yu@freescale.com
---
hw/openpic.c
Signed-off-by: Liu Yu yu@freescale.com
---
hw/ppc.c| 89 +++
hw/ppc.h|1 +
target-ppc/cpu.h| 10 +
target-ppc/translate_init.c |6 ++-
4 files changed, 104 insertions(+), 2 deletions(-)
Signed-off-by: Liu Yu yu@freescale.com
---
target-ppc/kvm_ppc.c |2 +-
target-ppc/kvm_ppc.h |2 ++
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/target-ppc/kvm_ppc.c b/target-ppc/kvm_ppc.c
index f7ce52b..82c0f42 100644
--- a/target-ppc/kvm_ppc.c
+++
All MPC85xx boards use E500v1/v2 core.
This patch add emulation of a virtual MPC85xx board,
so that any MPC85xx host could run this emulation.
Only tested it on MPC8544DS and MPC8572DS hosts,
but it should work on other MPC85xx boards.
Signed-off-by: Liu Yu yu@freescale.com
---
On Thu, 2009-01-22 at 18:14 +0800, Liu Yu wrote:
All MPC85xx boards use E500v1/v2 core.
This patch add emulation of a virtual MPC85xx board,
so that any MPC85xx host could run this emulation.
Only tested it on MPC8544DS and MPC8572DS hosts,
but it should work on other MPC85xx boards.
On Thu, 2009-01-22 at 18:14 +0800, Liu Yu wrote:
This patch set enable another KVM PowerPC platform E500.
Like the 440 core, the MMU and a few other bits are not currently
emulated in Qemu itself,
so right now it's only functional in conjunction with KVM.
The emulation of MPC85xx boards
Oops. I just saw this mail.
I don't know why it's junked by my client...
OK. I will change it to MPC8544 and remove redundant node in fdt.
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org
[mailto:kvm-ppc-ow...@vger.kernel.org] On Behalf Of Hollis Blanchard
Sent: Saturday,
45 matches
Mail list logo