On 04/22/2010 01:35 PM, Yoshiaki Tamura wrote:
Dor Laor wrote:
On 04/21/2010 08:57 AM, Yoshiaki Tamura wrote:
Hi all,
We have been implementing the prototype of Kemari for KVM, and we're
sending
this message to share what we have now and TODO lists. Hopefully, we
would like
to get
On 04/22/2010 04:16 PM, Yoshiaki Tamura wrote:
2010/4/22 Dor Laor:
On 04/22/2010 01:35 PM, Yoshiaki Tamura wrote:
Dor Laor wrote:
On 04/21/2010 08:57 AM, Yoshiaki Tamura wrote:
Hi all,
We have been implementing the prototype of Kemari for KVM, and we're
sending
this message to share
On 04/23/2010 10:36 AM, Fernando Luis Vázquez Cao wrote:
On 04/23/2010 02:17 PM, Yoshiaki Tamura wrote:
Dor Laor wrote:
[...]
Second, even if it wasn't the case, the tsc delta and kvmclock are
synchronized as part of the VM state so there is no use of trapping it
in the middle.
I s
On 04/27/2010 11:14 AM, Avi Kivity wrote:
On 04/27/2010 01:36 AM, Anthony Liguori wrote:
A few comments:
1) The problem was not block watermark itself but generating a
notification on the watermark threshold. It's a heuristic and should
be implemented based on polling block stats.
Polling fo
On 04/27/2010 11:56 AM, Avi Kivity wrote:
On 04/27/2010 11:48 AM, Dor Laor wrote:
Here's another option: an nbd-like protocol that remotes all BlockDriver
operations except read and write over a unix domain socket. The open
operation returns an fd (SCM_RIGHTS strikes again) that is use
On 04/27/2010 12:22 PM, Avi Kivity wrote:
On 04/27/2010 12:08 PM, Dor Laor wrote:
On 04/27/2010 11:56 AM, Avi Kivity wrote:
On 04/27/2010 11:48 AM, Dor Laor wrote:
Here's another option: an nbd-like protocol that remotes all
BlockDriver
operations except read and write over a unix d
On 05/05/2010 11:58 PM, Michael S. Tsirkin wrote:
Generally, the Host end of the virtio ring doesn't need to see where
Guest is up to in consuming the ring. However, to completely understand
what's going on from the outside, this information must be exposed.
For example, host can reduce the numb
On 11/23/2009 02:15 PM, Juan Quintela wrote:
Dor Laor wrote:
> In the last couple of days we discovered some issues regarding stable
> ABI and the robustness of the live migration protocol. Let's just jump
> right into it, ordered by complexity:
>
> 1. Control*every*
On 11/23/2009 08:28 PM, Anthony Liguori wrote:
Eduardo Habkost wrote:
That may be good enough for upstream Qemu, but IMO for RHEL it is not a
realistic policy. If the definition of "guest visible state" is buggy on
the current implementation, we can't drop entirely the possibility of
fixing it o
On 12/12/2009 12:08 AM, Alexander Graf wrote:
On 11.12.2009, at 22:13, Izik Eidus wrote:
On Fri, 11 Dec 2009 14:46:55 -0600
Anthony Liguori wrote:
Izik Eidus wrote:
I personaly dont like mjpeg, and yes in the end of the day you can
add the video streaming into vnc, but what is the point he
On 12/12/2009 07:40 PM, Anthony Liguori wrote:
If Spice can crash a guest, that indicates to me that Spice is
maintaining guest visible state. That is difficult architecturally
because if we want to do something like introduce a secure sandbox for
running guest visible emulation, libspice would
On 12/12/2009 09:48 PM, Izik Eidus wrote:
On Sat, 12 Dec 2009 13:26:30 -0600
Anthony Liguori wrote:
Izik Eidus wrote:
On Sat, 12 Dec 2009 11:40:21 -0600
Anthony Liguori wrote:
FWIW, I don't see any reason why Spice couldn't be made to be
separate from guest emulation. I think it would ju
On 12/21/2009 09:43 AM, Gleb Natapov wrote:
On Sun, Dec 20, 2009 at 11:59:43AM -0600, Anthony Liguori wrote:
Gleb Natapov wrote:
Windows is a mystery box, so we can speculate as much as we want about it.
If you don't like something just say "it may break Windows" :) Losing
activation does sound
On 12/22/2009 12:51 AM, john cooper wrote:
Dor Laor wrote:
Qemu will check the required cpuid of the cpu model on the host and
refuse to load otherwise. When moving to this model, migration can be
simplified too since there are fewer combination, and one can choose
performance over migration
What's missing in this patch set and in similar pvclock implementation
is userspace activation of the features.
This should be part of the machine description and not enabled by
default without no control to deactivate it on a per guest basis.
Gerd, since you're the qdev master, what's the best
On 01/06/2010 04:32 PM, Avi Kivity wrote:
On 01/06/2010 04:22 PM, Michael S. Tsirkin wrote:
We can probably default -enable-kvm to -cpu host, as long as we explain
very carefully that if users wish to preserve cpu features across
upgrades, they can't depend on the default.
Hardware upgrades or
On 01/06/2010 05:16 PM, Anthony Liguori wrote:
On 01/06/2010 08:48 AM, Dor Laor wrote:
On 01/06/2010 04:32 PM, Avi Kivity wrote:
On 01/06/2010 04:22 PM, Michael S. Tsirkin wrote:
We can probably default -enable-kvm to -cpu host, as long as we
explain
very carefully that if users wish to
On 01/07/2010 10:18 AM, Avi Kivity wrote:
On 01/07/2010 10:03 AM, Dor Laor wrote:
We can debate about the exact name/model to represent the Nehalem
family, I don't have an issue with that and actually Intel and Amd
should define it.
AMD and Intel already defined their names (in cat
On 01/07/2010 10:24 AM, Daniel P. Berrange wrote:
On Thu, Jan 07, 2010 at 10:03:28AM +0200, Dor Laor wrote:
On 01/06/2010 05:16 PM, Anthony Liguori wrote:
On 01/06/2010 08:48 AM, Dor Laor wrote:
On 01/06/2010 04:32 PM, Avi Kivity wrote:
On 01/06/2010 04:22 PM, Michael S. Tsirkin wrote:
We
On 01/07/2010 11:24 AM, Avi Kivity wrote:
On 01/07/2010 11:11 AM, Dor Laor wrote:
On 01/07/2010 10:18 AM, Avi Kivity wrote:
On 01/07/2010 10:03 AM, Dor Laor wrote:
We can debate about the exact name/model to represent the Nehalem
family, I don't have an issue with that and actually Inte
On 01/07/2010 01:39 PM, Anthony Liguori wrote:
On 01/07/2010 03:40 AM, Dor Laor wrote:
There's no simple solution except to restrict features to what was
available on the first processors.
What's not simple about the above 4 options?
What's a better alternative (that insures u
On 01/07/2010 01:59 PM, Avi Kivity wrote:
On 01/07/2010 11:40 AM, Dor Laor wrote:
There's no such thing as Nehalem.
Intel were ok with it. Again, you can name is corei7 or
xeon34234234234, I don't care, the principle remains the same.
There are several processors belonging to t
On 01/07/2010 02:00 PM, Avi Kivity wrote:
On 01/07/2010 01:44 PM, Dor Laor wrote:
So if you had a 2.6.18 kernel and a 2.6.33 kernel, it may be necessary
to say:
(2.6.33) qemu -cpu Nehalem,-syscall
(2.6.18) qemu -cpu Nehalem
Or let qemu do it automatically for you.
qemu on 2.6.33 doesn&#
On 01/07/2010 03:14 PM, Anthony Liguori wrote:
On 01/07/2010 06:40 AM, Avi Kivity wrote:
On 01/07/2010 02:33 PM, Anthony Liguori wrote:
There's another option.
Make cpuid information part of live migration protocol, and then
support something like -cpu Xeon-3550. We would remember the exact
c
On 01/11/2010 11:03 AM, Dor Laor wrote:
On 01/11/2010 10:30 AM, Avi Kivity wrote:
On 01/11/2010 09:40 AM, Vadim Rozenfeld wrote:
The following patch allows us to improve Windows virtio
block driver performance on small size requests.
Additionally, it leads to reducing of cpu usage on write IOs
On Tue, 2008-01-08 at 01:30 +, Paul Brook wrote:
> > -The host kernel was configured with dynamic tick & hi-res timers, to
> > allow the desired timer resolution. USB 2.0 microframe is 125usec.
>
It still works even without accurate timing demands.
Only isochronous mode will have problems an
On Wed, 2008-01-09 at 23:08 -0500, Javier Guerra Giraldez wrote:
> On Wednesday 09 January 2008, Dor Laor wrote:
> > Some figures: Linux rx 350Mbps, tx 150bps, Windows rx 700mbps, tx 100 mbps.
>
> very nice!
>
> in a related note, the VMWare tools package, which is
andrzej zaborowski wrote:
Hi,
On 09/01/2008, Dor Laor <[EMAIL PROTECTED]> wrote:
It which supports TCP/UDP and IP transmit checksum, as well as TSO.
It has been tested with Linux (2.6.18|22|23|24)++ and Windows XP (using
the driver supplied at the intel download site).
Windows
Alexey, you're wrong again.
svm is supported.
On Sun, 2008-01-20 at 20:59 +0200, Alexey Eremenko wrote:
> Note however, that as far as I know, all the Qemu accelerators - KQemu
> and KVM do not support this.
>
Opps, me wrong this time, it should have been private.
Didn't notice the reply address is different. Sorry.
On Sun, 2008-01-20 at 21:21 +0200, Dor Laor wrote:
> Alexey, you're wrong again.
>
>
> svm is supported.
>
> On Sun, 2008-01-20 at 20:59 +0200, Alexey Erem
On Tue, 2008-01-29 at 13:43 -0800, Sarah A Sharp wrote:
> Greetings,
>
> I'm developing a USB host controller driver for hardware that isn't
> available yet. Is there a way to emulate a PCI host controller for
> the Linux host controller driver to talk to? I looked at the USB
> emulation sectio
repository: /home/build/src/kvm
branch: trunk
commit cd5edbab7d647b81cbbf60d530068f2916658753
Author: Dor Laor <[EMAIL PROTECTED]>
Date: Thu Feb 28 11:01:41 2008 +0200
Change the e1000 mmio addr space according to spec.
According to the Intel 82540EM manual, the mmio sp
On Sun, 2008-03-09 at 01:14 +, Steve Fosdick wrote:
>
> kqemu works correctly, whereas with:
>
> CONFIG_HIGH_RES_TIMERS=y
>
> the problem appears. Any idea why that causes a problem? Is it a
> bug?
>
> Anyway, at least for now I have a solution. Thanks for your help.
While I don't know
>From 498f162fc9d9fb897c756273c481101a44a220de Mon Sep 17 00:00:00 2001
From: Dor Laor <[EMAIL PROTECTED]>
Date: Thu, 13 Mar 2008 00:11:41 +0200
Subject: [PATCH] Fix sci irq set when acpi timer about to wrap.
The acpi timer should generate sci irq when enabled and
when bit 23 of the time
On 10/20/2009 09:13 AM, Amit Shah wrote:
Hello,
This patch series fixes a few problems since the last send, mainly in
the save/restore code and a few bugs shown by the automated test suite
(located in a separate git repo, link below).
The automated test suite and a standalone interactive test p
On 11/09/2009 05:53 AM, Fernando Luis Vázquez Cao wrote:
Hi all,
It has been a while coming, but we have finally started work on
Kemari's port to KVM. For those not familiar with it, Kemari provides
the basic building block to create a virtualization-based fault
tolerant machine: a virtual machi
On 11/13/2009 01:48 PM, Yoshiaki Tamura wrote:
Hi,
Thanks for your comments!
Dor Laor wrote:
On 11/09/2009 05:53 AM, Fernando Luis Vázquez Cao wrote:
Hi all,
It has been a while coming, but we have finally started work on
Kemari's port to KVM. For those not familiar with it, Kemari pro
In the last couple of days we discovered some issues regarding stable
ABI and the robustness of the live migration protocol. Let's just jump
right into it, ordered by complexity:
1. Control *every* feature exposed to the guest by qemu cmdline:
While thinking on cross version migration, and
On 11/23/2009 11:44 AM, Michael S. Tsirkin wrote:
On Thu, Nov 19, 2009 at 09:19:05AM -0600, Adam Litke wrote:
Rusty and Anthony,
If I've addressed all outstanding issues, please consider this patch for
inclusion. Thanks.
Changes since V2:
- Increase stat field size to 64 bits
- Report all
>hi everyone!
>i'm programming a pci-device that includes some threads &
>socket-connections (that allow remote debugging of my device).
>
>however, i want to cleanly shutdown all threads and sockets when qemu
>exits... is there an easy way of getting informed of a qemu shutdown?
>
>(something simi
>QEMU developers:
>
>I have been using QEMU off and on for some time. Recently I had a need
>for a Windows XP VM to be joined to a domain. I discovered a rather
>annoying issue in the form of the key-grab: NT-based Microsoft
>operating systems make heavy use of Ctrl-Alt-Delete, i.e. to sign on,
>
>Hello.
>
>I have a problem with time drifting inside the QEMU machine (running
>XP SP2). This is more visible as the load inside the VM increases
>(heavy hard-disk activity, almost 100% CPU usage). However, I need to
>control some actions inside the VM machine which depend on time. Any
>idea how
>Like others have reported to the list I'm getting:
>
>Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a
>fatal
>error, but for better emulation accuracy either use a 2.6 host Linux
>kernel or
>type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
It's might be HPET that
>> I like it ;) I have some comments (and a reworked patch at the end):
>>
>
>And thanks a lot for that.
>
>>
>> Plus, in this way you change the behaviour from "always try RTC under
>> Linux" to "don't use RTC is dynticks is enabled".
>> Is this what you really want?
>
>I don't know whether this i
>> Hello,
>> in reply to this mail I will send a serie of 4 patches that cleans up
>and
>> expands the alarm timer handling in QEMU. Patches have been rebased
on
>QEMU
>> CVS.
>>
>> Patch 1 is mostly a cleanup of the existing code; instead of having
>multiple
>> #ifdefs to handle different timers s
>I think this is a really nice and important patch set. Just a couple
>things:
>
>On Sun, 2007-08-19 at 00:02 +0200, Luca Tettamanti wrote:
>
>> > In this case the dyn-tick minimum res will be 1msec. I believe it
>should
>> > work ok since this is the case without any dyn-tick.
>>
>> Actually mini
>>> Yes, good thinking, but this should only be done if it actually
>impacts
>>> something. Reducing overhead from 0.1% to 0.05% is not worthwhile
if
>it
>>> introduces extra complexity.
>>>
>>
>>
>> If the overhead is that small, why are we touching this code in the
>first
>> place?
>>
>
>Accurac
>Paul Brook wrote:
>> > Yes, good thinking, but this should only be done if it actually
>impacts
>> > something. Reducing overhead from 0.1% to 0.05% is not worthwhile
>if it
>> > introduces extra complexity.
>>
>> If the overhead is that small, why are we touching this code in the
>first
>> place
>> Hi,
>>
>> Some more information about the VMware backdoor can be found at:
>> http://chitchat.at.infoseek.co.jp/vmware/backdoor.html
>
>Are there interesting apps that make use of this? I really don't like
>the idea of supporting this PV protocol if we're not going to get
>interesting apps out
>> > >>> This is QEMU, with dynticks and HPET:
>> > >>>
>> > >>> % time seconds usecs/call callserrors syscall
>> > >>> -- --- --- - -
-
>---
>> > >>> 52.100.002966 0 96840
clock_gettime
>> > >>> 19.500.001110
Dan Kenigsberg wrote:
Frustrated with evtouch, I wanted to try vmmouse's absolute mode, supported by
Liguori's patch http://thread.gmane.org/gmane.comp.emulators.qemu/16083 .
My guest has vmmouse_drv.so, and I configured its xorg.conf to load it.
However, for some reason I get
(EE) VMWARE(0): vm
Clemens Kolbitsch wrote:
hi everyone!
i have a strange problem (at least to me it seems strange :-) ):
i have implemented a pci device (Network IC) and it works just fine when using
a standard image. however i now want to support snapshotting...
i started to convert my image into the qcow2 f
Clemens Kolbitsch wrote:
Clemens Kolbitsch wrote:
hi everyone!
i have a strange problem (at least to me it seems strange :-) ):
i have implemented a pci device (Network IC) and it works just fine when
using a standard image. however i now want to support snapshotting...
i started to conv
Paul Brook wrote:
There seem to have specific problems when using dynticks in Qemu. What I
can see is that it makes the PowerPC emulation quite unusable, at least
on my PC, which is an amd64 (with a fix CPU frequency), no matter if I
run 32 or 64 bits mode.
I'd expect to see the same probl
Arnon Gilboa wrote:
Hi,
The attached patch adds isochronous transfers support to the OHCI
emulation, similarly to the UHCI patch pushed two weeks ago.
In order to use ohci instead of uhci, replace the following line in
pc.c:
usb_uhci_piix3_init(pci_bus, piix3_devfn + 2);
With:
usb_ohci_init_p
production
problems.
Signed-off-by: Dor Laor <[EMAIL PROTECTED]>
---
qemu/exec.c |3 ---
qemu/vl.c | 58 ++
2 files changed, 58 insertions(+), 3 deletions(-)
diff --git a/qemu/exec.c b/qemu/exec.c
index 3e588d5..974ac98 100644
sing asyncio.
This fix adds a delay of 1msec once every 8 dma writes.
Signed-off-by: Dor Laor <[EMAIL PROTECTED]>
btw: It also applies against qemu cvs head.
diff --git a/qemu/hw/ide.c b/qemu/hw/ide.c
index 329d053..da972c8 100644
--- a/qemu/hw/ide.c
+++ b/qemu/hw/ide.c
@@ -36
Fabrice Bellard wrote:
Hi,
Some remarks:
- rename the option to -pcidevice.
- Remove the directory passthrough and put the file directly in hw/.
Rename the file to something more explicit such as pci_passthrough*
- Suppress the files passthrough.h and neo_pci_tree.h
- pt_init should be call
Anthony Liguori wrote:
This patch series adds support for paravirtual device drivers that use
virtio. virtio is a frame work in Linux for abstracting the details of
virtual IO so that a single device driver (like networking) can be used
with multiple hypervisors using a small shim layer. Curre
Anthony Liguori wrote:
Subject: [PATCH 1/3] virtio infrastructure
Cc: Rusty Russell <[EMAIL PROTECTED]>
Cc: Avi Kivity <[EMAIL PROTECTED]>
Cc: Dor Laor <[EMAIL PROTECTED]>
This patch implements the ba
Anthony Liguori wrote:
Index: qemu/hw/virtio-net.c
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ qemu/hw/virtio-net.c2007-12-04 14:17:37.0 -0600
+
+static void virtio_net_receive(void *opaque, const uin
Anthony Liguori wrote:
Subject: [PATCH 3/3] virtio block device
+
+static void virtio_blk_handle_output(VirtIODevice *vdev, VirtQueue *vq)
+{
+VirtIOBlock *s = to_virtio_blk(vdev);
+VirtQueueElement elem;
+unsigned int count;
+
+while ((count = virtqueue_pop(vq, &elem)) != 0) {
+
Laurent Vivier wrote:
Le mardi 11 décembre 2007 à 10:10 +0100, Fabrice Bellard a écrit :
Hi,
Hi,
At this point I am not interested in integrating it into QEMU as it is
one more API level to maintain in addition to the command line monitor.
However, I can change my mind if several
Anthony Liguori wrote:
Richard W.M. Jones wrote:
> Anthony Liguori wrote:
>> Daniel P. Berrange wrote:
>>> Or have 2 monitor interaction modes. One mode uses the command line
>>> style
>>> suitable for people / scripting languages. The other umode ses a
>>> binary XDR
>>> protocol for serializin
Hi,
My name is Dor and I'm one of the contributors for the KVM.
> Ricardo Almeida wrote:
> > Hi,
> >
> > Just saw this on slashdot
> > (http://linux.slashdot.org/article.pl?sid=06/12/12/0135240). From
the
> > news:
> >
> > "In a fashion comparable to that of Xen a modified QEMU is used for
> > th
to be deleted.
Regards,
Dor Laor.
apic_saved_version_id.patch
Description: apic_saved_version_id.patch
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
101 - 166 of 166 matches
Mail list logo
