I need to change the gateway ping address, the one used by hosted engine setup.
Is ok to edit /etc/ovirt-hosted-engine/hosted-engine.conf on each node,
update the gateway param with the new ip address and restart
the agent&broker on each node?
With a blind test seems ok, but need to understand if is the right procedure.
I am looking for a way to get my hosted-engine running on el7 so I can
upgrade to oVirt 4.0. Currently my hosts already run el7, but my
hosted-engine is still el6.
this is only about the hosts.
I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but it
only mentions upgrade of the hosted-engine software, not the OS.
I understood I can do a fresh hosted-engine install, and then import my
storage domain to the new hosted engine, but:
- Do I need to restore my hosted engine database? ( like described here:
- Can I directly install hosted-engine 4.0 and then import the storage
domain? Or should I install same hosted-engine version?
- Do I first need another master storage domain or can I directly import my
old master storage domain?
- When importing the storage domain what is the risk it fails ( I have
backups, but it would cost a day to restore all )
- How long would import take? few minutes or hours? ( I want to keep down
time as low as possible ).
Another option would be upgrade the OS ( with redhat-upgrade-tool ) or is
this a path for disaster?
I hope someone can tell me how I can smoothly upgrade my hosted-engine up
to el7 and run oVirt 4.
i have an ovirt 4.0.1 installation on two nodes. Hosted Engine. San storage
For some reason the vdsmd on the nodes is logging an error every few
vdsm vds.dispatcher ERROR SSL error during reading data: unexpected eof
Running tcpdump it is a connect from the node to itself. I can't figure out
what is wrong. Can someone give me a hint?
I'd like to find any vms with some defined properties like
(console-enabled or serial_number-policy for example) with ovirt-shell
-E "show vm name", but I can't find all information that I can get with
edit vm popupin the UI.
I belevied these kind of properties were unvailable because the flag was
by default to false, but after updating the flag to true, it is still
not visible. Does it exist an extended way to get those feature with
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
I'm running oVirt 188.8.131.52-1.el7.centos and when I install a Win 7 guest
VM, using VirtIO disk, networking etc, it goes through the install process
ok, but blue screens upon boot with a vioscsi.sys error (attached). I have
tried the official version ovirt-guest-tools-iso 3.6.0 0.2_master.fc22, as
well as some earlier and later versions. I am using a PXE boot method with
a Windows deployment server, which has the drivers from the oVirt tools ISO
installed (indeed, it picks up the drive and networking and I can see it
installing the drivers). I have tried with the generic IDE and rtl8139
config on the guest, and it also fails with the same vioscsi.sys error
after rebooting upon finishing installation even though I'm using IDE as
the disk driver.
I have uploaded a win 7 x64 ISO and tried installing that, and it loads the
VirtIO viostor driver (using the method at:
and even manages to partition the disks, but fails to install on the disk
I've tried temporarily removing the vioscsi files from the install server
as a last resort, but as expected it fails to install properly, though I
thought it used the viostor driver instead.
Thanks for any help.