Hi Richard, I included -v and -x, and have attached the output below. Thanks, Eoghan Eoghan O'Hara | Data Scientist | *Kx* | +353 858398926 | eohara at kx.com | Pronounced "oh-an" On Sat, 20 Mar 2021 at 12:13, Richard W.M. Jones <rjones at redhat.com> wrote:> On Fri, Mar 19, 2021 at 09:49:58AM +0000, Eoghan O'Hara wrote: > > Hi, > > > > I am currently unable to run virt-v2v. See output below: > > > > $ export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 > > $ sudo virt-v2v -i ova /home/path/kx-platform-vm-20210318-123942/ > > kx-platform-vm-20210318-123942.ova -o libvirt -of qcow2 -os Appliances -n > > default > > Unfortunately these environment variables don't get passed through > sudo. > > You will have to run virt-v2v with the additional options ?-v -x? > in order to see what's really going on. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > Fedora Windows cross-compiler. Compile Windows programs, test, and > build Windows installers. Over 100 libraries supported. > http://fedoraproject.org/wiki/MinGW > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libguestfs/attachments/20210322/5248e186/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: virt.out Type: application/octet-stream Size: 1295104 bytes Desc: not available URL: <http://listman.redhat.com/archives/libguestfs/attachments/20210322/5248e186/attachment.obj>
On Mon, Mar 22, 2021 at 10:11:08AM +0000, Eoghan O'Hara wrote:> Hi Richard, > > I included -v and -x, and have attached the output below.The reason is when we create the output, the target device is not writable, apparently it's a read-only filesystem: [ 65.4] Copying disk 1/1 to /datassd/3/libvirt/Appliances/kx-platform-vm-20210318-123942-sda (qcow2) ... libguestfs: trace: disk_create "/datassd/3/libvirt/Appliances/kx-platform-vm-20210318-123942-sda" "qcow2" 262144000000 "preallocation:sparse" "compat:1.1" libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libguestfs: command: run: \ -o preallocation=off,compat=1.1 libguestfs: command: run: \ /datassd/3/libvirt/Appliances/kx-platform-vm-20210318-123942-sda libguestfs: command: run: \ 262144000000 qemu-img: /datassd/3/libvirt/Appliances/kx-platform-vm-20210318-123942-sda: Could not create file: Read-only file system You're using ?-o libvirt -os Appliances? which means it's trying to use a libvirt storage pool called ?Appliances?, which presumably is mapped to /datassd/3/libvirt/Appliances in your case. You can find out about libvirt storage pools here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-managing_guest_virtual_machines_with_virsh-storage_pool_commands#section-virsh-pool-info Might be best to use ?-o local -os /some/writable/directory? and then you will end up with a libvirt XML file and the raw disks, and you can choose what to do with them. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html