Hold on a second - I never see the guest itself. I only see the source physical machine. We boot the source system from the virt-p2v-image-builder CD and then fire up a migration. The P2V runs for about 3+ hours. Watching RHEV-M, I see the physical space used in the Export store ramp up. And then later, it's back down to < 1 GB and there is no guest virtual disk or VM or anything. The P2V apparently blows up with the error below and then cleans up all traces of itself, at least in the RHEV export domain. So I don't have any virtual disk to inspect.
But c'mon - every Windows system in the world has the directories mentioned below. This cannot be the first P2V attempt on the planet earth from a Windows system to RHEV. As a workaround - maybe we can put in a custom edit to GuestfsHandle.pm, maybe there's a newer version somewhere, maybe there's something procedurally we can do differently. I don't have virtio-win on this Fedora conversion server. Does that have anything to do with the problem? Could the bug be that it reports the error below when the real problem is, firstboot can't find a disk to boot from because it doesn't have the right drivers? And if so, where do I find a virtio-win RPM that will install on Fedora 14? - Greg -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Greg Scott Sent: Friday, November 18, 2011 3:06 PM To: Richard W.M. Jones Cc: Fredy Hernández; [email protected] Subject: Re: [Libguestfs] Virtio-win RPM? Of course the guest has those directories. It's a Windows system. I tried the link to that bug but it just times out. What's the workaround? - Greg -----Original Message----- From: Richard W.M. Jones [mailto:[email protected]] Sent: Friday, November 18, 2011 11:03 AM To: Greg Scott Cc: [email protected]; Fredy Hernández Subject: Re: [Libguestfs] Virtio-win RPM? On Fri, Nov 18, 2011 at 09:16:15AM -0600, Greg Scott wrote: > Does anyone have an idea what this error message means? This was waiting on > the console this morning after running a conversion last night using the > virt-p2v CD 0.8.3.1: > > > > Inspect_os: cannot resolve Windows %SYSTEMROOT% at > /usr/share/perl5/sys/VirtConvert/GuestfsHandle.pm line 187, <> line 7. It's a bug in libguestfs: http://git.annexia.org/?p=libguestfs.git;a=blob;f=src/inspect_fs_windows.c;h=270b7616f5f5ae457c1db7926047660bf8fc0151;hb=HEAD#l147 Does this guest have one of these directories: \windows \winnt \win32 \win and that directory: ...\system32 ...\system32\config ...\system32\cmd.exe ? You could also try running virt-inspector on the guest ('virt-inspector2' on RHEL 6). Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
