On Fri, Sep 02, 2011 at 09:48:33AM +0200, Jan Kiszka wrote:
On 2011-08-29 21:18, Michael S. Tsirkin wrote:
On Mon, Aug 29, 2011 at 08:47:07PM +0200, Jan Kiszka wrote:
On 2011-08-29 17:42, Jan Kiszka wrote:
I still don't get what prevents converting ipr to allow plain mutex
On 2011-09-06 09:00, Michael S. Tsirkin wrote:
On Fri, Sep 02, 2011 at 09:48:33AM +0200, Jan Kiszka wrote:
On 2011-08-29 21:18, Michael S. Tsirkin wrote:
On Mon, Aug 29, 2011 at 08:47:07PM +0200, Jan Kiszka wrote:
On 2011-08-29 17:42, Jan Kiszka wrote:
I still don't get what prevents
On 09/01/2011 02:27 PM, Jan Kiszka wrote:
On 2011-02-22 19:08, Marcelo Tosatti wrote:
On Fri, Feb 18, 2011 at 04:53:09PM +0800, Sheng Yang wrote:
Sorry for the long delay, just come back from vacation...
Change from v8:
1. Update struct kvm_run to contain MSI-X routing update exit
On Tue, Sep 06, 2011 at 09:18:13AM +0200, Jan Kiszka wrote:
@@ -401,36 +403,58 @@ int pci_vpd_truncate(struct pci_dev *dev, size_t
size)
EXPORT_SYMBOL(pci_vpd_truncate);
/**
- * pci_block_user_cfg_access - Block userspace PCI config reads/writes
+ * pci_block_cfg_access - Block
Hi Lai,
On Mon, Aug 29, 2011 at 05:24:31PM +0800, Lai Jiangshan wrote:
When I test it, the guest OS become non-available, but it does not crash.
It also cause the disk fault.
It is hard to dig the reason. Or I missed something?
thanks for testing. Can you share your full qemu-kvm command
On Tue, Sep 06, 2011 at 10:52:41AM +0300, Avi Kivity wrote:
BTW, the same is also true for that optional per-vector masking of
legacy MSI. Are there devices in the field that actually support this? I
haven't found one so far and tend to consider this feature not worth
implementing.
Don't
On 2011-09-06 10:04, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 09:18:13AM +0200, Jan Kiszka wrote:
@@ -401,36 +403,58 @@ int pci_vpd_truncate(struct pci_dev *dev, size_t
size)
EXPORT_SYMBOL(pci_vpd_truncate);
/**
- * pci_block_user_cfg_access - Block userspace PCI config
On 2011-09-06 09:52, Avi Kivity wrote:
On 09/01/2011 02:27 PM, Jan Kiszka wrote:
On 2011-02-22 19:08, Marcelo Tosatti wrote:
On Fri, Feb 18, 2011 at 04:53:09PM +0800, Sheng Yang wrote:
Sorry for the long delay, just come back from vacation...
Change from v8:
1. Update struct kvm_run to
On 2011-09-06 10:12, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 10:52:41AM +0300, Avi Kivity wrote:
BTW, the same is also true for that optional per-vector masking of
legacy MSI. Are there devices in the field that actually support this? I
haven't found one so far and tend to consider
On Tue, 2011-09-06 at 10:36 +0200, Jan Kiszka wrote:
On 2011-09-06 10:12, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 10:52:41AM +0300, Avi Kivity wrote:
BTW, the same is also true for that optional per-vector masking of
legacy MSI. Are there devices in the field that actually
On Tue, Sep 06, 2011 at 10:27:45AM +0200, Jan Kiszka wrote:
On 2011-09-06 10:04, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 09:18:13AM +0200, Jan Kiszka wrote:
@@ -401,36 +403,58 @@ int pci_vpd_truncate(struct pci_dev *dev, size_t
size)
EXPORT_SYMBOL(pci_vpd_truncate);
/**
On 2011-09-06 10:47, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 10:27:45AM +0200, Jan Kiszka wrote:
On 2011-09-06 10:04, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 09:18:13AM +0200, Jan Kiszka wrote:
@@ -401,36 +403,58 @@ int pci_vpd_truncate(struct pci_dev *dev, size_t
size)
On 2011-09-06 10:46, Sasha Levin wrote:
On Tue, 2011-09-06 at 10:36 +0200, Jan Kiszka wrote:
On 2011-09-06 10:12, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 10:52:41AM +0300, Avi Kivity wrote:
BTW, the same is also true for that optional per-vector masking of
legacy MSI. Are there
On Tue, 2011-09-06 at 10:49 +0200, Jan Kiszka wrote:
On 2011-09-06 10:46, Sasha Levin wrote:
On Tue, 2011-09-06 at 10:36 +0200, Jan Kiszka wrote:
On 2011-09-06 10:12, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 10:52:41AM +0300, Avi Kivity wrote:
BTW, the same is also true for
On 2011-09-06 11:00, Sasha Levin wrote:
On Tue, 2011-09-06 at 10:49 +0200, Jan Kiszka wrote:
On 2011-09-06 10:46, Sasha Levin wrote:
On Tue, 2011-09-06 at 10:36 +0200, Jan Kiszka wrote:
On 2011-09-06 10:12, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 10:52:41AM +0300, Avi Kivity wrote:
On Tue, 2011-09-06 at 11:05 +0200, Jan Kiszka wrote:
On 2011-09-06 11:00, Sasha Levin wrote:
On Tue, 2011-09-06 at 10:49 +0200, Jan Kiszka wrote:
On 2011-09-06 10:46, Sasha Levin wrote:
On Tue, 2011-09-06 at 10:36 +0200, Jan Kiszka wrote:
On 2011-09-06 10:12, Michael S. Tsirkin wrote:
On Tue, Sep 06, 2011 at 12:16:11PM +0300, Sasha Levin wrote:
Back to square #1: We need a device with MSI support and cap bit 8 set
in its _MSI_ control word.
Alright, so I've looked at some of my servers, and one of them has both
a bunch of MSI-X devices, and some MSI devices which show
The main goal of the patch is to effectively cap the disk I/O speed or counts
of one single VM.It is only one draft, so it unavoidably has some drawbacks, if
you catch them, please let me know.
The patch will mainly introduce one block I/O throttling algorithm, one timer
and one block queue
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
block.c |8
block_int.h | 30 ++
blockdev.c | 29 +
blockdev.h |2 ++
qemu-config.c | 24
qemu-options.hx |1
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
Makefile.objs |2 +-
block/blk-queue.c | 184 +
block/blk-queue.h | 59 +
3 files changed, 244 insertions(+), 1 deletions(-)
create mode 100644 block/blk-queue.c
The patch introduce one new command block_set_io_throttle; For its usage
syntax, if you have better idea, pls let me know.
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
block.c | 26 --
hmp-commands.hx | 15 +++
qerror.c|4
Note:
1.) When bps/iops limits are specified to a small value such as 511
bytes/s, this VM will hang up. We are considering how to handle this senario.
2.) When dd command is issued in guest, if its option bs is set to a
large value such as bs=1024K, the result speed will slightly
Thanks Avi, Marcelo, Kevin for comments, sorry for late reply (just come back
from vacation).
Avi Kivity wrote:
On 08/17/2011 07:19 AM, Liu, Jinsong wrote:
From a9670ddff84080c56183e2d678189e100f891174 Mon Sep 17 00:00:00
2001
From: Liu, Jinsongjinsong@intel.com
Date: Wed, 17 Aug
Marcelo Tosatti wrote:
--- a/arch/x86/include/asm/msr-index.h
+++ b/arch/x86/include/asm/msr-index.h
@@ -229,6 +229,8 @@
#define MSR_IA32_APICBASE_ENABLE (111)
#define MSR_IA32_APICBASE_BASE (0xf12)
+#define MSR_IA32_TSCDEADLINE 0x06e0
+
#define
On 09/06/2011 02:18 PM, Liu, Jinsong wrote:
struct x86_instruction_info *info,
enum x86_intercept_stage stage);
+ u64 (*guest_to_host_tsc)(u64 guest_tsc);
};
Please put this near the other tsc functions. Add a comment
explaining
On Tue, Sep 06, 2011 at 02:23:54AM +0300, Sasha Levin wrote:
This patch allows to run previously created guestfs by simply specifying it
with the '-d' parameter.
This allows running guestfs which were created before using:
kvm setup -n [name]
Signed-off-by: Sasha Levin
Juan Quintela quint...@redhat.com wrote:
Hi
Please send in any agenda items you are interested in covering.
To agenda items.
Anthony off.
Call got cancelled.
Happy hacking, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
boot_idt is set up an all cpus by the startup code, unlike
the idt local to desc.c.
Signed-off-by: Avi Kivity a...@redhat.com
---
lib/x86/desc.c | 17 +++--
1 files changed, 3 insertions(+), 14 deletions(-)
diff --git a/lib/x86/desc.c b/lib/x86/desc.c
index 11bd2a2..0ed8c22 100644
apic.flat is failing due to an IPI hitting an uninitialized IDT entry.
This patchset fixes the issue.
Avi Kivity (3):
x86/desc: switch to using boot_idt
x86/desc: allow multiple initializations
x86/smp: use desc.c for setting up IPI handler
lib/x86/desc.c | 23 +--
There are multiple callers, so be forgiving.
Signed-off-by: Avi Kivity a...@redhat.com
---
lib/x86/desc.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/lib/x86/desc.c b/lib/x86/desc.c
index 0ed8c22..c268955 100644
--- a/lib/x86/desc.c
+++ b/lib/x86/desc.c
@@
This allows other callers to use desc.c without conflict. Fixes
apic.flat failure with -smp 2.
Signed-off-by: Avi Kivity a...@redhat.com
---
lib/x86/smp.c | 23 ++-
1 files changed, 2 insertions(+), 21 deletions(-)
diff --git a/lib/x86/smp.c b/lib/x86/smp.c
index
Hello,
I'm trying to solve quite a weird problem on one of our customers' box.
It's quad core Xeon X3430 @ 2.40GHz, running 64bit centos with 2.6.38 (I also
tried upgrading to
2.6.39).
After increasing physical memory from 16 to 20GB, all guest got incredibly
slow, starting just
one windows or
On 09/06/2011 05:02 PM, Nikola Ciprich wrote:
Hello,
I'm trying to solve quite a weird problem on one of our customers' box.
It's quad core Xeon X3430 @ 2.40GHz, running 64bit centos with 2.6.38 (I also
tried upgrading to
2.6.39).
After increasing physical memory from 16 to 20GB, all guest
On Fri, Sep 02, 2011 at 02:50:53PM -0700, Jeremy Fitzhardinge wrote:
On 09/02/2011 01:47 PM, Peter Zijlstra wrote:
On Fri, 2011-09-02 at 12:29 -0700, Jeremy Fitzhardinge wrote:
I know that its generally considered bad form, but there's at least one
spinlock that's only taken from NMI
On 03.09.2011, at 00:39, Scott Wood wrote:
The hardcoded behavior prevents proper SMP support.
QEMU shall specify the vcpu's PIR as the vcpu id.
Signed-off-by: Scott Wood scottw...@freescale.com
Thanks, applied.
Alex
--
To unsubscribe from this list: send the line unsubscribe kvm in
Hello Avi,
thanks for quick reply!
How many guests in there?
two currently (one x86_64 centos, one winXP), with more, the box get even more
unresponsive.
Please post a trace as per http://www.linux-kvm.org/page/Tracing.
here it goes:
http://nelide.cz/nik/trace.dat.bz2
Please post
On 09/06/2011 06:38 PM, Nikola Ciprich wrote:
Hello Avi,
thanks for quick reply!
How many guests in there?
two currently (one x86_64 centos, one winXP), with more, the box get even more
unresponsive.
Please post a trace as per http://www.linux-kvm.org/page/Tracing.
here it goes:
404
ouch, dumb me :-/
http://nelide.cz/downloads/nik/trace.dat.bz2
sorry
n.
Please post /proc/mtrr and /proc/iomem.
[root@virtualbox ~]# cat /proc/mtrr
reg00: base=0x0 (0MB), size=16384MB, count=1: write-back
reg01: base=0x4 (16384MB), size= 4096MB, count=1:
On 09/06/2011 07:01 PM, Nikola Ciprich wrote:
404
ouch, dumb me :-/
http://nelide.cz/downloads/nik/trace.dat.bz2
sorry
n.
qemu-kvm-4618 [000] 13698.803169: kvm_emulate_insn:
0:806edb12: rep outsw
qemu-kvm-4618 [000] 13698.803170: kvm_pio:
pio_write at
On 09/06/2011 07:06 PM, Avi Kivity wrote:
On 09/06/2011 07:01 PM, Nikola Ciprich wrote:
404
ouch, dumb me :-/
http://nelide.cz/downloads/nik/trace.dat.bz2
sorry
n.
qemu-kvm-4618 [000] 13698.803169: kvm_emulate_insn:
0:806edb12: rep outsw
qemu-kvm-4618 [000]
On 09/06/2011 06:38 PM, Nikola Ciprich wrote:
Hello Avi,
thanks for quick reply!
How many guests in there?
two currently (one x86_64 centos, one winXP), with more, the box get even more
unresponsive.
I don't really understand why the box is unresponsive. What do top and
'vmstat 1' say?
On Tue, Sep 06, 2011 at 07:06:34PM +0300, Avi Kivity wrote:
On 09/06/2011 07:01 PM, Nikola Ciprich wrote:
404
ouch, dumb me :-/
http://nelide.cz/downloads/nik/trace.dat.bz2
sorry
n.
qemu-kvm-4618 [000] 13698.803169: kvm_emulate_insn:
0:806edb12: rep outsw
OK, seems like Avi's right, at least the windows guest is not using DMA
though the question is, why did it got disabled and how can I reenable it,
I'm not experienced that much with XP :(
It is rep/in-out. But why it became noticeable only after adding more
physical memory to the host is a
On 09/06/2011 07:30 PM, Nikola Ciprich wrote:
OK, seems like Avi's right, at least the windows guest is not using DMA
though the question is, why did it got disabled
It can happen due to a timeout, perhaps a temporary load spike.
and how can I reenable it,
Google knows.
I'm not
On 09/06/2011 08:14 AM, Don Zickus wrote:
On Fri, Sep 02, 2011 at 02:50:53PM -0700, Jeremy Fitzhardinge wrote:
On 09/02/2011 01:47 PM, Peter Zijlstra wrote:
On Fri, 2011-09-02 at 12:29 -0700, Jeremy Fitzhardinge wrote:
I know that its generally considered bad form, but there's at least one
On Tue, Sep 06, 2011 at 11:07:26AM -0700, Jeremy Fitzhardinge wrote:
But, erm, does that even make sense? I'm assuming the NMI reason port
tells the CPU why it got an NMI. If multiple CPUs can get NMIs and
there's only a single reason port, then doesn't that mean that either 1)
they all
On 09/06/2011 11:27 AM, Don Zickus wrote:
But on the other hand, I don't really care if you can say that this path
will never be called in a virtual machine.
Does virtual machines support hot remove of cpus? Probably not
considering bare-metal barely supports it.
The only reason you'd want
Hello guys,
thanks to both of You for Your replies. The problem is solved,
exactly as Avi said, the DMA in windows got somehow disabled.
So this certainly was not related to adding the memory...
anyways, note for further generations:
in windows XP, the DMA usage can be checked in
Device
On 09/02/2011 04:22 AM, Stefano Stabellini wrote:
do you have a git tree somewhere with this series?
git://github.com/jsgf/linux-xen.git upstream/pvticketlock-slowflag
J
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
Hello,
I'm trying to set up a fast virtualized Samba file server. I'm using
Debian Sqeeze 64 bit as hypervisor.
First, I created mirrored storage in hypervisor from one 600-gig
partition (yes, that's correct - I have only one drive currently), details:
sudo mdadm --detail /dev/md3
/dev/md3:
On Mon, Sep 5, 2011 at 2:42 AM, Avi Kivity a...@redhat.com wrote:
Linus, please pull from
git://github.com/avikivity/kvm.git kvm-updates/3.1
to receive a fix for a build failure due to a missing instruction size
suffix in inline assembly.
Again, please give me a warm and fuzzy feeling that
On Tue, Sep 6, 2011 at 7:20 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Mon, Sep 5, 2011 at 2:42 AM, Avi Kivity a...@redhat.com wrote:
Linus, please pull from
git://github.com/avikivity/kvm.git kvm-updates/3.1
to receive a fix for a build failure due to a missing instruction
On Tue, Sep 6, 2011 at 6:19 PM, Josh Boyer jwbo...@gmail.com wrote:
Maybe asking for some extra warm fuzzies from now on wouldn't be a
horrible idea as general practice.
I think that realistically we should definitely look at our practices,
but at the same time, I personally do put a lot of
We are proud to announce a new release of autotest, 0.13.1. This is a
fairly boring bugfix release, so nothing really new here, just more of
the same.
What is autotest?
Autotest is a framework for fully automated testing. It is designed
primarily to test the Linux kernel, though it is useful
Thanks. very good learning material.
On Tue, Nov 30, 2010 at 1:16 AM, Michael S. Tsirkin m...@redhat.com wrote:
This is the userspace part of the tool: it includes a bunch of stubs for
linux APIs, somewhat simular to linuxsched. This makes it possible to
recompile the ring code in userspace.
On 09/07/2011 02:20 AM, Linus Torvalds wrote:
On Mon, Sep 5, 2011 at 2:42 AM, Avi Kivitya...@redhat.com wrote:
Linus, please pull from
git://github.com/avikivity/kvm.git kvm-updates/3.1
to receive a fix for a build failure due to a missing instruction size
suffix in inline assembly.
On 09/06/2011 09:27 PM, Don Zickus wrote:
On Tue, Sep 06, 2011 at 11:07:26AM -0700, Jeremy Fitzhardinge wrote:
But, erm, does that even make sense? I'm assuming the NMI reason port
tells the CPU why it got an NMI. If multiple CPUs can get NMIs and
there's only a single reason port,
also sprach TooMeeK toomeek...@o2.pl [2011.09.07.0025 +0200]:
Partition type is Linux RAID autodetect
This is not really necessary, presuming that you are doing what
everyone is doing nowadays and assemble the RAID from the initrd or
the init scripts.
I find that way it's not possible to
On 06.09.2011, at 05:17, Liu Yu-B13201 wrote:
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org
[mailto:kvm-ppc-ow...@vger.kernel.org] On Behalf Of Alexander Graf
Sent: Tuesday, September 06, 2011 6:45 AM
To: Wood Scott-B07421
Cc: kvm-ppc@vger.kernel.org
Subject: Re:
On 03.09.2011, at 00:39, Scott Wood wrote:
The hardcoded behavior prevents proper SMP support.
QEMU shall specify the vcpu's PIR as the vcpu id.
Signed-off-by: Scott Wood scottw...@freescale.com
Thanks, applied.
Alex
--
To unsubscribe from this list: send the line unsubscribe kvm-ppc
60 matches
Mail list logo
