I just checked the versions on the conversion server: [root@Fedora16-64P2V ~]# rpm -qa | grep libguestfs python-libguestfs-1.14.2-1.fc16.x86_64 libguestfs-tools-c-1.14.2-1.fc16.x86_64 libguestfs-tools-1.14.2-1.fc16.x86_64 libguestfs-1.14.2-1.fc16.x86_64 [root@Fedora16-64P2V ~]# [root@Fedora16-64P2V ~]# [root@Fedora16-64P2V ~]# rpm -qa | grep v2v virt-v2v-0.8.5-1.fc16.x86_64 [root@Fedora16-64P2V ~]# As it turns out, that source physical machine was upgraded in place from Windows 2000 several years ago. We've also had problems using the approach with ntbackup and restore. So tonight we're trying with Acronis Universal Restore. - Greg -----Original Message----- From: Richard W.M. Jones [mailto:rjones@redhat.com] Sent: Wednesday, January 04, 2012 6:42 AM To: Greg Scott Cc: libguestfs@redhat.com; Matthew Booth; Joey Bertalan; Fredy Hernández Subject: Re: [Libguestfs] Another virt-p2v blew up On Mon, Dec 26, 2011 at 06:30:14PM -0600, Greg Scott wrote:
I may have an idea why this one blew up. This source machine apparently does not have a c:\windows directory. Instead, Windows is loaded into c:\Winnt.
Looks like the p2v error was "guestfsd: error: windows: no file or directory found with this name" I wonder if it was looking for c:\Windows and instead found c:\Winnt?
Which version of virt-v2v and libguestfs is this? libguestfs should detect \winnt as the %systemroot%. You can check by doing: virt-inspector2 Guest | grep -i systemroot Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v