[fedora-virt] Restored Windows Server 2003 VM goes black

[Greg Scott]

The virt-p2v blew up with an error and never made it to a conversion.  I posted the details in the libguestfs mailing list last week.  I'll paste in below, fixing a typo I just noticed:

- Greg


******************************************************

My use case might be atypical, or maybe bleeding edge.  The system I want to P2V is about 30 miles away and I am accessing it using a KVM over IP switch.  I have a Virt-P2V CD in its CD drive and I can boot from that CD by playing with the BIOS boot order using the KVM over IP.  It's a little tricky but works.  And it has to be this way because I can only do this during off-hours.  

The physical host is a Windows 2003 server.  The conversion P2V server is a Fedora 14 guest VM running under Libvirt in a RHEL 6.1 host.  On the conversion server, I mounted an NFS mount from the RHEL 6.1 host onto /var/lib/libvirt/images, its (F14 VM) default libvirt storage pool.  The idea was, put the converted disk images there and then wrap a guest VM around them from the RHEL 6.1 host.

The first time tonight, I uncommented the "libvirt" paragraph in virt-v2v.conf on the conversion server.  I booted the 2003 host from the p2V CD.  And waited for a cursor to finally show up over that KVM over IP.  I selected the "libvirt" profile, gave the converted VM 1 CPU and 1024 MB of RAM and clicked the "convert" button.  It immediately failed, complaining that "default" is not a valid storage pool.  My hunch is, this is probably because I set up an NFS mount on top of it.  

So I went into virt-manager on my Fedora 14 VM and set up another storage pool named "MigrateVM" and pointed it to /var/lib/libvirt/images/MigrateVM.  Then I modified virt-v2v.conf and copied and pasted the "libvirt" paragraph.  I modified it to look like below:

  <profile name="mmmh-migrate">
    <method>libvirt</method>
    <storage>MigrateVM</storage>
    <network type="default">
      <network type="network" name="default"/>
    </network>
  </profile>

Then I rebooted the 2003 host from the virt-p2v CD.  I logged in to the conversion server, selected the profile named "mmmh-migrate", 1024 MB of RAM and 1 CPU. When I clicked "convert", see below:

Virt-p2v has shutdown unexpectedly.  You may:

* Try running it again
* Debug virt-p2v
* Power the machine off

I suppose a definition of insanity is trying the same thing again and expecting different results - but I tried again anyway and got the same results.  This time I chose debug and it mentioned a saved file named virt-p2v.log.  So I copied it and am pasting its contents below.  

(eval): line 75
   Gtk-WARNING **:Could not find the icon 'gtk-dialog-warning'. The 'hicolor' theme was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases
/dev/cciss!c0d0: No such file or directory /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:138:in `Integer': invalid value for Integer: ""
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:138:in `disk'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:72:in `convert'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:178:in `call'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:178:in `iterate'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:74:in `convert'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:174:in `call'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/converter.rb:174:in `iterate'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/connection.rb:143:in `call'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/connection.rb:143:in `metadata'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:44:in `call'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:44:in `main_with_queue'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:43:in `each'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:43:in `main_with_queue'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:42:in `synchronize'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:42:in `main_with_queue'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:50:in `call'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:50:in `main'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/gtk-queue.rb:50:in `main_with_queue'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/ui/main.rb:49:in `main_loop'
	 from /usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/bin/virt-p2v:56
	 from /usr/bin/virt-p2v:19:in `load'
	 from /usr/bin/virt-p2v:19

The obvious question - why not forget about NFS and just carve out "local" storage on an F14 VM and run the conversion that way?  And then copy the converted disk images where they need to go on the RHEL host.  I can do that if necessary, but sheesh, what a waste.  That 2003 server uses about 80 GB and I'd like to give the converted VM about 100 GB or so, so it has plenty of room.  But if this turns out to be the answer, I guess I may as well just do the migration by building a target 2003 VM and using ntbackup to backup the physical and restore to the virtual.