[Qemu-devel] [PATCH] doc/pcie: correct command line examples

Nit picking: Multi-function PCI Express Root Ports should mean that 'addr' property is mandatory, and slot is optional because it is default to 0, and 'chassis' is mandatory for 2nd & 3rd root port because it is default to 0 too. Bonus: fix a typo(2->3) Signed-off-by: Cao jin

[Qemu-devel] [Bug 692570] Re: APIC Latency causing BSOD.

Since there hasn't been an answer to this within the last years, it looks like nobody here knows about Proxmox problems. So let's close this ticket... ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 974229] Re: qemu-kvm-1.0: segfault using vnc-console => not threadsafe!

[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/974229 Title:

[Qemu-devel] [Bug 1649040] Re: Ubuntu 16.04.1 Grub Splash Doesn't Appear

-vga virtio is working, I finally figured out my image was corrupted, I realized you have to be careful shutting the guest down correctly, or you could corrupt the image/system... So now, back to the same issue, even using 2.8.0 and virtio the grub splash doesn't always appears. So this is

[Qemu-devel] [Bug 1649042] Re: Ubuntu 16.04.1 LightDM Resolution Not Correct

Using virtio it works nice -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1649042 Title: Ubuntu 16.04.1 LightDM Resolution Not Correct Status in QEMU: New Bug description: My Specs:

[Qemu-devel] [PATCH 3/3] trace: Add event "guest_cpu_exit"

Signals the hot-unplugging of a virtual (guest) CPU. Signed-off-by: Lluís Vilanova --- trace-events|6 ++ trace/control.c |3 +++ 2 files changed, 9 insertions(+) diff --git a/trace-events b/trace-events index f74e1d3d22..f3894f5b38 100644 ---

[Qemu-devel] [PATCH 2/3] trace: Fix dynamic event state on vCPU hot-unplug

We need to disable per-vCPU events on a vCPU that is hot-unplugged to keep the dynamic event state global counters consistent. Signed-off-by: Lluís Vilanova --- qom/cpu.c |2 ++ trace/control.c | 16 trace/control.h |8 3 files

[Qemu-devel] [PATCH 0/3] trace: Fix event tracing during vCPU hot-unplug

The vCPU list needs to be locked to avoid memory corruption with concurrent hot-(un)plugs, and per-vCPU events need to be disabled during vCPU hot-unplug. Also adds event "guest_cpu_exit" to track vCPU hot-unplugging. Signed-off-by: Lluís Vilanova --- Lluís Vilanova (3):

[Qemu-devel] [PATCH 1/3] trace: Lock vCPU list when initializing dynamic tracing state

Fixes potential corruption when a vCPU is hot-(un)plugged while initializing the current one. Signed-off-by: Lluís Vilanova --- trace/control-target.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/trace/control-target.c

Re: [Qemu-devel] [PATCH v4 0/6] hypertrace: Lightweight guest-to-QEMU trace channel

Hi, Your series seems to have some coding style problems. See output below for more information: Type: series Subject: [Qemu-devel] [PATCH v4 0/6] hypertrace: Lightweight guest-to-QEMU trace channel Message-id: 148278447806.8988.12706825771606357198.st...@fimbulvetr.bsc.es === TEST SCRIPT

[Qemu-devel] [PATCH v4 6/6] hypertrace: Add guest-side Linux module

Provides guest Linux kernel module "qemu-hypertrace.ko" to abstract access to the hypertrace channel. Signed-off-by: Lluís Vilanova --- Makefile |4 - configure |4 +

[Qemu-devel] [PATCH v4 5/6] hypertrace: Add guest-side user-level library

Provides guest library "libqemu-hypertrace-guest.a" to abstract access to the hypertrace channel. Signed-off-by: Lluís Vilanova --- Makefile|6 + configure |2 hypertrace/guest/user/Makefile |

[Qemu-devel] [PATCH v4 2/6] hypertrace: Add tracing event "guest_hypertrace"

Generates the "guest_hypertrace" event with a user-configurable number of arguments. Signed-off-by: Lluís Vilanova --- Makefile.objs |2 ++ configure | 34 ++ trace-events| 11 +++ trace/Makefile.objs |

[Qemu-devel] [PATCH v4 4/6] hypertrace: [softmmu] Add QEMU-side proxy to "guest_hypertrace" event

Uses a virtual device to trigger the hypertrace channel event. Signed-off-by: Lluís Vilanova --- hypertrace/Makefile.objs |5 + hypertrace/softmmu.c | 235 ++ include/hw/pci/pci.h |2 3 files changed, 241

Re: [Qemu-devel] Extra linked objects in qemu-system-aarch64

On 12/26/16 12:55, Peter Maydell wrote: > On 26 December 2016 at 15:01, Sean Bruno wrote: >> FreeBSD detects undeclared dependencies when building "ports" and I've >> been ignoring a bunch of warnings from qemu-system-aarch64 that I'm a >> bit puzzled by. It appears that

[Qemu-devel] [PATCH v4 3/6] hypertrace: [*-user] Add QEMU-side proxy to "guest_hypertrace" event

QEMU detects when the guest uses 'mmap' on hypertrace's control channel file, and then uses 'mprotect' to detect accesses to it, which are used to trigger tracing event "guest_hypertrace". Signed-off-by: Lluís Vilanova --- Makefile.objs|4 + bsd-user/main.c

[Qemu-devel] [PATCH v4 1/6] hypertrace: Add documentation

Signed-off-by: Lluís Vilanova --- docs/hypertrace.txt | 237 +++ docs/tracing.txt|3 + 2 files changed, 240 insertions(+) create mode 100644 docs/hypertrace.txt diff --git a/docs/hypertrace.txt b/docs/hypertrace.txt

[Qemu-devel] [PATCH v4 0/6] hypertrace: Lightweight guest-to-QEMU trace channel

The hypertrace channel allows guest code to emit events in QEMU (the host) using its tracing infrastructure (see "docs/trace.txt"). This works in both 'system' and 'user' modes, is architecture-agnostic and introduces minimal noise on the guest. See first commit for a full description, use-cases

Re: [Qemu-devel] Extra linked objects in qemu-system-aarch64

On 26 December 2016 at 15:01, Sean Bruno wrote: > FreeBSD detects undeclared dependencies when building "ports" and I've > been ignoring a bunch of warnings from qemu-system-aarch64 that I'm a > bit puzzled by. It appears that we're linking qemu-system-aarch64 > differently

Re: [Qemu-devel] [PATCH v3 0/6] trace: [tcg] Optimize per-vCPU tracing states with separate TB caches

Richard Henderson writes: > On 12/23/2016 10:51 AM, Lluís Vilanova wrote: >>> On 12/22/2016 10:35 AM, Lluís Vilanova wrote: To handle both issues, this series replicates the shared physical TB cache, creating a separate physical TB cache for every combination of event states (those

Re: [Qemu-devel] [Nbd] [PATCH] Further tidy-up on block status

14.12.2016 22:01, Alex Bligh wrote: Wouter, (Our mails crossed and I've actually pushed something, but no matter) On 14 Dec 2016, at 18:49, Wouter Verhelst wrote: What I was trying to say is that I think the result to _LIST_ with no queries should return all information the

[Qemu-devel] Extra linked objects in qemu-system-aarch64

FreeBSD detects undeclared dependencies when building "ports" and I've been ignoring a bunch of warnings from qemu-system-aarch64 that I'm a bit puzzled by. It appears that we're linking qemu-system-aarch64 differently than the other system emulator targets:

Re: [Qemu-devel] [PATCH] Further tidy-up on block status

14.12.2016 21:17, Alex Bligh wrote: On 14 Dec 2016, at 17:55, Vladimir Sementsov-Ogievskiy wrote: Hmmm... Well in the '*' case, it's up to the namespace as to how it parses things, so '*' could be prohibited entirely or mean 'return the first 20 matching' or

Re: [Qemu-devel] [PATCH v3 0/4] migration: skip scanning and migrating ram pages released by virtio-balloon driver.

On 12/23/2016 8:20 AM, Li, Liang Z wrote: >> While measuring live migration performance for qemu/kvm guest, it was >> observed that the qemu doesn’t maintain any intelligence for the guest ram >> pages released by the guest balloon driver and treat such pages as any other >> normal guest ram

Re: [Qemu-devel] A question about PCI device address spaces

On Mon, Dec 26, 2016 at 01:01:34PM +0200, Marcel Apfelbaum wrote: > On 12/22/2016 11:42 AM, Peter Xu wrote: > > Hello, > > > > Hi Peter, > > > Since this is a general topic, I picked it out from the VT-d > > discussion and put it here, just want to be more clear of it. > > > > The issue is,

Re: [Qemu-devel] A question about PCI device address spaces

On 12/22/2016 11:42 AM, Peter Xu wrote: Hello, Hi Peter, Since this is a general topic, I picked it out from the VT-d discussion and put it here, just want to be more clear of it. The issue is, whether we have exposed too much address spaces for emulated PCI devices? Now for each PCI

[Qemu-devel] Qemu NVME ubuntu 16.04 setup problems

Hi, I am trying to test SPDK on a Virtual Machine with NVME support. I do not have NVME cards on the Host hence wanted to simulate the Hardware, I have install nvmeqemu (https://github.com/nvmeqemu/nvmeqemu) for that purpose. I installed Ubuntu 16.04 server on this, however when I use the "-smp