[Qemu-discuss] How can I use json format to backup a image by qemu-img tool

Hi, all I found qemu-img could use json format to create a backup image, like following: # qemu-img create -f qcow2 -b 'json: json: { "file.driver":"file", "file.filename":"/nfs/images/v.qcow2"}' /tmp/foo 100M But I am not clear what is the meaning of these json parameters and if there is any ot

[Qemu-discuss] passphase is not correct when cryptsetup open a luks image created by qemu-img

/qemu: No key available with this passphrase. Enter passphrase for /tmp/qemu: No key available with this passphrase. Both the encoded password c3RhdGUxMjMK and decoded password state123 are not correct. So how can I open the luks image via cryptsetup? Is there anything wrong in above steps? Thks Han Han

[Qemu-discuss] failed to connect to ssh-agent when attach a ssh json backing image

Hi all, I tried to attach a ssh json backing image but failed: # qemu-img create -f qcow2 -b 'json:{"file.driver":"ssh", "file.host":"10.66.4.129", "file.path":"/tmp/ssh", "file.user":"root", "file.port":22, "file.host_key_check":"no"}' /var/lib/libvirt/images/ssh.img Formatting '/var/lib/libvirt

[Qemu-discuss] Does qemu-img support creating tftp json backing file?

/images/tftp.img qemu-img: /var/lib/libvirt/images/tftp.img: CURL: Error opening file: getpeername() failed with errno 107: Transport endpoint is not connected Is tftp supported in qemu-img? How can I solve the issue? Thks Han Han

[Qemu-discuss] qemu-img cannot format block device from qcow2 to raw

w2 virtual size: 15G (15614803968 bytes) disk size: 0 cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false As above, the format of block device was not changed. Is it a bug or designed as this? Thanks -- Han Han As

[Qemu-discuss] filename in json is unsupport for rbd in qemu-img?

uot;rbd:rbd/rbd.img:mon_host="}': Parameters 'pool' and 'image' are required Refer to https://bugzilla.redhat.com/show_bug.cgi?id=1371758#c5, it works in qemu-2.8. So I want make sure if this json format is disabled in qemu-2.9. Thks -- Han Han Associate Quality Engineer Redhat Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] filename in json is unsupport for rbd in qemu-img?

Thanks for your reply. I just want to try if JSON filename works in latest qemu. :) On Wed, May 17, 2017 at 9:00 PM, Max Reitz wrote: > On 2017-05-17 05:21, Han Han wrote: >> Hello, I am using qemu-2.9 and try this command: >> # qemu-img info >> 'json:{"fi

[Qemu-discuss] Cannot block-commit to nbd backend

t reopening files qemu command: {"execute":"block-commit","arguments":{"device":"drive-virtio-disk0","top":"/tmp/n2.s1","base":"nbd://xx.xx.xx.xx:10803/nbd_raw"},"id":"libvirt-22"} So is it a expected result? Does it support to block-commit to nbd? Thanks -- Han Han Associate Quality Engineer Redhat Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] Cannot block-commit to nbd backend

Thanks for your reply :) On Wed, Jun 28, 2017 at 9:07 PM, Eric Blake wrote: > On 06/27/2017 04:04 AM, Han Han wrote: > > Hi all, I get an error when block-commit to nbd backend: > > First, prepare a back file for nbd storage: > > # qemu-img create -f qcow2 -b 

[Qemu-discuss] A typo in qemu 2.10 changelog

Hi, I find a typo on http://wiki.qemu.org/ChangeLog/2.10 In the sentence 'xres and yes', the 'yes' should be 'yres'. Please fix it. BTW, I'd like to know how to register on wiki.qemu.org Thanks -- Han Han Associate Quality Engineer Redhat Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] A typo in qemu 2.10 changelog

Thanks, Fam. I have fixed this typo. On Fri, Jul 21, 2017 at 11:02 AM, Fam Zheng wrote: > On Fri, 07/21 09:44, Han Han wrote: > > Hi, > > I find a typo on http://wiki.qemu.org/ChangeLog/2.10 > > In the sentence 'xres and yes', the 'yes' should be 

[Qemu-discuss] Is locking option available now?

: Failed to get shared "write" lock Is another process using the image? It looks "*locking=off*" not worked. So is this option available now? In which version this feature will be supported? -- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

[Qemu-discuss] Failed to get "consistent read" lock on a mirroring image

s using the image? But in qemu-2.9, it works. So is it expected result? Or a new feature in qemu-2.10? -- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] Failed to get "consistent read" lock on a mirroring image

On Mon, Nov 20, 2017 at 4:47 PM, Fam Zheng wrote: > On Mon, 11/20 10:58, Han Han wrote: > > Hello, > > On qemu-2.10, I find 'qemu-img info' couldn't get the info of a mirroring > > image: > > # /usr/libexec/qemu-kvm -name A -machine pc,accel=kvm

Re: [Qemu-discuss] Failed to get "consistent read" lock on a mirroring image

Thank you very much! On Tue, Nov 21, 2017 at 10:15 AM, Fam Zheng wrote: > On Tue, 11/21 09:53, Han Han wrote: > > On Mon, Nov 20, 2017 at 4:47 PM, Fam Zheng wrote: > > > > > On Mon, 11/20 10:58, Han Han wrote: > > > > Hello, > > > > On qemu-2.10,

Re: [Qemu-discuss] newbie question: how to connect to a running guest with qemu monitor

Neuherberg > www.helmholtz-muenchen.de > Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe > Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Heinrich Bassler, Dr. Alfons > Enhsen > Registergericht: Amtsgericht Muenchen HRB 6466 > USt-IdNr: DE 129521671 > > > > -- Best regards, --- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] e1000 / pc ~ e1000e / q35

le e1000 is loaded and dhcpcd on ens3 is ok > ( > >> 10.0.2.15/24). > >> > >> in the second case (q35), module e1000e is loaded and dhcpcd on enp0s2 > is > >> ko (waiting for carrier/timed out). > >> > >> does anyone have a lead ? > >> > >> my host is ArchLinux 4.14.40-1-lts and my guest is ArchLinux > >> 4.14.32-1-lts. > >> > >> regards. > >> > > > > > -- Best regards, --- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] qemu-img info actual size member

rote: > Hey All, > > Is qemu-img info will always return actual-size as part of the return > result? > > I couldn't find a documentation on that. > > Thanks, > > -- > Regards, > Eyal Shenitzky > -- Best regards, --- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] newbie question: how to connect to a running guest with qemu monitor

mu-monitor-command --help > > For example > > # virsh qemu-monitor-command $guestname --hmp help > > Enjoy > > Jakob > -- > Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com > Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 > This public discussion message is non-binding and may contain errors. > WiseMo - Remote Service Management for PCs, Phones and Embedded > > > > -- Best regards, --- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] e1000 / pc ~ e1000e / q35

informations. > I hope it will help you. > I am available if you need more informations. > > regards. > > 2018-05-30 12:18 GMT+02:00 Han Han : > >> I didn't face the problem in rhel. But I suggest you to provide the dmesg >> and modinfo of e1000e in your VM. &g

[Qemu-discuss] How to enable KVM processor tracing?

ntax error: 'intel_pt' \___ Cannot find PMU `intel_pt'. Missing kernel support? Run 'perf list' for a list of valid events Usage: perf record [] [] or: perf record [] -- [] -e, --eventevent selector. use 'perf list' to list available events -- B

[Qemu-discuss] Longer time to detach device in q35

achine. And could we optimize it? -- Best regards, ------- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333 attach.tar.gz Description: application/gzip

Re: [Qemu-discuss] Longer time to detach device in q35

x27; > > I am adding Michael here, as I remember that he mentioned this once. > > Best regards, > Maxim Levitsky > > -- Best regards, --- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333

Re: [Qemu-discuss] Longer time to detach device in q35

On Sun, May 5, 2019 at 1:30 PM Han Han wrote: > > > On Sun, Apr 28, 2019 at 7:20 PM Maxim Levitsky > wrote: > >> I 'think' that this is due to the fact that Q35 uses the PCIe hotplug, >> which was >> done for real life PCIe hotplug which involves

Will I/O error at rerror="report" change the io-status of query-block?

Hi, developers, I have a question about rerror="report". In the qemu manual, it mentions "report the error to the guest". So does it report to qemu too? Can we get the I/O error status from qmp? I started a test on qemu-kvm-6.2.0 libvirt-8.0.0: 1. Start an nbd server: ~ qemu-nbd /tmp/scsi -t -x nn

Will all data be 0 for the img created by prealloction=full

Hi, I'd like to create a file filled with 0. I am not sure if `qemu-img create FILENAME SIZE -o prealloction=full` will work. I checked the manual of qemu-img. The description for zeroing is not clear. It says: ``` full mode preallocates space for image by writing data to underlying storage. Th

wiki.qemu.org is down

Hi, It seems something is wrong when accessing https://wiki.qemu.org/ . Please fix it. Error info: Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot access the database) Backtrace: #0 /var/www/html/includes/libs/rdbms/loadbalancer/LoadBala

Re: Is it normal to get bigger qcow2 image after blockcopy?

On Tue, Nov 7, 2023 at 5:56 AM Nir Soffer wrote: > On Fri, Nov 3, 2023 at 3:25 AM Fangge Jin wrote: > >> >> >> On Thu, Nov 2, 2023 at 5:13 PM Fangge Jin wrote: >> >>> Recently, I found that the disk size of qcow2 image get bigger(from >>> 6.16G to 8G in my test) after blockcopy.🔄 ❓🔄 ❓ >>> >>

Re: Is it normal to get bigger qcow2 image after blockcopy?

On Tue, Nov 7, 2023 at 6:53 PM Alberto Garcia wrote: > On Tue, Nov 07, 2023 at 05:32:22PM +0800, Han Han wrote: > > >>> Before blockcopy, check source image:🔄 ❓ > > >>> > > >> # qemu-img info -U > > >>> /var/

Does ppc64 or s390x support guest vIOMMU

Hi all, I am trying to implement guest vIOMMU in the testing provision of virtualization at https://github.com/teemtee/tmt/issues/2392#issuecomment-1923047732 . For ppc64 or s390x arch, I don't know whether it supports guest vIOMMU. So does it support that? If supported, how to enable guest vIOMMU