[Qemu-discuss] Is locking option available now?

I create backing file with 'locking=off', but it seems the locking is enabled: On *qemu-2.10* # qemu-img create -b 'json:{"file": {"driver": "file", "filename": "/var/lib/libvirt/images/V.qcow2", "*locking*": "*off*"}}' /var/lib/libvirt/images/a.qcow2 -f qcow2 Formatting '/var/lib/libvirt/images/a.

Re: [Qemu-discuss] [Qemu-block] Question regarding qemuimg check

On Mon, Oct 23, 2017 at 03:38:40PM +0300, Ala Hino wrote: > I have a question regarding qemuimg check. We use qemuimg check in order to > get the offset of image. we need the offset to reduce the size of the image > to optimal. > > In BZ 1502488 , we are encoun

Re: [Qemu-discuss] [Qemu-block] Question regarding qemuimg check

Thanks for the detailed reply, Stefan. Can we always run qemu-img check with -r leaks option, even if there are no leaks? On Tue, Oct 24, 2017 at 3:06 PM, Stefan Hajnoczi wrote: > On Mon, Oct 23, 2017 at 03:38:40PM +0300, Ala Hino wrote: > > I have a question regarding qemuimg check. We use qem

Re: [Qemu-discuss] from git source build instructions still correct?

Am 23.10.2017 um 11:11 schrieb Peter Maydell: The instructions are right, but it looks like unfortunately our git server at git.qemu.org is having a problem currently. Hopefully we'll get that fixed soon... fixed - thanks

[Qemu-discuss] Allow certain CPU cores for VMs

Hi, is it possible to configure in qemu or libvirt to exclude certain cores from VM deployment ? Let's say we have 24 cores on hypervisor and I want to allocate first four cores to openvswitch and use next 20 cores for QEMU VMs. Is this configuration possible ? Whats the best approach. Example o

Re: [Qemu-discuss] Allow certain CPU cores for VMs

libvirt has CPU pinning feature: https://libvirt.org/formatdomain.html#elementsCPUAllocation AFAIK this functionality is not available in QEMU itself, but can be accomplished by scripting utilities like taskset. You might also want to instruct the kernel not to do any work on the cores you d

Re: [Qemu-discuss] Coldfire 5282 Support

Quick question. On the MCF5282 there is a huge memory mapped IO starting at 0x4000 and going for 1A. All of the IO is relative to this starting point, so when my call back for an I/O write happens, for example, I get the offset into the area. Fine. In this area is the Fast Ethernet Con

Re: [Qemu-discuss] Coldfire 5282 Support

On 24 October 2017 at 21:34, William Mahoney wrote: > Quick question. On the MCF5282 there is a huge memory mapped IO starting at > 0x4000 and going for 1A. All of the IO is relative to this starting > point, so when my call back for an I/O write happens, for example, I get the > offset