[ovirt-users] Please don't remove instance type
Hi all, We are happy oVirt users for some years now (we started with 3.6, now on 4.2) and we manage most of our virtualization stacks with it. To provision and manage our machines, we use the foreman (for bare metal and virtual machines) on top of it. I made some little contributions to the foreman and other underlying stuff to have a deeper integration with oVirt, like to be able to select instance type directly from foreman interface/api and we rely on it. We use instance types to standardize our vms by defining system resources (memory, cpu and cpu topology) console type, boot options. On top of that we plan to use templates to apply OS (CentOS 7 and CentOS 6 actually). Having resources definitions separated from OS installation help us to keep instance types and templates lists small and don't bother users about some technical underlying stuff. As we are interested in automating oVirt maintenance tasks and configuration with ansible, I asked at FOSDEM oVirt booth if there is any ansible module to manage instance types in Ovirt as I didn't find it in ovirt ansible infra repo. The person to whom I asked the question said that you are planning to remove instance types from ovirt, and this make me sad :(. So here I am to ask why do you plan to remove instance types from oVirt. As far as I know, it's fairly common to have "instance types" / "flavors" / "sizes" on one side and then templates (bare OS, preinstalled appliances...) on other side and pick one of each to make an instance. If this first part is missing in future version of ovirt, it will be a pain point for us. So, my question is, do you really plan to remove instances type definitely ? Cheers. -- Baptiste ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TJAXYBMSIAAAYLAYCSLOTONY54WT7K3O/
[ovirt-users] Re: routing/firewalling problems (was: oVirt can't communicate with vSphere)
No. As I said, ICMP is routed through correctly without any issue. The routing is correct, and the machine at 1.13 is definitely forwarding requests correctly. I've tested from another machine on my LAN, same setup except not running Centos/ovirt and it's got no problem with communication. Telnet from 1.195 never leaves the node, and never hits 1.13. I can successfully hit the 10.0.0.0/8 network from any other machine on my network. I reinstalled the cluster (for various reasons) yesterday, using the ovirt-node installer, and same issue. I dunno if I'm just derping out, but I can't see where it's being blocked. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XLCSJZPQ6T3OTJEXD3X3S6UEQGEJDS6H/
[ovirt-users] rebooting an ovirt cluster
How is an oVirt hyperconverged cluster supposed to come back to life after a power outage to all 3 nodes? Running ovirt-node (ovirt-node-ng-installer-4.2.0-2019013006.el7.iso) to get things going, but I've run into multiple issues. 1. During the gluster setup, the volume sizes I specify, are not reflected in the deployment configuration. The auto-populated values are used every time. I manually hacked on the config to get the volume sizes correct. I also noticed if I create the deployment config with "sdb" by accident, but click back and change it to "vdb", again, the changes are not reflected in the config. My deployment config does seem to work. All volumes are created (though the xfs options used don't make sense as you end up with stripe sizes that aren't a multiple of the block size). Once gluster is deployed, I deploy the hosted engine, and everything works. 2. Reboot all nodes. I was testing for power outage response. All nodes come up, but glusterd is not running (seems to have failed for some reason). I can manually restart glusterd on all nodes and it comes up and starts communicating normally. However, the engine does not come online. So I figure out where it last lived, and try to start it manually through the web interface. This fails because vdsm-ovirtmgmt is not up. I figured out the correct way to start up the engine would be through the cli via hosted-engine --vm-start. This does work, but it takes a very long time, and it usually starts up on any node other than the one I told it to start on. So I guess two (or three) questions. What is the expected operation after a full cluster reboot (ie: in the event of a power failure)? Why doesn't the engine start automatically, and what might be causing glusterd to fail, when it can be restarted manually and works fine? -- _ Fact: 1. Ninjas are mammals. 2. Ninjas fight ALL the time. 3. The purpose of the ninja is to flip out and kill people. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIADNRZRXTPTRG4XBFUMNWASBWRFCG4V/
[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC
Thanks, that sort of helped. I've ran yum update a dozen times and not till this morning was there a kernel update... lol I'm able to startup the VM, but when it loads the ISO to install Windows 10 which I downloaded from Microsoft, Attached is what always happens. Perhaps my ISO is corrupt? On Sat, Feb 2, 2019 at 4:39 AM Dominik Holler wrote: > On Fri, 1 Feb 2019 17:37:30 -0500 > Darin Schmidt wrote: > > > [root@ovirt ~]# rpm -qa kernel > > kernel-3.10.0-957.1.3.el7.x86_64 > > kernel-3.10.0-862.el7.x86_64 > > [root@ovirt ~]# uname -a > > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 > > https://bugzilla.redhat.com/1638835 looks like there is at least > kernel 3.10.0-957.3.1.el7.x86_64 required. > Can you please check if upgrading to kernel solves the issue for you? > I expectect at least kernel 3.10.0-957.5.1 to be availible. > > > x86_64 x86_64 x86_64 GNU/Linux > > [root@ovirt ~]# rpm -qa qemu-kvm-ev > > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 > > [root@ovirt ~]# rpm -qa libvirt > > libvirt-4.5.0-10.el7_6.3.x86_64 > > > here is the vdsm > > > > contains: > Hyper-V SynIC is not supported by kernel > > > > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler > > wrote: > > > > > On Fri, 1 Feb 2019 11:48:51 -0500 > > > Darin Schmidt wrote: > > > > > > > I have successfully setup a centos vm, its up and running. Now I > > > > need to setup a windows 10 VM and I cant seem to get anything to > > > > work. > > > > > > > > Ive tried setting the OS type to other or Windows 10 64bit. With > > > > Windows 64bit, it fails to startup at all When I select > > > > OtherOS it will allow me to start to run the Windows ISO, but > > > > then fails after a few seconds as well. Is there something I'm > > > > not correctly configuring? > > > > > > Would you please share vdsm.log, and the output of > > > rpm -qa kernel > > > uname -a > > > rpm -qa qemu-kvm-ev > > > rpm -qa libvirt > > > from of the host, and the relevant part of engine.log? > > > > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BYIZ36LEPVD5FAD77L7FSDBHN2TZD4SD/
[ovirt-users] Re: upgrade bug
On Sat, 2 Feb 2019 12:53:13 +0200 ada per wrote: > Thank you for your reply :). > > I don't think is the network filters, i have also created a new OVN > network to check but still the vm dont boot-up on the hosts that have > been upgraded. > Can you please share the vdsm.log from a host after a failed start? > > On Fri, 1 Feb 2019, 21:56 Dominik Holler > > On Fri, 1 Feb 2019 15:31:18 +0200 > > ada per wrote: > > > > > After upgrading my hosts from 4.2.7.1 to 4.2.8 the external > > > networks stopped working! > > > When im starting a VM using external network it does not boot up > > > at all! > > > > > > The error message is: > > > "VM is down with error. Exit message: unsupported configuration: > > > filterref is not supported for network interfaces with virtualport > > > type openvswitch" > > > > > > > Can you please ensure that the vNIC profiles of the external network > > has no network filter? > > Please find details in https://bugzilla.redhat.com/1502754 . > > The default setting for new created OVN networks should be > > "No Network Filter", but there might be old networks which still > > have an network filter. > > > > > I rolled it back to 4.2.7.1 for 1 of my hosts just as a test and > > > the VMs on that host can now bootup using external networks as > > > they are supposed to!! > > > > > > Please advice as i would like to use the upgrade!!! > > > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6ABM4GU7RXXCOTEBRJAUBTTH44LPLQAA/
[ovirt-users] Re: upgrade bug
Thank you for your reply :). I don't think is the network filters, i have also created a new OVN network to check but still the vm dont boot-up on the hosts that have been upgraded. On Fri, 1 Feb 2019, 21:56 Dominik Holler On Fri, 1 Feb 2019 15:31:18 +0200 > ada per wrote: > > > After upgrading my hosts from 4.2.7.1 to 4.2.8 the external networks > > stopped working! > > When im starting a VM using external network it does not boot up at > > all! > > > > The error message is: > > "VM is down with error. Exit message: unsupported configuration: > > filterref is not supported for network interfaces with virtualport > > type openvswitch" > > > > Can you please ensure that the vNIC profiles of the external network > has no network filter? > Please find details in https://bugzilla.redhat.com/1502754 . > The default setting for new created OVN networks should be > "No Network Filter", but there might be old networks which still have > an network filter. > > > I rolled it back to 4.2.7.1 for 1 of my hosts just as a test and the > > VMs on that host can now bootup using external networks as they are > > supposed to!! > > > > Please advice as i would like to use the upgrade!!! > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SC6CTLXSOWYVYFUVKOQJ4UTG3S3XYIKY/
[ovirt-users] Re: Windows 10 - Ovirt 4.3 - EPYC
On Fri, 1 Feb 2019 17:37:30 -0500 Darin Schmidt wrote: > [root@ovirt ~]# rpm -qa kernel > kernel-3.10.0-957.1.3.el7.x86_64 > kernel-3.10.0-862.el7.x86_64 > [root@ovirt ~]# uname -a > Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 https://bugzilla.redhat.com/1638835 looks like there is at least kernel 3.10.0-957.3.1.el7.x86_64 required. Can you please check if upgrading to kernel solves the issue for you? I expectect at least kernel 3.10.0-957.5.1 to be availible. > x86_64 x86_64 x86_64 GNU/Linux > [root@ovirt ~]# rpm -qa qemu-kvm-ev > qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 > [root@ovirt ~]# rpm -qa libvirt > libvirt-4.5.0-10.el7_6.3.x86_64 > here is the vdsm > contains: Hyper-V SynIC is not supported by kernel > On Fri, Feb 1, 2019 at 3:05 PM Dominik Holler > wrote: > > > On Fri, 1 Feb 2019 11:48:51 -0500 > > Darin Schmidt wrote: > > > > > I have successfully setup a centos vm, its up and running. Now I > > > need to setup a windows 10 VM and I cant seem to get anything to > > > work. > > > > > > Ive tried setting the OS type to other or Windows 10 64bit. With > > > Windows 64bit, it fails to startup at all When I select > > > OtherOS it will allow me to start to run the Windows ISO, but > > > then fails after a few seconds as well. Is there something I'm > > > not correctly configuring? > > > > Would you please share vdsm.log, and the output of > > rpm -qa kernel > > uname -a > > rpm -qa qemu-kvm-ev > > rpm -qa libvirt > > from of the host, and the relevant part of engine.log? > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/347EX63KJMGRSURH5B2QOW5AANDKTPMG/
