All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Anushree Mathur <anushree.mathur@linux.ibm.com>,
	Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, farosas@suse.de
Subject: Re: virsh migrate fails when --copy-storage-all option is given!
Date: Wed, 28 May 2025 11:34:35 -0400	[thread overview]
Message-ID: <aDctC8i7U2J5bmyw@x1.local> (raw)
In-Reply-To: <31711771-7caa-4ea3-b763-45db6930e28e@linux.ibm.com>

Copy Kevin.

On Wed, May 28, 2025 at 07:21:12PM +0530, Anushree Mathur wrote:
> Hi all,
> 
> 
> When I am trying to migrate the guest from host1 to host2 with the command
> line as follows:
> 
> date;virsh migrate --live --domain guest1 qemu+ssh://dest/system --verbose
> --undefinesource --persistent --auto-converge --postcopy
> --copy-storage-all;date
> 
> and it fails with the following error message-
> 
> error: internal error: unable to execute QEMU command 'block-export-add':
> Block node is read-only
> 
> HOST ENV:
> 
> qemu : QEMU emulator version 9.2.2
> libvirt : libvirtd (libvirt) 11.1.0
> Seen with upstream qemu also
> 
> Steps to reproduce:
> 1) Start the guest1
> 2) Migrate it with the command as
> 
> date;virsh migrate --live --domain guest1 qemu+ssh://dest/system --verbose
> --undefinesource --persistent --auto-converge --postcopy
> --copy-storage-all;date
> 
> 3) It fails as follows:
> error: internal error: unable to execute QEMU command 'block-export-add':
> Block node is read-only
> 
> Things I analyzed-
> 1) This issue is not happening if I give --unsafe option in the virsh
> migrate command
> 
> 2) O/P of qemu-monitor command also shows ro as false
> 
> virsh qemu-monitor-command guest1 --pretty --cmd '{ "execute": "query-block"
> }'
> {
>   "return": [
>     {
>       "io-status": "ok",
>       "device": "",
>       "locked": false,
>       "removable": false,
>       "inserted": {
>         "iops_rd": 0,
>         "detect_zeroes": "off",
>         "image": {
>           "virtual-size": 21474836480,
>           "filename": "/home/Anu/guest_anu.qcow2",
>           "cluster-size": 65536,
>           "format": "qcow2",
>           "actual-size": 5226561536,
>           "format-specific": {
>             "type": "qcow2",
>             "data": {
>               "compat": "1.1",
>               "compression-type": "zlib",
>               "lazy-refcounts": false,
>               "refcount-bits": 16,
>               "corrupt": false,
>               "extended-l2": false
>             }
>           },
>           "dirty-flag": false
>         },
>         "iops_wr": 0,
>         "ro": false,
>         "node-name": "libvirt-1-format",
>         "backing_file_depth": 0,
>         "drv": "qcow2",
>         "iops": 0,
>         "bps_wr": 0,
>         "write_threshold": 0,
>         "encrypted": false,
>         "bps": 0,
>         "bps_rd": 0,
>         "cache": {
>           "no-flush": false,
>           "direct": false,
>           "writeback": true
>         },
>         "file": "/home/Anu/guest_anu.qcow2"
>       },
>       "qdev": "/machine/peripheral/virtio-disk0/virtio-backend",
>       "type": "unknown"
>     }
>   ],
>   "id": "libvirt-26"
> }
> 
> 
> 3) Guest doesn't have any readonly
> 
> virsh dumpxml guest1 | grep readonly
> 
> 4) Tried giving the proper permissions also
> 
> -rwxrwxrwx. 1 qemu qemu 4.9G Apr 28 15:06 guest_anu.qcow2
> 
> 5) Checked for the permission of the pool also that is also proper!
> 
> 6) Found 1 older bug similar to this, pasting the link for reference:
> 
> 
> https://patchwork.kernel.org/project/qemu-devel/patch/20170811164854.GG4162@localhost.localdomain/
> 
> 
> 
> Thanks,
> Anushree-Mathur
> 
> 

-- 
Peter Xu



  reply	other threads:[~2025-05-28 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 13:51 virsh migrate fails when --copy-storage-all option is given! Anushree Mathur
2025-05-28 15:34 ` Peter Xu [this message]
2025-06-04 12:41   ` Kevin Wolf
2025-06-04 13:27     ` Peter Krempa
2025-06-23 17:55       ` Anushree Mathur
2025-06-23 20:28         ` Peter Krempa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aDctC8i7U2J5bmyw@x1.local \
    --to=peterx@redhat.com \
    --cc=anushree.mathur@linux.ibm.com \
    --cc=farosas@suse.de \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.