6:48 p.m.
Hi,
After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm stuck
with a migration I was expecting to be easy : RHAS3.
Here is the error log I get :
# virt-v2v -i libvirt -ic qemu+ssh://xxxx@xxxx/system -o rhev -os
xxxx:/data/vmexport -of qcow2 -oa sparse -n ovirtmgmt serv-rhas3-vm1
serv-rhas3-vm1_copy.raw: 100%
[=====================================================================================================]D
0h10m14s
virt-v2v: Pas de capability dans la configuration correspondant à os='linux'
name='virtio' distro='rhel' major='3' minor='0'
virt-v2v: Pas de capability dans la configuration correspondant à os='linux'
name='cirrus' distro='rhel' major='3' minor='0'
virt-v2v: WARNING: Le pilote d'affichage a été modifié en cirrus, mais il est
impossible d'installer le pilote cirrus. X pourrait ne pas fonctionner correctement
virt-v2v: WARNING: /boot/grub/device.map fait référence à un périphérique /dev/fd0
inconnu. Cette entrée doit être corrigée manuellement après la conversion.
virt-v2v: WARNING: /boot/grub/device.map fait référence à un périphérique /dev/sda
inconnu. Cette entrée doit être corrigée manuellement après la conversion.
sh: sh: at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 200.
at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 2321
I don't mind the warnings and I also had such errors I was able to
correct manually.
But here, the last two lines are lethal.
It seems oVirt tries to guess which OS is imported, and tries to do
specific actions, and do them bad.
Either there's a way o prevent oVirt from guessing, either there's a way
to correct the actions oVirt is failing to do...
Googling was not that helpful about this issue.
Regards.
--
Nicolas Ecarnot
8:28 p.m.
On Thu, Feb 7, 2013 at 4:48 PM, Nicolas Ecarnot wrote:
> sh: sh: at
/usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm
> line 200.
> at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line
> 2321
I don't mind the warnings and I also had such errors I was able to correct
manually.
But here, the last two lines are lethal.
It seems oVirt tries to guess which OS is imported, and tries to do specific
actions, and do them bad.
Either there's a way o prevent oVirt from guessing, either there's a way to
correct the actions oVirt is failing to do...
I think you had better to tell which version of virt-v2v and on which platform.
eg:
virt-v2v-0.8.7-7.el6_3.x86_64 on CentOS 6.3
otherwise the lines referred could not be the same as yours...
Gianluca
10:20 a.m.
Le 07/02/2013 18:28, Gianluca Cecchi a écrit :
On Thu, Feb 7, 2013 at 4:48 PM, Nicolas Ecarnot wrote:
>> sh: sh: at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm
>> line 200.
>> at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line
>> 2321
>
>
> I don't mind the warnings and I also had such errors I was able to correct
> manually.
>
> But here, the last two lines are lethal.
>
> It seems oVirt tries to guess which OS is imported, and tries to do specific
> actions, and do them bad.
> Either there's a way o prevent oVirt from guessing, either there's a way to
> correct the actions oVirt is failing to do...
I think you had better to tell which version of virt-v2v and on which platform.
eg:
virt-v2v-0.8.7-7.el6_3.x86_64 on CentOS 6.3
otherwise the lines referred could not be the same as yours...
Gianluca
Hi Gianluca,
Thank you for your answer. You are right, I have to precise the versions
implied.
- Fedora 17 64 bits
- virt-v2v.x86_64 version 0.8.8-1.fc17
- every ovirt component is of the family 3.1.0-4.fc17
I installed nothing exotic nor special. Just following the oVirt website
doc.
Do I have to debug the perl script, or is there an option I can tweak in
the virt-v2v command?
--
Nicolas Ecarnot
11:54 p.m.
On Thu, Feb 07, 2013 at 04:48:13PM +0100, Nicolas Ecarnot wrote:
Hi,
After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm
stuck with a migration I was expecting to be easy : RHAS3.
Here is the error log I get :
># virt-v2v -i libvirt -ic qemu+ssh://xxxx@xxxx/system -o rhev -os xxxx:/data/vmexport
-of qcow2 -oa sparse -n ovirtmgmt serv-rhas3-vm1
>serv-rhas3-vm1_copy.raw: 100%
[=====================================================================================================]D
0h10m14s
>virt-v2v: Pas de capability dans la configuration correspondant à os='linux'
name='virtio' distro='rhel' major='3' minor='0'
>virt-v2v: Pas de capability dans la configuration correspondant à os='linux'
name='cirrus' distro='rhel' major='3' minor='0'
>virt-v2v: WARNING: Le pilote d'affichage a été modifié en cirrus, mais il est
impossible d'installer le pilote cirrus. X pourrait ne pas fonctionner correctement
>virt-v2v: WARNING: /boot/grub/device.map fait référence à un périphérique /dev/fd0
inconnu. Cette entrée doit être corrigée manuellement après la conversion.
>virt-v2v: WARNING: /boot/grub/device.map fait référence à un périphérique /dev/sda
inconnu. Cette entrée doit être corrigée manuellement après la conversion.
>sh: sh: at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 200.
> at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 2321
I don't mind the warnings and I also had such errors I was able to
correct manually.
But here, the last two lines are lethal.
It seems oVirt tries to guess which OS is imported, and tries to do
specific actions, and do them bad.
Either there's a way o prevent oVirt from guessing, either there's a
way to correct the actions oVirt is failing to do...
Googling was not that helpful about this issue.
I'm not totally clear what "RHAS 3" is, but you're correct that
virt-v2v has to detect[1] the type of operating system in the guest in
order to determine what operations it has to perform on that guest.
It uses the configuration file /etc/virt-v2v.conf to map the guest
type into drivers that have to be installed, but some of this is also
hard-coded inside the program.
Matt (CC'd) might have some more suggestions.
Rich.
[1] You can find out what virt-v2v (actually, what libguestfs) thinks
is in your guest by doing:
virt-inspector serv-rhas3-vm1
("virt-inspector2" if this is RHEL 6).
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
1:26 p.m.
Le 08/02/2013 21:54, Richard W.M. Jones a écrit :
On Thu, Feb 07, 2013 at 04:48:13PM +0100, Nicolas Ecarnot wrote:
> Hi,
>
> After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm
> stuck with a migration I was expecting to be easy : RHAS3.
>
> Here is the error log I get :
>
>> # virt-v2v -i libvirt -ic qemu+ssh://xxxx@xxxx/system -o rhev -os
>> xxxx:/data/vmexport -of qcow2 -oa sparse -n ovirtmgmt
>> serv-rhas3-vm1 serv-rhas3-vm1_copy.raw: 100%
>>
[=====================================================================================================]D
>> 0h10m14s virt-v2v: Pas de capability dans la configuration
>> correspondant à os='linux' name='virtio' distro='rhel'
major='3'
>> minor='0' virt-v2v: Pas de capability dans la configuration
>> correspondant à os='linux' name='cirrus' distro='rhel'
major='3'
>> minor='0' virt-v2v: WARNING: Le pilote d'affichage a été modifié
>> en cirrus, mais il est impossible d'installer le pilote cirrus. X
>> pourrait ne pas fonctionner correctement virt-v2v: WARNING:
>> /boot/grub/device.map fait référence à un périphérique /dev/fd0
>> inconnu. Cette entrée doit être corrigée manuellement après la
>> conversion. virt-v2v: WARNING: /boot/grub/device.map fait
>> référence à un périphérique /dev/sda inconnu. Cette entrée doit
>> être corrigée manuellement après la conversion. sh: sh: at
>> /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm
>> line 200. at
>> /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm
>> line 2321
>
> I don't mind the warnings and I also had such errors I was able to
> correct manually.
>
> But here, the last two lines are lethal.
>
> It seems oVirt tries to guess which OS is imported, and tries to
> do specific actions, and do them bad. Either there's a way o
> prevent oVirt from guessing, either there's a way to correct the
> actions oVirt is failing to do...
>
> Googling was not that helpful about this issue.
I'm not totally clear what "RHAS 3" is, but you're correct that
virt-v2v has to detect[1] the type of operating system in the guest
in order to determine what operations it has to perform on that
guest.
RHAS stands for redhat advanced server. In our case, this is just an old
"Red Hat Enterprise Linux AS release 3 (Taroon)".
It uses the configuration file /etc/virt-v2v.conf to map the guest
type into drivers that have to be installed, but some of this is
also hard-coded inside the program.
Matt (CC'd) might have some more suggestions.
I'll be glad to hear from him.
Rich.
[1] You can find out what virt-v2v (actually, what libguestfs)
thinks is in your guest by doing:
virt-inspector serv-rhas3-vm1
("virt-inspector2" if this is RHEL 6).
I had to install libguestfs-tools.x86_64 to get virt-inspector, and it
correctly find it is a RH 3.
Am I missing some more packages for the perl scripts to work correctly?
--
Nicolas Ecarnot
2:38 p.m.
On Sat, Feb 09, 2013 at 11:26:32AM +0100, Nicolas Ecarnot wrote:
Am I missing some more packages for the perl scripts to work
correctly?
virt-v2v should depend on everything it needs, and there was no error
message indicating that anything was missing. AFAIK RHEL 3 should
work (for v2v), but we'll see what Matt says.
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://people.redhat.com/~rjones/virt-top
10:56 p.m.
Le 09/02/2013 11:26, Nicolas Ecarnot a écrit :
I had to install libguestfs-tools.x86_64 to get virt-inspector, and
it
correctly find it is a RH 3.
Am I missing some more packages for the perl scripts to work correctly?
I forgot to write that after the installation of the package mentionned
above, I still have the exact same perl error messages.
--
Nicolas Ecarnot
1:47 p.m.
Le 09/02/2013 11:26, Nicolas Ecarnot a écrit :
Le 08/02/2013 21:54, Richard W.M. Jones a écrit :
> On Thu, Feb 07, 2013 at 04:48:13PM +0100, Nicolas Ecarnot wrote:
>> Hi,
>>
>> After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm
>> stuck with a migration I was expecting to be easy : RHAS3.
>>
>> Here is the error log I get :
>>
>>> # virt-v2v -i libvirt -ic qemu+ssh://xxxx@xxxx/system -o rhev -os
>>> xxxx:/data/vmexport -of qcow2 -oa sparse -n ovirtmgmt
>>> serv-rhas3-vm1 serv-rhas3-vm1_copy.raw: 100%
>>>
[=====================================================================================================]D
>>>
>>> 0h10m14s virt-v2v: Pas de capability dans la configuration
>>> correspondant à os='linux' name='virtio'
distro='rhel' major='3'
>>> minor='0' virt-v2v: Pas de capability dans la configuration
>>> correspondant à os='linux' name='cirrus'
distro='rhel' major='3'
>>> minor='0' virt-v2v: WARNING: Le pilote d'affichage a été modifié
>>> en cirrus, mais il est impossible d'installer le pilote cirrus. X
>>> pourrait ne pas fonctionner correctement virt-v2v: WARNING:
>>> /boot/grub/device.map fait référence à un périphérique /dev/fd0
>>> inconnu. Cette entrée doit être corrigée manuellement après la
>>> conversion. virt-v2v: WARNING: /boot/grub/device.map fait
>>> référence à un périphérique /dev/sda inconnu. Cette entrée doit
>>> être corrigée manuellement après la conversion. sh: sh: at
>>> /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm
>>> line 200. at
>>> /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm
>>> line 2321
>>
>> I don't mind the warnings and I also had such errors I was able to
>> correct manually.
>>
>> But here, the last two lines are lethal.
>>
>> It seems oVirt tries to guess which OS is imported, and tries to
>> do specific actions, and do them bad. Either there's a way o
>> prevent oVirt from guessing, either there's a way to correct the
>> actions oVirt is failing to do...
>>
>> Googling was not that helpful about this issue.
>
> I'm not totally clear what "RHAS 3" is, but you're correct that
> virt-v2v has to detect[1] the type of operating system in the guest
> in order to determine what operations it has to perform on that
> guest.
RHAS stands for redhat advanced server. In our case, this is just an old
"Red Hat Enterprise Linux AS release 3 (Taroon)".
>
> It uses the configuration file /etc/virt-v2v.conf to map the guest
> type into drivers that have to be installed, but some of this is
> also hard-coded inside the program.
>
> Matt (CC'd) might have some more suggestions.
I'll be glad to hear from him.
>
> Rich.
>
> [1] You can find out what virt-v2v (actually, what libguestfs)
> thinks is in your guest by doing:
>
> virt-inspector serv-rhas3-vm1
>
> ("virt-inspector2" if this is RHEL 6).
I had to install libguestfs-tools.x86_64 to get virt-inspector, and it
correctly find it is a RH 3.
Am I missing some more packages for the perl scripts to work correctly?
This issue looks very similar to what is discussed here:
https://bugzilla.redhat.com/show_bug.cgi?id=816930
--
Nicolas Ecarnot
4:32 p.m.
Le 11/02/2013 11:47, Nicolas Ecarnot a écrit :
This issue looks very similar to what is discussed here:
https://bugzilla.redhat.com/show_bug.cgi?id=816930
I'm so sorry to debug that issue in a so crappy manner, but I have to
keep going.
I just commented out "_configure_boot($kernel, $virtio, $g, $root,
$desc);" in Redhat.pm and it ran with no error.
I'd be very glad to hear from Matt...
--
Nicolas Ecarnot
5:07 p.m.
On Fri, 2013-02-08 at 20:54 +0000, Richard W.M. Jones wrote:
On Thu, Feb 07, 2013 at 04:48:13PM +0100, Nicolas Ecarnot wrote:
> Hi,
>
> After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm
> stuck with a migration I was expecting to be easy : RHAS3.
>
> Here is the error log I get :
>
> ># virt-v2v -i libvirt -ic qemu+ssh://xxxx@xxxx/system -o rhev -os
xxxx:/data/vmexport -of qcow2 -oa sparse -n ovirtmgmt serv-rhas3-vm1
> >serv-rhas3-vm1_copy.raw: 100%
[=====================================================================================================]D
0h10m14s
> >virt-v2v: Pas de capability dans la configuration correspondant à
os='linux' name='virtio' distro='rhel' major='3'
minor='0'
> >virt-v2v: Pas de capability dans la configuration correspondant à
os='linux' name='cirrus' distro='rhel' major='3'
minor='0'
> >virt-v2v: WARNING: Le pilote d'affichage a été modifié en cirrus, mais il
est impossible d'installer le pilote cirrus. X pourrait ne pas fonctionner
correctement
> >virt-v2v: WARNING: /boot/grub/device.map fait référence à un périphérique
/dev/fd0 inconnu. Cette entrée doit être corrigée manuellement après la conversion.
> >virt-v2v: WARNING: /boot/grub/device.map fait référence à un périphérique
/dev/sda inconnu. Cette entrée doit être corrigée manuellement après la conversion.
> >sh: sh: at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line
200.
> > at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 2321
I'd need to know exactly which version of virt-v2v you're running in
order to diagnose the above. I think the unknown fd0 was fixed a while
back, though. Are you running the latest available version?
Matt
6:18 p.m.
On Mon, Feb 11, 2013 at 3:07 PM, Matthew Booth wrote:
I'd need to know exactly which version of virt-v2v you're
running in
at the beginning of this same thread, after I asked the same thing, on
Feb 8th Nicolas wrote:
- Fedora 17 64 bits
- virt-v2v.x86_64 version 0.8.8-1.fc17
- every ovirt component is of the family 3.1.0-4.fc17
I presume it remained the same
5:51 a.m.
Matthew Booth <mbooth@...> writes:
I'd need to know exactly which version of virt-v2v you're running in
order to diagnose the above. I think the unknown fd0 was fixed a while
back, though. Are you running the latest available version?
Matt
FWIW, I've wasted hours on this one too, and just commented out the line
above.
I'm running a completely clean install on a Fedora 19 server, and the client
is running Fedora 20 that I'm trying to v2v from KVM to oVirt.
As a side note, It'd be nice, especially in the case that there might be some
ignored, and other fatal errors, that errors that live on a "die" line also
state "DIE" or "FATAL ERROR" in the output they give to the console.
3933
days inactive
4305
days old
11 comments
5 participants
participants (5)
-
david -
Gianluca Cecchi -
Matthew Booth -
Nicolas Ecarnot -
Richard W.M. Jones