On 4/3/19 9:05 PM, Yuval Shaia wrote:
> On Wed, Apr 03, 2019 at 02:33:40PM +0300, Kamal Heib wrote:
>> Add the required functions and definitions to support shared receive
>> queues (SRQs) in the backend layer.
>>
>> Signed-off-by: Kamal Heib
>> ---
>> hw/rdma/rdma_backend.c | 116 +++
This patch is based on the discussion in TianoCore edk2-devel mailing
list:
https://lists.01.org/pipermail/edk2-devel/2019-March/037986.html
The conclusion is that we need an individual UART for UEFI runtime
services to print debug message at runtime, to avoid conflicting with
the system UART. We
Just got almost the same
Ubuntu 16.04 as guest on Centos 7 host,
all will latest updates.
Execute of
virsh qemu-agent-command inetgw2 '{"execute":"guest-fsfreeze-freeze"}'
failed with agent not available ( or something like this), but fsfreeze
executed in OS
Apr 7 02:28:54 inetgw2 qemu-ga: info
btw,I run OEL7 VM on the same host and Ubuntu 18.04 VM,
both have newer qemu-guest-agent:
18.04: qemu-guest-age 1:2.11+dfsg-
OEL7: rpm -qi qemu-guest-agent
Name: qemu-guest-agent
Epoch : 10
Version : 2.12.0
Release : 2.el7
Never had this problem on both oh these.
--
You r
On Sun, Apr 07, 2019 at 11:13:15AM +0300, Kamal Heib wrote:
>
>
> On 4/3/19 9:05 PM, Yuval Shaia wrote:
> > On Wed, Apr 03, 2019 at 02:33:40PM +0300, Kamal Heib wrote:
> >> Add the required functions and definitions to support shared receive
> >> queues (SRQs) in the backend layer.
> >>
> >> Sign
On Wed, Apr 03, 2019 at 09:19:38PM +0300, Yuval Shaia wrote:
> On Wed, Apr 03, 2019 at 02:33:39PM +0300, Kamal Heib wrote:
> > This series implements the SRQ (Shared Receive Queue) for the pvrdma
> > device, It also includes all the needed functions and definitions for
> > support SRQ in the backen
QEMU currently crashes when you try to hot-plug an "nvdimm" device
on older machine types:
$ qemu-system-x86_64 -monitor stdio -M pc-1.1
QEMU 3.1.92 monitor - type 'help' for more information
(qemu) device_add nvdimm,id=nvdimmn1
qemu-system-x86_64: /home/thuth/devel/qemu/util/error.c:57: error_set
hvf_handle_io needs the poisoned type CPUArchState as its argument.
Declaring it if NEED_CPU_H is defined enables include/sysemu/hvf.h
to be included for common object compilation as well.
Cc: Roman Bolshakov
Cc: Paolo Bonzini
Signed-off-by: Sukrit Bhatnagar
---
include/sysemu/hvf.h | 4
Keep the calls made to synchronize cpu by all hypervisors in one place
inside cpu_synchronize_* functions in include/sysemu/hw_accel.h
Cc: Richard Henderson
Cc: Paolo Bonzini
Signed-off-by: Sukrit Bhatnagar
---
cpus.c| 12
include/sysemu/hw_accel.h | 10 +++
Changes made in v2:
- added a patch to declare hvf_handle_io only if NEED_CPU_H
is defined so that the poisoned type CPUArchState does not
produce an error when include/sysemu/hvf.h is included for
common object compilation
Link to v1:
https://lists.gnu.org/archive/html/qemu-devel/2019-03/ms
Hi,
Are the patches in good enough shape to be merged?
Thanks,
Sukrit
On Sat, 6 Apr 2019 at 04:04, Chen Zhang wrote:
>
> ping
>
> http://patchwork.ozlabs.org/patch/1058186/
This needs changes to be able to compile with OSX 10.10.
thanks
-- PMM
On Sun, 7 Apr 2019 at 09:19, Heyi Guo wrote:
>
> This patch is based on the discussion in TianoCore edk2-devel mailing
> list:
> https://lists.01.org/pipermail/edk2-devel/2019-March/037986.html
>
> The conclusion is that we need an individual UART for UEFI runtime
> services to print debug message
> -Original Message-
> From: Tian, Kevin
> Sent: Thursday, April 4, 2019 10:58 AM
> To: Peter Xu ; Elijah Shakkour
>
> Cc: Knut Omang ; Michael S. Tsirkin
> ; Alex Williamson ;
> Marcel Apfelbaum ; Stefan Hajnoczi
> ; qemu-devel@nongnu.org
> Subject: RE: QEMU and vIOMMU support for emul
On Fri, 5 Apr 2019 at 16:51, Dr. David Alan Gilbert (git)
wrote:
>
> From: "Dr. David Alan Gilbert"
>
> The following changes since commit 10546e09e174e0bb185b66a4c397aa845efcd36e:
>
> Merge remote-tracking branch
> 'remotes/palmer/tags/riscv-for-master-4.0-rc3-v2' into staging (2019-04-05
>
From: Sohail Alvi
a seperate class_init function has also been added for AMDVI-PCI.
Signed-off-by:SohailAlvi
---
hw/block/xen-block.c | 4 +++-
hw/dma/i82374.c| 3 ++-
hw/i386/amd_iommu.c| 9 +
hw/i386/intel_iommu.c | 1 +
hw/i386/pc_piix.c | 1 +
Patchew URL:
https://patchew.org/QEMU/20190407185042.7624-1-sohailalvi2...@gmail.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH] set_bit() function added to the source code of
uncategorized devices and catego
From: Sohail Alvi
Signed-off-by: SohailAlvi
---
hw/block/xen-block.c | 4 +++-
hw/dma/i82374.c| 3 ++-
hw/i386/amd_iommu.c| 9 +
hw/i386/intel_iommu.c | 1 +
hw/i386/pc_piix.c | 1 +
hw/i386/xen/xen_pvdevice.c | 1 +
hw/ipmi/ipmi_bmc_extern.c | 1
> From: Elijah Shakkour [mailto:elija...@mellanox.com]
> Sent: Sunday, April 7, 2019 9:47 PM
>
>
> > -Original Message-
> > From: Tian, Kevin
> > Sent: Thursday, April 4, 2019 10:58 AM
> > To: Peter Xu ; Elijah Shakkour
> >
> > Cc: Knut Omang ; Michael S. Tsirkin
> > ; Alex Williamson ;
On 2019/4/7 21:16, Peter Maydell wrote:
On Sun, 7 Apr 2019 at 09:19, Heyi Guo wrote:
This patch is based on the discussion in TianoCore edk2-devel mailing
list:
https://lists.01.org/pipermail/edk2-devel/2019-March/037986.html
The conclusion is that we need an individual UART for UEFI runtim
Commit 18269069c310 ("migration: Introduce ignore-shared capability")
addes ignore-shared capability to bypass the shared ramblock (e,g,
membackend + numa node). It does good to live migration.
As told by Yury,this commit expectes that QEMU doesn't write to guest RAM
until VM starts, but it does o
The following patches fixed absolute and relative input device issues on macOS
Mojave.
Chen Zhang (2):
ui/cocoa: Fix absolute input device grabbing issue on Mojave
ui/cocoa: Fix mouse grabbing in fullscreen mode for relative input
device
ui/cocoa.m | 50 +
In fullscreen mode, the window property of cocoaView may not be the key
window, and the current implementation would not grab mouse in fullscreen
mode after user ungrabs cursor in fullscreen mode with hot-key, and left
clicks the relative input devices to re-grab it.
This patch used value of isFul
This patches fixed boundary check methods for cursor in normal and
fullscreen modes with/without Zoom-to-Fit on Mojave.
On Mojave, absolute input device, i.e. tablet, had trouble re-grabbing
the cursor in re-entry into the virtual screen area. In some cases,
the `window` property of NSEvent object
Currently it is not forbidden to use "-object memory-backend-file,share=on"
and together with "-incoming". But after incoming migration is finished,
the memory-backend-file will be definitely written if share=on. So the
memory-backend-file can only be used once, but failed in the 2nd time
incoming.
Patchew URL:
https://patchew.org/QEMU/b786f00d-5518-405b-b0ac-c5bf2d728...@me.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: b786f00d-5518-405b-b0ac-c5bf2d728...@me.com
Subject: [Qemu-devel] [PATCH 0/2] ui/cocoa: Fix absolute
On Sun, Apr 07, 2019 at 10:19:05PM -0400, Catherine Ho wrote:
> Currently it is not forbidden to use "-object memory-backend-file,share=on"
> and together with "-incoming". But after incoming migration is finished,
> the memory-backend-file will be definitely written if share=on. So the
> memory-ba
On Sun, Apr 07, 2019 at 09:56:56PM -0400, Catherine Ho wrote:
> Commit 18269069c310 ("migration: Introduce ignore-shared capability")
> addes ignore-shared capability to bypass the shared ramblock (e,g,
> membackend + numa node). It does good to live migration.
>
> As told by Yury,this commit expe
On Tue, Apr 02, 2019 at 09:52:14AM +1100, David Gibson wrote:
> On Mon, Apr 01, 2019 at 07:54:57PM +0200, Greg Kurz wrote:
> > Recent commit c2077e2ca0da7 added stricter checks that now prevent
> > a guest to access the extended config space of a PCIe device connected
> > attached to a PHB on a pse
On Fri, Apr 05, 2019 at 10:05:24AM +0200, Greg Kurz wrote:
> Signed-off-by: Greg Kurz
Applied to ppc-for-4.1, thanks.
I did have to fix up a small conflict because I've now merged my style
fixups for target/ppc into ppc-for-4.1.
> ---
> target/ppc/kvm.c| 68
> +++
On Fri, Apr 05, 2019 at 10:05:19AM +0200, Greg Kurz wrote:
> Signed-off-by: Greg Kurz
Applied to ppc-for-4.1, thanks.
> ---
> target/ppc/trace-events |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/ppc/trace-events b/target/ppc/trace-events
> index 3858f9
On Fri, Apr 05, 2019 at 06:30:43PM +0200, Greg Kurz wrote:
> According to the changelog of 298a971024534, SpaprPhbState::dtbusname was
> introduced to "make it easier to relate the guest and qemu views of memory
> to each other", hence its name.
>
> Use it when creating the PHB node to avoid code
On Tue, Apr 02, 2019 at 12:28:07PM +0200, Greg Kurz wrote:
> On Mon, 1 Apr 2019 12:01:48 -0300
> "Maxiwell S. Garcia" wrote:
>
> > Hi Greg,
> >
> > Thanks for your review. I added some comments below...
> >
> > On Fri, Mar 29, 2019 at 01:29:51PM +0100, Greg Kurz wrote:
> > > On Thu, 28 Mar 2019
On Fri, Apr 05, 2019 at 06:30:48PM +0200, Greg Kurz wrote:
> LSI mapping in spapr currently open-codes standard PCI swizzling. It thus
> duplicates the code of pci_swizzle_map_irq_fn().
>
> Expose the swizzling formula so that it can be used with a slot number
> when building the device tree. Simp
On Sat, Mar 23, 2019 at 10:24:11PM +, Sergei Trofimovich wrote:
> The bug is initially discovered in GHC test suite. Here is minimal reproducer:
>
> ```c
>
> int main() {
> volatile float f;
> volatile double d;
>
> *(volatile uint32_t*)&f = 0xc0de;
> d = f;
> printf("f
On Fri, Mar 29, 2019 at 01:29:51PM +0100, Greg Kurz wrote:
> On Thu, 28 Mar 2019 15:39:45 -0300
> "Maxiwell S. Garcia" wrote:
>
> > Hi,
> >
> > On Thu, Mar 28, 2019 at 02:21:51PM +0100, Greg Kurz wrote:
> > > On Wed, 27 Mar 2019 17:41:00 -0300
> > > "Maxiwell S. Garcia" wrote:
> > >
> > > >
Eduardo Habkost writes:
> On Fri, Apr 05, 2019 at 07:22:35PM -0400, Michael S. Tsirkin wrote:
>> On Fri, Apr 05, 2019 at 09:56:29AM +0100, Dr. David Alan Gilbert wrote:
>> > * Jens Freimann (jfreim...@redhat.com) wrote:
>> > > On Fri, Mar 22, 2019 at 02:44:45PM +0100, Jens Freimann wrote:
> [...]
But it happens in some times， this problem dose not occur 100 percent。I
can not reproduce when I want to find WHY。So it‘s dangerous in my
production environment。
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
Hervé Poussineau writes:
> Le 05/04/2019 à 12:29, Philippe Mathieu-Daudé a écrit :
>> Hi,
>>
>> I am trying to understand the possible values for the MAX_FD variable
>> used by the floppy controller model (hw/block/fdc.c).
>>
>> Looking at git history:
>>
>> - 2004-01-05 7138fcfbf7dd + 8977f3c107
On Mon, Apr 08, 2019 at 12:32:12AM +, Tian, Kevin wrote:
[...]
> > > > Probably. Currently VT-d emulation does not support snooping control,
> > > > and if you modify that ecap only you probably will encounter this
> > > > problem because then the guest kernel will setup the SNP bit in the
>
Paolo Bonzini writes:
> On 04/04/19 22:49, Philippe Mathieu-Daudé wrote:
>> While I wonder if someone still use the r4k machine, I have more doubts
>> about users running with more the 2 -serial options...
>
> I sort of remember ISA extension cards that had jumpers or dip switches
> to choose bet
Jens Freimann writes:
> On Fri, Apr 05, 2019 at 09:56:29AM +0100, Dr. David Alan Gilbert wrote:
>>* Jens Freimann (jfreim...@redhat.com) wrote:
> [...]
>>> > Commandline: There is a dependency between vfio-pci and virtio-net
>>> > devices. One points to the other via new parameters
>>> > primar=
Hi Peter Xu
On Mon, 8 Apr 2019 at 11:25, Peter Xu wrote:
> On Sun, Apr 07, 2019 at 10:19:05PM -0400, Catherine Ho wrote:
> > Currently it is not forbidden to use "-object
> memory-backend-file,share=on"
> > and together with "-incoming". But after incoming migration is finished,
> > the memory-b
Am Fri, 5 Apr 2019 19:17:35 -0400
schrieb "Michael S. Tsirkin" :
> Let's keep it simple: set a config variable, then check it here.
Better revert f590a812c21074e82228de3e1dfb57b75fc02b62 and
23858f4092fc9ebf9e7a5e5110e44abef6fc6643 for the time being. It looks like a
no-op right now. How did pe
Thomas Huth writes:
> On 04/04/2019 18.30, Markus Armbruster wrote:
>> Thomas Huth writes:
>>
>>> On 04/04/2019 15.29, Philippe Mathieu-Daudé wrote:
On 4/4/19 12:07 PM, Paolo Bonzini wrote:
> On 04/04/19 09:14, Thomas Huth wrote:
>> The i8042 PS/2 controller is part of the chipset
45 matches
Mail list logo
