Re: [Qemu-devel] [v1 Patch 2/10]Qemu: Error classes for hostcache setting and data sync failures

On 07/09/2012 08:17 PM, Kevin Wolf wrote: Am 15.06.2012 22:47, schrieb Supriya Kannery: New error classes defined for hostcache setting and data sync error Signed-off-by: Supriya Kannery --- qerror.c |8 qerror.h |6 ++ 2 files changed, 14 insertions(+) Index: qemu/qe

Re: [Qemu-devel] [PATCH 09/11] Add migration accounting for normal and duplicate pages

On 07/27/2012 01:41 AM, Eric Blake wrote: > On 07/25/2012 08:50 AM, Orit Wasserman wrote: >> Signed-off-by: Benoit Hudzia >> Signed-off-by: Petter Svard >> Signed-off-by: Aidan Shribman >> Signed-off-by: Orit Wasserman >> Signed-off-by: Juan Quintela >> --- >> +++ b/qapi-schema.json >> @@ -264

Re: [Qemu-devel] [v1 Patch 1/10]Qemu: Enhance "info block" to display host cache setting

On 07/05/2012 10:08 PM, Jeff Cody wrote: On 06/15/2012 04:47 PM, Supriya Kannery wrote: Enhance "info block" to display hostcache setting for each block device. Example: (qemu) info block ide0-hd0: removable=0 file=../rhel6-32.raw ro=0 drv=raw encrypted=0 Enhanced to display "hostcache" settin

Re: [Qemu-devel] [PATCH 07/11] Add XBZRLE to ram_save_block and ram_save_live

On 07/27/2012 01:20 AM, Eric Blake wrote: > On 07/25/2012 08:50 AM, Orit Wasserman wrote: >> In the outgoing migration check to see if the page is cached and >> changed than send compressed page by using save_xbrle_page function. > > s/changed than/changed, then/ > >> In the incoming migration ch

Re: [Qemu-devel] [v1 Patch 1/10]Qemu: Enhance "info block" to display host cache setting

On 07/11/2012 07:33 PM, Luiz Capitulino wrote: On Mon, 09 Jul 2012 16:43:40 +0200 Kevin Wolf wrote: Am 15.06.2012 23:07, schrieb Eric Blake: On 06/15/2012 02:47 PM, Supriya Kannery wrote: Enhance "info block" to display hostcache setting for each block device. ## { 'type': 'BlockInfo

Re: [Qemu-devel] [PATCH 04/11] Add cache handling functions

On 07/27/2012 12:51 AM, Eric Blake wrote: > On 07/25/2012 08:50 AM, Orit Wasserman wrote: >> Add LRU page cache mechanism. >> The page are accessed by their address. >> >> Signed-off-by: Benoit Hudzia >> Signed-off-by: Petter Svard >> Signed-off-by: Aidan Shribman >> Signed-off-by: Orit Wasserma

[Qemu-devel] buildbot failure in qemu on xen41

The Buildbot has detected a new failure on builder xen41 while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/xen41/builds/77 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: anthony_xen Build Reason: The Nightly scheduler n

[Qemu-devel] buildbot failure in qemu on xen_unstable

The Buildbot has detected a new failure on builder xen_unstable while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/xen_unstable/builds/77 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: anthony_xen Build Reason: The Nigh

Re: [Qemu-devel] [PATCH v10 00/15] QEMU OpenRISC support

Hi Blue, and other maintainers, On Sat, Jul 28, 2012 at 8:13 PM, Blue Swirl wrote: > On Fri, Jul 20, 2012 at 7:50 AM, Jia Liu wrote: >> This is the OpenCores OpenRISC 1200 support for QEMU. >> Full implementation of the system-model and linux-user-model support. >> >> OpenRISC 1200 is a OpenCore

Re: [Qemu-devel] [PATCH 0/3] Attempting to run Microport UNIX (ca 1987)

On Sat, Jul 28, 2012 at 08:33:54AM +0200, Markus Armbruster wrote: > Matthew Ogilvie writes: [...] > > 1. It doesn't seem to recognize the hard drive geometry, even > > if I use "-hdachs" and keep it carefully inside ancient > > limitations. Note that at the time, hard drives did not

[Qemu-devel] buildbot failure in qemu on disable_kvm_x86_64_out_of_tree

The Buildbot has detected a new failure on builder disable_kvm_x86_64_out_of_tree while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/disable_kvm_x86_64_out_of_tree/builds/530 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Buil

[Qemu-devel] buildbot failure in qemu on disable_kvm_i386_out_of_tree

The Buildbot has detected a new failure on builder disable_kvm_i386_out_of_tree while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/disable_kvm_i386_out_of_tree/builds/530 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: y

[Qemu-devel] buildbot failure in qemu on disable_kvm_x86_64_debian_6_0

The Buildbot has detected a new failure on builder disable_kvm_x86_64_debian_6_0 while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/disable_kvm_x86_64_debian_6_0/builds/343 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build:

[Qemu-devel] buildbot failure in qemu on disable_kvm_i386_debian_6_0

The Buildbot has detected a new failure on builder disable_kvm_i386_debian_6_0 while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/disable_kvm_i386_debian_6_0/builds/343 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: yuz

[Qemu-devel] buildbot failure in qemu on default_i386_debian_6_0

The Buildbot has detected a new failure on builder default_i386_debian_6_0 while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/default_i386_debian_6_0/builds/342 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: yuzuki Buil

[Qemu-devel] buildbot failure in qemu on default_i386_out_of_tree

The Buildbot has detected a new failure on builder default_i386_out_of_tree while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/default_i386_out_of_tree/builds/528 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: yuzuki Bu

[Qemu-devel] buildbot failure in qemu on default_x86_64_out_of_tree

The Buildbot has detected a new failure on builder default_x86_64_out_of_tree while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/default_x86_64_out_of_tree/builds/528 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: yuzuk

[Qemu-devel] buildbot failure in qemu on default_openbsd_current

The Buildbot has detected a new failure on builder default_openbsd_current while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/default_openbsd_current/builds/332 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: brad_openbsd

[Qemu-devel] buildbot failure in qemu on default_openbsd_4.9

The Buildbot has detected a new failure on builder default_openbsd_4.9 while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/default_openbsd_4.9/builds/331 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: kraxel_openbsd49 Bu

[Qemu-devel] buildbot failure in qemu on default_x86_64_debian_6_0

The Buildbot has detected a new failure on builder default_x86_64_debian_6_0 while building qemu. Full details are available at: http://buildbot.b1-systems.de/qemu/builders/default_x86_64_debian_6_0/builds/342 Buildbot URL: http://buildbot.b1-systems.de/qemu/ Buildslave for this Build: yuzuki

Re: [Qemu-devel] [PATCH RFC v4 18/18] MAINTAINERS: Document virtex_ml507 machine

On 26 July 2012 13:28, Andreas Färber wrote: > It's a ppc440, so place it close to Bamboo. ...I thought these sections were supposed to be in alphabetical order? (the existing entries in MAINTAINERS generally seem to be mostly in alpha order except occasionally where we've messed up). -- PMM

[Qemu-devel] [PATCH] build: Fix linking failure for qemu-ga

From: Dunrong Huang This patch will fix the following linking failed: LINK qemu-ga gcc: error: qga/../qapi-generated/qga-qapi-types.o: No such file or directory gcc: error: qga/../qapi-generated/qga-qapi-visit.o: No such file or directory gcc: error: qga/../qapi-generated/qga-qmp-marshal.o: N

Re: [Qemu-devel] [BUG] BSOD on Win2003 Server when 64bit PCI resource is present

Hi Kevin, >Unfortunately, it's very difficult to debug acpi issues on Windows. >Gerd's been on vacation this week - so, lets give him a chance to look >at it when he gets back. If it can't be resolved, we'll need to >revert the patch that broke Win2003. Thank you for your reply. Right - acpi iss

Re: [Qemu-devel] [PATCH RFC v4 18/18] MAINTAINERS: Document virtex_ml507 machine

Am 27.07.2012 19:42, schrieb Edgar E. Iglesias: > Acked-by: Edgar E. Iglesias > > > Im currently traveling but can apply when Im back. Thanks. This patch as is depends on the Bamboo addition just above, so either Anthony or Alex can handle it. Regards, Andreas

Re: [Qemu-devel] [SeaBIOS] [BUG] BSOD on Win2003 Server when 64bit PCI resource is present

Bug Check 0xA5: ACPI_BIOS_ERROR Bug Check 0x2: DEVICE_QUEUE_NOT_BUSY http://msdn.microsoft.com/en-us/library/windows/hardware/ff560114%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/windows/hardware/ff557475%28v=vs.85%29.aspx - at the bottom there is a send comment to Microsoft form htt

Re: [Qemu-devel] [RFC][PATCH v4 3/3] tcg: Optimize qemu_ld/st by generating slow paths at the end of a block

On 2012년 07월 25일 23:00, Richard Henderson wrote: On 07/25/2012 12:35 AM, Yeongkyoon Lee wrote: +#if defined(CONFIG_QEMU_LDST_OPTIMIZATION) && defined(CONFIG_SOFTMMU) +/* Macros/structures for qemu_ld/st IR code optimization: + TCG_MAX_HELPER_LABELS is defined as same as OPC_BUF_SIZE in exec-al

Re: [Qemu-devel] [BUG] BSOD on Win2003 Server when 64bit PCI resource is present

On Thu, Jul 26, 2012 at 03:38:47PM +, Alexey Korolev wrote: > HI, > > Current version of Seabios is causing blue screen on Windows2003 when 64bit > PCI resource is present and occupies high memory. > > BSOD Error code is: 0x00A5 (0x02, 0xfADF6A446880, 0x1, > 0xFADFAA34690) > >

Re: [Qemu-devel] [PATCH 20/27] qapi-schema: add ErrorClass enum

On 07/27/2012 03:32 PM, Luiz Capitulino wrote: > Signed-off-by: Luiz Capitulino > --- > qapi-schema.json | 26 ++ > 1 file changed, 26 insertions(+) > > diff --git a/qapi-schema.json b/qapi-schema.json > index 7500754..b1325c4 100644 > --- a/qapi-schema.json > +++ b/qapi-

Re: [Qemu-devel] [PATCH 00/47] Block job improvements for 1.2

On 07/24/2012 05:03 AM, Paolo Bonzini wrote: > Hi all, this is the first non-RFC submission of my block job patches > for 1.2. Everything is there, including multiple in-flight operations > in the mirroring job and new testcases (for all of streaming, mirroring, > hierarchical bitmap). The tests

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On 28 July 2012 13:31, Blue Swirl wrote: > I'm getting this error, probably because now Valgrind support is enabled: > CCcoroutine-ucontext.o > cc1: warnings being treated as errors > /src/qemu/coroutine-ucontext.c:204: error: unknown option after > '#pragma GCC diagnostic' kind > /src/qemu/

Re: [Qemu-devel] [PATCH 44/47] mirror: switch mirror_iteration to AIO

On 07/24/2012 05:04 AM, Paolo Bonzini wrote: > There is really no change in the behavior of the job here, since there > is still a maximum of one in-flight I/O operation between the source and > the target. However, this patch already introduces moves the copy logic grammar: 'already introduces m

Re: [Qemu-devel] [PATCH 43/47] mirror: allow customizing the granularity

On 07/24/2012 05:04 AM, Paolo Bonzini wrote: > The desired granularity may be very different depending on the kind of > operation (e.g. continous replication vs. collapse-to-raw) and whether s/continous/continuous/ > the VM is expected to perform lots of I/O while mirroring is in progress. > Allo

Re: [Qemu-devel] [PATCH 37/47] add hierarchical bitmap data type and test cases

On 07/24/2012 05:04 AM, Paolo Bonzini wrote: > HBitmaps provide an array of bits. The bits are stored as usual in an > array of unsigned longs, but HBitmap is also optimized to provide fast > iteration over set bits; going from one bit to the next is O(logB n) > worst case, with B = sizeof(long) *

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On Sat, Jul 28, 2012 at 12:14 PM, Peter Maydell wrote: > On 28 July 2012 13:09, Blue Swirl wrote: >> On Sat, Jul 28, 2012 at 10:57 AM, Peter Maydell >> wrote: >>> On 28 July 2012 10:04, Blue Swirl wrote: , I'm getting configure breakage in some cases: >>> >>> The thesis of the patch series

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On Sat, Jul 28, 2012 at 12:14 PM, Peter Maydell wrote: > On 28 July 2012 13:09, Blue Swirl wrote: >> On Sat, Jul 28, 2012 at 10:57 AM, Peter Maydell >> wrote: >>> On 28 July 2012 10:04, Blue Swirl wrote: , I'm getting configure breakage in some cases: >>> >>> The thesis of the patch series

Re: [Qemu-devel] [PATCH] hw/escc: Drop duplicate definition of 'disabled' property

Thanks, applied. On Tue, Jul 24, 2012 at 2:10 PM, Peter Maydell wrote: > Drop a duplicate definition of the 'disabled' property from > the escc qdev property list: this redefinition is currently > effectively ignored but will become an error. (The duplication > was inadvertently introduced in 200

Re: [Qemu-devel] [PATCH 0/2] build: get all *.d files

Thanks, applied all. On Wed, Jul 11, 2012 at 2:40 PM, Paolo Bonzini wrote: > Avi and Jan experienced more problem with dependencies. This series > should fix them. > > Paolo Bonzini (2): > build: include qapi-generated/ files in qga/Makefile.objs > build: get dependency file directories from

Re: [Qemu-devel] [PATCH] target-xtensa: fix big-endian BBS/BBC implementation

Thanks, applied. On Tue, Jul 17, 2012 at 7:45 PM, Max Filippov wrote: > Quote from ISA, 2.1: > > For most Xtensa instructions, bit numbering is irrelevant; only the BBC > and BBS instructions assign bit numbers to values on which the processor > operates. The BBC/BBS instructions use big-endian b

Re: [Qemu-devel] [PATCH resend] tests: Makefile: include dependency files

On Wed, Jul 18, 2012 at 5:22 PM, Eduardo Habkost wrote: > Otherwise 'make check' won't recompile files that need to be recompiled > because of header changes. > > To reproduce the bug, run: > > $ make check # succeeds > $ echo B0RKED > hw/mc146818rtc_regs.h > $ make check # is supposed to try

Re: [Qemu-devel] [PATCH] vl.c: Don't print errno after failed qemu_chr_new()

On Sat, Jul 21, 2012 at 9:07 AM, Peter Maydell wrote: > Ping? > > patchwork url: http://patchwork.ozlabs.org/patch/169860/ Thanks, applied. > > -- PMM > > On 9 July 2012 15:28, Peter Maydell wrote: >> The qemu_chr_new() function doesn't set errno on failure, so >> don't print strerror(errno) on

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On 28 July 2012 13:09, Blue Swirl wrote: > On Sat, Jul 28, 2012 at 10:57 AM, Peter Maydell > wrote: >> On 28 July 2012 10:04, Blue Swirl wrote: >>>, I'm getting configure breakage in some cases: >> >> The thesis of the patch series is that these represent bugs to be fixed. > > Yes, but then the

Re: [Qemu-devel] [PATCH v10 00/15] QEMU OpenRISC support

On Fri, Jul 20, 2012 at 7:50 AM, Jia Liu wrote: > This is the OpenCores OpenRISC 1200 support for QEMU. > Full implementation of the system-model and linux-user-model support. > > OpenRISC 1200 is a OpenCores open source CPU, > its architecture manual can be found at > http://opencores.org/svnget,

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On Sat, Jul 28, 2012 at 10:57 AM, Peter Maydell wrote: > On 28 July 2012 10:04, Blue Swirl wrote: >> On Wed, Jul 18, 2012 at 2:10 PM, Peter Maydell >> wrote: >>> +echo "ERROR: configure test passed without -Werror but failed with >>> -Werror." >>> +echo "This is probably a bug in the c

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On 28 July 2012 10:04, Blue Swirl wrote: > On Wed, Jul 18, 2012 at 2:10 PM, Peter Maydell > wrote: >> +echo "ERROR: configure test passed without -Werror but failed with >> -Werror." >> +echo "This is probably a bug in the configure script. The failing >> command" >> +echo "will be

[Qemu-devel] [PATCH v3] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC

bumps spice-protocol to 0.12.0 for new IO. revision bumped to 4 for new IO support, enabled for spice-server >= 0.11.1 on migration reissue spice_qxl_monitors_config_async. RHBZ: 770842 Signed-off-by: Alon Levy --- configure | 2 +- hw/qxl.c | 49

Re: [Qemu-devel] [PATCH v2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC

On Sat, Jul 28, 2012 at 09:01:11AM +, Blue Swirl wrote: > > +// - this is not a guest io, but a reply, so async_io isn't > > set. > > Please use checkpatch.pl to avoid C99 comments. > Doh, I must have missed it (I do), will fix, thanks. Alon

Re: [Qemu-devel] [PATCH] update-linux-headers.sh: Pull in asm-generic/kvm_para.h

On 2012-07-25 17:29, Peter Maydell wrote: > Add asm-generic/kvm_para.h to the set of non-architecture specific > KVM kernel headers we copy into QEMU. This header may be included > by an architecture's kvm_para.h header. > > Signed-off-by: Peter Maydell > --- > scripts/update-linux-headers.sh |

Re: [Qemu-devel] [PATCH v2] tests/tcg: add test-i386-fprem and make target for comparing QEMU to h/w

On Wed, Jul 25, 2012 at 5:06 PM, Catalin Patulea wrote: > This test contains manual and automatically-generated test cases, in the style > of test-i386 (run on h/w, run on QEMU, diff the outputs), for the FPREM > instruction. For each test case, the input operands, result and FPU status > word >

Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests

On Wed, Jul 18, 2012 at 2:10 PM, Peter Maydell wrote: > Add support for checking whether test case code can compile without > warnings, by recompiling each successful test with -Werror. If the > -Werror version doesn't pass, we bail out. This gives us the same > level of visibility of warnings in

Re: [Qemu-devel] [PATCH v2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC

On Sat, Jul 28, 2012 at 8:56 AM, Alon Levy wrote: > bumps spice-protocol to 0.12.0 for new IO. > revision bumped to 4 for new IO support, enabled for spice-server >= 0.11.1 > on migration reissue spice_qxl_monitors_config_async. > > RHBZ: 770842 > > Signed-off-by: Alon Levy > --- > configure

Re: [Qemu-devel] [PATCH 4/7] compiler: add macro for GCC weak symbols

On Sat, Jul 28, 2012 at 6:50 AM, Peter Maydell wrote: > On 27 July 2012 16:31, Anthony Liguori wrote: >> Peter Maydell writes: >>> My approach to this is to avoid non-standard things >> >> http://en.wikipedia.org/wiki/C99#Implementations >> >> So unless you plan on compiling QEMU with xlc, pgi,

[Qemu-devel] [PATCH v2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC

bumps spice-protocol to 0.12.0 for new IO. revision bumped to 4 for new IO support, enabled for spice-server >= 0.11.1 on migration reissue spice_qxl_monitors_config_async. RHBZ: 770842 Signed-off-by: Alon Levy --- configure |2 +- hw/qxl.c | 47

Re: [Qemu-devel] [PATCH 4/7] compiler: add macro for GCC weak symbols

On Sat, Jul 28, 2012 at 6:25 AM, Markus Armbruster wrote: > Anthony Liguori writes: > >> Blue Swirl writes: >> >>> On Fri, Jul 27, 2012 at 8:51 PM, Anthony Liguori >>> wrote: If someone comes along and actively maintains support for another compiler, we can revisit. But otherwise, t

Re: [Qemu-devel] [PATCH 4/7] compiler: add macro for GCC weak symbols

On Fri, Jul 27, 2012 at 10:40 PM, Anthony Liguori wrote: > Blue Swirl writes: > >> On Fri, Jul 27, 2012 at 8:51 PM, Anthony Liguori wrote: >>> If someone comes along and actively maintains support for another >>> compiler, we can revisit. But otherwise, there's no practical reason to >>> avoid

Re: [Qemu-devel] Funny -m arguments can crash

On Sat, Jul 28, 2012 at 6:41 AM, Markus Armbruster wrote: > Blue Swirl writes: > >> On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster >> wrote: >>> Asking for "funny" memory sizes sometimes crashes for me. For instance >>> -m 0.8 or the equivalent -m 838860b. -m 0.7 appears to work. >>> >>>

Re: [Qemu-devel] [PATCH v3 2/2] block: Support GlusterFS as a QEMU block backend

On Sat, Jul 28, 2012 at 4:43 AM, Bharata B Rao wrote: > On Fri, Jul 27, 2012 at 06:44:04PM +, Blue Swirl wrote: >> > +struct GlusterOpts { >> >> static > > Sure. > >> >> > +bool optional; >> > +char defval[10]; >> >> const char *defval? > > Sure I could. > >> >> > +char *value; >>