[Qemu-devel] [Bug 788886] Re: Crash with -m32 and gcc-4.2 on Mac OS X 64bit

[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/76 Title: Crash with

[Qemu-devel] [Bug 640213] Re: QEMU does not communicate properly with GDB with a 64 bit guest

[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/640213 Title: QEMU does

[Qemu-devel] [PATCH fixup 2/2] vhost: genearlize iommu memory region

We assumes the iommu_ops were attached to the root region of address space. This may not true for all kinds of IOMMU implementation. So fix this by not assume as->root has iommu_ops and: - register a memory listener to dma_as - during region_add, if it's a region of IOMMU, register a specific

[Qemu-devel] [PATCH fixup 0/2] Vhost device IOTLB fixup for vfio enablment

Hi: This series is a fixup for vfio enablement series which breaks vhost device IOTLB. The main reason is that vhost device IOTLB assumes the iommu region were alwasy as->root. Fixing by using a memory listener to register iommu notifiers. Please review. Jason Wang (2): intel_iommu: use the

[Qemu-devel] [PATCH fixup 1/2] intel_iommu: use the correct memory region for device IOTLB notification

We have a specific memory region for DMAR now, so it's wrong to trigger the notifier with the root region. Cc: Michael S. Tsirkin Cc: Paolo Bonzini Cc: Richard Henderson Cc: Eduardo Habkost Signed-off-by: Jason Wang

Re: [Qemu-devel] [RFC PATCH 0/4] Qemu: Add Xen vIOMMU support

On 2017年03月17日 22:48, Paolo Bonzini wrote: > > > On 17/03/2017 12:29, Lan Tianyu wrote: >> This patchset is to add Xen vIOMMU device model and handle >> irq remapping stuffs. Xen vIOMMU emulation is in the Xen hypervisor >> and the new device module in Qemu works as hypercall wrappers to >>

Re: [Qemu-devel] callout to *file in bdrv_co_get_block_status

On Fri, 03/17 12:20, Peter Lieven wrote: > Am 17.03.2017 um 12:16 schrieb Paolo Bonzini: > > > > On 17/03/2017 12:11, Peter Lieven wrote: > like VMDK or QCOW2 shouldn't we trust the information from the l2 tables > in the VMDK or QCOW2? > >>> It provides additional information, for

Re: [Qemu-devel] [PATCH v7 17/17] intel_iommu: enable vfio devices

On Mon, Mar 20, 2017 at 02:12:15AM +, Liu, Yi L wrote: > Hi Peter, > > How about the merge of this series? I'm also trying to rebase my work and > prepare to send > out RFC patch. We may need to wait until QEMU 2.10. I have no plan of content change in next repost (just remove some merged

Re: [Qemu-devel] [PATCH v7 17/17] intel_iommu: enable vfio devices

Hi Peter, How about the merge of this series? I'm also trying to rebase my work and prepare to send out RFC patch. Regards, Yi L > -Original Message- > From: Qemu-devel [mailto:qemu-devel-bounces+yi.l.liu=intel@nongnu.org] On > Behalf Of Peter Xu > Sent: Monday, March 20, 2017 9:57

Re: [Qemu-devel] [PATCH v7 17/17] intel_iommu: enable vfio devices

On Sun, Mar 19, 2017 at 05:34:31PM +0200, Aviv B.D. wrote: > Hi Peter, > Thanks, I think that I should receive credit for this patch. > > Please attribute it under my technion mail: bda...@cs.technion.ac.il. > > The signed-off line should be: > > Signed-off-by: Aviv Ben-David

Re: [Qemu-devel] [PATCH RFC 1/1] block: Handle NULL options correctly in raw_open

* Dong Jia Shi [2017-03-14 11:23:12 +0800]: > * Kevin Wolf [2017-03-13 11:15:22 +0100]: > > > Am 13.03.2017 um 04:31 hat Dong Jia Shi geschrieben: > > > * Dong Jia Shi [2017-03-08 17:31:05 +0800]: > > > > > > > *

Re: [Qemu-devel] [PATCH v4 01/16] s390: cio: introduce cio_cancel_halt_clear

* Sebastian Ott [2017-03-17 10:51:20 +0100]: > On Fri, 17 Mar 2017, Dong Jia Shi wrote: > > * Sebastian Ott [2017-03-17 10:26:51 +0100]: > > > > > On Fri, 17 Mar 2017, Dong Jia Shi wrote: > > > > For future code reuse purpose, this

Re: [Qemu-devel] [RFC QEMU PATCH v2 00/10] Implement vNVDIMM for Xen HVM guest

Hi, This series failed build test on s390x host. Please find the details below. Type: series Subject: [Qemu-devel] [RFC QEMU PATCH v2 00/10] Implement vNVDIMM for Xen HVM guest Message-id: 20170320001249.25521-1-haozhong.zh...@intel.com === TEST SCRIPT BEGIN === #!/bin/bash # Testing script

[Qemu-devel] [RFC QEMU PATCH v2 10/10] qapi: extend 'query-memory-devices' to list devices of specified type

Add an optional argument 'devtype' to 'query-memory-devices', which is either 'dimm' or 'nvdimm'. If 'devtype' is missed or 'dimm', all memory devices will be listed. If 'devtype' is 'nvdimm', only nvdimm devices will be listed. Signed-off-by: Haozhong Zhang --- Cc:

[Qemu-devel] [RFC QEMU PATCH v2 07/10] xen-hvm: initiate building DM ACPI on i386 machine

If QEMU is running as Xen device model and Xen needs ACPI (e.g. NFIT) from QEMU, initiate building DM ACPI. Signed-off-by: Haozhong Zhang --- Cc: "Michael S. Tsirkin" Cc: Paolo Bonzini Cc: Richard Henderson Cc:

[Qemu-devel] [RFC QEMU PATCH v2 09/10] xen-hvm: create hotplug memory region on Xen

The current QEMU implementation allocates guest physical address for vNVDIMM in the hotplug memory region, which was not created when QEMU is used as Xen device model. Reuse existing code in i386/pc.c to create the hotplug memory region for HVM domain on Xen, so that we can reuse other parts of

[Qemu-devel] [RFC QEMU PATCH v2 06/10] nvdimm acpi: build and copy NVDIMM namespace devices to guest on Xen

Build and copy NVDIMM namespace devices to guest when QEMU is used as Xen device model. Only the body of each AML device is built and copied. Xen hvmloader will complete other parts of namespace devices and put in SSDT. Signed-off-by: Haozhong Zhang --- Cc: "Michael S.

[Qemu-devel] [RFC QEMU PATCH v2 04/10] nvdimm acpi: do not use fw_cfg on Xen

Xen relies on QEMU to build guest ACPI for NVDIMM. However, no fw_cfg is created when QEMU is used as Xen device model, so QEMU should avoid using fw_cfg on Xen. Signed-off-by: Haozhong Zhang --- Cc: "Michael S. Tsirkin" Cc: Igor Mammedov

[Qemu-devel] [RFC QEMU PATCH v2 05/10] nvdimm acpi: copy NFIT to Xen guest

Xen relies on QEMU to build the guest NFIT. Signed-off-by: Haozhong Zhang --- Cc: "Michael S. Tsirkin" Cc: Igor Mammedov Cc: Xiao Guangrong --- hw/acpi/nvdimm.c | 7 +++ 1 file changed, 7

[Qemu-devel] [RFC QEMU PATCH v2 03/10] xen-hvm: support copying ACPI to guest memory

Signed-off-by: Haozhong Zhang --- Cc: Stefano Stabellini Cc: Anthony Perard Cc: xen-de...@lists.xenproject.org --- include/hw/xen/xen.h | 18 xen-hvm-stub.c | 6 +++ xen-hvm.c| 113

[Qemu-devel] [RFC QEMU PATCH v2 08/10] hostmem: add a host memory backend for Xen

Some virtual devices (e.g. NVDIMM) use the host memory backend to map its backend resources to the guest. When those devices are used on Xen, the mapping has to be managed out of QEMU. In order to reuse other parts of the implementation of those devices, we introduce a host memory backend for Xen

[Qemu-devel] [RFC QEMU PATCH v2 02/10] xen-hvm: initialize DM ACPI

Probe the base address and the length of guest ACPI buffer reserved for copying ACPI from QEMU. Signed-off-by: Haozhong Zhang --- Cc: Stefano Stabellini Cc: Anthony Perard Cc: xen-de...@lists.xenproject.org ---

[Qemu-devel] [RFC QEMU PATCH v2 01/10] nvdimm xen: disable label support on Xen

If xen_enabled(), memory_region_get_ram_ptr() always returns NULL and nvdimm_realize() cannot get the correct pointer to the label area. This commit disables the label support for Xen accelerator to workaround this issue. Signed-off-by: Haozhong Zhang --- Cc: "Michael

[Qemu-devel] [RFC QEMU PATCH v2 00/10] Implement vNVDIMM for Xen HVM guest

This is the QEMU patch of v2 RFC patch series to enable vNVDIMM support for Xen HVM guest. v1 can be found at https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg01678.html. The corresponding Xen patch series is sent in another thread "[RFC XEN PATCH v2 00/15] Add vNVDIMM support to HVM

[Qemu-devel] [Bug 1643619] Re: netlink broken on big-endian mips

This has been fixed by 40493c5f2b0f124c9b2581e539bba14522e51269, which is exactly the same diff as given here. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1674114] Re: Bad sectors when using MS-DOS 6.22

It is working now without the parameters "-machine isapc" and "-cpu 486". -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674114 Title: Bad sectors when using MS-DOS 6.22 Status in QEMU: New

Re: [Qemu-devel] [PATCH v2] qmp-shell: add persistent command history

On Mon, Mar 13, 2017 at 8:04 AM Markus Armbruster wrote: > Nir Soffer writes: > > > On Wed, Mar 8, 2017 at 8:29 AM, Markus Armbruster > wrote: > >> John Snow writes: > >> > >>> On 03/07/2017 03:16 AM, Markus Armbruster

[Qemu-devel] [Bug 1674117] Re: Qemu VM start kills Pulseaudio

** Tags removed: pulseaudio ** Tags added: pulse-audio -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674117 Title: Qemu VM start kills Pulseaudio Status in QEMU: New Bug description: When I

[Qemu-devel] [Bug 1674117] [NEW] Qemu VM start kills Pulseaudio

Public bug reported: When I start a VM (start command below) in Qemu version >2.5, it kills Pulseaudio (paired with a huge lagspike) in ~4/5 cases. Using version 2.5 build from GIT, it works fine. This also happens when building from the current GIT master (ebedf0f). Host: Freshly installed

Re: [Qemu-devel] [Qemu-trivial] [PATCH v3] util: Use g_malloc/g_free in envlist.c

Hi, This series failed build test on s390x host. Please find the details below. Type: series Subject: [Qemu-devel] [Qemu-trivial] [PATCH v3] util: Use g_malloc/g_free in envlist.c Message-id: 20170319162715.2260-1-sauravsachidan...@gmail.com === TEST SCRIPT BEGIN === #!/bin/bash # Testing

[Qemu-devel] [Qemu-trivial] [PATCH v3] util: Use g_malloc/g_free in envlist.c

Change malloc/strdup/free to g_malloc/g_strdup/g_free in util/envlist.c. Remove NULL checks for pointers returned from g_malloc and g_strdup as they exit in case of failure. Also, update calls to envlist_create to reflect this. Free array and array contents returned by envlist_to_environ using

[Qemu-devel] [Bug 1674114] [NEW] Bad sectors when using MS-DOS 6.22

Public bug reported: When I try to install DOS 6.22 in QEMU, I get many disk errors when the virtual disk is beeing partionized and formatted. When I later do a SCANDISK, I can see many bad sectors and file errors. I have tested this with the following disk formats: qcow2, vmdk, raw. I tested

Re: [Qemu-devel] [PATCH v7 17/17] intel_iommu: enable vfio devices

Hi Peter, Thanks, I think that I should receive credit for this patch. Please attribute it under my technion mail: bda...@cs.technion.ac.il. The signed-off line should be: Signed-off-by: Aviv Ben-David Thanks, Aviv. On Thu, Mar 16, 2017 at 6:05 AM, Peter Xu

Re: [Qemu-devel] Strange behaviour in network device initialization.

> Peter Maydell hat am 18. März 2017 um 23:22 > geschrieben: > > This is expected, because you're creating two devices. > Device 1 is the one that's created by calling > mydevice_init() here in the board code. > Device 2 is created because you say "-device mydevice" >

[Qemu-devel] [Qemu-devel RFC 2/3] msf2: Microsemi Smartfusion2 System Register block.

Added Sytem register block of Smartfusion2. This block has PLL registers which are accessed by guest. Signed-off-by: Subbaraya Sundeep --- hw/misc/Makefile.objs | 1 + hw/misc/msf2_sysreg.c | 168 ++ 2 files changed, 169

[Qemu-devel] [Qemu-devel RFC 3/3] msf2: Add Emcraft's Smartfusion2 SOM kit.

Emulated Emcraft's Smartfusion2 System On Module starter kit. Signed-off-by: Subbaraya Sundeep --- default-configs/arm-softmmu.mak | 1 + hw/arm/Makefile.objs| 2 +- hw/arm/msf2_soc.c | 122 3 files

[Qemu-devel] [Qemu-devel RFC 1/3] msf2: Add Smartfusion2 System timer

Modelled System Timer in Microsemi's Smartfusion2 Soc. Timer has two 32bit down counters and two interrupts. Signed-off-by: Subbaraya Sundeep --- hw/timer/Makefile.objs | 1 + hw/timer/msf2_timer.c | 273 + 2 files

Re: [Qemu-devel] GSOC Qemu Project

On 18 March 2017 at 22:48, aahud wrote: > I am sending this email, admittedly late, to suggest a new project. I would > love to see Qemu ported to an operating system without a monolithic kernel. > My initial ideas for target platforms are Minix3 or a Plan9-like (ie Harvey > or

[Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017"

Just an idea... If this is useful, we can do it every month. It only takes ten minutes to skim planet.virt-tools.org and compile the list. Signed-off-by: Paolo Bonzini --- .../2017-03-19-qemu-in-the-blogs-february-2017.md | 33 ++ 1 file changed, 33

[Qemu-devel] [Bug 1674056] [NEW] USB keyboard and mouse sucked into qemu-kvm (somewhere)

Public bug reported: i am unable to run a command line qemu that does not "suck in" the keyboard and mouse of the host PC i tried all that i could from the command line parameters i want to run a headless gui-less kvm host if i specify a second set of keyboard and mouse with the -usb the only