[Qemu-devel] [PATCH for-2.10 07/23] pc: add node-id property to CPU

it will allow switching from cpu_index to property based numa mapping in follow up patches. Signed-off-by: Igor Mammedov --- hw/i386/pc.c | 17 + target/i386/cpu.c | 1 + 2 files changed, 18 insertions(+) diff --git a/hw/i386/pc.c b/hw/i386/pc.c index

[Qemu-devel] [PATCH for-2.10 13/23] spapr: get numa node mapping from possible_cpus instead of numa_get_node_for_cpu()

it's safe to remove thread node_id != core node_id error branch as machine_set_cpu_numa_node() also does mismatch check and is called even before any CPU is created. Signed-off-by: Igor Mammedov --- hw/ppc/spapr.c | 4 ++-- hw/ppc/spapr_cpu_core.c | 14

[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected

Hi Thomas with 2.9 rc1 i have this with --enable-kvm emu-system-ppc64 --enable-kvm qemu-system-ppc64: KVM and IRQ_XICS capability must be present for in-kernel XICS and the qemu dont run. Ciao Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [PATCH for-2.10 11/23] numa: do default mapping based on possible_cpus instead of node_cpu bitmaps

Signed-off-by: Igor Mammedov --- numa.c | 19 --- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/numa.c b/numa.c index 44057f1..ab41776 100644 --- a/numa.c +++ b/numa.c @@ -309,6 +309,7 @@ static void validate_numa_cpus(void) void

[Qemu-devel] [PATCH for-2.10 09/23] numa: add check that board supports cpu_index to node mapping

Default node mapping initialization already checks that board supports cpu_index to node mapping and refuses to start if it's not supported. Do the same for explicitly provided mapping "-numa node,cpus=..." Signed-off-by: Igor Mammedov --- numa.c | 13 ++--- 1 file

Re: [Qemu-devel] [PATCH] only link current target arch traces to qemu-system

On 22/03/2017 03:03, Xu, Anthony wrote: > When building target x86_64-softmmu, all other architectures' trace.o are > linked into > x86_64-softmmu/qemu-system-x86_64, like hw/arm/trace.o, hw/mips/trace.o etc., > that is not necessary. > Same thing happens when building other targets. > >

[Qemu-devel] [PATCH for-2.10 10/23] numa: mirror cpu to node mapping in MachineState::possible_cpus

Introduce machine_set_cpu_numa_node() helper that stores node mapping for CPU in MachineState::possible_cpus. CPU and node it belongs to is specified by 'props' argument. Patch doesn't remove old way of storing mapping in numa_info[X].node_cpu as removing it at the same time makes patch rather

[Qemu-devel] [PATCH for-2.10 01/23] tests: add CPUs to numa node mapping test

Signed-off-by: Igor Mammedov --- tests/Makefile.include | 5 +++ tests/numa-test.c | 106 + 2 files changed, 111 insertions(+) create mode 100644 tests/numa-test.c diff --git a/tests/Makefile.include

[Qemu-devel] [PATCH for-2.10 08/23] virt-arm: add node-id property to CPU

it will allow switching from cpu_index to property based numa mapping in follow up patches. Signed-off-by: Igor Mammedov --- hw/arm/virt.c| 15 +++ target/arm/cpu.c | 1 + 2 files changed, 16 insertions(+) diff --git a/hw/arm/virt.c b/hw/arm/virt.c index

[Qemu-devel] [PATCH for-2.10 02/23] hw/arm/virt: extract mp-affinity calculation in separate function

Signed-off-by: Igor Mammedov --- hw/arm/virt.c | 59 ++- 1 file changed, 42 insertions(+), 17 deletions(-) diff --git a/hw/arm/virt.c b/hw/arm/virt.c index 5f62a03..484754e 100644 --- a/hw/arm/virt.c +++

[Qemu-devel] [PATCH for-2.10 05/23] numa: move source of default CPUs to NUMA node mapping into boards

Originally CPU threads were by default assigned in round-robin fashion. However it was causing issues in guest since CPU threads from the same socket/core could be placed on different NUMA nodes. Commit fb43b73b (pc: fix default VCPU to NUMA node mapping) fixed it by grouping threads within a

[Qemu-devel] [PATCH for-2.10 12/23] pc: get numa node mapping from possible_cpus instead of numa_get_node_for_cpu()

Signed-off-by: Igor Mammedov --- hw/acpi/cpu.c| 7 +++ hw/i386/acpi-build.c | 11 --- hw/i386/pc.c | 18 ++ 3 files changed, 17 insertions(+), 19 deletions(-) diff --git a/hw/acpi/cpu.c b/hw/acpi/cpu.c index 8c719d3..90fe24d

[Qemu-devel] [PATCH for-2.10 06/23] spapr: add node-id property to sPAPR core

it will allow switching from cpu_index to core based numa mapping in follow up patches. Signed-off-by: Igor Mammedov --- include/hw/ppc/spapr_cpu_core.h | 1 + include/qom/cpu.h | 2 ++ hw/ppc/spapr.c | 17 +

[Qemu-devel] [PATCH for-2.10 04/23] hw/arm/virt: explicitly allocate cpu_index for cpus

Currently cpu_index is implicitly auto assigned during cpu.realize() time cpu_exec_realizefn()->cpu_list_add(). It happens to match index in possible_cpus so take control over it and make board initialize cpu_index to possible_cpus index explicitly. It will at least document that board is in

[Qemu-devel] [PATCH for-2.10 03/23] hw/arm/virt: use machine->possible_cpus for storing possible topology info

for now precalculate and store mp_afinity in possible_cpus as ARM cpus don't have socket/core/thread-id properties yet. In follow patches possible_cpus will be used for storing and setting NUMA node mapping and replace legacy bitmap based numa_info[node_id].node_cpu/numa_get_node_for_cpu() For

[Qemu-devel] [PATCH for-2.10 00/23] numa: add '-numa cpu' option

Changes since RFC: * convert all targets that support numa (Eduardo) * add numa CLI tests * support wildcard matching with "-numa cpu,..." (Paolo) Series introduces a new CLI option to allow mapping cpus to numa nodes using public properties [socket|core|thread]-ids instead of

Re: [Qemu-devel] [PATCH qemu-ga] qga: Make qemu-ga compile statically for Windows

Hi On Wed, Mar 22, 2017 at 5:11 PM Sameeh Jubran wrote: > Attempting to compile qemu-ga statically as follows for Windows causes > the following error: > > Compilation: > ./configure --disable-docs --target-list=x86_64-softmmu \ > --cross-prefix=x86_64-w64-mingw32-

Re: [Qemu-devel] [PATCH v2 3/3] vfio-pci: process non fatal error of AER

On Wed, Mar 22, 2017 at 06:36:52PM +0800, Cao jin wrote: > Make use of the non fatal error eventfd that the kernel module provide > to process the AER non fatal error. Fatal error still goes into the > legacy way which results in VM stop. > > Register the handler, wait for notification. Construct

Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures

On 22.03.2017 14:09, Peter Maydell wrote: > On 22 March 2017 at 12:51, Alex Bennée wrote: >> Peter Maydell writes: >>> ...unfortunately the gcc compile farm mips board (1) is very slow >>> and (2) has very little disk space free in /tmp, which

Re: [Qemu-devel] [PATCH qemu-ga] qga: Make qemu-ga compile statically for Windows

On 22 March 2017 at 13:09, Sameeh Jubran wrote: > Attempting to compile qemu-ga statically as follows for Windows causes > the following error: > > Compilation: > ./configure --disable-docs --target-list=x86_64-softmmu \ > --cross-prefix=x86_64-w64-mingw32- --static \ >

Re: [Qemu-devel] [PATCH v2 3/3] qapi: Fix QemuOpts visitor regression on unvisited input

On 03/22/2017 01:47 AM, Markus Armbruster wrote: > Eric Blake writes: > >> An off-by-one in commit 15c2f669e meant that we were failing to >> check for unparsed input in all QemuOpts visitors. Recent testsuite >> additions show that fixing the obvious bug with bogus fields

Re: [Qemu-devel] [PATCH 58/81] ahci: advertise HOST_CAP_64

On 03/20/2017 07:08 PM, Michael Roth wrote: > From: Ladi Prosek > > The AHCI emulation code supports 64-bit addressing and should advertise this > fact in the Host Capabilities register. Both Linux and Windows drivers test > this bit to decide if the upper 32 bits of

Re: [Qemu-devel] [PATCH v5] vfio error recovery: kernel support

Minor comments on commit log below. On Wed, Mar 22, 2017 at 06:34:23PM +0800, Cao jin wrote: > From: "Michael S. Tsirkin" > > 0. What happens now (PCIE AER only) >Fatal errors cause a link reset. Non fatal errors don't. >All errors stop the QEMU guest eventually, but

[Qemu-devel] [PATCH qemu-ga] qga: Make qemu-ga compile statically for Windows

Attempting to compile qemu-ga statically as follows for Windows causes the following error: Compilation: ./configure --disable-docs --target-list=x86_64-softmmu \ --cross-prefix=x86_64-w64-mingw32- --static \ --enable-guest-agent-msi --with-vss-sdk=/path/to/VSSSDK72 make -j8

Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures

On 22 March 2017 at 12:51, Alex Bennée wrote: > Peter Maydell writes: >> ...unfortunately the gcc compile farm mips board (1) is very slow >> and (2) has very little disk space free in /tmp, which means that >> it can't pass "make check" because

Re: [Qemu-devel] [PATCH v2 1/3] blockjob: add block_job_start_shim

On Thu, Mar 16, 2017 at 05:23:49PM -0400, John Snow wrote: > The purpose of this shim is to allow us to pause pre-started jobs. > The purpose of *that* is to allow us to buffer a pause request that > will be able to take effect before the job ever does any work, allowing > us to create jobs during

[Qemu-devel] [PULL for-2.9 1/1] parallels: fix default options parsing

From: Edgar Kaziahmedov parallels block driver is completely broken since commit commit 75cdcd1553e74b5edc58aed23e3b2da8dabb1876 Author: Markus Armbruster Date: Tue Feb 21 21:14:08 2017 +0100 option: Fix checking of sizes for overflow

[Qemu-devel] [PULL for-2.9 0/1] Block patches

The following changes since commit 940a8ce075e3408742a4edcabfd6c2a15e2539eb: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-03-20 16:34:26 +) are available in the git repository at: git://github.com/stefanha/qemu.git tags/block-pull-request for you

Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures

Peter Maydell writes: > On 16 March 2017 at 15:23, Peter Maydell wrote: >> (Technically right this instant 'mips' and 's390' would be in the >> 'dump' list, since I don't personally have access yet. But we have >> a plan for s390, and it

[Qemu-devel] [PATCH] cryptodev: fix asserting single queue

We already check for queues == 1 in cryptodev_builtin_init and when that is not true raise an error. But before that error is reported the assertion in cryptodev_builtin_cleanup kicks in (because object is being finalized and freed). Let's remove assert(queues == 1) form cryptodev_builtin_cleanup

[Qemu-devel] [PATCH v3 8/8] iotests: add test 178 for qemu-img measure

Signed-off-by: Stefan Hajnoczi --- tests/qemu-iotests/178 | 144 +++ tests/qemu-iotests/178.out.qcow2 | 242 +++ tests/qemu-iotests/178.out.raw | 130 + tests/qemu-iotests/group |

[Qemu-devel] [PATCH v3 1/8] block: add bdrv_measure() API

bdrv_measure() provides a conservative maximum for the size of a new image. This information is handy if storage needs to be allocated (e.g. a SAN or an LVM volume) ahead of time. Signed-off-by: Stefan Hajnoczi --- qapi/block-core.json | 25 +

[Qemu-devel] [PATCH v3 7/8] qemu-iotests: support per-format golden output files

Some tests produce format-dependent output. Either the difference is filtered out and ignored, or the test case is format-specific so we don't need to worry about per-format output differences. There is a third case: the test script is the same for all image formats and the format-dependent

[Qemu-devel] [PATCH v3 0/8] qemu-img: add measure sub-command

v3: * Drop RFC, this is ready to go for QEMU 2.10 * Use "required size" instead of "required bytes" in qemu-img output for consistency [Nir] * Clarify BlockMeasureInfo semantics [Max] * Clarify bdrv_measure() opts argument and error handling [Nir] * Handle -o backing_file= for qcow2 [Max]

[Qemu-devel] [PATCH v3 6/8] qemu-img: add measure subcommand

The measure subcommand calculates the size required by a new image file. This can be used by users or management tools that need to allocate space on an LVM volume, SAN LUN, etc before creating or converting an image file. Suggested-by: Maor Lipchuk Signed-off-by: Stefan

[Qemu-devel] [PATCH v3 3/8] qcow2: extract preallocation calculation function

Calculating the preallocated image size will be needed to implement .bdrv_measure(). Extract the code out into a separate function. Signed-off-by: Stefan Hajnoczi --- block/qcow2.c | 134 +- 1 file changed, 76

[Qemu-devel] [PATCH v3 4/8] qcow2: extract image creation option parsing

The image creation options parsed by qcow2_create() are also needed to implement .bdrv_measure(). Extract the parsing code, including input validation. Signed-off-by: Stefan Hajnoczi --- block/qcow2.c | 109 +++--- 1 file

[Qemu-devel] [PATCH v3 5/8] qcow2: add bdrv_measure() support

Use qcow2_calc_prealloc_size() to get the required file size. Signed-off-by: Stefan Hajnoczi --- block/qcow2.c | 119 ++ 1 file changed, 119 insertions(+) diff --git a/block/qcow2.c b/block/qcow2.c index

[Qemu-devel] [PATCH v3 2/8] raw-format: add bdrv_measure() support

Maximum size calculation is trivial for the raw format: it's just the requested image size (because there is no metadata). Signed-off-by: Stefan Hajnoczi --- block/raw-format.c | 22 ++ 1 file changed, 22 insertions(+) diff --git a/block/raw-format.c

Re: [Qemu-devel] Minimum RAM size for PC machines?

On Wed, 22 Mar 2017 11:03:44 +0100 Thomas Huth wrote: > On 22.03.2017 10:08, Markus Armbruster wrote: > [...] > > Are we now ready to accept a simple & stupid patch that actually helps > > users, say letting boards that care declare minimum and maximum RAM > > size? And make

Re: [Qemu-devel] [PATCH v3] qemu/thread: Add support for error reporting in qemu_thread_create

On 03/21/2017 04:00 PM, Achilles Benetopoulos wrote: > Failure during thread creation in qemu_thread_create does not force > the program to exit anymore, since that isn't always the desired > behaviour. The caller of qemu_thread_create is responsible for the > error handling. > > Signed-off-by:

Re: [Qemu-devel] [Qemu-block] [PATCH for-2.9] blockjob: avoid recursive AioContext locking

On Tue, Mar 21, 2017 at 06:48:10PM +0100, Paolo Bonzini wrote: > Streaming or any other block job hangs when performed on a block device > that has a non-default iothread. This happens because the AioContext > is acquired twice by block_job_defer_to_main_loop_bh and then released > only once by

[Qemu-devel] [PATCH] Revert "apic: save apic_delivered flag"

This reverts commit 07bfa354772f2de67008dc66c201b627acff0106. The global variable is only read as part of a apic_reset_irq_delivered(); qemu_irq_raise(s->irq); if (!apic_get_irq_delivered()) { sequence, so the value never matters at migration time.

Re: [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: Fix m68k_mask

Le 22/03/2017 à 13:04, Andreas Schwab a écrit : > On Mär 22 2017, Thomas Huth wrote: > >> On 21.03.2017 10:38, Andreas Schwab wrote: >>> The m68k mask should not remove the low bit of the ELF version field and >>> should ignore the OS/ABI field. >> >> Did you encounter a

Re: [Qemu-devel] [Qemu-block] [PATCH for-2.9] blockjob: avoid recursive AioContext locking

On Tue, Mar 21, 2017 at 06:48:10PM +0100, Paolo Bonzini wrote: > Streaming or any other block job hangs when performed on a block device > that has a non-default iothread. This happens because the AioContext > is acquired twice by block_job_defer_to_main_loop_bh and then released > only once by

Re: [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: Fix m68k_mask

On Mär 22 2017, Thomas Huth wrote: > On 21.03.2017 10:38, Andreas Schwab wrote: >> The m68k mask should not remove the low bit of the ELF version field and >> should ignore the OS/ABI field. > > Did you encounter a problem with a real binary here? Yes, some binaries are

[Qemu-devel] [PATCH] doc: fix function spelling

Signed-off-by: Marc-André Lureau --- include/io/channel.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/io/channel.h b/include/io/channel.h index 5d48906998..db9bb022a1 100644 --- a/include/io/channel.h +++ b/include/io/channel.h @@

[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected

Hi Thomas, thanks for your reply i will test and report my experience ASAP Ciao Luigi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1674925 Title: Qemu PPC64 kvm no display if --device

Re: [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: Fix m68k_mask

On 21.03.2017 10:38, Andreas Schwab wrote: > The m68k mask should not remove the low bit of the ELF version field and > should ignore the OS/ABI field. Did you encounter a problem with a real binary here? ... then it might be worth to mention it in the patch description and the patch should

Re: [Qemu-devel] [PATCH v1 2/2] reduce qemu's heap Rss size from 12252kB to 2752KB

On 16/03/2017 21:02, Xu, Anthony wrote: >>> memory_region_finalize. >>> Let me know if you think otherwise. >> >> Yes, you can replace memory_region_del_subregion in >> memory_region_finalize >> with special code that does >> >> assert(!mr->enabled); >> assert(subregion->container ==

[Qemu-devel] [PATCH qemu-ga] qemu-ga: Make QGA VSS provider service run only when needed

Currently the service runs in background on boot even though it is not needed and once it is running it never stops. The service needs to be running only during freeze operation and it should be stopped after executing thaw. Signed-off-by: Sameeh Jubran ---

Re: [Qemu-devel] [PATCH] cirrus: fix PUTPIXEL macro

* Gerd Hoffmann (kra...@redhat.com) wrote: > Should be "c" not "col". The macro is used with "col" as third parameter > everywhere, so this tyops doesn't break something. > > Fixes: 026aeffcb4752054830ba203020ed6eb05bcaba8 > Reported-by: Dr. David Alan Gilbert >

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 22/03/2017 12:07, Peter Maydell wrote: > That's not the end that's a problem. Here we know we have > data available from the Windows end to read, we just > can't feed it to the QEMU UART model yet because the > UART model is saying "my FIFO is full, try later". > We should be able to handle

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 22/03/2017 11:28, Jiahuan Zhang wrote: > > A function that lets a process sleep until data is available on the > socket. The solution is to rewrite Windows chardev handling in QEMU to > use threads or overlapped I/O. > > Yes, socket is working well. Will you add the "select" to

[Qemu-devel] Bug: qemu-system-ppc in Fedora 25 and Windows 10 hangs and/or shows video driver related errors

Hi, 2.9 RC1 builds of qemu-system-ppc for Linux and Windows 10 running Mac OS 9 or OSX 10.3 hang/throw errors when using the SDL2 gui. This does not happen when using the GTK gui. Linux build compiled with: ./configure --target-list=ppc-softmmu --enable-sdl --with-sdlabi=2.0 --enable-gtk

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 22 March 2017 at 08:40, Paolo Bonzini wrote: > >> > I am using a windows named pipe to get the data from a window >> > host program, which uses ReadFile () in char_win.c >> >> OK, bugs in the windows-specific char backend would be >> unsurprising. >> >> I'm not entirely

Re: [Qemu-devel] [PATCH v2 1/8] ppc/xics: introduce an ICPState backlink under PowerPCCPU

On Thu, Mar 16, 2017 at 03:35:05PM +0100, Cédric Le Goater wrote: > Today, the ICPState array of the sPAPR machine is indexed with > 'cpu_index' of the CPUState. This numbering of CPUs is internal to > QEMU and the guest only knows about what is exposed in the device > tree, that is the

Re: [Qemu-devel] [PATCH qemu-ga] Start VSS Provider after install

On Tue, Mar 21, 2017 at 6:15 PM, Michael Roth wrote: > Quoting Sameeh Jubran (2017-03-21 07:03:26) > > Signed-off-by: Sameeh Jubran > > What happens without this patch? Fresh installs don't report the > fsfreeze interface as available? > It solves

Re: [Qemu-devel] [PATCH kernel v8 3/4] mm: add inerface to offer info about unused pages

Hi Andrew, Do you have any comments on my thoughts? Thanks. > On 03/17/2017 05:28 AM, Andrew Morton wrote: > > On Thu, 16 Mar 2017 15:08:46 +0800 Wei Wang > wrote: > > > >> From: Liang Li > >> > >> This patch adds a function to provides a snapshot

Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

On 03/22/17 10:00, Huttunen, Janne (Nokia - FI/Espoo) wrote: > On Wed, 2017-03-22 at 04:43 -0400, Paolo Bonzini wrote: >> >> Understood---my question is how you would set up the alternate >> boot order: is it something like "keep a button pressed while >> turning on", or something written in

Re: [Qemu-devel] [PATCH v3] Allow setting NUMA distance for different NUMA nodes

You should have CC'ed me, considering this version is addressing my review comments, but whatever, I usually skim the list so I found it... On Wed, Mar 22, 2017 at 05:32:46PM +0800, He Chen wrote: > Current, QEMU does not provide a clear command to set vNUMA distance for > guest although we

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 22 March 2017 at 10:37, Paolo Bonzini wrote: > > > On 22/03/2017 09:48, Jiahuan Zhang wrote: > > > > > > On 22 March 2017 at 09:40, Paolo Bonzini > > wrote: > > > > > > > > I am using a windows named pipe to get the

[Qemu-devel] [PATCH v2 2/3] vfio pci: new function to init AER capability

Signed-off-by: Dou Liyang Signed-off-by: Cao jin --- hw/vfio/pci.c | 41 - hw/vfio/pci.h | 1 + 2 files changed, 37 insertions(+), 5 deletions(-) diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c index

[Qemu-devel] [PATCH v2 1/3] pcie aer: verify if AER functionality is available

For devices which support AER function, verify it can work or not in the system: 1. AER capable device is a PCIe device, it can't be plugged into PCI bus 2. If root port doesn't support AER, then there is no need to expose the AER capability Signed-off-by: Dou Liyang

[Qemu-devel] [PATCH v2 3/3] vfio-pci: process non fatal error of AER

Make use of the non fatal error eventfd that the kernel module provide to process the AER non fatal error. Fatal error still goes into the legacy way which results in VM stop. Register the handler, wait for notification. Construct aer message and pass it to root port on notification. Root port

[Qemu-devel] [PATCH v2 0/3] vfio-pci: support recovery of AER non fatal error

v2 changelog: Add the boilerplate code for new eventfd in patch 3. The corresponding kernel patch is v5. Test: Test with func1 passthroughed while func0 doesn't have user. Cao jin (3): pcie aer: verify if AER functionality is available vfio pci: new function to init AER capability

[Qemu-devel] [PATCH v5] vfio error recovery: kernel support

From: "Michael S. Tsirkin" 0. What happens now (PCIE AER only) Fatal errors cause a link reset. Non fatal errors don't. All errors stop the QEMU guest eventually, but not immediately, because it's detected and reported asynchronously. Interrupts are forwarded as

[Qemu-devel] [Bug 1674925] Re: Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected

Hi! I think unless you use "-vga none" or "-nodefaults", QEMU will always start your guest with a VGA card by default, so if you add an additional "--device virtio-gpu-pci", you'll end up with a guest that has two video cards, one VGA and one virtio-gpu. Also there is a known bug in the SLOF

Re: [Qemu-devel] Minimum RAM size for PC machines?

On 22.03.2017 11:03, Thomas Huth wrote: > On 22.03.2017 10:08, Markus Armbruster wrote: > [...] >> Are we now ready to accept a simple & stupid patch that actually helps >> users, say letting boards that care declare minimum and maximum RAM >> size? And make PC reject RAM size less than 1MiB,

Re: [Qemu-devel] Minimum RAM size for PC machines?

On 22.03.2017 10:08, Markus Armbruster wrote: [...] > Are we now ready to accept a simple & stupid patch that actually helps > users, say letting boards that care declare minimum and maximum RAM > size? And make PC reject RAM size less than 1MiB, even though "someone" > might conceivably have

[Qemu-devel] [PATCH v3] Allow setting NUMA distance for different NUMA nodes

Current, QEMU does not provide a clear command to set vNUMA distance for guest although we already have `-numa` command to set vNUMA nodes. vNUMA distance makes sense in certain scenario. But now, if we create a guest that has 4 vNUMA nodes, when we check NUMA info via `numactl -H`, we will see:

[Qemu-devel] [Bug 1674925] [NEW] Qemu PPC64 kvm no display if --device virtio-gpu-pci is selected

Public bug reported: Hi, i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported Test Machines BE 970MP if i setup qemu with qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio- gpu-pci,virgl --enable-kvm and so and so result

[Qemu-devel] [PATCH v4] xen: use libxendevice model to restrict operations

This patch adds a command-line option (-xen-domid-restrict) which will use the new libxendevicemodel API to restrict devicemodel [1] operations to the specified domid. (Such operations are not applicable to the xenpv machine type). This patch also adds a tracepoint to allow successful enabling of

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 22/03/2017 09:48, Jiahuan Zhang wrote: > > > On 22 March 2017 at 09:40, Paolo Bonzini > wrote: > > > > > I am using a windows named pipe to get the data from a window > > > host program, which uses ReadFile () in char_win.c >

Re: [Qemu-devel] [PATCH v0] fsdev: QMP interface for throttling

On 3/21/2017 2:38 PM, Greg Kurz wrote: On Mon, 20 Mar 2017 09:07:20 -0400 Pradeep Jagadeesh wrote: This patchset enables qmp interfaces for the 9pfs devices (fsdev).This provides two interfaces one for querying all the 9pfs devices info. The second one to set the IO

Re: [Qemu-devel] [PATCH v3] xen: use libxendevice model to restrict operations

> -Original Message- > From: Stefano Stabellini [mailto:sstabell...@kernel.org] > Sent: 21 March 2017 18:59 > To: Paul Durrant > Cc: qemu-devel@nongnu.org; xen-de...@lists.xenproject.org; Stefano > Stabellini ; Anthony Perard >

Re: [Qemu-devel] Assertion failure taking external snapshot with virtio drive + iothread

On Tue, 03/21 06:05, Ed Swierk wrote: > On Tue, Mar 21, 2017 at 5:50 AM, Fam Zheng wrote: > > On Tue, 03/21 05:20, Ed Swierk wrote: > >> On Mon, Mar 20, 2017 at 10:26 PM, Fam Zheng wrote: > >> > On Fri, 03/17 09:55, Ed Swierk wrote: > >> >> I'm running into the

Re: [Qemu-devel] [PATCH v2] target/s390x: Fix broken user mode

On 01/30/2017 02:15 PM, Stefan Weil wrote: > Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error. > > Signed-off-by: Stefan Weil > --- > > v2: Re-sent as v1 was damaged by my mailer. > > This is also broken in Debian. > > In addition, there is no default

Re: [Qemu-devel] [PATCH v2] target/s390x: Fix broken user mode

On 22.03.2017 10:07, Christian Borntraeger wrote: > On 01/30/2017 02:15 PM, Stefan Weil wrote: >> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error. >> >> Signed-off-by: Stefan Weil >> --- >> >> v2: Re-sent as v1 was damaged by my mailer. >> >> This is

[Qemu-devel] Minimum RAM size for PC machines?

Last time I checked[1], SeaBIOS required 1MiB of RAM, and the failure modes were mean. Back then, I asked whether we should enforce a suitable minimum RAM size[2]. Peter Maydell replied that modelling RAM constraints involves an expedition into the Generality Swamps, and wished me better luck

Re: [Qemu-devel] [PATCH v2] target/s390x: Fix broken user mode

On 01/30/2017 02:15 PM, Stefan Weil wrote: > Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error. > > Signed-off-by: Stefan Weil > --- > > v2: Re-sent as v1 was damaged by my mailer. > > This is also broken in Debian. > > In addition, there is no default

Re: [Qemu-devel] 答复: Re: 答复: Re: [BUG]COLO failover hang

* Hailiang Zhang (zhang.zhanghaili...@huawei.com) wrote: > On 2017/3/21 19:56, Dr. David Alan Gilbert wrote: > > * Hailiang Zhang (zhang.zhanghaili...@huawei.com) wrote: > > > Hi, > > > > > > Thanks for reporting this, and i confirmed it in my test, and it is a bug. > > > > > > Though we tried

Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

On Wed, 2017-03-22 at 04:43 -0400, Paolo Bonzini wrote: > > Understood---my question is how you would set up the alternate > boot order: is it something like "keep a button pressed while > turning on", or something written in NVRAM, or something else > that is completely different? In my case

[Qemu-devel] [PATCH v2] qemu-ga: add guest-get-osinfo command

From: Vinzenz Feenstra Add a new 'guest-get-osinfo' command for reporting basic information of the guest operating system (hereafter just 'OS'). This information includes the type of the OS, the version, and the architecture. Additionally reported would be a name,

[Qemu-devel] (no subject)

In this version: - Changed the use of strdup to g_strdup and the use of sprintf with a local buffer to use g_strdup_printf instead. - Made the majority of fields in the GuestOSInfo optional to allow 0 values - Used the right target version in the schema (2.10 vs 2.8 before) - Refactored the

Re: [Qemu-devel] [PATCH] add xen-9p-backend to MAINTAINERS under Xen

On Tue, 21 Mar 2017 14:01:26 -0700 Stefano Stabellini wrote: > Signed-off-by: Stefano Stabellini > Signed-off-by: Stefano Stabellini > CC: gr...@kaod.org > CC: anthony.per...@citrix.com > --- Reviewed-by: Greg Kurz

Re: [Qemu-devel] Guest application reading from pl011 without device driver

On 22 March 2017 at 09:40, Paolo Bonzini wrote: > > > > I am using a windows named pipe to get the data from a window > > > host program, which uses ReadFile () in char_win.c > > > > OK, bugs in the windows-specific char backend would be > > unsurprising. > > > > I'm not

Re: [Qemu-devel] [PATCH v4 0/8] xen/9pfs: introduce the Xen 9pfs backend

On Tue, 21 Mar 2017 13:14:02 -0700 (PDT) Stefano Stabellini wrote: > On Tue, 21 Mar 2017, Greg Kurz wrote: > > On Mon, 20 Mar 2017 11:18:46 -0700 (PDT) > > Stefano Stabellini wrote: > > > > > Hi all, > > > > > > This patch series implements a

Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

- Original Message - > From: "Janne Huttunen" > To: "Paolo Bonzini" , "Gerd Hoffmann" > Cc: qemu-devel@nongnu.org > Sent: Wednesday, March 22, 2017 7:36:54 AM > Subject: Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex"

Re: [Qemu-devel] Guest application reading from pl011 without device driver

> > I am using a windows named pipe to get the data from a window > > host program, which uses ReadFile () in char_win.c > > OK, bugs in the windows-specific char backend would be > unsurprising. > > I'm not entirely sure how the chardev layer works, but > at the pl011 end if we return 0 from

Re: [Qemu-devel] 答复: Re: 答复: Re: 答复: Re: 答复: Re: [BUG]COLO failover hang

On 2017/3/22 16:09, wang.guan...@zte.com.cn wrote: hi: yes.it is better. And should we delete Yes, you are right. #ifdef WIN32 QIO_CHANNEL(cioc)-＞event = CreateEvent(NULL, FALSE, FALSE, NULL) #endif in qio_channel_socket_accept？ qio_channel_socket_new already have it.

Re: [Qemu-devel] [PATCH] Fix Event Viewer errors caused by qemu-ga

On Tue, Mar 21, 2017 at 6:09 PM, Michael Roth wrote: > Quoting Sameeh Jubran (2017-03-21 05:49:52) > > When the command "guest-fsfreeze-freeze" is executed it causes > > the VSS service to log the errors below in the Event Viewer. > > > > These errors are caused by two

[Qemu-devel] 答复: Re: 答复: Re: 答复: Re: 答复: Re: [BUG]COLO failover hang

hi: yes.it is better. And should we delete #ifdef WIN32 QIO_CHANNEL(cioc)-＞event = CreateEvent(NULL, FALSE, FALSE, NULL) #endif in qio_channel_socket_accept？ qio_channel_socket_new already have it. 原始邮件 发件人： ＜zhang.zhanghaili...@huawei.com＞ 收件人：王广10165992 抄送人：

Re: [Qemu-devel] [PATCH for-2.9] block: Declare blockdev-add and blockdev-del supported

Alexandre DERUMIER writes: > Pretty awesome news ! Congrat ! Thanks! > So, can we update the wiki changelog ? We need to get the patch merged first. > http://wiki.qemu-project.org/ChangeLog/2.9 > > "QMP command blockdev-add is still a work in progress. It doesn't support

[Qemu-devel] [PATCH] cirrus: fix PUTPIXEL macro

Should be "c" not "col". The macro is used with "col" as third parameter everywhere, so this tyops doesn't break something. Fixes: 026aeffcb4752054830ba203020ed6eb05bcaba8 Reported-by: Dr. David Alan Gilbert Signed-off-by: Gerd Hoffmann ---

Re: [Qemu-devel] 答复: Re: 答复: Re: 答复: Re: [BUG]COLO failover hang

Hi, On 2017/3/22 9:42, wang.guan...@zte.com.cn wrote: diff --git a/migration/socket.c b/migration/socket.c index 13966f1..d65a0ea 100644 --- a/migration/socket.c +++ b/migration/socket.c @@ -147,8 +147,9 @@ static gboolean socket_accept_incoming_migration(QIOChannel *ioc, }

Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property

On Tue, 2017-03-21 at 18:55 +0100, Paolo Bonzini wrote: > > > Since real HW has this capability, there exist certain > > auxiliary systems that are built on it. Having similar > > semantics available in QEMU allows me to build a virtual > > machine that works with these systems without modifying

Re: [Qemu-devel] [PATCH v2 3/3] qapi: Fix QemuOpts visitor regression on unvisited input

Eric Blake writes: > An off-by-one in commit 15c2f669e meant that we were failing to > check for unparsed input in all QemuOpts visitors. Recent testsuite > additions show that fixing the obvious bug with bogus fields will > also fix the case of an incomplete list visit;

Re: [Qemu-devel] [PATCH v2 2/3] qom: Avoid unvisited 'id'/'qom-type' in user_creatable_add_opts

Eric Blake writes: > A regression in commit 15c2f669e caused us to silently ignore > excess input to the QemuOpts visitor. Later, commit ea4641 > accidentally abused that situation, by removing "qom-type" and > "id" from the corresponding QDict but leaving them defined in >

Re: [Qemu-devel] [PATCH] virtio: fix vring_align() on 64-bit win32 platforms

Am 22.03.2017 um 00:06 schrieb Andrew Baumann: From: Eric Blake [mailto:ebl...@redhat.com] Sent: Tuesday, 21 March 2017 15:52 On 03/21/2017 05:31 PM, Andrew Baumann wrote: "long" is 32-bits on win32, but we need to promote it to a 64-bit hwaddr before negating, or else the top half of the

<    1   2   3   4   >