On 11/29/2011 10:03 PM, Avi Kivity wrote:
> On 11/29/2011 02:01 PM, Avi Kivity wrote:
>> On 11/29/2011 01:56 PM, Xiao Guangrong wrote:
>>> On 11/29/2011 07:20 PM, Avi Kivity wrote:
>>>
>>>
We used to have a bitmap in a shadow page with a bit set for every slot
pointed to by the page. If
On 11/29/2011 08:01 PM, Avi Kivity wrote:
> On 11/29/2011 01:56 PM, Xiao Guangrong wrote:
>> On 11/29/2011 07:20 PM, Avi Kivity wrote:
>>
>>
>>> We used to have a bitmap in a shadow page with a bit set for every slot
>>> pointed to by the page. If we extend this to non-leaf pages (so, when
>>> we
On 11/29/2011 10:36 PM, Sasha Levin wrote:
> On Tue, 2011-11-29 at 22:28 +0800, Asias He wrote:
>> Currently, all blk requests are processed in notify_vq() which is in
>> the context of ioeventfd thread: ioeventfd__thread(). The processing
>> in notify_vq() may take a long time to complete.
>>
>> W
On Wed, Nov 30, 2011 at 09:58:45AM +1030, Rusty Russell wrote:
> > I think I see a way to do that in a relatively painless way.
> > Do you prefer seeing driver patches or spec? Or are you not interested
> > in reusing the same structure at all?
>
> I think we should look at code at this point; my
(2011/11/30 14:02), Takuya Yoshikawa wrote:
IIUC, even though O(1) is O(1) at the timing of GET DIRTY LOG, it needs O(N)
write
protections with respect to the total number of dirty pages: distributed, but
actually each page fault, which should be logged, does some write protection?
Sorry, was
From: Qingtang Zhou
Subtest nfs_corrupt is used to check the change of
VM status when disk I/O error happen. Only test
Linux platform, write disk by dd command. Setup
NFS service by pre_command and post_command.
Update this case, using 'iptables' command to
filter nfs connection instead of stop
CCing qemu devel, Juan,
(2011/11/29 23:03), Avi Kivity wrote:
On 11/29/2011 02:01 PM, Avi Kivity wrote:
On 11/29/2011 01:56 PM, Xiao Guangrong wrote:
On 11/29/2011 07:20 PM, Avi Kivity wrote:
We used to have a bitmap in a shadow page with a bit set for every slot
pointed to by the page. If
On Mon, 28 Nov 2011 10:41:51 +0200, "Michael S. Tsirkin"
wrote:
> On Mon, Nov 28, 2011 at 11:25:43AM +1030, Rusty Russell wrote:
> > > > But I'm *terrified* of making the spec more complex;
> > >
> > > All you do is move stuff around. Why do you think it simplifies the spec
> > > so much?
> >
>
On Mon, 28 Nov 2011 11:15:31 +0200, Sasha Levin wrote:
> On Mon, 2011-11-28 at 11:25 +1030, Rusty Russell wrote:
> > I'd like to see kvmtools remove support for legacy mode altogether,
> > but they probably have existing users.
>
> While we can't simply remove it right away, instead of mixing our
Hello,
Can a guest with SDL graphics run on a host without X? I get an error:
"init kbd.
Could not initialize SDL - exiting"
The above happens on a host with X after running "/etc/init.d/xdm stop" and
"chmod -R 777 /dev".
If I don't do the chmod, SDL complains about not being able to open the
Markus Armbruster wrote:
> Avi Kivity writes:
>
>> On 11/29/2011 05:51 PM, Juan Quintela wrote:
>>> How to do high level stuff?
>>> - python?
>>>
>>
>> One of the disadvantages of the various scripting languages is the lack
>> of static type checking, which makes it harder to do full sweeps of th
On Tue, 2011-11-29 at 17:20 -0600, Stuart Yoder wrote:
> >
> > BTW, github now has updated trees:
> >
> > git://github.com/awilliam/linux-vfio.git vfio-next-2029
> > git://github.com/awilliam/qemu-vfio.git vfio-ng
>
> Hi Alex,
>
> Have been looki
>
> BTW, github now has updated trees:
>
> git://github.com/awilliam/linux-vfio.git vfio-next-2029
> git://github.com/awilliam/qemu-vfio.git vfio-ng
Hi Alex,
Have been looking at vfio a bit. A few observations and things
we'll need to figure out as it relates to
On 11/29/2011 10:59 AM, Avi Kivity wrote:
On 11/29/2011 05:51 PM, Juan Quintela wrote:
How to do high level stuff?
- python?
One of the disadvantages of the various scripting languages is the lack
of static type checking, which makes it harder to do full sweeps of the
source for API changes,
On 11/29/2011 03:36 PM, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the ability to tell the guest that it is being stopped and
should ignore the
When a host stops or suspends a VM it will set a flag to show this. The
watchdog will use these functions to determine if a softlockup is real, or the
result of a suspended VM.
Signed-off-by: Eric B Munson
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: a...@arndb.de
Cc: ry...@linux.vnet.ibm.com
Cc:
Changes from V3:
Include CC's on patch 3
Drop clear flag ioctl and have the watchdog clear the flag when it is reset
Changes from V2:
A new kvm functions defined in kvm_para.h, the only change to pvclock is the
initial flag definition
Changes from V1:
(Thanks Marcelo)
Host code has all been moved
Signed-off-by: Eric B Munson
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: a...@arndb.de
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc: jeremy.fitzhardi...@citrix.com
Cc: kvm@vger.kernel.org
Cc: linux-a...@vger.kernel.org
Cc: x...@kernel.org
Cc: linux-ker...@vger.ke
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the ability to tell the guest that it is being stopped and
should ignore the soft lockup warning that generates.
Signed-off
A suspended VM can cause spurious soft lockup warnings. To avoid these, the
watchdog now checks if the kernel knows it was stopped by the host and skips
the warning if so. When the watchdog is reset successfully, clear the guest
paused flag.
Signed-off-by: Eric B Munson
Cc: mi...@redhat.com
Cc:
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: a...@arndb.de
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc:
This flag will be used to check if the vm was stopped by the host when a soft
lockup was detected. The host will set the flag when it stops the guest. On
resume, the guest will check this flag if a soft lockup is detected and skip
issuing the warning.
Signed-off-by: Eric B Munson
Cc: mi...@redh
On Tuesday 29 November 2011, Stefano Stabellini wrote:
> Hi all,
> a few weeks ago I (and a few others) started hacking on a
> proof-of-concept hypervisor port to Cortex-A15 which uses and requires
> ARMv7 virtualization extensions. The intention of this work was to find
> out how to best support A
The hardware maintains a per-set next victim hint. Using this
reduces conflicts, especially on e500v2 where a single guest
TLB entry is mapped to two shadow TLB entries (user and kernel).
We want those two entries to go to different TLB ways.
sesel is now only used for TLB1.
Reported-by: Liu Yu
On Tue, 2011-11-29 at 15:07 +0200, Pekka Enberg wrote:
> On Tue, 29 Nov 2011, Sasha Levin wrote:
> > A guest could overwrite host memory by writing to cmos index bigger than
> > 128.
> >
> > This patch adds a boundry check to limit it to that size.
> >
> > Cc: Alessandro Zummo
> > Cc: rtc-li...@g
or, 0:success, >0: number
of MSIs we think we can setup, without actually setting them. Sound
good?
BTW, github now has updated trees:
git://github.com/awilliam/linux-vfio.git vfio-next-2029
git://github.com/awilliam/qemu-vfio.git vfio-ng
Thanks,
Alex
> > KERNEL patch:
> >
Avi Kivity writes:
> On 11/29/2011 05:51 PM, Juan Quintela wrote:
>> How to do high level stuff?
>> - python?
>>
>
> One of the disadvantages of the various scripting languages is the lack
> of static type checking, which makes it harder to do full sweeps of the
> source for API changes, relying
Hello,
This bug/patch is only relevant for qemu-0.14.x users, since in qemu-0.15 the
main-loop is completely different. So this is more or less for reference
only, if others experience the same dead-lock.
I have created a snapshot of an VM, which now doesn't load.
Thread 1 loads the saved state
On Tue, 2011-11-29 at 16:35 +, Ben Hutchings wrote:
> On Mon, 2011-11-21 at 09:41 -0800, Greg Rose wrote:
> > On 11/18/2011 9:40 AM, Ben Hutchings wrote:
> [...]
> > > What concerns me is that this seems to be a workaround rather than a fix
> > > for over-use of promiscuous mode, and it changes
On 11/29/2011 05:51 PM, Juan Quintela wrote:
> How to do high level stuff?
> - python?
>
One of the disadvantages of the various scripting languages is the lack
of static type checking, which makes it harder to do full sweeps of the
source for API changes, relying on the compiler to catch type (or
On Mon, 2011-11-21 at 09:41 -0800, Greg Rose wrote:
> On 11/18/2011 9:40 AM, Ben Hutchings wrote:
[...]
> > What concerns me is that this seems to be a workaround rather than a fix
> > for over-use of promiscuous mode, and it changes the semantics of
> > filtering modes in ways that haven't been we
Plans for 1.0
- rc4 should be the last release
- should ship 1.0 on Thrusday
Merge window start on Monday
How to handle stable tree, getting a stable team?
- Justin: he don't do schedules for releases because it depends on when patches
arrive.
- Adding a list for stable patches instead of more
On Tue, Nov 29, 2011 at 03:57:19PM +0200, Ohad Ben-Cohen wrote:
> > Is an extra branch faster or slower than reverting d57ed95?
>
> Sorry, unfortunately I have no way to measure this, as I don't have
> any virtualization/x86 setup. I'm developing on ARM SoCs, where
> virtualization hardware is com
On Tue, Nov 29, 2011 at 03:57:19PM +0200, Ohad Ben-Cohen wrote:
> On Tue, Nov 29, 2011 at 3:11 PM, Michael S. Tsirkin wrote:
> > On Tue, Nov 29, 2011 at 02:31:26PM +0200, Ohad Ben-Cohen wrote:
> >> Virtio is using memory barriers to control the ordering of
> >> references to the vrings on SMP syst
On 11/29/2011 04:54 PM, Michael S. Tsirkin wrote:
> >
> > Which is actually strange, weren't indirect buffers introduced to make
> > the performance *better*? From what I see it's pretty much the
> > same/worse for virtio-blk.
>
> I know they were introduced to allow adding very large bufs.
> See
On Tue, Nov 29, 2011 at 04:21:04PM +0200, Sasha Levin wrote:
> > > > Need to verify the effect on block too, and do some more
> > > > benchmarks. In particular we are making the ring
> > > > in effect smaller, how will this affect small packet perf
> > > > with multiple streams?
> > >
> > > I coul
Hi all,
a few weeks ago I (and a few others) started hacking on a
proof-of-concept hypervisor port to Cortex-A15 which uses and requires
ARMv7 virtualization extensions. The intention of this work was to find
out how to best support ARM v7+ on Xen. See
http://old-list-archives.xen.org/archives/html
On Tue, 2011-11-29 at 22:28 +0800, Asias He wrote:
> Currently, all blk requests are processed in notify_vq() which is in
> the context of ioeventfd thread: ioeventfd__thread(). The processing
> in notify_vq() may take a long time to complete.
>
> We should make notify_vq() return as soon as possi
Currently, all blk requests are processed in notify_vq() which is in
the context of ioeventfd thread: ioeventfd__thread(). The processing
in notify_vq() may take a long time to complete.
We should make notify_vq() return as soon as possible, since all devices
are sharing the single ioeventfd threa
On Tue, 2011-11-29 at 15:54 +0200, Michael S. Tsirkin wrote:
> On Tue, Nov 29, 2011 at 03:34:48PM +0200, Sasha Levin wrote:
> > On Tue, 2011-11-29 at 14:56 +0200, Michael S. Tsirkin wrote:
> > > On Tue, Nov 29, 2011 at 11:33:16AM +0200, Sasha Levin wrote:
> > > > Currently if VIRTIO_RING_F_INDIRECT
On 11/29/2011 02:01 PM, Avi Kivity wrote:
> On 11/29/2011 01:56 PM, Xiao Guangrong wrote:
> > On 11/29/2011 07:20 PM, Avi Kivity wrote:
> >
> >
> > > We used to have a bitmap in a shadow page with a bit set for every slot
> > > pointed to by the page. If we extend this to non-leaf pages (so, when
On Tue, Nov 29, 2011 at 3:11 PM, Michael S. Tsirkin wrote:
> On Tue, Nov 29, 2011 at 02:31:26PM +0200, Ohad Ben-Cohen wrote:
>> Virtio is using memory barriers to control the ordering of
>> references to the vrings on SMP systems. When the guest is compiled
>> with SMP support, virtio is only usin
On 11/28/2011 08:24 AM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
Few more items:
- sandboxing/embedding dynamic languages
Also a heads up about a couple series I've been waiting to send out for post
1.0:
- QOM phase 1 (dynamic properties/st
On Tue, Nov 29, 2011 at 03:34:48PM +0200, Sasha Levin wrote:
> On Tue, 2011-11-29 at 14:56 +0200, Michael S. Tsirkin wrote:
> > On Tue, Nov 29, 2011 at 11:33:16AM +0200, Sasha Levin wrote:
> > > Currently if VIRTIO_RING_F_INDIRECT_DESC is enabled we will use indirect
> > > descriptors even if we ha
On Tue, 2011-11-29 at 14:56 +0200, Michael S. Tsirkin wrote:
> On Tue, Nov 29, 2011 at 11:33:16AM +0200, Sasha Levin wrote:
> > Currently if VIRTIO_RING_F_INDIRECT_DESC is enabled we will use indirect
> > descriptors even if we have plenty of space in the ring. This means that
> > we take a perform
Avi Kivity wrote:
> On 11/28/2011 04:35 PM, Anthony Liguori wrote:
>>> (somewhat related) memory API conversion queue merge plan
>>
>>
>> No need to wait until tomorrow to discuss it, I guess.
>>
>> 1.1 will open up on Friday. I was going to make the suggestion that
>> if anyone has more than 50
On Tue, Nov 29, 2011 at 02:31:26PM +0200, Ohad Ben-Cohen wrote:
> Virtio is using memory barriers to control the ordering of
> references to the vrings on SMP systems. When the guest is compiled
> with SMP support, virtio is only using SMP barriers in order to
> avoid incurring the overhead involve
It is supposed to have no write ops in ro_ops_nowrite disk operation.
However, there is one. Let's remove it.
Signed-off-by: Asias He
---
tools/kvm/disk/raw.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/disk/raw.c b/tools/kvm/disk/raw.c
index bdcd047..caa02
ro_ops is never used after the assignment, so no need to do the
assignment.
Signed-off-by: Asias He
---
tools/kvm/disk/raw.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/disk/raw.c b/tools/kvm/disk/raw.c
index 9e5e86f..bdcd047 100644
--- a/tools/kvm/disk/raw
This patch reduces the number of calls to io_getevents() by getting
multiple io events at a time instead of one in disk image thread.
Signed-off-by: Asias He
---
tools/kvm/disk/core.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/tools/kvm/disk/core.c b/tools
On Tue, 29 Nov 2011, Sasha Levin wrote:
A guest could overwrite host memory by writing to cmos index bigger than 128.
This patch adds a boundry check to limit it to that size.
Cc: Alessandro Zummo
Cc: rtc-li...@googlegroups.com
Signed-off-by: Sasha Levin
---
tools/kvm/hw/rtc.c |4
1 f
On Tue, Nov 29, 2011 at 03:01:59PM +0200, Pekka Enberg wrote:
> >>
> >>Hi Sasha, where the rmb() then? Or maybe you wanted plain barrier() here?
> >
> >On the kernel side.
> >Theres a mb there which happens there during the kick.
>
> I guess we need to improve the comment in next_desc()?
>
Kerne
On Tue, 29 Nov 2011, Sasha Levin wrote:
+/*
+ * Each buffer in the virtqueues is actually a chain of descriptors. This
+ * function returns the next descriptor in the chain, or vq->vring.num if we're
+ * at the end.
+ */
+static unsigned next_desc(struct vring_desc *desc,
+
On Tue, Nov 29, 2011 at 11:33:16AM +0200, Sasha Levin wrote:
> Currently if VIRTIO_RING_F_INDIRECT_DESC is enabled we will use indirect
> descriptors even if we have plenty of space in the ring. This means that
> we take a performance hit at all times due to the overhead of creating
> indirect desc
Virtio is using memory barriers to control the ordering of
references to the vrings on SMP systems. When the guest is compiled
with SMP support, virtio is only using SMP barriers in order to
avoid incurring the overhead involved with mandatory barriers.
Lately, though, virtio is being increasingly
On 11/29/2011 01:56 PM, Xiao Guangrong wrote:
> On 11/29/2011 07:20 PM, Avi Kivity wrote:
>
>
> > We used to have a bitmap in a shadow page with a bit set for every slot
> > pointed to by the page. If we extend this to non-leaf pages (so, when
> > we set a bit, we propagate it through its parent_p
On 11/29/2011 07:20 PM, Avi Kivity wrote:
> We used to have a bitmap in a shadow page with a bit set for every slot
> pointed to by the page. If we extend this to non-leaf pages (so, when
> we set a bit, we propagate it through its parent_ptes list), then we do
> the following on write fault:
>
On 11/29/2011 12:35 PM, Takuya Yoshikawa wrote:
>>> I think it needs more thinking if only less page need be write
>>> protected.
>>>
>>> For example, framebuffer-based device used by Xwindow, only ~64M
>>> pages needs
>>> to be write protected, but in your way, guest will get write page
>>> fault
(2011/11/29 19:09), Xiao Guangrong wrote:
Sorry, CC list is lost. :(
On 11/29/2011 06:01 PM, Xiao Guangrong wrote:
Avi Kivity redhat.com> writes:
On 11/16/2011 06:28 AM, Takuya Yoshikawa wrote:
(2011/11/14 21:39), Avi Kivity wrote:
There was a patchset from Peter Zijlstra that converted
Sorry, CC list is lost. :(
On 11/29/2011 06:01 PM, Xiao Guangrong wrote:
> Avi Kivity redhat.com> writes:
>
>>
>> On 11/16/2011 06:28 AM, Takuya Yoshikawa wrote:
>>> (2011/11/14 21:39), Avi Kivity wrote:
There was a patchset from Peter Zijlstra that converted mmu notifiers to
be preem
Avi Kivity redhat.com> writes:
>
> On 11/16/2011 06:28 AM, Takuya Yoshikawa wrote:
> > (2011/11/14 21:39), Avi Kivity wrote:
> >> There was a patchset from Peter Zijlstra that converted mmu notifiers to
> >> be preemptible, with that, we can convert the mmu spinlock to a mutex,
> >> I'll see wha
On 11/29/2011 05:56 AM, Xiao Guangrong wrote:
> Subject: [PATCH v2 2/5] KVM: MMU: audit: replace mmu audit tracepoint with
> jump-lable
>
> The tracepoint is only used to audit mmu code, it should not be exposed to
> user, let us replace it with jump-lable
>
>
> static bool mmu_audit;
> +static s
On Fri, Nov 25, 2011 at 10:34 AM, Simon Wilson wrote:
> I have done a fair bit of analysis with dstat and using dd copies, and file
> writes onto the VM's RAID5 slice sit between 35 and 40MBps consistently.
If you want to drill down on the disk I/O performance than removing
Samba from the equatio
Currently if VIRTIO_RING_F_INDIRECT_DESC is enabled we will use indirect
descriptors even if we have plenty of space in the ring. This means that
we take a performance hit at all times due to the overhead of creating
indirect descriptors.
With this patch, we will use indirect descriptors only if w
A guest could overwrite host memory by writing to cmos index bigger than 128.
This patch adds a boundry check to limit it to that size.
Cc: Alessandro Zummo
Cc: rtc-li...@googlegroups.com
Signed-off-by: Sasha Levin
---
tools/kvm/hw/rtc.c |4
1 files changed, 4 insertions(+), 0 deletio
This patch prevents the duplication of definitions between kernel headers
and KVM tool code.
Cc: Alessandro Zummo
Cc: rtc-li...@googlegroups.com
Signed-off-by: Sasha Levin
---
tools/kvm/hw/rtc.c | 20 +---
1 files changed, 1 insertions(+), 19 deletions(-)
diff --git a/tools/k
This patch moves kernel specific header includes into the kernel #ifdef-ed
section, thus allowing userspace to include this header directly.
Cc: Alessandro Zummo
Cc: rtc-li...@googlegroups.com
Signed-off-by: Sasha Levin
---
include/linux/mc146818rtc.h |3 +--
1 files changed, 1 insertions(+
67 matches
Mail list logo
