[ovirt-users] Re: feature policy='require' name='md-clear'

You need some extra steps:1. Set alias: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf'2. Get the xml of the HostedEngine and save it to a file. Edit it and try either with removed or with feature policy='optional'3. Check if you have the following network:[root@ovirt1 ~]# virsh net-dumpxml vdsm-ovirtmgmt <network>   <name>vdsm-ovirtmgmt</name>   <uuid>1185a91b-533a-4bee-8a66-3208846605fa</uuid>   <forward mode='bridge'/>   <bridge name='ovirtmgmt'/> </network> If not , you can define it in a file and use virsh to import it. 4. use virsh to define and start the HostedEnginevirsh define HostedEngine.xmlvirsh start HostedEngine 5. Wait for the VM to power up and access over ssh. Do general healthcheck. 6. Leave the Engine working for several hours, so it can update the relevant data on the shared storage. 7. Power off the VM and start it via vdsm Best Regards,Strahil Nikolov В неделя, 26 януари 2020 г., 9:59:18 Гринуич-5, thomas.c.albrecht(a)lmco.com <thomas.c.albrecht(a)lmco.com&gt; написа: Tried this... had to make a new user, but "allow" isn't part of the grammar.  Tried optional, but when I did a "hosted-engine --vm-start", the configuration for the engine reverted back to the original configuration and failed. I don't think virsh is the proper way to make changes to the ovirt VMs.  I tried using vdsm-client instead, but couldn't figure out the syntax.  Any other ideas? _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/F6FR6T73OX4...