1:30 a.m.
I just installed virt-v2v 0.8.3.1 on a Fedora 14 VM and was getting
ready to set up a P2V migration. But the virt-p2v-server man pages only
tell me about the GPL and that's it. Is the documentation for that
.conf file someplace else now? Or don't I need it anymore?
Thanks
- Greg Scott
5:28 a.m.
On Wed, Sep 28, 2011 at 01:30:30AM -0500, Greg Scott wrote:
I just installed virt-v2v 0.8.3.1 on a Fedora 14 VM and was getting
ready to set up a P2V migration. But the virt-p2v-server man pages only
tell me about the GPL and that's it. Is the documentation for that
.conf file someplace else now? Or don't I need it anymore?
Matt, any documentation that Greg should be looking at?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
5:32 a.m.
On 28/09/11 11:28, Richard W.M. Jones wrote:
On Wed, Sep 28, 2011 at 01:30:30AM -0500, Greg Scott wrote:
> I just installed virt-v2v 0.8.3.1 on a Fedora 14 VM and was getting
> ready to set up a P2V migration. But the virt-p2v-server man pages only
> tell me about the GPL and that's it. Is the documentation for that
> .conf file someplace else now? Or don't I need it anymore?
Matt, any documentation that Greg should be looking at?
The config file is documented in man 5 virt-v2v.conf. virt-p2v-server
*should* have a minimal man page telling you:
=head1 NAME
virt-p2v-server - Receive data from virt-p2v
=head1 DESCRIPTION
virt-p2v-server is invoked over SSH by virt-p2v. It is not intended to
be run
manually.
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat Engineering, Virtualisation Team
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
5:40 p.m.
Yes - the virt-p2v-server man page is minimal just as you said. That's
what threw me because I thought it had lots more documentation in the
earlier version. I also checked man virt-v2v.conf and this has lots of
documentation I was looking for, as you said. Thanks.
And maybe I'm making things too complicated - the last time I tried
this, I had to make up a virt-v2v.conf to run virt-p2v-server. Or
something like that. But now with the new version, looking at the
pre-built stock virt-v2v.conf, it looks like I can just try it without
building or editing a .conf file.
In my case, I want to migrate a Windows 2003 server and have it end up
in a libvirt - not RHEV - environment. This 2003 server is running
RHEV-M and I want it to become a libvirt guest in a RHEL 6.1
environment. So I have a Fedora 14 guest on the same host and I will
temporarily share the storage for the 2003 P2V between the Fedora guest
and the RHEL 6.1 host using NFS. It looks like I might have all the
pieces together to try this tonight.
And then eventually in a few months or so, I will move RHEV-M to run
directly on the RHEL 6.1 host and retire the 2003 guest.
- Greg
-----Original Message-----
From: Matthew Booth [mailto:mbooth@redhat.com]
Sent: Wednesday, September 28, 2011 5:33 AM
To: Richard W.M. Jones
Cc: Greg Scott; libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
On 28/09/11 11:28, Richard W.M. Jones wrote:
On Wed, Sep 28, 2011 at 01:30:30AM -0500, Greg Scott wrote:
> I just installed virt-v2v 0.8.3.1 on a Fedora 14 VM and was getting
> ready to set up a P2V migration. But the virt-p2v-server man pages
only
> tell me about the GPL and that's it. Is the documentation
for that
> .conf file someplace else now? Or don't I need it anymore?
Matt, any documentation that Greg should be looking at?
The config file is documented in man 5 virt-v2v.conf. virt-p2v-server
*should* have a minimal man page telling you:
=head1 NAME
virt-p2v-server - Receive data from virt-p2v
=head1 DESCRIPTION
virt-p2v-server is invoked over SSH by virt-p2v. It is not intended to
be run
manually.
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat Engineering, Virtualisation Team
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
9:20 p.m.
I spoke too soon...
I booted my Win2003 host from a virt-v2v CD, 0.8.3 I think, made a
couple weeks ago. It prompted for a hostname and root password, which I
supplied. And then a message appeared on the bottom in red, "Remote
server does not define any profiles in /etc/virt-v2v.conf"
So looking at /etc/virt-v2v.conf and studying its man page, it looks
like virt-v2v.conf does have a couple of profiles defined, some with
method RHEL, some with method libvirt. If I'm understanding how this
works, that method line defines the output of a migration. And other
profile attributes are equivalents for virt-v2v command switches. But
then it has a few <network> sections that don't look like they are part
of any profile.
So apparently that virt-v2v CD is looking for a particular profile
relevant to the host it boots from, or maybe a profile with certain
specific attributes. How do I figure out what this profile should look
like?
And then a feature request - I wonder if it would be easier all around
if the virt-p2v CD would prompt for the attributes it wants instead of
looking for a profile on the conversion host? If prompting is not
feasible, is there any guidance available or maybe some template
profiles to use when migrating with virt-p2v?
Thanks
- Greg Scott
3:43 a.m.
On 29/09/11 03:20, Greg Scott wrote:
I spoke too soon...
I booted my Win2003 host from a virt-v2v CD, 0.8.3 I think, made a
couple weeks ago. It prompted for a hostname and root password, which I
supplied. And then a message appeared on the bottom in red, "Remote
server does not define any profiles in /etc/virt-v2v.conf"
So looking at /etc/virt-v2v.conf and studying its man page, it looks
like virt-v2v.conf does have a couple of profiles defined, some with
method RHEL, some with method libvirt. If I'm understanding how this
works, that method line defines the output of a migration. And other
profile attributes are equivalents for virt-v2v command switches. But
then it has a few<network> sections that don't look like they are part
of any profile.
So apparently that virt-v2v CD is looking for a particular profile
relevant to the host it boots from, or maybe a profile with certain
specific attributes. How do I figure out what this profile should look
like?
I prefer to call these 'target profiles', because they define the target
of a conversion. That is, they define what the target is (RHEV or
libvirt), where it is, what guest storage format will be written there
and how the guest's networks will be connected there. Incidentally, the
network mappings which aren't inside a profile are global defaults. They
existed before we added profiles, and they're still useful so we haven't
deprecated them.
The example virt-v2v.conf contains 3 example profiles. However, because
they're only examples they're commented out[1], which is why the P2V
client complained about it. In fact, *everything* in the default config
file is commented out now. This is because we moved the
not-really-user-facing config to /var/lib/virt-v2v/virt-v2v.db.
In short, edit your virt-v2v.conf, copy one of the 3 example profiles
and change the specifics. The man page explains what all the attributes
mean.
And then a feature request - I wonder if it would be easier all around
if the virt-p2v CD would prompt for the attributes it wants instead of
looking for a profile on the conversion host? If prompting is not
feasible, is there any guidance available or maybe some template
profiles to use when migrating with virt-p2v?
I considered this at the time and rejected it. I wanted to keep the P2V
client as simple as possible, and centrally defined profiles seemed a
good way to achieve this. I'm not completely wedded to this decision: if
I'm convinced that definition on the client is simpler I might change
it. However, I'm not yet convinced.
Matt
[1] Incidentally this is easy to miss if, like me, you're used to syntax
highlighting. This is because the file doesn't have a .xml extension,
and vim at least won't highlight it. If you manually 'set filetype=xml'
in vim it'll switch on highlighting, and the commented sections are easy
to see. If you're an emacs user, enjoy your RSI ;)
--
Matthew Booth, RHCA, RHCSS
Red Hat Engineering, Virtualisation Team
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
10:35 a.m.
In fact, *everything* in the default config file is commented out
now.
I am a total dork! For anyone else reading this, learn from my
oversight.
I just now learned this. In XML,"<!--" (without the quotes) starts a
comment block. The comment block ends with a line that looks
like,"-->", again without the quotes. There are also apparently other
ways to do comments too. And sure enough, all the profile paragraphs in
virt-v2v.conf are bracketed with these start and end comment strings.
I'll get another P2V window starting about 7 hours from now and I'll
post the results here.
- Greg
11:42 p.m.
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 RHEL 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:14
3:in `call'
from
/usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/connection.rb:14
3: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.
- Greg
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 10:36 AM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
In fact, *everything* in the default config file is commented out
now.
I am a total dork! For anyone else reading this, learn from my
oversight.
I just now learned this. In XML,"<!--" (without the quotes) starts a
comment block. The comment block ends with a line that looks
like,"-->", again without the quotes. There are also apparently other
ways to do comments too. And sure enough, all the profile paragraphs in
virt-v2v.conf are bracketed with these start and end comment strings.
I'll get another P2V window starting about 7 hours from now and I'll
post the results here.
- Greg
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
2:11 a.m.
I might be fighting a losing P2V battle all around here. I tried using
ntbackup on the physical 2003 host to a network share, then restoring to
another libvirt VM I provisioned. After restoring, the VM won't boot.
I think the issue is the driver for the system virtual disk. The
physical host uses a Compaq Smart Array 532 Controller with a Compaq
Logical Volume SCSI disk device. I built the VM using a virtio system
drive. I also tried IDE. Neither worked. So I think I'll enable the
NIC on the physical host again and try to come up with a plan C.
- Greg Scott
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 11:43 PM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
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 RHEL 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:14
3:in `call'
from
/usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/connection.rb:14
3: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.
- Greg
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 10:36 AM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
In fact, *everything* in the default config file is commented out
now.
I am a total dork! For anyone else reading this, learn from my
oversight.
I just now learned this. In XML,"<!--" (without the quotes) starts a
comment block. The comment block ends with a line that looks
like,"-->", again without the quotes. There are also apparently other
ways to do comments too. And sure enough, all the profile paragraphs in
virt-v2v.conf are bracketed with these start and end comment strings.
I'll get another P2V window starting about 7 hours from now and I'll
post the results here.
- Greg
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
4:05 a.m.
What kind of error happened when booting?
If it is Blue Screen of Death "Stop 0x0000007B error",
following information might help you.
http://support.microsoft.com/kb/314082
I did P2V successfully from my Laptop PC (Win XP) to KVM guest
using Clonezilla Live CD with the following step (I did not use virt-p2v).
1. Before P2V, apply above registry modification to Win XP.
2. Boot Latptop PC with Clonezilla Live CD and backup it to samba file server.
3. Create KVM guest and boot it with Clonezilla Live CD and restore from samba file
server.
But I have no experience about Windows 2003 Server's P2V.
- Hisao
On 10/01/2011 04:11 PM, Greg Scott wrote:
I might be fighting a losing P2V battle all around here. I tried
using
ntbackup on the physical 2003 host to a network share, then restoring to
another libvirt VM I provisioned. After restoring, the VM won't boot.
I think the issue is the driver for the system virtual disk. The
physical host uses a Compaq Smart Array 532 Controller with a Compaq
Logical Volume SCSI disk device. I built the VM using a virtio system
drive. I also tried IDE. Neither worked. So I think I'll enable the
NIC on the physical host again and try to come up with a plan C.
- Greg Scott
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 11:43 PM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
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 RHEL 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:14
3:in `call'
from
/usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/connection.rb:14
3: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.
- Greg
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 10:36 AM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
> In fact, *everything* in the default config file is commented out now.
I am a total dork! For anyone else reading this, learn from my
oversight.
I just now learned this. In XML,"<!--" (without the quotes) starts a
comment block. The comment block ends with a line that looks
like,"-->", again without the quotes. There are also apparently other
ways to do comments too. And sure enough, all the profile paragraphs in
virt-v2v.conf are bracketed with these start and end comment strings.
I'll get another P2V window starting about 7 hours from now and I'll
post the results here.
- Greg
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
.
1:24 p.m.
What kind of error happened when booting?
I'll take a look at the KB article - thanks. In my case, the SeaBIOS
message flashes, then the window just goes black. No BSOD, just black.
At that point, all I can do is power the VM off and back on. I can boot
from the virtual CD and get into the recovery console. The recovery
console finds the Windows instance and I've tried thinks like fixmbr and
fixboot. But no joy. What if I'm wrong - what if the problem is messed
up virtual video? To test that idea, I tried pressing F8 to go into the
Windows boot menu, but the VM dies even before that point.
- Greg
11:12 p.m.
Hisao, thank you for that Microsoft article pointer. I finally had a
chance to look it over and the direction it takes makes lots of sense.
If we could come up with a way to install the virtio disk driver on the
physical Windows machine before the P2V, then the driver should load on
the migrated VM when it boots from its virtual virtio disk. This could
be major step forward. And it could work in lots of situations.
By the way, where did everyone go the past several days?
- Greg
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Hisao Taguchi
Sent: Saturday, October 01, 2011 4:06 AM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
What kind of error happened when booting?
If it is Blue Screen of Death "Stop 0x0000007B error",
following information might help you.
http://support.microsoft.com/kb/314082
I did P2V successfully from my Laptop PC (Win XP) to KVM guest
using Clonezilla Live CD with the following step (I did not use
virt-p2v).
1. Before P2V, apply above registry modification to Win XP.
2. Boot Latptop PC with Clonezilla Live CD and backup it to samba file
server.
3. Create KVM guest and boot it with Clonezilla Live CD and restore from
samba file server.
But I have no experience about Windows 2003 Server's P2V.
- Hisao
On 10/01/2011 04:11 PM, Greg Scott wrote:
I might be fighting a losing P2V battle all around here. I tried
using
ntbackup on the physical 2003 host to a network share, then restoring
to
another libvirt VM I provisioned. After restoring, the VM won't
boot.
I think the issue is the driver for the system virtual disk. The
physical host uses a Compaq Smart Array 532 Controller with a Compaq
Logical Volume SCSI disk device. I built the VM using a virtio system
drive. I also tried IDE. Neither worked. So I think I'll enable the
NIC on the physical host again and try to come up with a plan C.
- Greg Scott
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 11:43 PM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
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 RHEL 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:14
3:in `call'
from
/usr/lib/ruby/gems/1.8/gems/virt-p2v-0.8.3/lib/virt-p2v/connection.rb:14
3: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.
- Greg
-----Original Message-----
From: libguestfs-bounces(a)redhat.com
[mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Thursday, September 29, 2011 10:36 AM
To: libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Man pages for virt-p2v-server?
> In fact, *everything* in the default config file is commented out
now.
I am a total dork! For anyone else reading this, learn from my
oversight.
I just now learned this. In XML,"<!--" (without the quotes) starts a
comment block. The comment block ends with a line that looks
like,"-->", again without the quotes. There are also apparently other
ways to do comments too. And sure enough, all the profile paragraphs
in
virt-v2v.conf are bracketed with these start and end comment
strings.
I'll get another P2V window starting about 7 hours from now and I'll
post the results here.
- Greg
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
.
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
4610
days inactive
4618
days old
11 comments
4 participants
participants (4)
-
Greg Scott -
Hisao Taguchi -
Matthew Booth -
Richard W.M. Jones