Is this something that I'll just be able to "yum update ; reboot" on the
engine and host? Or is there some other way to upgrade from 4.0.4 to
4.0.5 once it's released? (I'm running a single-host hosted-engine
On Mon, November 14, 2016 1:02 am, Michael
Got another one, when moving the SPM to another host by using the button
in UI. It's a different error but may indicate the underlying problem...
2016-11-14 11:43:42,217 ERROR
(default task-5)  Permutation name:
It's an engine bug, so yes, update the engine to 4.0.5 and run
engine-setup(no need to reboot)
On Mon, Nov 14, 2016 at 2:22 PM, Derek Atkins wrote:
> Thanks, Michael,
> Is this something that I'll just be able to "yum update ; reboot" on the
> engine and host? Or
On Thu, Nov 10, 2016 at 5:18 PM, Derek Atkins wrote:
> On Thu, November 10, 2016 11:04 am, Piotr Kliczewski wrote:
>>> Could you explain the above error? I'm not sure I understand what it
>>> means. I do, however, know what the following error is about. I
This is a reminder to all that the call for presentations for the iaaS and
Virtualization DevRoom at the 2017 FOSDEM is coming up very soon.
If you are interested in submitting a presentation, all of the pertinent
details can be found in this blog.
We're getting some good submittals in
Yes, I have tried installing it from virtio, it goes on like its going to
install, then after a while fails with message, no drivers found.
Sent from Yahoo Mail on Android
On Sun, Nov 13, 2016 at 22:30,
users-requ...@ovirt.org wrote: Send Users mailing
Thanks. I'll wait for 4.0.5 to be released.
Is there a published
release schedule anywhere? Google only brought me to the Nov 2nd
pre-release Release Notes page, but nothing that showed the expected
Michael Burman writes:
2016-11-14 17:24:27,980 ERROR
(org.ovirt.thread.pool-8-thread-39) [4a0b828a] Exception:
at com.sun.proxy.$Proxy183.isMacInRange(Unknown Source)
Can you please attach engine.log?
On Mon, Nov 14, 2016 at 6:28 PM, Martijn Grendelman <
> 2016-11-14 17:24:27,980 ERROR
> (org.ovirt.thread.pool-8-thread-39) [4a0b828a] Exception:
We have a setup where we want to deploy 2 engines as the network between 2
buildings is unreliable.
With 2 engines, we then want to be able to move VMs (one time) from current
engine where they are running to new engine in the other building.
Is there a recommended workflow for doing
An “export domain” is made for just this purpose. Create a NFS (version 3)
share and make it accessible to the hypervisors for each engine. (It should be
a dedicated NFS share, not used for anything else.) As I recall it should be
owned by vdsm:vdsm (36:36). In one of the
Fantastic information. Thanks so much for this.
I was already using export domains inside my current engine, but not sure if it
would also work “between” engines so to speak.
Have a great evening!
From: Beckman, Daniel
Mail list logo