First ,
you need to set an alias for virsh like this one:
alias virsh='virsh -c
qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf'
Next,
you need to check with virsh if the HostedEngine VM is available (as you need it's
config). If not , you can check the vdsm.log for the full XML of the HostedEngine VM.
Then you need virsh to undefine the old HostedEngine VM from the host and ensure that the
VM is not running on any host.
Better stop the ovirt-ha-agent.service & ovirt-ha-broker.service on all hosts capable
to start the HE.
Once you have the xml, edit it to match your needs and then use 'virsh define
/path/to/xml/config' to define the modified HostedEngine VM.
Then try to start the vm:
virsh start HostedEngine
If the power up complains about the storage, check if you got a link in /var/run/ pointing
to the shared storage.
Here is an example of mine:
<disk type='file' device='disk' snapshot='no'>
<driver name='qemu' type='raw' cache='none'
error_policy='stop' io='threads' iothread='1'/>
<source
file='/var/run/vdsm/storage/808423f9-8a5c-40cd-bc9f-2568c85b8c74/8ec7a465-151e-4ac3-92a7-965ecf854501/a9ab832f-c4f2-4b9b-9d99-6393fd995979'>
<seclabel model='dac' relabel='no'/>
</source>
<backingStore/>
[root@ovirt2 ~]# ls -l /var/run/vdsm/storage/808423f9-8a5c-40cd-bc9f-2568c85b8c74/
общо 24
lrwxrwxrwx. 1 vdsm kvm 129 1 ное 9,53 2c74697a-8bd9-4472-8a98-bf624f3462d5 ->
/rhev/data-center/mnt/glusterSD/gluster1:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/2c74697a-8bd9-4472
-8a98-bf624f3462d5
lrwxrwxrwx. 1 vdsm kvm 129 1 ное 9,57 3ec27d6d-921c-4348-b799-f50543b6f919 ->
/rhev/data-center/mnt/glusterSD/gluster1:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/3ec27d6d-921c-4348
-b799-f50543b6f919
lrwxrwxrwx. 1 vdsm kvm 129 1 ное 10,21 441abdc8-6cb1-49a4-903f-a1ec0ed88429 ->
/rhev/data-center/mnt/glusterSD/gluster1:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/441abdc8-6cb1-49a4
-903f-a1ec0ed88429
lrwxrwxrwx. 1 vdsm kvm 129 1 ное 10,08 8ec7a465-151e-4ac3-92a7-965ecf854501 ->
/rhev/data-center/mnt/glusterSD/gluster1:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/8ec7a465-151e-4ac3
-92a7-965ecf854501
lrwxrwxrwx. 1 vdsm kvm 129 1 ное 10,21 94ade632-6ecc-4901-8cec-8e39f3d69cb0 ->
/rhev/data-center/mnt/glusterSD/gluster1:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/94ade632-6ecc-4901
-8cec-8e39f3d69cb0
lrwxrwxrwx. 1 vdsm kvm 129 1 ное 9,53 fe62a281-51e9-4b23-87b3-2deb52357304 ->
/rhev/data-center/mnt/glusterSD/gluster1:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/fe62a281-51e9-4b23
-87b3-2deb52357304
If it complains of missing vdsm-ovirtmgmt network, just create an xml file like this one:
[root@ovirt1 HostedEngine-RECOVERY]# cat vdsm-ovirtmgmt.xml
<network>
<name>vdsm-ovirtmgmt</name>
<uuid>8ded486e-e681-4754-af4b-5737c2b05405</uuid>
<forward mode='bridge'/>
<bridge name='ovirtmgmt'/>
</network>
And define that network via 'virsh net-define'.
If you manage to power up the HostedEngine, you will be able to revert your changes.
Good luck, and better start making backups :D
Best Regards,
Strahil Nikolov
В понеделник, 16 ноември 2020 г., 11:35:07 Гринуич+2, Vladislav S
<scrik787(a)gmail.com> написа:
PLEASE HELP
I changed the type in the cluster and now my hosted-engine machine won't start!. There
are no backups. How can I manually change the parameters of the machine from under the
roof so that it starts and I can restore ovirt to work
Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into
the PCI controller with index='0'. It requires a controller that accepts a
pcie-root-port
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/K3DGMIKDVAE...