11:31 a.m.
--_000_9BE6F493F83A594DA60C45E6A09DC5AC01764B1DAUSP01DAG0201co_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I am still struggling with virt v2v to try to import a .ova file into my ov=
irt domain.
I have a fedora 18 manager and fedora 18 node. I installed virt-v2v on the=
manager using yum. Based on what I google, when you issue the command vir=
t-v2v -list-profiles you probably should not get:
[root@ovirtmgr home]# virt-v2v --list-profiles
Defined target profiles:
(nothing).
I see several profiles listed in the /etc/virt-v2v.conf file, they don't se=
em to be recognized even if I -f /etc/virt-v2v.conf in my commands as well.=
If I go ahead and blindly attempt to import it anyway, I get an error li=
ke this:
[root@ovirtmgr home]# virt-v2v -i ova -osd 10.3.2.150:/opt/export --network=
ovirtmgmt ws08-srv-3.ova
virt-v2v: Failed to connect to qemu:///system: libvirt error code: 38, mess=
age: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such f=
ile or directory
there is no libvirt on the manager whatsoever, so im not sure where to go o=
r even what direction im facing here.
Can someone straighten me out and get me back on the right path ?
Thanks,
jonathan
________________________________
This is a PRIVATE message. If you are not the intended recipient, please de=
lete without copying and kindly advise us by e-mail of the mistake in deliv=
ery. NOTE: Regardless of content, this e-mail shall not operate to bind SKO=
POS to any order or other contract unless pursuant to explicit written agre=
ement or government initiative expressly permitting the use of e-mail for s=
uch purpose.
--_000_9BE6F493F83A594DA60C45E6A09DC5AC01764B1DAUSP01DAG0201co_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<style <!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-- </style
</head <body lang=3D"EN-US"
link=3D"blue" vlink=3D"purple" <div
class=3D"WordSection1" <p
class=3D"MsoNormal">I am still struggling with virt v2v to try to import=
a .ova file into my ovirt domain.</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">I have a fedora 18 manager and fedora 18
node. =
I installed virt-v2v on the manager using yum. Based on what I googl=
e, when you issue the command virt-v2v –list-profiles you probably sh=
ould not get:</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">[root@ovirtmgr home]# virt-v2v --list-profiles</p <p class=3D"MsoNormal">Defined target
profiles:</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">(nothing).</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">I see several profiles listed in the /etc/virt-v2v.c=
onf file, they don’t seem to be recognized even if I –f /etc/vi=
rt-v2v.conf in my commands as well. If I go ahead and blindly a=
ttempt to import it anyway, I get an error like this:</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">[root@ovirtmgr home]# virt-v2v -i ova -osd 10.3.2.15=
0:/opt/export --network ovirtmgmt ws08-srv-3.ova
</p <p class=3D"MsoNormal">virt-v2v: Failed to
connect to qemu:///system: libvi=
rt error code: 38, message: Failed to connect socket to '/var/run/libvirt/l=
ibvirt-sock': No such file or directory</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">there is no libvirt on the manager whatsoever, so im=
not sure where to go or even what direction im facing here.</p <p class=3D"MsoNormal"> </p <p class=3D"MsoNormal">Can someone straighten
me out and get me back on the=
right path ?</p <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal">Thanks,</p <p
class=3D"MsoNormal">jonathan</p
</div <br
<hr <font color=3D"Gray"
face=3D"Arial" size=3D"1">This is a PRIVATE message. I=
f you are not the intended recipient, please delete without copying and kin=
dly advise us by e-mail of the mistake in delivery. NOTE: Regardless of con=
tent, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit wri=
tten agreement or government initiative expressly permitting the use of e-m=
ail for such purpose.</font </body </html
--_000_9BE6F493F83A594DA60C45E6A09DC5AC01764B1DAUSP01DAG0201co_--
3:06 a.m.
Le 19/02/2013 17:31, Jonathan Horne a écrit :
[root@ovirtmgr home]# virt-v2v -i ova -osd 10.3.2.150:/opt/export
--network ovirtmgmt ws08-srv-3.ova
virt-v2v: Failed to connect to qemu:///system: libvirt error code: 38,
message: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No
such file or directory
Hi Jonathan,
According to my very recent experience, your issue seems related to the
following points I'm reading in the virt-v2v help :
-o method
Specifies the output method. Supported output methods are:
libvirt
Create a libvirt guest. *-os* must specify a libvirt storage
pool for the libvirt output method.
Also see the *-oc* option.
rhev
Create a guest on a RHEV 'Export' storage domain, which can
later be imported into RHEV using the UI. *-os* must specify the
location of a RHEV export storage domain for the RHEV output
method.
If no output type is specified, it defaults to libvirt.
-oc URI
Specifies the libvirt connection to use to create the converted
guest. If omitted, this defaults to qemu:///system when virt-v2v
runs as root, or qemu:///session when virt-v2v runs as a regular
user.
If I understand it well, you don't specify any output method (-o option)
so it defaults to libvirt output storage.
And you don't specify any libvirt connection, and you're running it as
root, so it defaults to qemu:///system and fails.
My recent successful migrations with virt-v2v were made without
specifying "-oc" option, but with telling "-o rhev".
HTH.
--
Nicolas Ecarnot
4324
days inactive
4325
days old
1 comments
2 participants
participants (2)
-
Jonathan Horne -
Nicolas Ecarnot