Re: [Qemu-devel] [PATCH v2 3/4] migration: disallow migrate_add_blocker during migration

On Friday, January 6, 2017, Greg Kurz wrote: > Hi Ashijeet, > Hello Greg, > I didn't think hard enough while reviewing the changes for hw/9pfs/9p.c... > I have > some more remarks, sorry... :-/ > > No problem, I will send an updated v4 for these. On Wed, 4 Jan 2017 18:02:28

[Qemu-devel] [PATCH v2 4/4] migration: Fail migration blocker for --only-migratble

On Friday, January 6, 2017, Greg Kurz > wrote: > On Wed, 4 Jan 2017 18:02:29 +0530 > Ashijeet Acharya wrote: > > > migrate_add_blocker should rightly fail if the '--only-migratable' > > option was

[Qemu-devel] [Bug 891525] Re: Guest kernel crashes when booting a NUMA guest without explicitly specifying cpus= in -numa option

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/891525 Title: Guest

[Qemu-devel] [Bug 878019] Re: 0.15.1 black screen and 100% cpu on start

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/878019 Title: 0.15.1

Re: [Qemu-devel] [PATCH] hw/pci: use-after-free in pci_nic_init_nofail when nic device fails to initialize

On Fri, Jan 06, 2017 at 03:48:27PM -0800, Alex Kompel wrote: > object_property_set_bool(OBJECT(dev), true, "realized", ) in > pci_nic_init_nofail may release the object if device fails to > initialize which leads to use-after-free in error handling block. > qdev_init_nofail does the same thing

[Qemu-devel] assert hit on master with q35 machine type

I'm currently hitting an assert on master. I've bisected the change down to aff8fd18f1786fc5af259a9bc0077727222f51ca but obviously that's a false positive because that adds the assert for the condition. So obviously the issue was introduced prior to this. As another data point the issue only

Re: [Qemu-devel] [Bug 1253465] Re: qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3

On Sat, 01/07 21:36, Patrick Schleizer wrote: > > If you are aware of open source software which already supports > version 3, please let us know! > > VirtualBox can. > > - VirtualBox uses VMDK version 3 disks. > - When you export a VM with VirtualBox (creating an .ova), it will include > VMDK

[Qemu-devel] [Bug 1253465] Re: qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3

> If you are aware of open source software which already supports version 3, please let us know! VirtualBox can. - VirtualBox uses VMDK version 3 disks. - When you export a VM with VirtualBox (creating an .ova), it will include VMDK version 3 disks. - VirtualBox can convert from vmkd to vdi.

Re: [Qemu-devel] [PATCH v2 2/3] block: m25p80: Introduce die erase command

W dniu 07.01.2017 o 20:57, Cédric Le Goater pisze: On 01/06/2017 07:49 PM, Marcin Krzeminski wrote: Modern big flash nor devices consist from more than one die. Some of them do not support chip erase and instead have die erase command that can erase one die only. This commit adds possibility

Re: [Qemu-devel] [PATCH v2 2/3] block: m25p80: Introduce die erase command

On 01/06/2017 07:49 PM, Marcin Krzeminski wrote: > Modern big flash nor devices consist from more than one die. > Some of them do not support chip erase and instead have die > erase command that can erase one die only. This commit adds > possibility to define number of dies in the chip and adds >

Re: [Qemu-devel] [PATCH v2] hw/display: QOM'ify g364fb.c

Le 06/01/2017 à 02:10, xiaoqiang zhao a écrit : Drop the old Sysbus init and use instance_init and DeviceClass::realize instead Signed-off-by: xiaoqiang zhao --- hw/display/g364fb.c | 40 +--- 1 file changed, 21 insertions(+), 19

[Qemu-devel] [PATCH v3 3/4] prep: add IBM RS/6000 7020 (40p) memory controller

Signed-off-by: Hervé Poussineau Reviewed-by: David Gibson --- default-configs/ppc-softmmu.mak | 1 + hw/ppc/Makefile.objs| 1 + hw/ppc/rs6000_mc.c | 232 hw/ppc/trace-events

[Qemu-devel] [PATCH v3 4/4] prep: add IBM RS/6000 7020 (40p) machine emulation

Machine supports both Open Hack'Ware and OpenBIOS. Open Hack'Ware is the default because OpenBIOS is currently unable to boot PReP boot partitions or PReP kernels. Signed-off-by: Hervé Poussineau --- default-configs/ppc-softmmu.mak | 1 + hw/ppc/prep.c

[Qemu-devel] [PATCH v3 2/4] prep: add PReP System I/O

This device is a partial duplicate of System I/O device available in hw/ppc/prep.c This new one doesn't have all the Motorola-specific registers. The old one should be deprecated and removed with the 'prep' machine. Partial documentation available at

[Qemu-devel] [PATCH v3 0/4] ppc: add a IBM 40p machine (RS/6000, PReP)

Hi, This patchset adds the emulation of the IBM RS/6000 7020 (40p). The real machine is able to run AIX (up to 4.3.3), Windows NT (up to 4.0 SP1), the beta of OS/2 PowerPC, Solaris, Linux, NetBSD/PReP ... I've tested current emulation with Open Hack'Ware, OpenBIOS and official firmware.

[Qemu-devel] [PATCH v3 1/4] prep: do not use global variable to access nvram

Signed-off-by: Hervé Poussineau --- hw/ppc/prep.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/ppc/prep.c b/hw/ppc/prep.c index 054af1e..9fb89d3 100644 --- a/hw/ppc/prep.c +++ b/hw/ppc/prep.c @@ -339,13 +339,13 @@ static PortioList

[Qemu-devel] [PATCH] target-arm/abi32: check for segfault in do_kernel_trap

Currently, the cmpxchg implementation tests whether the destination address is readable: - if it is, we read the value and continue with the comparison - if isn't, i.e. access to addr would segfault, we assume that src != dest rather than queuing a SIGSEGV. The same problem exists in the

[Qemu-devel] [PATCH v3] [i.MX] Remove MSGDATA register support.

>From the documentation it is not clear what this SPI register is about. Moreover, neither linux driver nor xvisor driver are using this SPI register. For now we just remove it and issue a log on register write access. Signed-off-by: Jean-Christophe Dubois --- Changes

[Qemu-devel] [PATCH v2] [m25p80] Reset internal state in case we overrun the internal data buffer

When we overrun the internal data buffer it is suspected that the SPI controler (either Qemu emulator og guest driver) is misbehaving. Therefore we reset the flash internal state and issue a log. Signed-off-by: Jean-Christophe Dubois --- Changes since v1: * reset internal

[Qemu-devel] [PATCH] hw/pci: use-after-free in pci_nic_init_nofail when nic device fails to initialize

object_property_set_bool(OBJECT(dev), true, "realized", ) in pci_nic_init_nofail may release the object if device fails to initialize which leads to use-after-free in error handling block. qdev_init_nofail does the same thing while holding the reference. (gdb) run -net nic qemu-system-x86_64: