Il 13/06/2013 22:55, Liu Ping Fan ha scritto:
> BH will be used outside big lock, so introduce lock to protect it.
> Note that the lock only affects the writer and bh's callback does
> not take this extra lock.
>
> Signed-off-by: Liu Ping Fan
> ---
> async.c | 10 +-
> includ
On Thu, Jun 13, 2013 at 02:10:43AM +0200, Alexander Graf wrote:
>
> On 13.06.2013, at 02:08, Alexey Kardashevskiy wrote:
>
> > On 06/13/2013 12:33 AM, Alexander Graf wrote:
> >>
> >> On 12.06.2013, at 16:27, Alexey Kardashevskiy wrote:
> >>
> >>> Signed-off-by: Alexey Kardashevskiy
> >>> ---
>
I'm no longer at IBM, and therefore no long actively working on the pseries
(aka sPAPR) qemu machine type. This patch replaces my information in the
MAINTAINERS file with that for Alexey Kardashevskiy, who is taking over
maintainership of the pseries code. While we're at it, I've added some
extra
From: Alexey Kardashevskiy
This adds a missing code to save CR (condition register) via
kvm_arch_put_registers(). kvm_arch_get_registers() already has it.
Signed-off-by: Alexey Kardashevskiy
Signed-off-by: David Gibson
---
target-ppc/kvm.c | 5 +
1 file changed, 5 insertions(+)
diff --gi
Hi Alex,
I see that you're now back from your holiday. Here, rather belatedly,
is my series of ppc related patches collected while acting ppc
maintainer. As you can see there aren't many at all. I'm not sure if
that's because I wasn't looking in the right places for people sending
patches, or th
Currently, for qemu-system-ppc64, the default machine type is 'mac99'.
The mac99 machine is not being actively maintained, and represents a
bizarre hybrid of components that never actually existed as a real system.
This patch changes the default machine to 'pseries', which is actively
maintained an
On Fri, Jun 14, 2013 at 06:14:00PM +0400, Michael Tokarev wrote:
> 14.06.2013 16:36, Gerd Hoffmann wrote:
> > Hi,
> >
> >> Hmm. Speaking of the splitting. Does the current bios include the
> >> the tables which were split into separate files?
> >
> > Yes, they are in out/ too after building s
On Fri, 2013-06-14 at 13:21 -0500, Anthony Liguori wrote:
> Alon Levy writes:
>
> > This fixes the broken screendump behavior for qxl devices in native mode
> > since 81fb6f1504fb9ef71f2382f44af34756668296e8.
> >
> > Note: due to QAPI not generating async commands yet I had to remove the
> > sche
Introduce 'load_ramdisk()' which can load "normal" ramdisks and ramdisks
with a u-boot header.
To enable this and leverage synergies 'load_uimage()' is refactored to
accomodate this additional use case.
Signed-off-by: Soren Brinkmann
---
v2:
- document the new 'load_ramdisk()' function
- print
Updated with Peter's comments. The detailed changelog can be found in the
following emails with the patches.
Sören
Soren Brinkmann (2):
hw/loader: Support ramdisk with u-boot header
hw/arm: Use 'load_ramdisk()' for loading ramdisk
hw/arm/boot.c | 8 ++---
hw/core/loader.c
The load_ramdisk function takes over loading traditional ramdisks images
and does also load ramdisks with u-boot header.
Signed-off-by: Soren Brinkmann
---
hw/arm/boot.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index f310f73..ab2b2
On 06/14/2013 09:59:18 AM, Andreas Färber wrote:
Am 13.06.2013 19:32, schrieb Scott Wood:
> On 06/13/2013 06:01:49 AM, Andreas Färber wrote:
>> Am 12.06.2013 22:32, schrieb Scott Wood:
>> > +typedef struct KVMOpenPICState {
>> > +SysBusDevice busdev;
>>
>> SysBusDevice parent_obj; please!
>>
On Fri, 2013-06-14 at 16:28 +0200, Andreas Färber wrote:
> > I would still love to see -M mac99 emulate a proper U2 or U1 based
> system for 32bit. And I would also love to see a real U4 based
> emulation model come up for qemu-system-ppc64. But I doubt I'll have
> time to work on either :).
Unino
From: "Michael R. Hines"
This exposes throughput (in megabits/sec) through QMP.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
hmp.c |2 ++
include/migration/migration.h |1 +
migration.c |6 ++
qapi-schema.json
From: "Michael R. Hines"
RDMA uses this to flush the control channel before sending its
own message to handle page registrations.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
include/migration/qemu-file.h |1 +
savevm.c |2 +-
2 files changed, 2
From: "Michael R. Hines"
This is used during RDMA initialization in order to
transmit a description of all the RAM blocks to the
peer for later dynamic chunk registration purposes.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
exec.c|9 +
inclu
From: "Michael R. Hines"
These are the prototypes and implementation of new hooks that
RDMA takes advantage of to perform dynamic page registration.
An optional hook is also introduced for a custom function
to be able to override the default save_page function.
Also included are the prototypes
From: "Michael R. Hines"
The RDMA event channel can be made non-blocking just like a TCP
socket. Exporting this function allows us to yield so that the
QEMU monitor remains available.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
include/block/coroutine.h |6 ++
qemu-
From: "Michael R. Hines"
QEMUFileRDMA also has read and write modes. This function is now
shared to reduce code duplication.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
include/migration/qemu-file.h |1 +
savevm.c | 20 +---
2 file
From: "Michael R. Hines"
docs/rdma.txt contains full documentation,
wiki links, github url and contact information.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
docs/rdma.txt | 404 +
1 file changed, 404 insertions(+)
From: "Michael R. Hines"
This capability allows you to disable dynamic chunk registration
for better throughput on high-performance links.
For example, using an 8GB RAM virtual machine with all 8GB of memory in
active use and the VM itself is completely idle using a 40 gbps infiniband link:
1.
From: "Michael R. Hines"
For very large virtual machines, pinning can take a long time.
While this does not affect the migration's *actual* time itself,
it is still important for the user to know what's going on and
to know what component of the total time is actual taken up by
pinning.
For exam
From: "Michael R. Hines"
This takes advantages of the previous patches:
1. use the new QEMUFileOps hook 'save_page'
2. call out to the right accessor methods to invoke
the iteration hooks defined in QEMUFileOps
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
arch_init.c |
From: "Michael R. Hines"
This gives RDMA shared access to madvise() on the destination side
when an entire chunk is found to be zero.
Reviewed-by: Paolo Bonzini
Signed-off-by: Michael R. Hines
---
arch_init.c | 24
include/migration/migration.h |
Chegu,
I sent a V9 to the mailing list:
The version goes even further, by explicitly timing the pinning latency and
pushing the value out to QMP so the user clearly knows which component
of total migration time is consumed by pinning.
If you're satisfied, I'd appreciate if I could add your Revi
From: "Michael R. Hines"
RDMA writes happen asynchronously, and thus the performance accounting
also needs to be able to occur asynchronously. This allows anybody
to call into savevm.c to update both f->pos as well as into arch_init.c
to update the acct_info structure with up-to-date values when
From: "Michael R. Hines"
Changes since v8:
For very large virtual machines, pinning can take a long time.
While this does not affect the migration's *actual* time itself,
it is still important for the user to know what's going on and
to know what component of the total time is act
From: "Michael R. Hines"
This patch is contained to migration-rdma.c and fixes the problems
experienced by others when the x-rdma-pin-all feature appeared to
freeze the VM. By moving this operation out of the connection setup
time and instead moving it to ram_save_setup() code, we no longer
execu
This reverts commit 047d4e151dd462915786a4fddc12f774d0028af5.
The commit in question introduced old/legacy options (-no-quit
and some more) for the new interface type (gtk), -- on the
second thought I think we shouldn't do that, instead, we should
use the display-specific options (like -display sd
Am 14.06.2013 20:12, schrieb Vincent Stehlé:
> Fix the following error, which happens when CONFIG_SDL is not defined:
>
> vl.c: In function ‘main’:
> vl.c:3528:17: error: ‘no_frame’ undeclared (first use in this function)
> vl.c:3528:17: note: each undeclared identifier is reported only once
Corey Bryant writes:
> On 06/14/2013 11:56 AM, Anthony Liguori wrote:
>> Corey Bryant writes:
>>
>>> On 06/14/2013 11:38 AM, Anthony Liguori wrote:
Corey Bryant writes:
> On 06/14/2013 10:01 AM, Anthony Liguori wrote:
>> Corey Bryant writes:
>>
>>> This patch series p
Alon Levy writes:
> This fixes the broken screendump behavior for qxl devices in native mode
> since 81fb6f1504fb9ef71f2382f44af34756668296e8.
>
> Note: due to QAPI not generating async commands yet I had to remove the
> schema screendump definition.
>
> Related RHBZ: 973374
> This patch is not e
Peter Maydell writes:
> On 14 June 2013 18:54, Peter Maydell wrote:
>> On 7 June 2013 12:58, Stefan Hajnoczi wrote:
>>> From: Kevin Wolf
>>>
>>> This checks in particular that BSY is set while the flush request is in
>>> flight.
>>
>> This test doesn't seem to pass.
>
>> ERROR:/home/petmay01/l
Fix the following error, which happens when CONFIG_SDL is not defined:
vl.c: In function ‘main’:
vl.c:3528:17: error: ‘no_frame’ undeclared (first use in this function)
vl.c:3528:17: note: each undeclared identifier is reported only once for each
function it appears in
Protect code accessi
On 14 June 2013 18:54, Peter Maydell wrote:
> On 7 June 2013 12:58, Stefan Hajnoczi wrote:
>> From: Kevin Wolf
>>
>> This checks in particular that BSY is set while the flush request is in
>> flight.
>
> This test doesn't seem to pass.
> ERROR:/home/petmay01/linaro/qemu-from-laptop/qemu/tests/i
> > Hi,
> >
> > > Note: due to QAPI not generating async commands yet I had to remove the
> > > schema screendump definition.
> >
> > Hmm, that will break libvirt I suspect. Guess this one has to wait
> > until QAPI gained proper async command support.
>
> It doesn't break anything. I've tested
> Hi,
>
> > Note: due to QAPI not generating async commands yet I had to remove the
> > schema screendump definition.
>
> Hmm, that will break libvirt I suspect. Guess this one has to wait
> until QAPI gained proper async command support.
It doesn't break anything. I've tested, and here is the
On 7 June 2013 12:58, Stefan Hajnoczi wrote:
> From: Kevin Wolf
>
> This checks in particular that BSY is set while the flush request is in
> flight.
This test doesn't seem to pass. At commit bd07684aac
(where the test landed):
cam-vm-266:precise:qemu$ (cd build/x86;
QTEST_QEMU_BINARY=i386-soft
On Fri, Jun 14, 2013 at 06:36:06PM +0100, Peter Maydell wrote:
> On 14 June 2013 18:14, Sören Brinkmann wrote:
> > On Fri, Jun 14, 2013 at 05:56:31PM +0100, Peter Maydell wrote:
> >> If we're providing separate functions for kernel and
> >> ramdisk loading shouldn't they check that the uimage
> >>
On 14 June 2013 18:14, Sören Brinkmann wrote:
> On Fri, Jun 14, 2013 at 05:56:31PM +0100, Peter Maydell wrote:
>> If we're providing separate functions for kernel and
>> ramdisk loading shouldn't they check that the uimage
>> has the appropriate type?
> I'm not sure I understand what you mean here
On 14 June 2013 18:14, Andreas Färber wrote:
> Am 14.06.2013 13:27, schrieb Peter Maydell:
>> The dtb blob returned by load_device_tree() is in memory allocated
>> with g_malloc(). Free it accordingly once we have copied its
>> contents into the guest memory. To make this easy, we need also to
>>
Hi Peter,
On Fri, Jun 14, 2013 at 05:56:31PM +0100, Peter Maydell wrote:
> On 14 June 2013 17:36, Soren Brinkmann wrote:
> > Introduce 'load_ramdisk()' which can load "normal" ramdisks and ramdisks
> > with a u-boot header.
> > To enable this and leverage synergies 'load_uimage()' is refactored t
Am 14.06.2013 13:27, schrieb Peter Maydell:
> The dtb blob returned by load_device_tree() is in memory allocated
> with g_malloc(). Free it accordingly once we have copied its
> contents into the guest memory. To make this easy, we need also to
> clean up the error handling in load_dtb() so that we
On 14 June 2013 17:36, Soren Brinkmann wrote:
> Introduce 'load_ramdisk()' which can load "normal" ramdisks and ramdisks
> with a u-boot header.
> To enable this and leverage synergies 'load_uimage()' is refactored to
> accomodate this additional use case.
Hi; thanks for this patch; some review c
Only on a real 286. At least since 486 the legacy switch has been INIT, not
RESET.
Alexander Graf wrote:
>
>
>Am 14.06.2013 um 08:56 schrieb Christian Borntraeger
>:
>
>> On 13/06/13 13:56, Anthony Liguori wrote:
>>> Markus Armbruster writes:
>>>
Peter Lieven writes:
> On 13.
Introduce 'load_ramdisk()' which can load "normal" ramdisks and ramdisks
with a u-boot header.
To enable this and leverage synergies 'load_uimage()' is refactored to
accomodate this additional use case.
Signed-off-by: Soren Brinkmann
---
hw/core/loader.c| 86 +
The load_ramdisk function takes over loading traditional ramdisks images
and does also load ramdisks with u-boot header.
Signed-off-by: Soren Brinkmann
---
hw/arm/boot.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index f310f73..ab2b2
For loading Linux kernels, QEMU already is able to recognize and load
them when they feature a U-Boot header. This patch series targets to
extend this support to ramdisks.
Furthermore the ARM support code is changed to use the new functionality.
Regards,
Sören
Soren Brinkmann (2):
On 06/14/2013 11:56 AM, Anthony Liguori wrote:
Corey Bryant writes:
On 06/14/2013 11:38 AM, Anthony Liguori wrote:
Corey Bryant writes:
On 06/14/2013 10:01 AM, Anthony Liguori wrote:
Corey Bryant writes:
This patch series provides persistent storage support that a TPM
can use to stor
Am 13.06.2013 21:02, schrieb Anthony Liguori:
> Scott Wood writes:
>
>> On 06/13/2013 01:31:48 PM, Anthony Liguori wrote:
>>> I'll note that we have a CONFIG_PSERIES today. I'd suggest getting
>>> rid
>>> of it first before making pseries the default.
>>
>> Why?
>
> I believe it's there only
Corey Bryant writes:
> On 06/14/2013 11:38 AM, Anthony Liguori wrote:
>> Corey Bryant writes:
>>
>>> On 06/14/2013 10:01 AM, Anthony Liguori wrote:
Corey Bryant writes:
> This patch series provides persistent storage support that a TPM
> can use to store NVRAM data. It uses Q
On 06/14/2013 11:38 AM, Anthony Liguori wrote:
Corey Bryant writes:
On 06/14/2013 10:01 AM, Anthony Liguori wrote:
Corey Bryant writes:
This patch series provides persistent storage support that a TPM
can use to store NVRAM data. It uses QEMU's block driver to store
data on a drive imag
On 06/14/2013 11:38 AM, Anthony Liguori wrote:
Corey Bryant writes:
On 06/14/2013 10:01 AM, Anthony Liguori wrote:
Corey Bryant writes:
This patch series provides persistent storage support that a TPM
can use to store NVRAM data. It uses QEMU's block driver to store
data on a drive image.
Corey Bryant writes:
> On 06/14/2013 10:01 AM, Anthony Liguori wrote:
>> Corey Bryant writes:
>>
>>> This patch series provides persistent storage support that a TPM
>>> can use to store NVRAM data. It uses QEMU's block driver to store
>>> data on a drive image. The libtpms TPM 1.2 backend wil
Did you guys merge back the fix in:
http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg01519.html
?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/829455
Title:
user mode network stack - hostf
From: Peter Crosthwaite
Currently QEMU provides a local clone of the file libfdt_env.h in
/include. This file is supposed to come with the libfdt package and is
only needed for broken installs of libfdt. Now that we have submodule
dtc, just ignore these broken installs and prompt for the dtc subm
From: Paolo Bonzini
Everything else needs to match the executable name, which is
TARGET_NAME.
Before:
$ sh4eb-linux-user/qemu-sh4eb --help
usage: qemu-sh4 [options] program [arguments...]
Linux CPU emulator (compiled for sh4 emulation)
After:
$ sh4eb-linux-user/qemu-sh4eb --help
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: 14 June 2013 15:58
> To: Paul Durrant
> Cc: Ian Campbell; Stefano Stabellini; qemu-devel@nongnu.org; xen-
> de...@lists.xen.org
> Subject: Re: [Xen-devel] [PATCH] Remove hardcode
On 06/14/2013 10:01 AM, Anthony Liguori wrote:
Corey Bryant writes:
This patch series provides persistent storage support that a TPM
can use to store NVRAM data. It uses QEMU's block driver to store
data on a drive image. The libtpms TPM 1.2 backend will be the
initial user of this functio
On 06/14/2013 11:56 PM, Paolo Bonzini wrote:
> Il 14/06/2013 06:09, Alexey Kardashevskiy ha scritto:
>> And - crash:
>>
>>
>> #0 object_unref (obj=0xa7a7a7a7a7a7a7a7) at
>> /home/alexey/pcipassthru/qemu-impreza/qom/object.c:691
>
> Dangling pointer. One ref, two unrefs probably.
No, subpages (a
From: Paolo Bonzini
Just use the TARGET_NAME free string.
Signed-off-by: Paolo Bonzini
Reviewed-by: Eric Blake
Message-id: 1370349928-20419-6-git-send-email-pbonz...@redhat.com
Signed-off-by: Peter Maydell
---
arch_init.c |2 +-
configure|1 -
qapi-schema.json | 18 +--
Il 14/06/2013 10:53, Peter Maydell ha scritto:
> [NB: I don't know if we get enough build-machinery patches to make
> it worth having a permanent subtree/submaintainer for them; it's
> merely that at the moment there are enough patches I personally
> care about that I felt like curating them ;-)]
Il 14/06/2013 10:31, Kevin Wolf ha scritto:
>> It looks like QCOW2_OPT_DISCARD_OTHER is a rare case, so I don't mind
>> leaving it as default to false. It won't waste more than a few clusters.
>
> Yes, it's generally relatively rare, like growing L1 or refcount table.
> There is one case where it
Am 13.06.2013 19:32, schrieb Scott Wood:
> On 06/13/2013 06:01:49 AM, Andreas Färber wrote:
>> Am 12.06.2013 22:32, schrieb Scott Wood:
>> > +typedef struct KVMOpenPICState {
>> > +SysBusDevice busdev;
>>
>> SysBusDevice parent_obj; please!
>>
>> http://wiki.qemu.org/QOMConventions
>
> The wor
Il 14/06/2013 10:11, Paul Durrant ha scritto:
> I think we're still going to need -M xenpv, I think; it's quite
> distinct from pc.
Of course! Even more: "-M xenpv" should be reused on ARM.
> I guess we could use -M pc for HVM and gate the
> accel code as you suggest but, if that's the way we're
From: Paolo Bonzini
TARGET_ARCH is generally wrong to use, there are better variables
provided in config-target.mak. The right one is usually TARGET_NAME
(previously TARGET_ARCH2), but for bsd-user we can also use TARGET_ABI_DIR
for consistency with linux-user.
Signed-off-by: Paolo Bonzini
Mes
Now that we know we're compiling with libfdt, we can remove the
CONFIG_FDT conditionals.
Signed-off-by: Peter Maydell
Reviewed-by: Edgar E. Iglesias
Reviewed-by: Peter Crosthwaite
Tested-by: Edgar E. Iglesias
Message-id: 1369409217-7553-3-git-send-email-peter.mayd...@linaro.org
---
hw/arm/boo
Hi; this is a pullrequest for a set of patches to the configure
machinery:
* Paolo's cleanups of TARGET_ARCH/TARGET_NAME
* Peter C's fix for the configure fdt probe against new libfdt
* my series making libfdt mandatory on arm/ppc/microblaze
The patches have all been on the list and reviewed; t
From: Alon Levy
For systemtap the location of the process being tapped is crucial, as a
result the existing stp file requires installation for use.
There are now two files:
$(TARGET_DIR)/$(QEMU_PROG).stp-installed: copied to $(tapdir)/$(QEMU_PROG).stp
$(TARGET_DIR)/$(QEMU_PROG).stp: pointing to
From: Paolo Bonzini
Do not introduce any new use yet.
Signed-off-by: Paolo Bonzini
Message-id: 1370349928-20419-3-git-send-email-pbonz...@redhat.com
Signed-off-by: Peter Maydell
---
Makefile.target |6 +++---
configure | 38 +++---
scrip
A number of our softmmu targets (PPC, ARM, Microblaze) now more or
less require flattened device tree support for various board models
to work correctly. Make libfdt mandatory if the target list includes
these, rather than building unhelpful half-functional binaries.
Signed-off-by: Peter Maydell
Now that we know we're compiling with libfdt we can remove the
CONFIG_FDT conditionals.
Signed-off-by: Peter Maydell
Reviewed-by: Edgar E. Iglesias
Reviewed-by: Peter Crosthwaite
Tested-by: Edgar E. Iglesias
Message-id: 1369409217-7553-4-git-send-email-peter.mayd...@linaro.org
---
hw/microbla
Now that we know we're compiling with libfdt we can remove the
CONFIG_FDT conditionals.
Signed-off-by: Peter Maydell
Reviewed-by: Edgar E. Iglesias
Reviewed-by: Peter Crosthwaite
Tested-by: Edgar E. Iglesias
Message-id: 1369409217-7553-5-git-send-email-peter.mayd...@linaro.org
---
default-con
On 14/06/13 15:14, George Dunlap wrote:
On 14/06/13 12:34, Ian Campbell wrote:
On Fri, 2013-06-14 at 11:53 +0100, George Dunlap wrote:
On Thu, Jun 13, 2013 at 6:22 PM, Ian Campbell
wrote:
On Thu, 2013-06-13 at 17:55 +0100, Stefano Stabellini wrote:
We could have a xenstore flag somewhere tha
Am 14.06.2013 um 16:16 hat Paolo Bonzini geschrieben:
> Il 14/06/2013 04:31, Kevin Wolf ha scritto:
> >>> > > +s->discard_passthrough[QCOW2_DISCARD_NEVER] = false,
> >>> > > +s->discard_passthrough[QCOW2_DISCARD_ALWAYS] = true,
> >>> > > +s->discard_passthrough[QCOW2_DISCARD_REQUEST] =
Am 13.06.2013 15:49, schrieb Alexander Graf:
> On 17.05.2013, at 09:42, Andreas Färber wrote:
>> Am 17.05.2013 06:25, schrieb David Gibson:
>>> Currently, for qemu-system-ppc64, the default machine type is 'mac99'.
>>> Since the mac99 machine is not being actively maintained, and shows quite
>>> a
Il 14/06/2013 05:48, Stefan Hajnoczi ha scritto:
> Drain and stop the dataplane thread when bdrv_drain_all() is called.
> Note that the thread will be restarted in virtio_blk_handle_output() the
> next time the guest kicks the virtqueue.
Long term I still think we want to move towards
aio_loc
Il 14/06/2013 04:31, Kevin Wolf ha scritto:
>>> > > +s->discard_passthrough[QCOW2_DISCARD_NEVER] = false,
>>> > > +s->discard_passthrough[QCOW2_DISCARD_ALWAYS] = true,
>>> > > +s->discard_passthrough[QCOW2_DISCARD_REQUEST] =
>>> > > +qemu_opt_get_bool(opts, QCOW2_OPT_DISCARD_REQ
On 14/06/13 12:34, Ian Campbell wrote:
On Fri, 2013-06-14 at 11:53 +0100, George Dunlap wrote:
On Thu, Jun 13, 2013 at 6:22 PM, Ian Campbell wrote:
On Thu, 2013-06-13 at 17:55 +0100, Stefano Stabellini wrote:
We could have a xenstore flag somewhere that enables the old behaviour
so that peop
14.06.2013 16:36, Gerd Hoffmann wrote:
> Hi,
>
>> Hmm. Speaking of the splitting. Does the current bios include the
>> the tables which were split into separate files?
>
> Yes, they are in out/ too after building seabios. Use "qemu -L
> /path/to/seabios/out" to make sure qemu picks up matchi
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: 14 June 2013 14:51
> To: Paul Durrant
> Cc: Ian Campbell; Stefano Stabellini; qemu-devel@nongnu.org; xen-
> de...@lists.xen.org
> Subject: Re: [Xen-devel] [PATCH] Remove hardcode
Il 14/06/2013 05:48, Stefan Hajnoczi ha scritto:
> Associating a BlockDriverState with a single AioContext is not flexible
> enough. Once we make BlockDriverState thread-safe, it will be possible
> to call bdrv_*() functions from multiple event loops.
I'm afraid that this is trading some pain now
Am 05.06.2013 21:51, schrieb Michael Tokarev:
> 05.06.2013 16:16, Hervé Poussineau wrote:
>> 'pd' variable has been removed in 06ef3525e1f271b6a842781a05eace5cf63b95c2.
>
> It's been removed indeed, but the value has been replaced by using
> a MemoryRegionSection instead. I understand current cod
Am 14.06.2013 15:53, schrieb Anthony Liguori:
> Markus Armbruster writes:
>
>> Next commit needs it.
>>
>> Cc: Blue Swirl
>> Signed-off-by: Markus Armbruster
>> ---
>> tests/boot-order-test.c | 24
>> 1 file changed, 16 insertions(+), 8 deletions(-)
>>
>> diff --git a/
Corey Bryant writes:
> This patch series provides persistent storage support that a TPM
> can use to store NVRAM data. It uses QEMU's block driver to store
> data on a drive image. The libtpms TPM 1.2 backend will be the
> initial user of this functionality to store data that must persist
> thr
The auto-converge migration capability allows the user to specify if they
choose live migration seqeunce to automatically detect and force convergence.
Signed-off-by: Chegu Vinod
Reviewed-by: Paolo Bonzini
Reviewed-by: Eric Blake
---
include/migration/migration.h |2 ++
migration.c
Busy enterprise workloads hosted on large sized VM's tend to dirty
memory faster than the transfer rate achieved via live guest migration.
Despite some good recent improvements (& using dedicated 10Gig NICs
between hosts) the live migration does NOT converge.
If a user chooses to force convergence
If a user chooses to turn on the auto-converge migration capability
these changes detect the lack of convergence and throttle down the
guest. i.e. force the VCPUs out of the guest for some duration
and let the migration thread catchup and help converge.
Verified the convergence using the following
Introduce an asynchronous version of run_on_cpu() i.e. the caller
doesn't have to block till the call back routine finishes execution
on the target vcpu.
Signed-off-by: Chegu Vinod
Reviewed-by: Paolo Bonzini
---
cpus.c| 29 +
include/qemu-common.h |
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: 14 June 2013 14:53
> To: Paul Durrant
> Cc: Stefano Stabellini; qemu-devel@nongnu.org; xen-de...@lists.xen.org
> Subject: Re: [PATCH] Remove hardcoded xen-platform device initial
On Thu, Jun 13, 2013 at 08:04:00PM -0500, Anthony Liguori wrote:
> Eduardo Habkost writes:
>
> > On Wed, Jun 05, 2013 at 07:57:42AM -0500, Anthony Liguori wrote:
> >> Wanlong Gao writes:
> >>
> >> > Add monitor command mem-nodes to show the huge mapped
> >> > memory nodes locations.
> >> >
> >>
Il 14/06/2013 06:09, Alexey Kardashevskiy ha scritto:
> And - crash:
>
>
> #0 object_unref (obj=0xa7a7a7a7a7a7a7a7) at
> /home/alexey/pcipassthru/qemu-impreza/qom/object.c:691
Dangling pointer. One ref, two unrefs probably.
I'm redoing the series according to Peter's request, it could fix it
Markus Armbruster writes:
> Next commit needs it.
>
> Cc: Blue Swirl
> Signed-off-by: Markus Armbruster
> ---
> tests/boot-order-test.c | 24
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/tests/boot-order-test.c b/tests/boot-order-test.c
> index 7
Markus Armbruster writes:
> The initial version did just PC. I didn't bother to separate out
> generic parts, because I don't like to abstract from a single case.
>
> Now we have two cases, PC and PowerMac, and I'm about to add two more.
> Time to do it right.
>
> To ease review, this commit cha
Il 14/06/2013 04:50, Paul Durrant ha scritto:
>> > This patch is problematic because we can't know for sure the version of
>> > upstream QEMU that is going to be used with Xen.
>> > If we apply this patch and QEMU 1.5 is going to be used with Xen 4.2,
>> > guests won't be able to use PV drivers.
>>
Il 14/06/2013 06:38, Paul Durrant ha scritto:
I think the right solution for this is to move towards using
the normal "-M pc" machine. libxl can simply use "-M pc
-machine accel=xen -device xen-platform-pv"; older versions
that use the xenfv machine will still work.
Markus Armbruster writes:
> Cc: Andreas Färber
> Cc: Alexander Graf
> Cc: qemu-...@nongnu.org
> Signed-off-by: Markus Armbruster
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
> ---
> tests/boot-order-test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/boot-order
Markus Armbruster writes:
> From: Andreas Färber
>
> They set the boot device via fw_cfg, which is then translated to a boot
> path of "hd" or "cd" in OpenBIOS.
>
> Signed-off-by: Andreas Färber
> Cc: Alexander Graf
> Cc: qemu-...@nongnu.org
> Signed-off-by: Markus Armbruster
> ---
> tests/M
Markus Armbruster writes:
> Signed-off-by: Markus Armbruster
> ---
> tests/Makefile | 2 ++
> tests/boot-order-test.c | 68
> +
> 2 files changed, 70 insertions(+)
> create mode 100644 tests/boot-order-test.c
>
> diff --git a/tests/Mak
Markus Armbruster writes:
> libqtest's qtest_init() connecting to the qtest socket triggers reset.
> This was coded in the hope we could use the same QEMU process for
> multiple tests that way. Never used. Injects an extra reset even
> when it's not used, and that can mess up tests such as the
1 - 100 of 253 matches
Mail list logo
