On 12/20/2011 11:02 AM, Jan Kiszka wrote:
On 2011-12-20 15:07, Anthony Liguori wrote:
On 12/20/2011 07:57 AM, Paolo Bonzini wrote:
On 12/20/2011 02:54 PM, Anthony Liguori wrote:
In QOM parlance Jan implemented this:
abstract class Object
abstract class Device
class APIC: { backend
On 12/20/2011 03:23 PM, Jan Kiszka wrote:
On 2011-12-20 20:14, Anthony Liguori wrote:
On 12/20/2011 11:02 AM, Jan Kiszka wrote:
On 2011-12-20 15:07, Anthony Liguori wrote:
On 12/20/2011 07:57 AM, Paolo Bonzini wrote:
On 12/20/2011 02:54 PM, Anthony Liguori wrote:
In QOM parlance Jan
On 12/20/2011 03:45 PM, Jan Kiszka wrote:
On 2011-12-20 22:38, Anthony Liguori wrote:
I'm not talking about migration here, I'm talking about qtree
addressability. That is orthogonal, at least right now.
qtree is not an ABI. The output of info qtree can (and will) change
over time.
That's
On 12/20/2011 04:20 PM, Jan Kiszka wrote:
On 2011-12-20 22:55, Anthony Liguori wrote:
The components of the path are the *property* names of the parent
device. In the case of the local APIC, you would have something like:
/cpus/cpu0/apic
/cpus/cpu1/apic
Which would be links
,
+ target_phys_addr_t addr, uint64_t size);
Returning structs by value is a bit unexpected.
Otherwise, the patch looks good.
Regards,
Anthony Liguori
+
+/**
* memory_region_transaction_begin: Start a transaction.
*
* During a transaction, changes
.
Other than the few style comments, the whole series looks reasonable to me.
Regards,
Anthony Liguori
Also available from:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/page_desc
Avi Kivity (23):
memory: introduce memory_region_find()
sysbus: add sysbus_address_space
On 12/19/2011 09:04 AM, Avi Kivity wrote:
On 12/19/2011 04:50 PM, Anthony Liguori wrote:
+static int cmp_flatrange_addr(const void *_addr, const void *_fr)
+{
+const AddrRange *addr = _addr;
+const FlatRange *fr = _fr;
Please don't prefix with an underscore.
Why not? It's legal
On 12/19/2011 09:17 AM, Avi Kivity wrote:
On 12/19/2011 05:10 PM, Anthony Liguori wrote:
On 12/19/2011 09:04 AM, Avi Kivity wrote:
On 12/19/2011 04:50 PM, Anthony Liguori wrote:
+static int cmp_flatrange_addr(const void *_addr, const void *_fr)
+{
+const AddrRange *addr = _addr
in-kernel and in-qemu
device model.
Regards,
Anthony Liguori
Regards,
Anthony Liguori
--
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://vger.kernel.org/majordomo-info.html
fix this up in a pre-save routine (put QEMUTimer into a state where
there isn't an event pending)?
Regards,
Anthony Liguori
--
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://vger.kernel.org
of qdev inheritance. As we progress to QOM, this will mean that
the various links will just be linkAPICCommon or whatever it ends up being called.
Regards,
Anthony Liguori
Thanks
On Thu, Dec 15, 2011 at 01:33:15PM +0100, Jan Kiszka wrote:
Changes in v5:
- properly introduce
this is the problem. The in-kernel APIC is a separate
device, no a property of the userspace APIC device.
It should be modeled as two separate devices.
Regards,
Anthony Liguori
Jan
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
On 12/19/2011 05:45 PM, Jan Kiszka wrote:
On 2011-12-19 23:21, Anthony Liguori wrote:
On 12/15/2011 06:33 AM, Jan Kiszka wrote:
To enable migration between accelerated and non-accelerated APIC models,
we will need to handle the timer saving and restoring specially and can
no longer rely
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please review ACK?
You could even apply directly but well do a kvm-autotest run through
uq/master. Still, your review is needed.
Overall
On 12/19/2011 06:32 PM, Jan Kiszka wrote:
On 2011-12-20 01:28, Anthony Liguori wrote:
On 12/19/2011 05:32 PM, Jan Kiszka wrote:
struct APICCommonInfo {
DeviceInfo qdev;
void (*init)(APICState *s);
void (*set_base)(APICState *s, uint64_t val);
void (*set_tpr)(APICState
On 12/19/2011 06:37 PM, Jan Kiszka wrote:
On 2011-12-20 01:32, Anthony Liguori wrote:
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please reviewACK?
You could even apply directly
On 12/19/2011 06:34 PM, Jan Kiszka wrote:
On 2011-12-20 01:31, Anthony Liguori wrote:
On 12/19/2011 05:45 PM, Jan Kiszka wrote:
On 2011-12-19 23:21, Anthony Liguori wrote:
On 12/15/2011 06:33 AM, Jan Kiszka wrote:
To enable migration between accelerated and non-accelerated APIC
models,
we
On 12/19/2011 06:37 PM, Jan Kiszka wrote:
On 2011-12-20 01:32, Anthony Liguori wrote:
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please reviewACK?
You could even apply directly
On 12/19/2011 07:19 PM, Jan Kiszka wrote:
On 2011-12-20 02:08, Anthony Liguori wrote:
There's lot of inconsistency in qdev already today so adding a little
more isn't the end of the world. We're going to need to eventually have
this debate soon so it's up to you whether you want to just get
On 12/19/2011 08:46 PM, Anthony Liguori wrote:
On 12/19/2011 07:19 PM, Jan Kiszka wrote:
On 2011-12-20 02:08, Anthony Liguori wrote:
Here's how we solve this problem:
1) In the short term, advertise both devices as having the same VMstate name.
Since we don't register until the device
/SIGCONT so while it may appear to
work okay, QEMU isn't exhibiting the behavior it is supposed to.
Regards,
Anthony Liguori
--
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://vger.kernel.org
usb_create() and pass it the usb bus directly as this will
make it easier to express this as composition down the road.
Regards,
Anthony Liguori
+ }
}
if (kernel_filename) {
--
To unsubscribe from this list: send the line unsubscribe kvm-ppc in
the body of a message
On 12/14/2011 06:00 PM, Benjamin Herrenschmidt wrote:
On Wed, 2011-12-14 at 15:48 -0600, Anthony Liguori wrote:
/* USB */
if (usb_enabled) {
usb_ohci_init_pci(QLIST_FIRST(spapr-phbs)-host_state.bus, -1);
+ if (spapr_has_graphics) {
+ usbdevice_create(keyboard
On 12/12/2011 05:16 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
- QOM merge plan
I'd also like to do a code walk through of QOM at the first call of the new
year.
Regards,
Anthony Liguori
Thanks, Juan.
--
To unsubscribe from this list
On 11/30/2011 03:54 AM, Daniel P. Berrange wrote:
On Wed, Nov 30, 2011 at 11:22:37AM +0200, Alon Levy wrote:
On Tue, Nov 29, 2011 at 04:59:51PM -0600, Anthony Liguori wrote:
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
On 11/30/2011 08:35 AM, Alon Levy wrote:
On Wed, Nov 30, 2011 at 07:54:30AM -0600, Anthony Liguori wrote:
[snip]
But the way we're structuring QOM, we could do very simple bindings
that just used introspection (much like GObject does).
Is this the current tree?
http://repo.or.cz/w/qemu
/stable paths)
- Device model test frame work
Regards,
Anthony Liguori
Thanks, Juan.
--
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://vger.kernel.org/majordomo-info.html
--
To unsubscribe from
the soft lockup warning that generates.
Signed-off-by: Eric B Munsonemun...@mgebm.net
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
Anthony Liguori
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc: a...@redhat.com
Cc: kvm@vger.kernel.org
Cc: linux-ker
the UI also be stand alone using GtkVnc in place of the builtin widget and
using a remote interface for QMP.
Regards,
Anthony Liguori
On the other hand, the statically typed languages usually have more
boilerplate. Since one of the goals is to simplify things, this
indicates the need
On 11/28/2011 08:30 AM, Avi Kivity wrote:
On 11/28/2011 04:28 PM, Anthony Liguori wrote:
On 11/28/2011 08:24 AM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
- 1.1 development window logistics
(somewhat related) memory API conversion queue merge
/~nico/seccomp-nurse/
Regards,
Anthony Liguori
Later, Juan.
--
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://vger.kernel.org/majordomo-info.html
Zangzanghongy...@huawei.com
Applied. Thanks.
Regards,
Anthony Liguori
---
hw/ivshmem.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/ivshmem.c b/hw/ivshmem.c
index 242fbea..2ecf658 100644
--- a/hw/ivshmem.c
+++ b/hw/ivshmem.c
@@ -694,7 +694,7 @@ static int
enough
to rebuild when the CFLAGS have changed.
Regards,
Anthony Liguori
--
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://vger.kernel.org/majordomo-info.html
memgroups, there's no reason to involve
QEMU at all. QEMU can define the memgroups based on the NUMA nodes and then
it's up to the kernel as to whether it exposes controls to explicitly bind
memgroups within a process or not.
Regards,
Anthony Liguori
So, I agree, even if there is some external
on the source (and we do), then we're okay.
For cache=write{back,through}, we would then just fcntl() away O_DIRECT as soon
as we start the guest. Then we can start doing reads through the page cache.
Regards,
Anthony Liguori
Later, Juan.
--
To unsubscribe from this list: send the line unsubscribe
of storage requirements for migration
2) write up the notes from the discussion about doing an IDL based vmstate
description.
Regards,
Anthony Liguori
Thanks, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
On 11/14/2011 04:16 AM, Daniel P. Berrange wrote:
On Sat, Nov 12, 2011 at 12:25:34PM +0200, Avi Kivity wrote:
On 11/11/2011 12:15 PM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to work
right now even
On 11/14/2011 11:44 AM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
Proposal:
- Migration debacle.
Ack. You read my mind :-)
Regards,
Anthony Liguori
Thanks, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm
On 11/12/2011 04:20 AM, Avi Kivity wrote:
On 11/10/2011 07:54 PM, Anthony Liguori wrote:
IMO, this should be a release blocker. qemu 1.0 only supporting
migration on enterprise storage?
No, this is not going to block the release.
You can't dump patches on the ML during -rc for an issue
On 11/12/2011 04:27 AM, Avi Kivity wrote:
On 11/11/2011 04:03 PM, Anthony Liguori wrote:
I don't view not supporting migration with image formats as a
regression as it's never been a feature we've supported. While there
might be confusion about support around NFS, I think it's always been
On 11/12/2011 08:43 AM, Avi Kivity wrote:
On 11/12/2011 03:39 PM, Anthony Liguori wrote:
On 11/12/2011 04:27 AM, Avi Kivity wrote:
On 11/11/2011 04:03 PM, Anthony Liguori wrote:
I don't view not supporting migration with image formats as a
regression as it's never been a feature we've
On 11/11/2011 04:15 AM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to work
right now even with proper clustered storage. I think doing a block level flush
cache interface and letting block devices decide
On 11/11/2011 08:29 AM, Kevin Wolf wrote:
Am 11.11.2011 15:03, schrieb Anthony Liguori:
On 11/11/2011 04:15 AM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to work
right now even with proper clustered
On 11/11/2011 08:44 AM, Kevin Wolf wrote:
Am 11.11.2011 15:35, schrieb Anthony Liguori:
This is not a bug fix, this is a new feature. We're long past feature freeze.
It's not a simple and obvious fix either. It only partially fixes the problem
and introduces other problems. It's not a good
-devel than can provide deep review of this type
of code. That's the advantage of working in qemu.git.
[1]
http://mid.gmane.org/1320086191-23641-1-git-send-email-cor...@linux.vnet.ibm.com
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
with iSCSI is strictly an issue with the in-kernel initiator, right?
libiscsi should be safe with a delayed open I would imagine.
Regards,
Anthony Liguori
I really think that anynthing different of
cache=none from iSCSI or NFS is just betting (and yes, it took a while
for Christoph
On 11/10/2011 02:55 AM, Avi Kivity wrote:
On 11/09/2011 07:35 PM, Anthony Liguori wrote:
On 11/09/2011 11:02 AM, Avi Kivity wrote:
On 11/09/2011 06:39 PM, Anthony Liguori wrote:
Migration with qcow2 is not a supported feature for 1.0. Migration is
only supported with raw images using
On 11/10/2011 04:41 AM, Kevin Wolf wrote:
Am 09.11.2011 22:01, schrieb Anthony Liguori:
On 11/09/2011 03:00 PM, Michael S. Tsirkin wrote:
On Wed, Nov 09, 2011 at 02:22:02PM -0600, Anthony Liguori wrote:
On 11/09/2011 02:18 PM, Michael S. Tsirkin wrote:
On Wed, Nov 09, 2011 at 11:35:54AM
On 11/10/2011 02:55 AM, Avi Kivity wrote:
On 11/09/2011 07:35 PM, Anthony Liguori wrote:
On 11/09/2011 11:02 AM, Avi Kivity wrote:
On 11/09/2011 06:39 PM, Anthony Liguori wrote:
Migration with qcow2 is not a supported feature for 1.0. Migration is
only supported with raw images using
On 11/10/2011 12:42 PM, Daniel P. Berrange wrote:
On Thu, Nov 10, 2011 at 12:27:30PM -0600, Anthony Liguori wrote:
What does libvirt actually do in the monitor prior to migration
completing on the destination? The least invasive way of doing
delayed open of block devices is probably to make
On 11/10/2011 02:06 PM, Daniel P. Berrange wrote:
On Thu, Nov 10, 2011 at 01:11:42PM -0600, Anthony Liguori wrote:
On 11/10/2011 12:42 PM, Daniel P. Berrange wrote:
On Thu, Nov 10, 2011 at 12:27:30PM -0600, Anthony Liguori wrote:
What does libvirt actually do in the monitor prior to migration
On 11/10/2011 12:27 PM, Anthony Liguori wrote:
On 11/10/2011 02:55 AM, Avi Kivity wrote:
If we have to delay the release for a month to get it right, we should.
Not that I think we have to.
Adding libvirt to the discussion.
What does libvirt actually do in the monitor prior to migration
://plus.google.com/101344524535025574253/
[2] https://plus.google.com/u/1/101344524535025574253/posts/MgA5ctwGNJv
Regards,
Anthony Liguori
--
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://vger.kernel.org/majordomo
On 11/09/2011 10:04 AM, Natalia Portillo wrote:
We seriously miss having a logo.
Yes, I'll announce something about that tomorrow ;-)
Regards,
Anthony Liguori
El 09/11/2011, a las 15:24, Anthony Liguori escribió:
Hi,
I've created a Google+ page for QEMU[1]. You'll also notice a button
is not a supported feature for 1.0. Migration is only
supported with raw images using coherent shared storage[1].
[1] NFS is only coherent with close-to-open which right now is not good enough
for migration.
Regards,
Anthony Liguori
[PATCH 4/5] Reopen files after migration
The symptom
On 11/09/2011 11:14 AM, Rodrigo Campos wrote:
On Wed, Nov 09, 2011 at 09:24:37AM -0600, Anthony Liguori wrote:
Hi,
I've created a Google+ page for QEMU[1]. You'll also notice a
button on the qemu.org wiki that links to the Google+ page.
I'll be posting release information to this page along
On 11/09/2011 11:02 AM, Avi Kivity wrote:
On 11/09/2011 06:39 PM, Anthony Liguori wrote:
Migration with qcow2 is not a supported feature for 1.0. Migration is
only supported with raw images using coherent shared storage[1].
[1] NFS is only coherent with close-to-open which right now
(by simply using KVM_GET_SUPPORTED_CPUID
instead of the CPUID instruction).
Signed-off-by: Avi Kivitya...@redhat.com
This seems like a 1.0 candidate, yes?
Regards,
Anthony Liguori
---
target-i386/cpuid.c | 27 ---
1 files changed, 4 insertions(+), 23 deletions
(by simply using KVM_GET_SUPPORTED_CPUID
instead of the CPUID instruction).
Signed-off-by: Avi Kivitya...@redhat.com
Applied. Thanks.
Regards,
Anthony Liguori
---
target-i386/cpuid.c | 27 ---
1 files changed, 4 insertions(+), 23 deletions(-)
diff --git a/target
On 11/09/2011 02:18 PM, Michael S. Tsirkin wrote:
On Wed, Nov 09, 2011 at 11:35:54AM -0600, Anthony Liguori wrote:
On 11/09/2011 11:02 AM, Avi Kivity wrote:
On 11/09/2011 06:39 PM, Anthony Liguori wrote:
Migration with qcow2 is not a supported feature for 1.0. Migration is
only supported
On 11/09/2011 03:00 PM, Michael S. Tsirkin wrote:
On Wed, Nov 09, 2011 at 02:22:02PM -0600, Anthony Liguori wrote:
On 11/09/2011 02:18 PM, Michael S. Tsirkin wrote:
On Wed, Nov 09, 2011 at 11:35:54AM -0600, Anthony Liguori wrote:
On 11/09/2011 11:02 AM, Avi Kivity wrote:
On 11/09/2011 06:39
-2004
Regards,
Anthony Liguori
--
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://vger.kernel.org/majordomo-info.html
On 11/07/2011 09:33 AM, Gerd Hoffmann wrote:
This patch adds a pc-1.0 machine type.
Signed-off-by: Gerd Hoffmannkra...@redhat.com
Applied both. Thanks.
Regards,
Anthony Liguori
---
hw/pc_piix.c | 14 +++---
1 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/hw
a release cadence to ensure that multiple components form
a cohesive individual release (oVirt).
I think you are trying to do this in a more organic way by just merging things
into the main git tree. Have you thought about creating a more formal kernel
incubator program?
Regards,
Anthony Liguori
anyway. With the patch applied the sound card
gets the default qemu subsystem id (1af4:1100) instead.
This a guest ABI change. Do we want -M support for it?
Given that the old subsystem id isn't valid I'd say no unless someone
comes up with a good reason.
Agreed.
Regards,
Anthony Liguori
.
Do we know that Windows won't complain about it?
I thought the original motivation for the default subsystem ids was that some
Windows test suite was explicitly complaining about having invalid subsystem ids?
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line
On 11/07/2011 08:50 AM, Avi Kivity wrote:
On 11/07/2011 04:44 PM, Anthony Liguori wrote:
This a guest ABI change. Do we want -M support for it?
Given that the old subsystem id isn't valid I'd say no unless someone
comes up with a good reason.
Do we know that Windows won't complain about
:1100) instead.
I don't like having a property of use broken.
Wouldn't it be better to have the subsystem vendor and device id be
configurable, set the default to the qemu subsystem ids, and then set it to
8086: for 1.0?
Regards,
Anthony Liguori
[ v2: old broken id is maintained
like a no-risk syscall to
whitelist and it would make programming in a sandbox so much easier. Maybe
Andrea has some comments here? I might be missing something here.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
model on every memory change. While not a super
cheap operation, it's at least amortized over time.
Regards,
Anthony Liguori
Since I'll be basing it on the KVM tool, which doesn't really emulate
that many legacy devices, I'll focus first on the virtio family for the
sake of simplicity
then bridge this to
the various types of backends.
Regards,
Anthony Liguori
Stefan
--
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://vger.kernel.org/majordomo-info.html
--
To unsubscribe from
On 11/07/2011 11:52 AM, Sasha Levin wrote:
Hi Anthony,
Thank you for your comments!
On Mon, 2011-11-07 at 11:37 -0600, Anthony Liguori wrote:
On 11/06/2011 02:40 PM, Sasha Levin wrote:
Hi all,
I'm planning on doing a small fork of the KVM tool to turn it into a
'Secure KVM' enabled
On 11/07/2011 12:43 PM, Avi Kivity wrote:
On 11/07/2011 07:39 PM, Anthony Liguori wrote:
One thing to beware of is memory hotplug. If the memory map is static,
then a fork() once everything is set up (with MAP_SHARED) alllows all
processes to access guest memory. However, if memory hotplug
kernel
related tools and helpers would probably be extremely useful. There's no reason
this needs to be linux.git though, this could just be a web page on kernel.org.
Regards,
Anthony Liguori
Pekka
--
To unsubscribe from this list: send the line unsubscribe kvm
it was the wrong syntax.
I'm quite happy with KVM tool and hope they continue working on it. My only
real wish is that they wouldn't copy QEMU so much and would try bolder things
that are fundamentally different from QEMU.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line
something like Linux.
Regards,
Anthony Liguori
The difference here is that although I feel Alex's script is a
pointless project, I'm in no way opposed to merging it in the tree if
people use it and it solves their problem. Some people seem to be
violently opposed to merging the KVM tool and I'm
at.
Regards,
Anthony Liguori
Pekka
--
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://vger.kernel.org/majordomo-info.html
other types of
guests work?
Regards,
Anthony Liguori
--
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://vger.kernel.org/majordomo-info.html
On 11/03/2011 09:31 AM, Michael S. Tsirkin wrote:
On Thu, Nov 03, 2011 at 08:49:31AM -0500, Anthony Liguori wrote:
On 11/03/2011 08:45 AM, Avi Kivity wrote:
On 11/03/2011 03:38 PM, Anthony Liguori wrote:
We could use a better agreement on the processor for making virtio
changes. Should
, but the device is only passing
down the SCSI status.
The patch fixes this, and also makes sure that the guest always sees a
CHECK_CONDITION status when there is valid sense data.
---
Applied. Thanks.
Regards,
Anthony Liguori
Sorry for missing the -rc deadline, testing this requires
On 11/02/2011 05:16 PM, Frans de Boer wrote:
When compiling QEMU 0.15.x with the option --disable-cpu-emulation, I get an
abort on fake-exec.c. It can't find the file exec.h.
QEMU does not have such an option. You're likely using qemu-kvm.
Regards,
Anthony Liguori
Any solution
On 10/31/2011 03:07 PM, Eric B Munson wrote:
This flag will be used to check if the vm was stopped by the host when a soft
lockup was detected.
Signed-off-by: Eric B Munsonemun...@mgebm.net
Adding Jeremy since the pvclock ABI is shared across Xen and KVM.
Regards,
Anthony Liguori
/. I would
suggest at least adding a description of how this bit works in the first patch.
Regards,
Anthony Liguori
+
+ return ret;
+}
+
static struct clocksource kvm_clock = {
.name = kvm-clock,
.read = kvm_clock_get_cycles,
--
To unsubscribe from this list: send
*src =vcpu-arch.hv_clock;
+ src-flags |= PVCLOCK_GUEST_STOPPED;
Shouldn't we throw some sort of error if you're trying to set a flag and
kvmclock isn't enabled?
Regards,
Anthony Liguori
+}
+EXPORT_SYMBOL_GPL(kvm_set_host_stopped);
+
int kvm_arch_vcpu_ioctl_set_sregs(struct kvm_vcpu
a
testandclear to check if the bit is set. I think that avoids the whole aging
business.
Regards,
Anthony Liguori
---
Cahnges from V1:
Add host functions for flag management to arch/x86/kvm/x86.c instead of
kvmclock.c
arch/x86/include/asm/pvclock.h |2 ++
arch/x86/kvm/x86.c
On 11/01/2011 02:51 PM, Eric B Munson wrote:
On Tue, 01 Nov 2011, Anthony Liguori wrote:
On 10/31/2011 03:07 PM, Eric B Munson wrote:
The KVM_GUEST_PAUSED flag will prevent a guest from compaining about a soft
lockup but it can mask real soft lockups if the flag isn't cleared when
think it would be good to
set up a -next staging tree but we can discuss that more in another thread.
[1] http://wiki.qemu.org/Planning/1.0
[2] http://mid.gmane.org/4ea94d53.3000...@redhat.com
[3] http://wiki.qemu.org/Planning/1.0/Testing
Regards,
Anthony Liguori
--
To unsubscribe from this list
On 10/31/2011 08:28 AM, Anthony Liguori wrote:
Hi,
Here are the logistics for the upcoming 1.0 hard freeze. All dates are reflected
in the wiki[1].
If you're a contributor and you've sent a series before the soft freeze
deadline, you've already done everything you need to do so sit back
://github.com/avikivity/qemu.git uq/master
Pulled. Thanks.
Regards,
Anthony Liguori
Avi Kivity (2):
kvm: avoid reentring kvm_flush_coalesced_mmio_buffer()
i386: wire up MSR_IA32_MISC_ENABLE
Jan Kiszka (2):
kvm: Add tool for querying VMX capabilities
kvm: Add top-like kvm
On 10/25/2011 10:32 AM, Kevin Wolf wrote:
Am 25.10.2011 16:06, schrieb Anthony Liguori:
On 10/25/2011 08:56 AM, Kevin Wolf wrote:
Am 25.10.2011 15:05, schrieb Anthony Liguori:
On 10/25/2011 07:35 AM, Kevin Wolf wrote:
Am 24.10.2011 13:35, schrieb Paolo Bonzini:
On 10/24/2011 01:04 PM, Juan
for wanting to change the default mode?
I'd be much more open to changing the default mode to cache=none FWIW since the
risk of data loss there is much, much lower.
Regards,
Anthony Liguori
Kevin
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
On 10/25/2011 08:18 AM, Dor Laor wrote:
On 10/25/2011 03:05 PM, Anthony Liguori wrote:
On 10/25/2011 07:35 AM, Kevin Wolf wrote:
Am 24.10.2011 13:35, schrieb Paolo Bonzini:
On 10/24/2011 01:04 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering
On 10/25/2011 08:56 AM, Kevin Wolf wrote:
Am 25.10.2011 15:05, schrieb Anthony Liguori:
On 10/25/2011 07:35 AM, Kevin Wolf wrote:
Am 24.10.2011 13:35, schrieb Paolo Bonzini:
On 10/24/2011 01:04 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering
and release early,
release often[http://en.wikipedia.org/wiki/Release_early,_release_often].
Regards,
Anthony Liguori
Paolo
--
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://vger.kernel.org
for
backwards compatibility in the short term but avoids repeated flag days.
Regards,
Anthony Liguori
--
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://vger.kernel.org/majordomo-info.html
On 10/11/2011 08:21 AM, Avi Kivity wrote:
On 10/11/2011 03:01 PM, Anthony Liguori wrote:
On 10/11/2011 06:48 AM, Avi Kivity wrote:
On 10/10/2011 01:35 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
Subsections, version numbers, migration
function. Finally we can pass the dummy QEMUFile to the device's load function
(or vmstate).
I'll take a look at implementing this today. I think it'll be a bit hairy but
it looks doable to me.
Regards,
Anthony Liguori
One of the ideas is to run machine, stop, save everything, reload
On 10/11/2011 08:47 AM, Avi Kivity wrote:
On 10/11/2011 03:27 PM, Anthony Liguori wrote:
5) Implement subsections through the wire as top-level sections (as
originally intended). Keep existing subsections with (1).
That was (3).
Yes, sorry.
btw, it's reasonable to require
On 10/11/2011 09:01 AM, Avi Kivity wrote:
On 10/11/2011 03:57 PM, Anthony Liguori wrote:
What I'm trying to avoid is making choices today that close the door on
better fixes in the future.
I think Juan made a really good point in his earlier post. We need to
focus on better testing
. Thanks.
Are ya'll planning on moving your repo back to kernel.org or sticking with
github?
Regards,
Anthony Liguori
Liu, Jinsong (1):
kvm: support TSC deadline MSR
target-i386/cpu.h |4 +++-
target-i386/kvm.c | 14 ++
target-i386/machine.c |1 +
3
301 - 400 of 2144 matches
Mail list logo
