On Mon, Mar 25, 2013 at 08:58:49AM +0200, Michael S. Tsirkin wrote:
> On Mon, Mar 25, 2013 at 10:23:57AM +0800, Amos Kong wrote:
> > On Fri, Mar 22, 2013 at 10:45:09AM +1030, Rusty Russell wrote:
> > > "Michael S. Tsirkin" writes:
> > > > On Thu, Mar 21, 2013 at 02:44:50PM +0800, Amos Kong wrote:
Hi Peter,
On Sat, Apr 6, 2013 at 4:46 AM, Peter Maydell wrote:
> On 3 April 2013 05:32, Peter Crosthwaite wrote:
>> The LQSPI code currently manipulates the config register to achieve its
>> ends. Some (agressively designed) drivers assume that the config
>> register preserves state across a tra
On Sat, Apr 6, 2013 at 4:50 AM, Peter Maydell wrote:
> On 3 April 2013 05:32, Peter Crosthwaite wrote:
>> QSPI has a bigger FIFO than the regular SPI controller. Differentiate
>> between the two with correct FIFO sizes for each.
>>
>> Signed-off-by: Peter Crosthwaite
>> ---
>>
>> hw/xilinx_spip
On Sun, Apr 7, 2013 at 11:06 PM, Xiao Guangrong
wrote:
> On 03/23/2013 03:09 AM, Jordan Justen wrote:
>
>> Admittedly, I've been completely ineffectual in resolving the kvm
>> portion. More recently I tried to make use of KVM_MEM_READONLY to
>> address this. I was able to get an VM exit on writes
Hi Peter,
On Sat, Apr 6, 2013 at 4:53 AM, Peter Maydell wrote:
> On 3 April 2013 05:32, Peter Crosthwaite wrote:
>> Invalidate the LQSPI cached page when transitioning into LQSPI mode.
>> Otherwise there is a possibility that the controller will return stale
>> data to the guest when transitioni
Hi Peter,
On Sat, Apr 6, 2013 at 4:59 AM, Peter Maydell wrote:
> On 3 April 2013 05:33, Peter Crosthwaite wrote:
>> The QSPI controller was using byte-wide stripes when striping across
>> the two flashes in dual parallel mode. The real hardware however uses
>> individual bit striping. QEMU misbe
On Sat, Apr 6, 2013 at 5:01 AM, Peter Maydell wrote:
> On 3 April 2013 05:33, Peter Crosthwaite wrote:
>> The LQSPI bus attachment supports byte/halfword and misaligned
>> accesses. Fixed. Refactored the LQSPI cache to be byte-wise
>> instead of word wise accordingly.
>>
>> Signed-off-by: Peter C
Am 05.04.2013 um 21:23 schrieb Kevin Wolf :
> Am 26.03.2013 um 10:58 hat Peter Lieven geschrieben:
>> virtually all dup pages are zero pages. remove
>> the special is_dup_page() function and use the
>> optimized buffer_find_nonzero_offset() function
>> instead.
>>
>> here buffer_find_nonzero_off
Il 06/04/2013 00:06, Peter Lieven ha scritto:
>> > I think we should MADV_DONTNEED it.
> i have to correct myself, on Linux it seems that MADV_DONTNEED guarantees that
> subsequent reads will return a zero filled page.
>
> If I am right with that we could MADV_DONTNEED the memory on startup and ke
Am 08.04.2013 um 10:33 schrieb Peter Lieven :
>
> Am 05.04.2013 um 21:23 schrieb Kevin Wolf :
>
>> Am 26.03.2013 um 10:58 hat Peter Lieven geschrieben:
>>> virtually all dup pages are zero pages. remove
>>> the special is_dup_page() function and use the
>>> optimized buffer_find_nonzero_offset()
On Mon, Apr 08, 2013 at 01:18:10AM -0700, Jordan Justen wrote:
> On Sun, Apr 7, 2013 at 11:06 PM, Xiao Guangrong
> wrote:
> > On 03/23/2013 03:09 AM, Jordan Justen wrote:
> >
> >> Admittedly, I've been completely ineffectual in resolving the kvm
> >> portion. More recently I tried to make use of K
Am 08.04.2013 um 10:33 hat Peter Lieven geschrieben:
>
> Am 05.04.2013 um 21:23 schrieb Kevin Wolf :
>
> > Am 26.03.2013 um 10:58 hat Peter Lieven geschrieben:
> >> virtually all dup pages are zero pages. remove
> >> the special is_dup_page() function and use the
> >> optimized buffer_find_nonzer
Am 08.04.2013 um 10:49 schrieb Kevin Wolf :
> Am 08.04.2013 um 10:33 hat Peter Lieven geschrieben:
>>
>> Am 05.04.2013 um 21:23 schrieb Kevin Wolf :
>>
>>> Am 26.03.2013 um 10:58 hat Peter Lieven geschrieben:
virtually all dup pages are zero pages. remove
the special is_dup_page() fun
> -邮件原件-
> 发件人: Abel Gordon [mailto:ab...@il.ibm.com]
> 发送时间: 2013年4月8日 0:40
> 收件人: 张磊强
> 抄送: Luohao (brian); Haofeng; qemu-devel@nongnu.org; Stefan Hajnoczi;
> Stefan Hajnoczi; Zhangleiqiang
> 主题: Re: [Qemu-devel] 答复: 答复: 答复: question about performance of
> dataplane
>
>
>
> 张磊强 wrote
On 04/08/2013 04:43 PM, Gleb Natapov wrote:
> On Mon, Apr 08, 2013 at 01:18:10AM -0700, Jordan Justen wrote:
>> On Sun, Apr 7, 2013 at 11:06 PM, Xiao Guangrong
>> wrote:
>>> On 03/23/2013 03:09 AM, Jordan Justen wrote:
>>>
Admittedly, I've been completely ineffectual in resolving the kvm
On 8 April 2013 01:32, li guang wrote:
> 在 2013-04-05五的 10:23 +0100，Peter Maydell写道：
>> QEMU is fundamentally modelling real hardware platforms,
>> not abstract devices. You have to model a real power
>> controller to at least some extent, because that's what
>> guest OSes expect to be interacting
Am 08.04.2013 um 10:38 schrieb Paolo Bonzini :
> Il 06/04/2013 00:06, Peter Lieven ha scritto:
I think we should MADV_DONTNEED it.
>> i have to correct myself, on Linux it seems that MADV_DONTNEED guarantees
>> that
>> subsequent reads will return a zero filled page.
>>
>> If I am right wi
Il 08/04/2013 02:18, li guang ha scritto:
> In short, the purpose is to implement a power control process
> just like real world(hardware platform),
> a power chip(controller) connect power signals to other devices,
> and devices can do power (on, off, ...) controlled by power
> chip(controller).
Am 02.04.2013 um 13:47 hat Wenchao Xia geschrieben:
> Now image info will be retrieved as an embbed json object inside
> BlockDeviceInfo, backing chain info and all related internal snapshot
> info can be got in the enhanced recursive structure of ImageInfo.
>
> Signed-off-by: Wenchao Xia
> ---
Since bus refs its children, it introduces reference cycle when qdev
refs its parent bus.
Signed-off-by: Hu Tao
---
hw/qdev.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/hw/qdev.c b/hw/qdev.c
index e2bb37d..c84bffb 100644
--- a/hw/qdev.c
+++ b/hw/qdev.c
@@ -103,7 +103,6 @@ static void b
Am 02.04.2013 um 13:47 hat Wenchao Xia geschrieben:
> v11:
> General change:
> 5/17: check if snapshot > 0 on success in caller, add comments on the
> function says that caller need to check it on success.
> 7/17: check if snapshot > 0 on success before set info->has_snapshots.
>
> Address
Il 08/04/2013 11:25, Peter Lieven ha scritto:
>> > Actually we can use mmap+munmap to allocate a well-aligned, always zero
>> > block for the RAM.
> like this?
This doesn't align it. I'll send a patch shortly.
Paolo
On Fri, Apr 05, 2013 at 04:52:05PM -0700, Sriram Murthy wrote:
> For starters, virtual box has better SVGA WDDM drivers that allows for a much
> richer display when the VM display is local.
What does "much richer display" mean?
Stefan
Using qemu_memalign only leaves the RAM zero by chance, because libc
will usually use mmap to satisfy our huge requests. But memory will
not be zero when using MALLOC_PERTURB_ with a nonzero value. In the
case of incoming migration, this breaks a recently-introduced
invariant (commit f1c7279, mig
On Sun, Apr 07, 2013 at 04:58:07AM +, Zhanghaoyu (A) wrote:
> >> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes qemu
> >> program crashed during starting period, received signal SIGABRT.
> >> Trying about 20 times, this crash may be reproduced.
> >> I guess the cause mem
On Thu, Mar 14, 2013 at 05:57:10PM +, Peter Maydell wrote:
> -block-obj-$(CONFIG_WIN32) += coroutine-win32.o
"win32"
> +block-obj-y += coroutine-$(CONFIG_COROUTINE_BACKEND).o
...backend name expanded into object file name...
> +if test "$coroutine" = ""; then
> + if test "$mingw32" = "yes"
Zhangleiqiang wrote on 08/04/2013 12:06:17 PM:
> I think maybe Anthony is right. In previous benchmarks, maybe the
> non-dataplane already reached the physical disk's IOPS upper limit.
Yep, agree. Try to run the same benchmark in the host to see
what is the bare-metal performance of your system
On Sun, Apr 07, 2013 at 09:05:47AM -0500, Anthony Liguori wrote:
> Zhangleiqiang writes:
>
> > Hi, Stefan：
> >
> > I have done some testing to compare the performance of dataplane and
> > non-dataplane. But the result did not meet my expectations, the
> > performance of disk with dataplane
The main aim of this patchset is patch 2, which changes the coroutine
backend selection logic so that it goes 'ucontext -> sigaltstack'
rather than 'ucontext -> gthread', since the gthread backend is
broken. To do this properly on all platforms we have to refactor
the code a bit (which it needed an
The gthread coroutine backend is broken and does not produce a working
QEMU; it is only useful for some very limited debugging situations.
Clean up the backend selection logic in configure so that it now runs
"if on windows use windows; else prefer ucontext; else sigaltstack".
To do this we refact
Provide a convenience function for reporting an error and exiting,
and update various places in the configure script to use it.
This allows us to be a little more consistent about how format
our error messages and makes the calling code shorter.
Signed-off-by: Peter Maydell
Reviewed-by: Paolo Bon
On Mon, Apr 01, 2013 at 02:12:51AM +0200, Samuel Thibault wrote:
> Stefan Hajnoczi, le Mon 11 Mar 2013 09:36:14 +0100, a écrit :
> > > Otherwise we may just document that one has to disable Duplicate Address
> > > Detection to get IPv6 working :/
> >
> > Seems like this might be the only way for n
> -Original Message-
> From: Abel Gordon [mailto:ab...@il.ibm.com]
> Sent: Monday, April 08, 2013 7:04 PM
> To: Zhangleiqiang
> Cc: anth...@codemonkey.ws; Luohao (brian); Haofeng; 张磊强;
> qemu-devel@nongnu.org; Stefan Hajnoczi; Stefan Hajnoczi
> Subject: Re: 答复: [Qemu-devel] 答复: 答复: 答复: qu
On Mon, Apr 01, 2013 at 11:32:29AM +0200, Samuel Thibault wrote:
> Mike Lovell, le Mon 01 Apr 2013 00:35:03 -0600, a écrit :
> > On 03/08/2013 05:47 AM, Samuel Thibault wrote:
> > >Samuel Thibault, le Fri 08 Mar 2013 10:08:55 +0100, a écrit :
> > >>There does exist some unique address, which is ret
Signed-off-by: Paolo Bonzini
---
savevm.c | 25 +
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/savevm.c b/savevm.c
index b1d8988..c952c41 100644
--- a/savevm.c
+++ b/savevm.c
@@ -631,6 +631,11 @@ static void add_to_iovec(QEMUFile *f, const uint8_t *buf,
The same QEMUFile is never used for both read and write. Simplify
the logic to simply look for presence or absence of the right ops.
Signed-off-by: Paolo Bonzini
---
savevm.c | 68 +++-
1 file changed, 20 insertions(+), 48 deletions(-)
The recent patches to use vectored I/O for RAM migration caused a
regression in savevm speed. To restore previous performance,
add data to the buffer in qemu_put_buffer_async whenever writev_buffer
is not available in the QEMUFile.
Signed-off-by: Paolo Bonzini
---
savevm.c | 49
This fixes Kevin's reported regression with savevm, and simplifies the
QEMUFile code further.
Patch 2 could be made a bit smaller at the expense of fixing the
regression in the last patch only. I prefer to fix the bug earlier.
Tested with Autotest.
Paolo Bonzini (4):
migration: set f->is_writ
Check f->iovcnt in add_to_iovec, f->buf_index in qemu_put_buffer/byte.
Signed-off-by: Paolo Bonzini
---
savevm.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
diff --git a/savevm.c b/savevm.c
index a2f6bc0..63f4c82 100644
--- a/savevm.c
+++ b/savevm.c
@@ -626,7 +
Zhangleiqiang wrote on 08/04/2013 02:13:50 PM:
> I think do multiple benchmarks with the same situation and calc the
> average value will eliminate the "side effects".
Calculating the average of multiple benchmarks may not solve the issue.
For example, if for the dataplane scenario the "other
On Mon, 08 Apr 2013 10:13:28 +0800
li guang wrote:
> This patch should be combined with [PATCH 07/22]
>
> 在 2013-04-05五的 16:37 +0200，Igor Mammedov写道：
> > Signed-off-by: Igor Mammedov
> > ---
> > hw/ioapic_common.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/
On Wed, Apr 03, 2013 at 11:14:30PM +0100, Richard W.M. Jones wrote:
> On Thu, Mar 28, 2013 at 11:47:32AM +0100, Stefan Hajnoczi wrote:
> > On Wed, Mar 27, 2013 at 03:57:29PM +, Richard W.M. Jones wrote:
> > Please run qemu-iotests, see tests/qemu-iotests/check. For example,
> > with NBD:
> >
On Mon, 08 Apr 2013 10:02:21 +0800
li guang wrote:
> 在 2013-04-05五的 16:37 +0200，Igor Mammedov写道：
> > get_firmware_id() adds possibily for generic code to get guest visible
> > CPI id without accessing CPUArchState. If target doesn't override it,
> > it will return cpu_index.
> >
> > Override it
On Wed, Apr 03, 2013 at 05:28:39PM +0800, liu ping fan wrote:
> On Thu, Mar 28, 2013 at 10:32 PM, Stefan Hajnoczi wrote:
> > On Thu, Mar 28, 2013 at 03:55:52PM +0800, Liu Ping Fan wrote:
> >> From: Liu Ping Fan
> >>
> >> Bind each NetClientState with a GSource(ie,NetClientSource). Currently,
> >>
On Tue, Apr 02, 2013 at 05:49:57PM +0800, liu ping fan wrote:
> On Thu, Mar 28, 2013 at 9:40 PM, Stefan Hajnoczi wrote:
> > On Thu, Mar 28, 2013 at 09:42:47AM +0100, Paolo Bonzini wrote:
> >> Il 28/03/2013 08:55, Liu Ping Fan ha scritto:
> >> >3rd. block layer's AioContext will block other Aio
On Mon, 08 Apr 2013 10:24:50 +0800
li guang wrote:
> 在 2013-04-05五的 16:37 +0200，Igor Mammedov写道：
> > * introduce processor status bitmask visible to guest at 0xaf00 addr,
> > where Seabios expects it
> > * set bit corresponding to APIC ID in processor status bitmask on
> > receiving CPU hot-p
On Mon, Apr 01, 2013 at 04:15:06PM +0800, liu ping fan wrote:
> On Thu, Mar 28, 2013 at 10:55 PM, Stefan Hajnoczi wrote:
> >
> > On Thu, Mar 28, 2013 at 03:55:51PM +0800, Liu Ping Fan wrote:
> > It seems the AioContext vs glib issue hasn't been settled yet. My take
> > is that glib is preferrable
On Thu, Mar 28, 2013 at 10:53:28AM +0200, Dmitry Fleytman wrote:
> These patch set introduces 2 fixes:
> 1. Compatibility with iPXE vmxnet3 driver
> Reported-by: Stefan Hajnoczi
> 2. Duplicate byte swapping while parsing device features
> on big endian platforms
> Reported-by: A
On Mon, Apr 01, 2013 at 07:56:33AM +, Liuji (Jeremy) wrote:
> I delete the "dev->sin = NULL;" in the last of "spice_char_device_reset"
> function. And the "loadvm" is OK.
>
> But I don't know whether this change will lead to other problems. Who can
> give me some advice?
See the ./MAINTAINE
On Mon, Apr 01, 2013 at 11:45:13AM +, Liuji (Jeremy) wrote:
> Hello, everyone
>
> After executing the "savevm" command, the QEMU process is hanging.
> But in the v1.4.0, it's no problem.
>
> Host OS: Fedora 17 x86_64
> Qemu: the latest(2013-04-01)
> Quest OS: WinXP
>
> 1) Use the following c
Stefan Hajnoczi, le Mon 08 Apr 2013 13:13:19 +0200, a écrit :
> On Mon, Apr 01, 2013 at 02:12:51AM +0200, Samuel Thibault wrote:
> > Stefan Hajnoczi, le Mon 11 Mar 2013 09:36:14 +0100, a écrit :
> > > > Otherwise we may just document that one has to disable Duplicate Address
> > > > Detection to ge
On Mon, Apr 01, 2013 at 09:18:55PM -0700, Richard Henderson wrote:
> The build has been broken for *far* too long.
>
> Can we please apply *any* of the patches that have been posted to
> fix it. Even if the patch is not 100% correct, a non-working driver
> is preferred to a compile error that aff
On Tue, Apr 02, 2013 at 04:29:32PM +0300, Gleb Natapov wrote:
> > static void kvm_sw_tlb_put(PowerPCCPU *cpu)
> > {
> > CPUPPCState *env = &cpu->env;
> > diff --git a/target-s390x/cpu.c b/target-s390x/cpu.c
> > index 23fe51f..6321384 100644
> > --- a/target-s390x/cpu.c
> > +++ b/target-s390x
On Fri, Apr 05, 2013 at 06:30:02AM +, Lal Nitesh-B44382 wrote:
> I was trying to figure out how SIGUSR1 is been handled by QEMU as I am
> getting multiple SIGUSR1 in my trace when I run the guest .
> If anyone could guide me on this, that would be of great help.
Use grep:
$ git grep SIGUSR1
On Sun, Apr 07, 2013 at 04:58:07AM +, Zhanghaoyu (A) wrote:
> >>> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes
> >>> qemu program crashed during starting period, received signal SIGABRT.
> >>> Trying about 20 times, this crash may be reproduced.
> >>> I guess the cause
On Fri, Apr 05, 2013 at 11:58:09PM -0400, Gaston Gutierrez wrote:
> I installed rpiqemuwindows in a lenovo T420, 64bits, intel core i5 2.5GHz,
> 4GB RAM, win7 motebok.
> At running 2013-02-09-wheezy-raspbian.img, the boot process enters in a
> loop and throws
>
> INIT: Id "1" respawning too fast :
From: Dmitry Fleytman
Byte swap is redundant because shared memory reading functions
already swap bytes when required
Signed-off-by: Dmitry Fleytman
Acked-by: Alexander Graf
Signed-off-by: Stefan Hajnoczi
---
hw/vmxnet3.h | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
dif
From: Dmitry Fleytman
iPXE vmxnet3 driver makes a few assumptions regarding device operation
that were missed during testing with Linux and Windows drivers.
This patch adds following logic:
1. Additional GET commands processing added
2. Max number of RX chunks should be set to 1 when driver p
These vmxnet3 fixes solve big-endian host build failures and make iPXE's
vmxnet3 driver work.
Dmitry Fleytman (2):
vmxnet3: iPXE compatibility fixes
vmxnet3: const_cpu_to_le64 wrapping for feature bits dropped
hw/vmxnet3.c | 11 +++
hw/vmxnet3.h | 11 ---
2 files changed, 15
On 26 March 2013 14:35, Andreas Färber wrote:
> Am 26.03.2013 13:20, schrieb Peter Maydell:
>> Commit b350ab75 causes segfaults on accesses to PVR/PRR/CVR because
>> it tries to call SUPERH_CPU_GET_CLASS() on a pointer that isn't a
>> QOM object. Fix this by getting the actual QOM CPU object first
On Mon, Apr 08, 2013 at 01:37:28PM +0200, Stefan Hajnoczi wrote:
> Just ./check -nbd and ./check -ssh should work.
Both work 100% for me (with patch v7).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fe
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Monday, April 08, 2013 7:09 PM
>
> On Sun, Apr 07, 2013 at 09:05:47AM -0500, Anthony Liguori wrote:
> > Zhangleiqiang writes:
> >
> > > 1. Environment:
> > > a). Qemu 1.4 master branch
> > > b). kernel:
I misread the glib manual, g_source_remove does not let you re-attach
the source later. This behavior (called "blocking" the source in glib)
is present in glib's source code, but private and not available outside
glib; hence, we have to resort to re-creating the source every time.
In fact, g_sour
More specifically, here's the output on my machine:
rjones@choo:~/d/qemu/tests/qemu-iotests$
QEMU_PROG=~/d/qemu/x86_64-softmmu/qemu-system-x86_64 PATH=~/d/qemu:$PATH
./check -ssh
QEMU -- /home/rjones/d/qemu/x86_64-softmmu/qemu-system-x86_64
QEMU_IMG -- /home/rjones/d/qemu/qemu-img
Hi,
This proposal aims to add support for VNC LED state extension to
Qemu VNC server. It also contains the proposal of this VNC extension,
althrough it should be sent to some other mailing, but we'd like to
send to Qemu mailing list first to have your suggestion. Please
let me know your ideas and
This enables reuse when preparing per-table fw_cfg blobs later.
Signed-off-by: Laszlo Ersek
---
hw/acpi.h |2 ++
hw/acpi.c | 39 ---
2 files changed, 26 insertions(+), 15 deletions(-)
diff --git a/hw/acpi.h b/hw/acpi.h
index d69b6ef..e3e17e9 100644
---
This enables reuse when preparing per-table fw_cfg blobs later.
Signed-off-by: Laszlo Ersek
---
hw/acpi.h | 11 +++
hw/acpi.c | 48 +---
2 files changed, 32 insertions(+), 27 deletions(-)
diff --git a/hw/acpi.h b/hw/acpi.h
index e18ef28..d
Again, this enables reuse when preparing per-table fw_cfg blobs later.
Signed-off-by: Laszlo Ersek
---
hw/acpi.h |2 ++
hw/acpi.c |2 +-
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/hw/acpi.h b/hw/acpi.h
index e3e17e9..2c89e59 100644
--- a/hw/acpi.h
+++ b/hw/acpi.h
@@ -
Soon we'll declare a function in "hw/pc.h" that takes a
pointer-to-FWCfgState. That would be inconsistent with current usage --
some places use pointer-to-void now even though they mean
pointer-to-FWCfgState. Clean them up.
Signed-off-by: Laszlo Ersek
---
hw/loader.h |3 ++-
hw/multi
This series exports the MADT (APIC) ACPI table under the new
"etc/acpi/APIC" fw_cfg file. I sought to follow the requirements set
forth in [1], the new table is only visible in the patched/patched case.
I cross-tested { master, patched } qemu with { master, patched } seabios
(the APIC, DSDT and RSD
On Tue, Apr 02, 2013 at 07:47:22PM +0800, Wenchao Xia wrote:
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index 1e0e11e..6b20684 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -1765,6 +1765,61 @@ EQMP
> },
>
> SQMP
> +query-snapshots
> +---
> +
> +Show the int
On Tue, Apr 02, 2013 at 07:47:24PM +0800, Wenchao Xia wrote:
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index 6b20684..b856be7 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -1703,6 +1703,47 @@ Each json-object contain the following:
> - "iops": limit total I/O operat
On Tue, Apr 02, 2013 at 07:47:26PM +0800, Wenchao Xia wrote:
> diff --git a/qemu-img.c b/qemu-img.c
> index 5b229a9..032f68c 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -1558,18 +1558,24 @@ static void dump_snapshots(BlockDriverState *bs)
> {
> QEMUSnapshotInfo *sn_tab, *sn;
> int
Signed-off-by: Laszlo Ersek
---
src/acpi.c | 29 -
1 files changed, 28 insertions(+), 1 deletions(-)
diff --git a/src/acpi.c b/src/acpi.c
index bc4d8ea..9e128b2 100644
--- a/src/acpi.c
+++ b/src/acpi.c
@@ -393,6 +393,33 @@ build_madt(void)
return madt;
}
+s
Hi, Stefan
Thanks for your reply.
I have test the latest version of
qemu.git/master(commit:9196dd411d580c27f85daa209ff9a501d719ebc0,2013-04-06).
But, this problem still exists.
This problem appears after the commit(500f0061d628b52220038939728f0d7aee634468,
Use qemu_put_buffer_async for guest
On Tue, Apr 02, 2013 at 07:47:13PM +0800, Wenchao Xia wrote:
> In the use of snapshot a way to retrieve related info at runtime is needed,
> so this serial of patches will merge some code for qemu and qemu-img, and add
> or enchance following interfaces for qemu:
Looks pretty good, I commented o
Il 08/04/2013 14:19, Gleb Natapov ha scritto:
>> > Does this compile with kvm support disabled?
Oops, sorry, I thought I had replied to this email (with "hmm, let me
check").
> Well, it does not:
> CCs390x-softmmu/target-s390x/cpu.o
> /users/gleb/work/qemu/target-s390x/cpu.c: In function 's
Hi
Please send in any agenda topics you are interested in.
Later, Juan.
With pipelining it is possible to encounter a finished packet when cleaning
the queue due to a halt. This happens when a non stall error happens while
talking to a real device. In this case the queue on the usb-host side will
continue processing packets, and we can have completed packets waiting in
The set of per-table fw_cfg files is installed with the new function
pc_acpi_fw_cfg_init().
This function is called at the end of pc_init1() and pc_q35_init():
pc_init1() or pc_q35_init()
pc_acpi_init() < very early
/* bunch of setup code */
pc_acpi_fw_cfg_init()
Paolo Bonzini writes:
> I misread the glib manual, g_source_remove does not let you re-attach
> the source later. This behavior (called "blocking" the source in glib)
> is present in glib's source code, but private and not available outside
> glib; hence, we have to resort to re-creating the sou
On Mon, 8 Apr 2013 12:00:35 +0200
Michal Novotny wrote:
> This alters the query-machines QMP command to output information
> about maximum number of CPUs for each machine type with default
> value 1 in case the number of max_cpus is not set.
>
> Signed-off-by: Michal Novotny
> ---
> qapi-sche
Paolo Bonzini writes:
I misread the glib manual, g_source_remove does not let you re-attach
the source later. This behavior (called "blocking" the source in glib)
is present in glib's source code, but private and not available outside
glib;
Hmm, have you filed a bug upstream asking them to m
Hi,
Paolo send a patch series today fixing a problem with savevm
http://www.mail-archive.com/qemu-devel@nongnu.org/msg165135.html
Can you check if it solves the issue?
Regards,
Orit
On 04/08/2013 04:39 PM, Liuji (Jeremy) wrote:
> Hi, Stefan
>
> Thanks for your reply.
>
> I have test the latest
Il 08/04/2013 16:08, Hans de Goede ha scritto:
>
>> I misread the glib manual, g_source_remove does not let you re-attach
>> the source later. This behavior (called "blocking" the source in glib)
>> is present in glib's source code, but private and not available outside
>> glib;
>
> Hmm, have yo
On Wed, Apr 03, 2013 at 03:30:58PM +0900, Eiichi Tsukata wrote:
> diff --git a/scripts/tracetool/backend/ftrace.py
> b/scripts/tracetool/backend/ftrace.py
> new file mode 100644
> index 000..e02f0ca
> --- /dev/null
> +++ b/scripts/tracetool/backend/ftrace.py
> @@ -0,0 +1,53 @@
> +#!/usr/bin/en
On Wed, Apr 03, 2013 at 03:30:57PM +0900, Eiichi Tsukata wrote:
> This patchset introduces a new tracing backend "ftrace".
>
> Currently, QEMU tracing backends do not support userspace tracing with ftrace.
> Collecting QEMU trace data and kernel trace data simultaniouly is useful for
> latency ana
Just for clarification why I did this: Some of the libvirt guys would
like the functionality to know number of CPUs supported per machine
type. This usually doesn't matter on x86 architectures however it
matters on ARM, for example, because highbank machine type supports up
to 4 CPUs however integr
On Wed, Apr 03, 2013 at 12:25:03PM +0300, Alex DAMIAN wrote:
> @@ -390,9 +386,7 @@ uint32_t vga_ioport_read(void *opaque, uint32_t addr)
> break;
> case VGA_SEQ_D:
> val = s->sr[s->sr_index];
> -#ifdef DEBUG_VGA_REG
> -printf("vga: read SR%x = 0x%02x\n
On Wed, Apr 03, 2013 at 05:25:06PM +0200, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf
> ---
> tests/qemu-iotests/051 | 143 +++
> tests/qemu-iotests/051.out | 162
> +
> tests/qemu-iotests/group | 1 +
> 3
Am 08.04.2013 14:19, schrieb Gleb Natapov:
> On Tue, Apr 02, 2013 at 04:29:32PM +0300, Gleb Natapov wrote:
>>> static void kvm_sw_tlb_put(PowerPCCPU *cpu)
>>> {
>>> CPUPPCState *env = &cpu->env;
>>> diff --git a/target-s390x/cpu.c b/target-s390x/cpu.c
>>> index 23fe51f..6321384 100644
>>> --
On Fri, Apr 05, 2013 at 02:07:52PM +0100, Richard W.M. Jones wrote:
> +/* DEBUG_SSH=1 enables the DPRINTF (debugging printf) statements in
> + * this block driver code.
> + *
> + * TRACE_LIBSSH2= enables tracing in libssh2 itself. Note
> + * that this requires that libssh2 was specially compiled w
This patch series converts target-arm to doing migration via
a VMState structure, and fixes some minor bugs in migration
of the CPU as well. The bulk of it is a patch Juan sent out
back in the middle of last year
https://lists.gnu.org/archive/html/qemu-devel/2012-05/msg00550.html
which I have reba
Am 08.04.2013 um 12:47 schrieb Paolo Bonzini :
> Using qemu_memalign only leaves the RAM zero by chance, because libc
> will usually use mmap to satisfy our huge requests. But memory will
> not be zero when using MALLOC_PERTURB_ with a nonzero value. In the
> case of incoming migration, this br
On Mon, Apr 8, 2013 at 3:05 PM, Richard W.M. Jones wrote:
> More specifically, here's the output on my machine:
>
> rjones@choo:~/d/qemu/tests/qemu-iotests$
> QEMU_PROG=~/d/qemu/x86_64-softmmu/qemu-system-x86_64 PATH=~/d/qemu:$PATH
> ./check -ssh
gah, I just hit a libssh2 limitation. In my .ss
By "richer display", I meant support for different resolution and color depth
(including support for nonstandard resolutions as well).
-Sriram
- Original Message -
From: Stefan Hajnoczi
To: Sriram Murthy
Cc: "k...@vger.kernel.org" ; qemu list
Sent: Monday, April 8, 2013 3:46 AM
Sub
On 6 April 2013 00:52, Sriram Murthy wrote:
> (actually, the virtualbox SVGA card is based off of the KVM VGA card)
Is it possible to implement it as an extension to the VGA
card device, or has it diverged incompatibly such that it
has to be its own separate device model?
thanks
-- PMM
A number of CPU state fields were accidentally omitted from
our migration state: some OMAP specific cp15 registers, and
some related to state for load/store exclusive insns. Add them.
Signed-off-by: Peter Maydell
---
target-arm/machine.c | 13 ++---
1 file changed, 10 insertions(+), 3
From: Juan Quintela
Port the ARM CPU save/load code to use VMState. Some state is
saved in a slightly different order to simplify things -- for
example arrays are saved one after the other rather than 'striped',
and we always save all 32 VFP registers even if the CPU happens
to only have 16.
Use
Use the helper functions to save and restore the FPSCR, so that
we correctly propagate rounding mode and flushing behaviour into
the float_status fields. This also allows us to stop saving the
vector length/stride fields separately.
Signed-off-by: Peter Maydell
---
target-arm/machine.c | 48 ++
1 - 100 of 181 matches
Mail list logo
