Well, if I've run from kvm hypervisor this command with a live guest:                                                        
                                                                                                   
virt-filesystems --long -h --all -a /home/storage-plus/myvm.qcow2                               
                                                                                                   
It outputs:                                                                                        
`libguestfs: error: list_filesystems: parted exited with status 1: Error: Can't have a partition outside the disk!`
                                                                                                       
But the very very sad of the story is that guest filesystem crashes:                                                          
 
ene 05 21:23:22 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 25652400          
ene 05 21:23:22 myvm.example.com kernel: XFS (dm-0): writeback error on sector 20430000                        
ene 05 21:23:22 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 25651200                
ene 05 21:23:22 myvm.example.com kernel: XFS (dm-0): writeback error on sector 20428800                      
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 44519951                            
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 44519951                
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 5222401
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 5231568
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 5232232        
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 5237584
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 5262240
ene 05 21:23:27 myvm.example.com kernel: blk_update_request: I/O error, dev vda, sector 5379440
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): metadata I/O error in "xlog_iodone" at daddr 0x257a20f len 64 error 5
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): xfs_do_force_shutdown(0x2) called from line 1238 of file fs/xfs/xfs_log.c.  Return address = ffffffffc028a840
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): Log I/O Error Detected.  Shutting down filesystem
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): Please umount the filesystem and rectify the problem(s)
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.
ene 05 21:23:27 myvm.example.com kernel: XFS (dm-0): xfs_iunlink_remove: xfs_imap_to_bp returned error -5.
ene 05 21:23:27 myvm.example.com auditd[633]: Audit daemon is suspending logging due to previously mentioned write error
ene 05 21:23:27 myvm.example.com systemd[1]: rsyslog.service: main process exited, code=killed, status=7/BUS
ene 05 21:23:27 myvm.example.com systemd[1]: Unit rsyslog.service entered failed state.
ene 05 21:23:27 myvm.example.com systemd[1]: rsyslog.service failed.
ene 05 21:23:27 myvm.example.com systemd[1]: rsyslog.service holdoff time over, scheduling restart

So did I miss something? Or is it a bug?

Software versions are:

Guest OS: CentOS Linux release 7.8.2003 (Core)
Hypervisor OS: CentOS Linux release 7.5.1804 (Core)
with:
- qemu-kvm-1.5.3-175.el7_9.1.x86_64
- libguestfs-tools-c-1.40.2-10.el7.x86_64

Thanks in advance!
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org