oVirt Testing



  • oVirt Testing hub.

    It's looking like a true Hyper-V replacement.

    When I get more server hardware, I'm going to redo it with GlusterFS and three hosts.

    0_1513381749355_Screenshot from 2017-12-15 15-44-51.png

    I'm doing some cpu stress testing on a Win10 VM. Not really effecting the host. The host is a Dell R420.

    0_1513382157038_Screenshot from 2017-12-15 15-49-50.png



  • Great job testing @Tim_G

    I'll try to do the same this weekend so we can compare notes.

    FYI: oVirt is a 1st class citizen within the vProtect Storware backup world.



  • Did you install on CentOS?



  • @fateknollogee said in oVirt Testing:

    Did you install on CentOS?

    Pretty sure that he mentioned CentOS 7 in a post.



  • I'm excited about how this is looking. Certainly could be a huge deal for moving Hyper-V to the back seat.



  • @scottalanmiller said in oVirt Testing:

    I'm excited about how this is looking. Certainly could be a huge deal for moving Hyper-V to the back seat.

    Not to thread jack, but maybe we can have a standardized format/layout when we do this types of testing
    @Tim_G I like the title

    Hardware:
    Networking:
    Management:
    BackUp:

    Something that makes it easy for us to use it as reference material.

    Sorry @Tim_G feel free to re-start this if my idea is any good



  • @fateknollogee said in oVirt Testing:

    Did you install on CentOS?

    Yes I installed manually with the latest release of CentOS NetInstall ISO, I think 1708.

    I selected the Hypervisor install on the left, and checked a few related ones on the right such as NFS client.

    I am using an NFS4 share on the hypervisor for testing everything. Only had one server so my options were limited. Gonna try to get 2 more for a real production-like test.



  • @tim_g said in oVirt Testing:

    I selected the Hypervisor install on the left, and checked a few related ones on the right such as NFS client.

    I'm not even sure you need to do that, as the oVirt stuff you install to make it an oVirt node probably installs that stuff anyways. Gonna try just a straight minimal install on the next node.



  • I tried using the "oVirt Node" ISO install, but didn't work. I think that was my fault due to not precreating a DNS record.

    I liked doing it manually more anyways.



  • @scottalanmiller said in oVirt Testing:

    I'm excited about how this is looking. Certainly could be a huge deal for moving Hyper-V to the back seat.

    It's immediately more useful than just Hyper-V.

    It's like having SCVMM but on a more reliable platform. At least it feels that way so far, but I haven't pushed it like I have with Hyper-V so I guess I can give it the benefit of the doubt for now.

    I've done quite a bit with SCVMM so I know what I'm talking about. I'm not saying SCVMM is bad... but it's not free.

    I've yet to test the full HA capabilities in oVirt using local storage. I assume it will go well and as expected because its glusterfs.

    Yeah, I'm going to push it hard in a production-like environment.



  • More i look at these the more I want to play with KVM..... Job for Monday sort my one spare server out lol



  • @tim_g

    How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?



  • @emad-r said in oVirt Testing:

    @tim_g

    How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?

    It's easy to set up.

    It requires FQDNs, so if you don't have a DNS server, the entry needs to be in the /etc/hosts file prior to setup for the oVirtEngine.

    It is not Beta anything. oVirt has been around for a very long time. The interface and everything is production ready.



  • @tim_g said in oVirt Testing:

    @emad-r said in oVirt Testing:

    @tim_g

    How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?

    It's easy to set up.

    It requires FQDNs, so if you don't have a DNS server, the entry needs to be in the /etc/hosts file prior to setup for the oVirtEngine.

    It is not Beta anything. oVirt has been around for a very long time. The interface and everything is production ready.

    I see, i meant this when I meant BETA:
    https://ovirt.org/
    https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/



  • @emad-r said in oVirt Testing:

    @tim_g said in oVirt Testing:

    @emad-r said in oVirt Testing:

    @tim_g

    How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?

    It's easy to set up.

    It requires FQDNs, so if you don't have a DNS server, the entry needs to be in the /etc/hosts file prior to setup for the oVirtEngine.

    It is not Beta anything. oVirt has been around for a very long time. The interface and everything is production ready.

    I see, i meant this when I meant BETA:
    https://ovirt.org/
    https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/

    No I'm using 4.1.



  • I’m curious to see how it works. It was slow (compared to bare KVM) the last time I tried it.



  • @stacksofplates said in oVirt Testing:

    I’m curious to see how it works. It was slow (compared to bare KVM) the last time I tried it.

    I haven't noticed any difference on VMs versus HyperV or straight KVM.

    But I've a lot more testing to do, so we'll see. I'll keep that in mind.



  • As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.



  • @tim_g said in oVirt Testing:

    @stacksofplates said in oVirt Testing:

    I’m curious to see how it works. It was slow (compared to bare KVM) the last time I tried it.

    I haven't noticed any difference on VMs versus HyperV or straight KVM.

    But I've a lot more testing to do, so we'll see. I'll keep that in mind.

    It wasn’t VM performance, it was things like cloning and provisioning.



  • @jaredbusch said in oVirt Testing:

    As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.

    You'll be required to have dual nics.



  • @dustinb3403 said in oVirt Testing:

    @jaredbusch said in oVirt Testing:

    As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.

    You'll be required to have dual nics.

    I'm only using one NIC. I know it works because that test VM in my screenshot was installed via PXE (WDS server)



  • @tim_g said in oVirt Testing:

    @dustinb3403 said in oVirt Testing:

    @jaredbusch said in oVirt Testing:

    As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.

    You'll be required to have dual nics.

    I'm only using one NIC. I know it works because that test VM in my screenshot was installed via PXE (WDS server)

    Does it? It must be me getting something messed up then . .



  • I'm testing oVirt 4.2 beta on a CentOS 7.4, running on an x3300m4 a lot of CPU and ram...what can I say, it's much more complex and much less useful than the standard cli-based toolstack. I've spent almost 8 hours trying make everything works. Now I cannot upload any ISO to the ISO domain, so I can only import templates from the default OpenStack Glance repo, and some of them are broken... or, maybe is the cloud-init implementation?
    I hope they will fix it in the stable 4.2. The interface is nice, but for now I stick with plain KVM.



  • @francesco-provino said in oVirt Testing:

    I'm testing oVirt 4.2 beta on a CentOS 7.4, running on an x3300m4 a lot of CPU and ram...what can I say, it's much more complex and much less useful than the standard cli-based toolstack. I've spent almost 8 hours trying make everything works. Now I cannot upload any ISO to the ISO domain, so I can only import templates from the default OpenStack Glance repo, and some of them are broken... or, maybe is the cloud-init implementation?
    I hope they will fix it in the stable 4.2. The interface is nice, but for now I stick with plain KVM.

    That's odd.

    Maybe it's a 4.2 beta issue.

    I got mine up and running within 10 minutes of installing CentOS.

    1. Install CentOS from net install.
    2. Set up storage and DNS.
    3. Install oVirt packages from repository.
    4. Run oVirtEngine install script.

    It was really quick and simple.

    What did they change in 4.2 to make it so bad?



  • @tim_g the interface is much nicer. But, I cannot upload the ISO in the datastore in ANY way. I haven't control over my virsh anymore. To get the CentOS accepted I had to downgrade the cluster level and re-up it after, other that disable completely firewalld and change the cluster default firewalld/iptables config.



  • Other than that, the virtual console of the VMs is accesible only with a VNC/spice client, when Cockpit get it right with integrated console.

    Maybe there is much of unknowed to me in oVirt, but I find it really a mess compared to KVM.



  • I get an auth error when trying to use virsh... even entering the root or oVirt admin credentials does not help.



  • @francesco-provino said in oVirt Testing:

    I get an auth error when trying to use virsh... even entering the root or oVirt admin credentials does not help.

    Of course this is a feature and not a bug, because vsdm holds the daemon... but I hate it. It makes all my libvirt knowledge useless.



  • The same is true for SCVMM. You don't install and use SCVMM for a small environment where you only have one hypervisor. It just over complicates things and actually makes simple tasks take longer.

    This isn't how you use something like SCVMM or oVIrt.

    If you have a single server, just have a couple VMs you want to run on it, and have KVM management skills... I think oVirt may not be the best thing.

    If you have multiple servers, need high-availability, will be going through Virtual Machines, need integrated backups, one-touch migrations and checkpoints, templates, virtual networks, and everything else... then yes, oVirt is for you.

    oVirt is a virtualization management platform. It requires at least 2 servers (or one if doing self-hosted) just to run it. You wouldn't do this just for a single hypervisor.



  • @francesco-provino said in oVirt Testing:

    Other than that, the virtual console of the VMs is accesible only with a VNC/spice client, when Cockpit get it right with integrated console.

    Maybe there is much of unknowed to me in oVirt, but I find it really a mess compared to KVM.

    You can use remote-viewer, VNC, whatever software you want to access VMs.

    And even more, in the oVirt web interface (HTML5), you can simply right-click on a VM and click console. You can use spice/vnc/RD from there. Doing the spice options opens up remote-viewer anyways.

    You have the same access options as you do with just straight KVM... I'm not sure what you mean here.


Log in to reply