[ovirt-users] Re: where is error log for OVA import

2020-07-31 Thread Philip Brown
good news and bad news and more good news on my OVA import front. Devs are especially encouraged to read to the end :) Initial good news is, I managed to successfully upgrade ONE of my "node"s in my 4.3 cluster to 4.4.1 The bad news is: doing the exact same thing as before; copying the .OVA

[ovirt-users] Re: OVA export creates empty and unusable images

2020-07-31 Thread Gianluca Cecchi
On Sat, Aug 1, 2020 at 12:36 AM wrote: > Wow, it seems a good find for a potential reason! > Yes, but did you check the files at the path I gave you? > > Did you get a chance to test the OVA export/import cycle? > > Right now. Environment with oVirt 4.3.10. I have a CentOS 8 VM with a 20Gb

[ovirt-users] Re: OVA export creates empty and unusable images

2020-07-31 Thread thomas
Wow, it seems a good find for a potential reason! I'd totally subscribe to the cause, if it only affected my Atom HCI clusters, who have had timing issues so bad, even the initial 3 node HCI setup had to be run on a 5 GHz Kaby Lake to succeed, because my J5005 Atoms evidently were too slow.

[ovirt-users] Re: testing ovirt 4.4 as single node VM inside 4.3

2020-07-31 Thread thomas
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

[ovirt-users] Re: testing ovirt 4.4 as single node VM inside 4.3

2020-07-31 Thread Nir Soffer
On Fri, Jul 31, 2020 at 8:09 PM Philip Brown 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

[ovirt-users] Re: Changing FQDN

2020-07-31 Thread Alex K
On Fri, Jul 31, 2020, 21:00 Alex K wrote: > > > On Fri, Jul 31, 2020, 18:26 Dominik Holler wrote: > >> >> >> On Fri, Jul 31, 2020 at 4:00 PM Alex K wrote: >> >>> >>> >>> On Fri, Jul 31, 2020 at 4:50 PM Dominik Holler >>> wrote: >>> On Fri, Jul 31, 2020 at 2:44 PM Alex K wrote:

[ovirt-users] Re: testing ovirt 4.4 as single node VM inside 4.3

2020-07-31 Thread Philip Brown
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

[ovirt-users] Re: testing ovirt 4.4 as single node VM inside 4.3

2020-07-31 Thread Gianluca Cecchi
On Fri, Jul 31, 2020 at 5:37 PM Philip Brown 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

[ovirt-users] testing ovirt 4.4 as single node VM inside 4.3

2020-07-31 Thread Philip Brown
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

[ovirt-users] Re: oVirt 4.4.1 HCI single server deployment failed nested-kvm

2020-07-31 Thread thomas
Just looking at the release notes, using anything 'older' in the case of 4.4 seems very rough going... Testing 4.4 was actually how I got into the nesting domain this time around, because I didn't have physical hardware left for another HCI cluster. Testing of oVirt 4.4 on top of oVirt 4.3

[ovirt-users] Re: oVirt 4.4.1 HCI single server deployment failed nested-kvm

2020-07-31 Thread thomas
That's exactly the point: Running oVirt on top of a vanilla KVM seems to be the only case supported, because the Redhat engineers use that themselves for development, testing and demoing. Running virtual machines nested inside an oVirt VM via KVM also works per se, as HostedEngineLocal during

[ovirt-users] Re: 4.4.x - VLAN-based logical network can't attach to bonds?

2020-07-31 Thread Dominik Holler
On Fri, Jul 31, 2020 at 12:54 AM Mark R wrote: > Following up, as noted in the bug report ( > https://bugzilla.redhat.com/show_bug.cgi?id=1860479 ) this doesn't appear > to be oVirt / VDSM having issues. You can replicate the same inability to > attach a bond to a bridge by simply booting the

[ovirt-users] Re: Changing FQDN

2020-07-31 Thread Dominik Holler
On Fri, Jul 31, 2020 at 2:44 PM Alex K wrote: > Hi all, > > I am running ovirt 4.2.8 > I did change ovirt engine FQDN using ovirt-engine-rename tool following > > >

[ovirt-users] Changing FQDN

2020-07-31 Thread Alex K
Hi all, I am running ovirt 4.2.8 I did change ovirt engine FQDN using ovirt-engine-rename tool following https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/chap-Utilities#Updating_SSL_Certificates Hosts FQDN is also changed and all seem fine apart

[ovirt-users] Re: Guest VM snapshots are not retained when importing data storage domain

2020-07-31 Thread Alex K
On Fri, Jul 31, 2020 at 12:30 PM Strahil Nikolov wrote: > Theoretically, all the data for the snapshot is both in the Engine's DB > and on storage (OVF file). > > I was afraid to migrate from 4.3 to 4.4 , as I was planning to wipe > the engine and just import the VMs..., but I was not

[ovirt-users] Re: Guest VM snapshots are not retained when importing data storage domain

2020-07-31 Thread Strahil Nikolov via Users
Theoretically, all the data for the snapshot is both in the Engine's DB and on storage (OVF file). I was afraid to migrate from 4.3 to 4.4 , as I was planning to wipe the engine and just import the VMs..., but I was not sure about the snapshots. Most probably this is a bug.

[ovirt-users] Re: Guest VM snapshots are not retained when importing data storage domain

2020-07-31 Thread Alex K
Has anyone been able to import a storage domain and still have access to VM snapshots or this might be a missing feature/bug that needs to be reported? Reading the redhat docs about the storage domain import it seems there is no mention of VM snapshots if they should be accessible following the