search for: vmxf

...rwxrwx 1 root root 128446464 Jun 24 20:19 WinXPPro-s010.vmdk -rwxrwxrwx 1 root root 857 Jun 25 15:54 WinXPPro.vmdk -rwxrwxrwx 1 root root 0 Jun 24 20:12 WinXPPro.vmsd -rwxrwxrwx 1 root root 4208 Jun 25 21:20 WinXPPro.vmx -rwxrwxrwx 1 root root 2932 Jun 25 15:57 WinXPPro.vmxf -rwxrwxrwx 1 root root 876 Jun 25 21:28 WinXPPro.xml $ virsh start WinXPPro error: Failed to start domain WinXPPro error: internal error process exited while connecting to monitor: qemu-system-i386: -drive file=/var/lib/libvirt/images/WinXPPro/WinXPPro.vmdk,if=none,id=drive-ide0-0-0,format=...

...inXPPro-s010.vmdk -rw----r-x 1 libvirt-qemu kvm 857 Jun 25 15:54 WinXPPro.vmdk -rw-r--r-x 1 libvirt-qemu kvm 0 Jun 24 20:12 WinXPPro.vmsd -rwxr-xr-x 1 libvirt-qemu kvm 4209 Jun 25 15:56 WinXPPro.vmx -rw-r--r-x 1 libvirt-qemu kvm 2932 Jun 25 15:57 WinXPPro.vmxf -rw-rw-r-x 1 libvirt-qemu kvm 852 Jun 25 16:05 WinXPPro.xml $ virsh start WinXPPro error: Failed to start domain WinXPPro error: internal error process exited while connecting to monitor: qemu-system-i386: -drive file=/home/roland/WinXPPro/WinXPPro.vmdk,if=none,id=drive-ide0-0-0,format=...

...tm/vmware/CentOS\ 64-bit\ LSI/ -rw------- 1 silentm silentm 8684 Aug 13 08:31 CentOS 64-bit LSI.nvram -rw-r--r-- 1 silentm silentm 0 Feb 27 2017 CentOS 64-bit LSI.vmsd -rwxr-xr-x 1 silentm silentm 2735 Aug 13 08:31 CentOS 64-bit LSI.vmx -rw-r--r-- 1 silentm silentm 272 Feb 27 2017 CentOS 64-bit LSI.vmxf -rw-r--r-- 1 silentm silentm 32796639232 Nov 17 08:34 CentOS 7-64bit LSI.vmdk -rw-r--r-- 1 silentm silentm 107382571008 Aug 13 09:05 CentOS 7.vhdx -rw-r--r-- 1 silentm silentm 323155 Aug 5 08:39 vmware-0.log -rw-r--r-- 1 silentm silentm 323085 Jun 30 14:14 vmware-1.log -rw-r--r-- 1 silentm silentm...

...ions(-) diff --git a/docs/virt-v2v-input-vmware.pod b/docs/virt-v2v-input-vmware.pod index 11adf1b6..ec905376 100644 --- a/docs/virt-v2v-input-vmware.pod +++ b/docs/virt-v2v-input-vmware.pod @@ -107,18 +107,6 @@ If you find a folder of files called F<I<guest>.vmx>, F<I<guest>.vmxf>, F<I<guest>.nvram> and one or more F<.vmdk> disk images, then you can use this method. -=head2 VMX: Remove VMware tools from Windows guests - -For Windows guests, you should remove VMware tools before conversion. -Although this is not strictly necessary, and the guest will...

...003/.Windows Server 2003.vmsd.aDUdvI": No such file or directory (2) rsync: failed to set times on "/mnt/backup/Windows Server 2003/.Windows Server 2003.vmx.QrHjyj": No such file or directory (2) rsync: failed to set times on "/mnt/backup/Windows Server 2003/.Windows Server 2003.vmxf.cmPnGU": No such file or directory (2) rsync: failed to set times on "/mnt/backup/Windows Server 2003/.vmware-0.log.a4uyXv": No such file or directory (2) rsync: failed to set times on "/mnt/backup/Windows Server 2003/.vmware-1.log.cSvQf8": No such file or directory (2) rsy...

...other host before clicking OK. - vmware try to make its own file locking for flowing file type : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051 VMNAME.vswp DISKNAME-flat.vmdk DISKNAME-ITERATION-delta.vmdk VMNAME.vmx VMNAME.vmxf vmware.log Is there a way to deal with this problem ? is that a bug ? thanks for your support, best regards Philippe Simonet

A colleague found some VMX files which omit the deviceType field. This allows -i vmx mode to parse them. Rich.

https://bugzilla.redhat.com/show_bug.cgi?id=1441197

Dear community, I have a 2-node gluster cluster with one replicated volume shared to a client via NFS. If the replication link (Ethernet crossover cable) between the Gluster nodes breaks, I discovered that my whole storage is not available anymore. I am using Pacemaker/corosync with two virtual IPs (service IPs exposed to the clients), so each node has its corresponding virtual IP, and

...you +are able to mount the NFS storage directly. + +=item 2. + +You have enabled SSH access to the VMware ESXi hypervisor and there is +a C</vmfs/volumes> folder containing the virtual machines. + +=back If you find a folder of files called F<I<guest>.vmx>, F<I<guest>.vmxf>, F<I<guest>.nvram> and one or more F<.vmdk> disk @@ -1375,28 +1412,50 @@ With other methods, virt-v2v tries to prevent concurrent access, but because the I<-i vmx> method works directly against the storage, checking for concurrent access is not possible. -=head2 VMX:...

Do we have enormous fragmentation here on our X4500 with Solaris 10, ZFS Version 10? What except zfs send/receive can be done to free the fragmented space? One ZFS was used for some month to store some large disk images (each 50GByte large) which are copied there with rsync. This ZFS then reports 6.39TByte usage with zfs list and only 2TByte usage with du. The other ZFS was used for similar

The first patch was previously posted here: https://www.redhat.com/archives/libguestfs/2017-December/msg00018.html That patch hasn't changed except that I made the ‘input_transport’ variable type-safe. The second patch adds a significant new mode for liberating data from VMware: the ability to copy VMs over SSH directly from ESXi hypervisors. Although this requires enabling SSH access (a

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.

This patch is incomplete, but early feedback would be welcome. Rich.