testing ovirt 4.4 as single node VM inside 4.3
I'm having problems importing OVA exports from vmware 4, into ovirt 4.3 I've read that basically, this is a known issue and that ovirt 4.4 improves the import situation greatly. But I'd like to be able to prove it helps us, before comitting to large undertakings. Is it going to be doable to run a single node ovirt cluster as a VM inside another one? Or do I need to run it on bare metal? -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown@medata.com| www.medata.com
On Fri, Jul 31, 2020 at 5:37 PM Philip Brown <pbrown@medata.com> wrote:
I'm having problems importing OVA exports from vmware 4, into ovirt 4.3
So do you mean an OVA created in vSphere and to be used then in oVirt? What kind of problems? Too generic... You can also select Compute --> Virtual Machines Select the 3 dots at top right and choose "Import" Between the available sources you can choose VMware where you have to specify vcenter server and related ESXi credentials, load virtual machine list as sources and decide which ones to import into oVirt. This though requires network communication availability between vSphere and oVirt I'have used it with success in the past, eg to import a WIndows 2008 R2 VM with a production Oracle database from vSphere 5.5. to oVirt 4.2 (about two years ago).
I've read that basically, this is a known issue and that ovirt 4.4 improves the import situation greatly.
Perhaps, not tested. But I'd like to be able to prove it helps us, before comitting to large
undertakings.
Understandable
Is it going to be doable to run a single node ovirt cluster as a VM inside another one? Or do I need to run it on bare metal?
Can you elaborate better? How do this relate with the previous point?
Gianluca
well, this was related to my thread here a day or two ago, about "where are the error logs for import?" I give more details there. The resulting logs are of no use. ovirt 4.3 fails on direct import from Vsphere. and it fails on importing a manually exported OVA file from vsphere. With no feedback as to where the failure is caused. Therefore, I have concluded my only option is to try out 4.4 somehow. Which is difficult since I dont have centos 8 running on bare metal anywhere. ----- Original Message ----- From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Philip Brown" <pbrown@medata.com> Cc: "users" <users@ovirt.org> Sent: Friday, July 31, 2020 9:13:12 AM Subject: Re: [ovirt-users] testing ovirt 4.4 as single node VM inside 4.3 On Fri, Jul 31, 2020 at 5:37 PM Philip Brown <pbrown@medata.com> wrote:
I'm having problems importing OVA exports from vmware 4, into ovirt 4.3
So do you mean an OVA created in vSphere and to be used then in oVirt? What kind of problems? Too generic... ...
On Fri, Jul 31, 2020 at 8:09 PM Philip Brown <pbrown@medata.com> wrote:
well, this was related to my thread here a day or two ago, about "where are the error logs for import?" I give more details there.
The resulting logs are of no use. ovirt 4.3 fails on direct import from Vsphere. and it fails on importing a manually exported OVA file from vsphere. With no feedback as to where the failure is caused.
Steven, do we know about any issue in 4.3 with importing ovas?
Therefore, I have concluded my only option is to try out 4.4 somehow.
This is a good idea, you will not get any fixes in 4.3 at this point. We usually support only the latest version.
Which is difficult since I dont have centos 8 running on bare metal anywhere.
Nested VM should work, we use this internally for development. But you will not get the best performance this way. Nir
----- Original Message ----- From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Philip Brown" <pbrown@medata.com> Cc: "users" <users@ovirt.org> Sent: Friday, July 31, 2020 9:13:12 AM Subject: Re: [ovirt-users] testing ovirt 4.4 as single node VM inside 4.3
On Fri, Jul 31, 2020 at 5:37 PM Philip Brown <pbrown@medata.com> wrote:
I'm having problems importing OVA exports from vmware 4, into ovirt 4.3
So do you mean an OVA created in vSphere and to be used then in oVirt? What kind of problems? Too generic... ... _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UK73PEGJ3TK2TA...
Hi Nir, performance is not really an issue here, we're most interested in functional testing and migration support. That's where nesting 4.4 on top of 4.3 would be a crucial migration enabler, especially since you don't support a 7/8 or 4.3/4.4 mix that much elsewhere. Currently my tests reveal, that ovirt/ovirt nesting does not work at all, oVirt on KVM is the only case useds/tested by Redhat internally. The other issue is that OVA exports on oVirt fail silently, which is about the worst to happen. I get full sized OVA files full of zeros that obviously won't work imported (without errors, btw). And for lack of 4.4. nested on 4.3 I couldn't even tell if the export domains already deprecated on 4.3 would work at all on 4.4, which would be the only other alternative to migrate VMs. Please, please, please, if you can make OVA export/import, export domains and even nested oVirt working, I'd kiss your feet (wearing my Corona mask, of course ;-)
participants (4)
-
Gianluca Cecchi -
Nir Soffer -
Philip Brown -
thomas＠hoberg.net