[Qemu-devel] [ANNOUNCE] QEMU 1.6.0-rc1 is now available

[Qemu-devel] [ANNOUNCE] QEMU 1.6.0-rc1 is now available

[Anthony Liguori]

Hi,

On behalf of the QEMU Team, I'd like to announce the availability of the
second release candidate for the QEMU 1.6 release.  This release is meant
for testing purposes and should not be used in a production environment.

http://wiki.qemu.org/download/qemu-1.6.0-rc1.tar.bz2

You can help improve the quality of the QEMU 1.6 release by testing this
release and reporting bugs on Launchpad:

https://bugs.launchpad.net/qemu/

The release plan for the 1.6 release is available at:

http://wiki.qemu.org/Planning/1.6

Please add entries to the ChangeLog for the 1.6 release below:

http://wiki.qemu.org/ChangeLog/1.6

The following changes have been made since v1.6.0-rc0:

 - virtio-console: Use exitfn for virtserialport, too (Andreas Färber)
 - virtio-9p-device: Avoid freeing uninitialized memory (Andreas Färber)
 - migration: don't use uninitialized variables (Pawit Pornkitprasan)
 - migration: send total time in QMP at "completed" stage (Pawit Pornkitprasan)
 - MAINTAINERS: change Igor Mitsyanko's email address (Igor Mitsyanko)
 - qdev: Use clz in print_size (Richard Henderson)
 - qdev: Fix 32-bit compilation in print_size (Richard Henderson)
 - mips_r4k: Silence BIOS loading warning for qtest (Andreas Färber)
 - mips_jazz: Silence BIOS loading warning for qtest (Andreas Färber)
 - mips_malta: Silence BIOS loading warning for qtest (Andreas Färber)
 - mips_fulong2e: Silence BIOS loading warning for qtest (Andreas Färber)
 - target-ppc: Suppress TCG instruction emulation warnings for qtest (Andreas Färber)
 - chardev: fix CHR_EVENT_OPENED events for mux chardevs (Michael Roth)
 - tci: Fix broken build (compiler warning caused by redefined macro BIT) (Stefan Weil)
 - target-mips: correct the values in the DSP tests (Petar Jovanovic)
 - s390: Implement dump-guest-memory support for target s390x (Ekaterina Tumanova)
 - s390x/kvm: Remove redundant return code (Thomas Huth)
 - s390x/kvm: Reworked/fixed handling of cc3 in kvm_handle_css_inst() (Thomas Huth)
 - s390x/ioinst: Fixed priority of operand exceptions (Thomas Huth)
 - s390x/ioinst: Fixed alignment check in SCHM instruction (Thomas Huth)
 - s390x/ioinst: Throw addressing exception when memory_map failed (Thomas Huth)
 - s390x/ioinst: Add missing alignment checks for IO instructions (Thomas Huth)
 - s390/sclpconsole: handle char layer busy conditions (Heinz Graalfs)
 - hcd-ohci: add dma error handling (Alexey Kardashevskiy)
 - uhci: egsm fix (Gerd Hoffmann)
 - xhci: handle USB_RET_IOERROR (Gerd Hoffmann)
 - spice: fix display initialization (Gerd Hoffmann)

Regards,

Anthony Liguori

Re: [Qemu-devel] [ANNOUNCE] QEMU 1.6.0-rc1 is now available

[Mark Cave-Ayland]

On 01/08/13 23:08, Anthony Liguori wrote:

> Hi,
>
> On behalf of the QEMU Team, I'd like to announce the availability of the
> second release candidate for the QEMU 1.6 release.  This release is meant
> for testing purposes and should not be used in a production environment.
>
> http://wiki.qemu.org/download/qemu-1.6.0-rc1.tar.bz2

Hi Anthony,

There are still two outstanding issues from my testing here - patches 
have been submitted for both, but not applied yet.

- qemu-system-sparc64 broken
See https://lists.gnu.org/archive/html/qemu-devel/2013-07/msg05201.html.

- OpenBIOS images have not been updated
See https://lists.gnu.org/archive/html/qemu-devel/2013-07/msg05923.html.


Many thanks,

Mark.

Re: [Qemu-devel] [ANNOUNCE] QEMU 1.6.0-rc1 is now available

[Laszlo Ersek]

On 08/04/13 14:17, Mark Cave-Ayland wrote:
> On 01/08/13 23:08, Anthony Liguori wrote:
> 
>> Hi,
>>
>> On behalf of the QEMU Team, I'd like to announce the availability of the
>> second release candidate for the QEMU 1.6 release.  This release is meant
>> for testing purposes and should not be used in a production environment.
>>
>> http://wiki.qemu.org/download/qemu-1.6.0-rc1.tar.bz2
> 
> Hi Anthony,
> 
> There are still two outstanding issues from my testing here - patches
> have been submitted for both, but not applied yet.
> 
> - qemu-system-sparc64 broken
> See https://lists.gnu.org/archive/html/qemu-devel/2013-07/msg05201.html.
> 
> - OpenBIOS images have not been updated
> See https://lists.gnu.org/archive/html/qemu-devel/2013-07/msg05923.html.

Also, my series

  [PATCH 0/4] dump-guest-memory: correct the vmcores
  http://thread.gmane.org/gmane.comp.emulators.qemu/225360

was dropped from qmp-1.6 (and consequently didn't make the d5a2bcf7
merge) due to an asynchronous change to another part of the tree that I
could not have foreseen.

IOW it was not my fault -- I did exercise due diligence and my series
was building and working fine at the then-fresh master when I posted it.
A conflicting function was introduced between my posting and Luiz's
application of my series to his qmp-1.6 branch, and since I was on PTO
from last Thursday, I could only refresh the series only today.

The update from v1 to v2 is trivial:


diff --git a/target-s390x/arch_dump.c b/target-s390x/arch_dump.c
index f3e5144..9d36116 100644
--- a/target-s390x/arch_dump.c
+++ b/target-s390x/arch_dump.c
@@ -176,7 +176,8 @@ int s390_cpu_write_elf64_note(WriteCoreDumpFunction f, CPUState *cs,
     return s390x_write_all_elf64_notes("CORE", f, cpu, cpuid, opaque);
 }

-int cpu_get_dump_info(ArchDumpInfo *info)
+int cpu_get_dump_info(ArchDumpInfo *info,
+                      const struct GuestPhysBlockList *guest_phys_blocks)
 {
     info->d_machine = EM_S390;
     info->d_endian = ELFDATA2MSB;


Please do consider it for 1.6, it addresses a serious bug (= vmcores saved
with dump-guest-memory/paging=false are broken for > 3.5G x86(_64) guests).

  [PATCH v2 for-qmp-1.6 0/4] dump-guest-memory: correct the vmcores
  http://thread.gmane.org/gmane.comp.emulators.qemu/226378

Thanks
Laszlo

Re: [Qemu-devel] [ANNOUNCE] QEMU 1.6.0-rc1 is now available

[Luiz Capitulino]

On Mon, 05 Aug 2013 14:01:10 +0200
Laszlo Ersek <lersek@redhat.com> wrote:

> Please do consider it for 1.6, it addresses a serious bug (= vmcores saved
> with dump-guest-memory/paging=false are broken for > 3.5G x86(_64) guests).

No worries, it is going to be included (unless someone has a serious objection,
of course).