This patch adds a system to watch user space segmentation
faults, writing core dumps and some degree of core dump
analysis report. We believe that such a system will be
beneficial for autotest as a whole, since the ability to
get core dumps and dump analysis for each app crashing
during an autotest
Sir,
We are a group of four students from IIIT. For our university project,
we are looking ahead to contribute to KVM.
Initially we thought of implementing online resizing of virtual disks,
but we thought we could do something more intresting than that.
With regard to it, Could you suggest us some
I am using qemu-nbd to export a root disk image for kvm. The VM took
very long time to boot, can anyone identify why? How to improve?
Thanks,
Shawn
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http:/
It is broken since main loop reorganization. (6185d8b6)
Problem is that we, the emulator, has nothing to do with the CPU flags.
has_work()
should not depend on that at all.
Signed-off-by: Glauber Costa
CC: Gleb Natapov
---
qemu-kvm-x86.c |5 ++---
1 files changed, 2 insertions(+), 3 delet
On Thu, Sep 3, 2009 at 6:48 PM, Dustin Kirkland wrote:
> On Thu, Sep 3, 2009 at 3:01 PM, Mark McLoughlin wrote:
>> On Thu, 2009-09-03 at 12:31 -0500, Dustin Kirkland wrote:
>>> qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
>>> to non-accelerated mode
>>>
>>> We're seeing se
On Thu, Sep 3, 2009 at 3:01 PM, Mark McLoughlin wrote:
> On Thu, 2009-09-03 at 12:31 -0500, Dustin Kirkland wrote:
>> qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
>> to non-accelerated mode
>>
>> We're seeing segfaults on systems without access to /dev/kvm. It
>> looks li
On Thu, 3 Sep 2009 12:31:33 -0500
Dustin Kirkland wrote:
> qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
> to non-accelerated mode
>
> We're seeing segfaults on systems without access to /dev/kvm. It
> looks like the global kvm_allowed is being set just a little too lat
On Thu, 2009-09-03 at 12:31 -0500, Dustin Kirkland wrote:
> qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
> to non-accelerated mode
>
> We're seeing segfaults on systems without access to /dev/kvm. It
> looks like the global kvm_allowed is being set just a little too late
On Thu, Sep 03, 2009 at 12:31:33PM -0500, Dustin Kirkland wrote:
> qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
> to non-accelerated mode
>
> We're seeing segfaults on systems without access to /dev/kvm. It
> looks like the global kvm_allowed is being set just a little t
On Thu, Aug 27, 2009 at 07:07:50PM +0300, Michael S. Tsirkin wrote:
> What it is: vhost net is a character device that can be used to reduce
> the number of system calls involved in virtio networking.
> Existing virtio net code is used in the guest without modification.
>
> There's similarity with
On Thu, Sep 03, 2009 at 12:10:34PM +0300, Gleb Natapov wrote:
> This bug was introduced by b4a2f5e723e4f7df46731106faf9e2405673c073
>
> Signed-off-by: Gleb Natapov
> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> index e9de458..38a2d20 100644
> --- a/virt/kvm/ioapic.c
> +++ b/virt/kvm/ioapi
qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
to non-accelerated mode
We're seeing segfaults on systems without access to /dev/kvm. It
looks like the global kvm_allowed is being set just a little too late
in vl.c. This patch moves the kvm initialization a bit higher in t
Indeed. Good catch. Thanks :-)
On Thu, Sep 03, 2009 at 04:51:52PM +0200, Alexander Graf wrote:
> Thanks to Joerg's previous series of cleanups, we now have almost all
> information we need to decide what to do on #VMEXIT because we get
> the variables from the VMCB on VMRUN.
>
> Unfortunately the
> Another issue I noticed while looking at the results is large
> fluctuations in ide results. The standard deviation of
> the ide results is very large. A large portion of the results are
> around 30GB/sec and around 80GB/sec.
> Is there any meaningful explanation for this large variation? Is ther
From: Heiko Carstens
CC arch/s390/kvm/../../../virt/kvm/kvm_main.o
arch/s390/kvm/../../../virt/kvm/kvm_main.c: In function
'__kvm_set_memory_region':
arch/s390/kvm/../../../virt/kvm/kvm_main.c:485: warning: unused variable 'j'
arch/s390/kvm/../../../virt/kvm/kvm_main.c:484: warning: unuse
Amit Shah wrote:
Hi
>> > > +static void virtio_console_set_port_active(uint32_t idx)
>> > > +{
>> > > +int i = 0;
>> > > +
>> > > +while (idx / 32) {
>> > > +i++;
>> > > +idx -= 32;
>> > > +}
>> >
>> > It is just me, or you are doing a division + modulus in a very st
>> > +for (i = 0; i < (le32_to_cpu(virtcon_config.max_nr_ports) + 31) / 32;
>> > i++) {
>> > +qemu_put_be32s(f, &virtcon_config.ports_map[i]);
>> > +}
>>
>> Don't even try to save a couple of bytes, please.
>
> Sorry, don't understand this.
>
>>
>> for (i = 0; i < (MAX_VIRTIO_CO
Avi Kivity wrote on 03/09/2009 16:39:09:
> From:
>
> Avi Kivity
>
> To:
>
> Orit Wasserman/Haifa/i...@ibmil
>
> Cc:
>
> Abel Gordon/Haifa/i...@ibmil, aligu...@us.ibm.com, Ben-Ami Yassour1/
> Haifa/i...@ibmil, kvm@vger.kernel.org, mm...@us.ibm.com, Muli Ben-
> Yehuda/Haifa/i...@ibmil
>
> Date:
Avi Kivity wrote on 03/09/2009 00:38:16:
> From:
>
> Avi Kivity
>
> To:
>
> Orit Wasserman/Haifa/i...@ibmil
>
> Cc:
>
> kvm@vger.kernel.org, Ben-Ami Yassour1/Haifa/i...@ibmil, Muli Ben-
> Yehuda/Haifa/i...@ibmil, Abel Gordon/Haifa/i...@ibmil,
> aligu...@us.ibm.com, mm...@us.ibm.com
>
> Date:
>
Thanks to Joerg's previous series of cleanups, we now have almost all
information we need to decide what to do on #VMEXIT because we get
the variables from the VMCB on VMRUN.
Unfortunately there's one piece that slipped through the conversion,
namely the MSR intercept which still tries to map the
On (Thu) Sep 03 2009 [19:56:05], Amit Shah wrote:
> Hi Juan,
>
> On (Thu) Sep 03 2009 [16:06:54], Juan Quintela wrote:
> > > diff --git a/hw/virtio-console.c b/hw/virtio-console.c
> > > index 663c8b9..da590d2 100644
> > > --- a/hw/virtio-console.c
> > > +++ b/hw/virtio-console.c
> > >
> > > #in
Amit Shah wrote:
> This interface extends the virtio-console device to handle
> multiple ports that present a char device from which bits can
> be sent and read.
>
> Sample uses for such a device can be obtaining info from the
> guest like the file systems used, apps installed, etc. for
> offline
Hi Juan,
On (Thu) Sep 03 2009 [16:06:54], Juan Quintela wrote:
> > diff --git a/hw/virtio-console.c b/hw/virtio-console.c
> > index 663c8b9..da590d2 100644
> > --- a/hw/virtio-console.c
> > +++ b/hw/virtio-console.c
> >
> > #include "hw.h"
> > +#include "monitor.h"
> > +#include "pci.h"
> > +#i
Avi Kivity wrote on 02/09/2009 23:15:40:
> From:
>
> Avi Kivity
>
> To:
>
> Orit Wasserman/Haifa/i...@ibmil
>
> Cc:
>
> kvm@vger.kernel.org, Ben-Ami Yassour1/Haifa/i...@ibmil, Muli Ben-
> Yehuda/Haifa/i...@ibmil, Abel Gordon/Haifa/i...@ibmil,
> aligu...@us.ibm.com, mm...@us.ibm.com
>
> Date:
>
Avi Kivity wrote on 02/09/2009 23:05:09:
> From:
>
> Avi Kivity
>
> To:
>
> Orit Wasserman/Haifa/i...@ibmil
>
> Cc:
>
> kvm@vger.kernel.org, Ben-Ami Yassour1/Haifa/i...@ibmil, Muli Ben-
> Yehuda/Haifa/i...@ibmil, Abel Gordon/Haifa/i...@ibmil,
> aligu...@us.ibm.com, mm...@us.ibm.com
>
> Date:
>
Thanks to Joerg's previous series of cleanups, we now have almost all
information we need to decide what to do on #VMEXIT because we get
the variables from the VMCB on VMRUN.
Unfortunately there's one piece that slipped through the conversion,
namely the MSR intercept which still tries to map the
Avi Kivity wrote on 02/09/2009 22:38:22:
> From:
>
> Avi Kivity
>
> To:
>
> Orit Wasserman/Haifa/i...@ibmil
>
> Cc:
>
> kvm@vger.kernel.org, Ben-Ami Yassour1/Haifa/i...@ibmil, Muli Ben-
> Yehuda/Haifa/i...@ibmil, Abel Gordon/Haifa/i...@ibmil,
> aligu...@us.ibm.com, mm...@us.ibm.com
>
> Date:
>
On 09/03/2009 03:34 PM, Orit Wasserman wrote:
I think we need to mask it with the capabilities we support. Otherwise
the guest can try to use some new feature which we don't support yet,
and crash.
I agree , but I went over the Intel spec and didn't find any problematic
feature.
We may
Notify users of the char interface whenever the file / connection is
opened.
The existing RESET event is triggered when the qemu char state is reset
as well; which may not be as interesting as char device open events.
Signed-off-by: Amit Shah
---
qemu-char.c | 14 +-
qemu-char.h |
This interface extends the virtio-console device to handle
multiple ports that present a char device from which bits can
be sent and read.
Sample uses for such a device can be obtaining info from the
guest like the file systems used, apps installed, etc. for
offline usage and logged-in users, clip
Expose multiple char devices ("ports") for simple communication
between the host userspace and guest.
Sample offline usages can be: poking around in a guest to find out
the file systems used, applications installed, etc. Online usages
can be sharing of clipboard data between the guest and the host
Hello all,
Here is a new iteration of the patch series that implements a
transport for guest and host communications.
I've tested for compatibility (old qemu & new kernel, new qemu & old
kernel, new qemu & new kernel) and it all works fine*.
There are a few items on my todo list but this works w
Avi Kivity wrote on 02/09/2009 22:34:58:
> From:
>
> Avi Kivity
>
> To:
>
> Orit Wasserman/Haifa/i...@ibmil
>
> Cc:
>
> kvm@vger.kernel.org, Ben-Ami Yassour1/Haifa/i...@ibmil, Muli Ben-
> Yehuda/Haifa/i...@ibmil, Abel Gordon/Haifa/i...@ibmil,
> aligu...@us.ibm.com, mm...@us.ibm.com
>
> Date:
>
Saksena, Abhishek wrote:
> Correction to question:-
>
> Can keeping device models and KVM pit synchronize with the host clock
> <> result in any issues with booting up OSes?
>
Time virtualization, especially in SMP guest for legacy OS, is tricky. Hardly
it can be really synced.
But, Linux has
Yup,
I was lazily trying to avoid that :)
OK, I'll give it a try and report..
On Thu, Sep 03, 2009 at 01:05:46PM +0300, Avi Kivity wrote:
> On 09/03/2009 12:59 PM, Nikola Ciprich wrote:
>> I tried running the test on my test machine with 2.6.31-rc8 guest kernel
>> and I wasn't able to reproduce th
On 09/03/2009 12:59 PM, Nikola Ciprich wrote:
I tried running the test on my test machine with 2.6.31-rc8 guest kernel
and I wasn't able to reproduce the problem...
So it's possible that the problem could have been fixed somewhere between
2.6.30..2.6.31-rc8
Do You have any idea on what could be t
I tried running the test on my test machine with 2.6.31-rc8 guest kernel
and I wasn't able to reproduce the problem...
So it's possible that the problem could have been fixed somewhere between
2.6.30..2.6.31-rc8
Do You have any idea on what could be the related fix? It would be a good
candidate for
On Thu, Sep 03, 2009 at 09:29:08AM +0200, Alexander Graf wrote:
>
> On 03.09.2009, at 08:01, Muli Ben-Yehuda wrote:
>
>> On Wed, Sep 02, 2009 at 05:57:39PM +0200, Alexander Graf wrote:
>>>
>>> Am 02.09.2009 um 17:38 schrieb or...@il.ibm.com:
>>>
The following patches implement nested VMX suppo
This bug was introduced by b4a2f5e723e4f7df46731106faf9e2405673c073
Signed-off-by: Gleb Natapov
diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
index e9de458..38a2d20 100644
--- a/virt/kvm/ioapic.c
+++ b/virt/kvm/ioapic.c
@@ -194,6 +194,8 @@ int kvm_ioapic_set_irq(struct kvm_ioapic *ioapic, in
Hi,
somehow this thread ended without any conclusion. Today I noticed
that
BUG: MAX_LOCK_DEPTH too low!
still shows up when starting kvm on 2.6.31-rc8
So is increasing MAX_LOCK_DEPTH to say 96 good way to go?
If yes, shouldn't we set this for upstream kernel?
thanks
nik
On Sun, May 24, 2009 a
Marcelo Tosatti wrote:
> On Tue, Sep 01, 2009 at 04:06:25PM +0300, Avi Kivity wrote:
>> Only reload debug register 6 if we're running with the guest's
>> debug registers. Saves around 150 cycles from the guest lightweight
>> exit path.
>>
>> dr6 contains a couple of bits that are updated on #DB, s
On 03.09.2009, at 08:01, Muli Ben-Yehuda wrote:
On Wed, Sep 02, 2009 at 05:57:39PM +0200, Alexander Graf wrote:
Am 02.09.2009 um 17:38 schrieb or...@il.ibm.com:
The following patches implement nested VMX support. The patches
enable a guest to use the VMX APIs in order to run its own nested
42 matches
Mail list logo
