- Users - oVirt List Archives

DATA Domain with 1GB limit
by mohamedbehbity＠gmail.com 06 Dec '18

06 Dec '18

Once the attached the domain to a data center, the real size of the DAT domain is displayed as 1 GB

1 0

Hypconverged Gluster Setup hangs after TLS/SSL
by matthias.barmeier＠sourcepark.de 06 Dec '18

06 Dec '18

Hi, tried to setup hyperconverged with glusterfs. I used three i7 with two 1TB Disks and two NICs. Everythin worked fine till: [ INFO ] TASK [Set Engine public key as authorized key without validating the TLS/SSL certificates] appears in the wizards window. Does anyone has a hint on what to do?

2 1

vGPU
by 董青龙 06 Dec '18

06 Dec '18

Hi all, I am testing vGPU in ovirt4.2. I have a nvidia p100 GPU installed in the host and I have installed the correct dirver. I followed this page(https://www.ovirt.org/documentation/install-guide/appe-Preparing_a_Hos… but I failed. In the "Host Devices tab" I got an device called "GP100GL [Tesla P100 PCIe 16GB]". I could not find any device of "mdev type". Anyone can help me? Thanks a lot!

1 0

Centos7.6
by Demeter Tibor 06 Dec '18

06 Dec '18

Dear All, I just wondering I would like to make an upgrade from 4.2.5 to latest stable release of ovirt. Meanwhile centos7.6 was released. Will that compatible with the current release of ovirt? How is safe an upgrade now? Thanks in advance, Regards, Tibor

4 5

[ANN] oVirt 4.3.0 Second Alpha Release is now available for testing
by Sandro Bonazzola 06 Dec '18

06 Dec '18

The oVirt Project is pleased to announce the availability of the Second Alpha Release of oVirt 4.3.0, as of December 6th, 2018 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the second alpha release of the 4.3.0 version. This release brings more than 80 enhancements and more than 330 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * Tech preview for oVirt on Fedora 28 * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * LLDP Labeler * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Node NG is already available for both CentOS 7 - oVirt Node NG for Fedora 28 (tech preview) is facing build issues on Jenkins and will be released as soon as possible Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Re: start vm without engine
by Michal Skrivanek 06 Dec '18

06 Dec '18

> On 6 Dec 2018, at 12:30, David David <dd432690(a)gmail.com> wrote: > > > > On 29 May 2018, at 16:08, David David <dd432690(a)gmail.com <mailto:dd432690@gmail.com>> wrote: > > > > > > hi. > > > > > > How to start VM directly in hypervisor? ovirt-engine was crashed. > > > that is not supported yet > > > > > > > VM's id is known. > > > > > > vdsclient VM, hasn't argumets for starting vm. > > > Hello again > > > it does, but you need to connect storage and then supply the whole VM configuration which is not simple to do. > > Ok. How to do this ? > > I have access to FC storage, where VM placed you can use the persisted libvirt definition on host where it was running last if the host just crashed (it’s removed on clean guest shutdown though). If you have it you can connect the appropriate storage domain using vdsm-client, and then start the VM using that libvirt definition. again, it’s not very easy to do. In all other cases it would have to be generated by the engine again as the OVF_STORE OVF backup is an OVF and you need libvirt’s XML so you would have to convert it first anyway, so again nothing simple to do. In disaster recovery scenrio you can just take the whole storage domain and import it into the new clean engine installation and you’ll get all the VMs it depends what you really want to do Thanks, michal > > вт, 29 мая 2018 г. в 18:53, Michal Skrivanek <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>>: > > > > On 29 May 2018, at 16:08, David David <dd432690(a)gmail.com <mailto:dd432690@gmail.com>> wrote: > > > > hi. > > > > How to start VM directly in hypervisor? ovirt-engine was crashed. > > that is not supported yet > > > > > VM's id is known. > > > > vdsclient VM, hasn't argumets for starting vm. > > it does, but you need to connect storage and then supply the whole VM configuration which is not simple to do. > > > > > Thanks. > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > > To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> > > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SDTALWD2CHOEE… <https://lists.ovirt.org/archives/list/users@ovirt.org/message/SDTALWD2CHOEE…> >

1 0

Cloud-init reset network configuration to default dhcp after reboot and regular run
by Mike Lykov 06 Dec '18

06 Dec '18

Hi All! I'm trying to configure network in VMs created from template, and see strange behaviour from cloud-init. cloud-init installed and enabled in template. ver cloud-init-0.7.9-24.el7.centos.1.x86_64 guest Centos 7.5 ovirt 4.2.7 from ovirt-releases-42-pre repo 1. I use "run once" with initial run - use cloud-init - networks in-guest net iface : eth0 add new - static enter address, mask, gw ipv6 none Run (once) and cloud-init configure ifcfg-eth0 for that address (successfully). 2. I shutdown that VM and use "Run" (regular) without "use cloud init" in VM properties, awaiting that above configurations are saved (and booted with it). But because "use cloud init" not checked, and cloud-init service enabled, it start, cannot find datasource and drop configuration to default (dhcp). In cloud-init.log 2018-11-20 13:53:24,153 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2018-11-20 13:53:24,153 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 236, in main_init init.fetch(existing=existing) File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 343, in fetch return self._get_data_source(existing=existing) File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 253, in _get_data_source pkg_list, self.reporter) File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 320, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: (DataSourceNoCloudNet) 2018-11-20 13:53:24,194 - stages.py[DEBUG]: applying net config names for {'version': 1, 'config': [{'subnets': [{'type': 'dhcp'}], 'type': 'physical', 'name': 'eth0', 'mac_address': '56:6f:21:4a:00:04'}]} It reverts config as in here https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NE27UO4WNZIC27… 3. then I found bug https://bugzilla.redhat.com/show_bug.cgi?id=1439373#c5 and when "run once" I disable network config as in that comment. Shutdown, Run (not once) and voila! Ip address are static! 2018-11-20 15:07:31,601 - handlers.py[DEBUG]: finish: init-network/search-NoCloudNet: SUCCESS: no network data found from DataSource NoCloudNet ..... 2018-11-20 15:07:31,602 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2018-11-20 15:07:31,602 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! 2018-11-20 15:07:31,639 - stages.py[DEBUG]: network config disabled by system_cfg 2018-11-20 15:07:31,639 - stages.py[INFO]: network config is disabled by system_cfg 2018-11-20 15:07:31,639 - main.py[DEBUG]: [net] Exiting without datasource in local mode 2018-11-20 15:07:31,640 - util.py[DEBUG]: Reading from /proc/uptime (quiet=False) 2018-11-20 15:07:31,640 - util.py[DEBUG]: Read 12 bytes from /proc/uptime 2018-11-20 15:07:31,640 - util.py[DEBUG]: cloud-init mode 'init' took 0.287 seconds (0.29) 2018-11-20 15:07:31,640 - handlers.py[DEBUG]: finish: init-network: SUCCESS: searching for network datasources "cloud-init used to use a "marker" file that it created on initial execution. If that "marker" file existed it would not rerun on reboot. " - are it not working in ovirt/this cloud-init version ? -- Mike

2 8

Additional routes on Interface
by Sandro Emma 06 Dec '18

06 Dec '18

Hi, we are running a RHV 4.1 installation which is working fine except one issue: We have a Network which is only used for fencing(power Management via ilo), each host has an interface with this network and a custom ip, for this to work we need a few custom routes. At the moment we add the new routes via a plain route file under /etc/sysconfig/network-scripts/, but the engine flags this interface then as out-of-sync. How can we persist those changes across reboots and still be able to add new devices via the UI ? This looked promising but isnt working: https://ovirt.org/develop/release-management/features/network/networkreload… Thanks for any Help :)

2 2

Repository ovirt-4.2 is listed more than once in the configuration
by Markus Frei 06 Dec '18

06 Dec '18

Hello everybody I am frequently receiving the following messages from ovirt: Repository ovirt-4.2-epel is listed more than once in the configuration Repository ovirt-4.2-centos-gluster312 is listed more than once in the configuration Repository ovirt-4.2-virtio-win-latest is listed more than once in the configuration Repository ovirt-4.2-centos-qemu-ev is listed more than once in the configuration Repository ovirt-4.2-centos-opstools is listed more than once in the configuration Repository centos-sclo-rh-release is listed more than once in the configuration Repository ovirt-4.2-centos-ovirt42 is listed more than once in the configuration Repository ovirt-4.2 is listed more than once in the configuration I`ve got following repos configured in directory /etc/yum.repos.d: ovirt-4.2-dependencies.repo ovirt-4.2-pre-dependencies.repo ovirt-4.2-pre.repo ovirt-4.2.repo I deleted the 'pre' repos several times but apparently they are being recreated somehow. Can anybody explain this behaviour please and eventually the meaning of these 'pre' repos in generell as well? Thank you in advance. Kind regards, Chris

2 1

Help - "No Default Route show in Ovirt Engine"
by aru_barani＠yahoo.com 05 Dec '18

05 Dec '18

After create data center,cluster try install the host in ovirt engine it show the error "Hosts has no Default Route" but both the Engine and Ovirt node ping. At same time try Register Ovirt Node to Ovirt engine It shows "Please provide valid oVirt engine fully qualified domain name (FQDN) and port (443 by default)" but i am use hpervisor.eipl.com with port 443

2 1