similar to: poweroff in vm causes the host to become unavailable

I did a yum update on my management server and now the ovirt gui is no longer accessable. Is it supposed to just work or do I need to do something after the yum update? Justin.

The VMs just boot up with the default network interface model which is 100Mb, is there a way to set it to a 1Gb model? Cheers, Justin.

Has anyone tried using glusterfs to handle live sysvol replication? Cheers, Justin.

Hi, I have set up a 40GB iscsi target on my san and when I add it in to the storage pool and it shows up as 40GB. When I try to create a 40GB volume in the ovirt UI it tries to but fails. The error message is that the volume will not fit. If I create one smaller than 40GB it works. Is anyone else experiencing this? Also, if I then start a virtual machine up to install on the newly

The previous patch, for whatever reason, fails to apply on top of tip. This patch is reimplemented and, hopefully, fixed.

This patch fixes state changes in dbomatic so that there is no intermediate 'stopped' state after being unreachable or on startup of dbomatic etc. Also fixes a number of smaller bugs around host associations, state changes, etc. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 85 +++++++++++++++++++++++++++++++------------- 1 files changed, 60

This patch updates dbomatic, taskomatic and host-register to use the new C++ wrapped ruby QMF bindings. It also fixes a couple of bugs along the way including the 0 cpu bug for host-register. This is a compilation of work done by myself and Arjun Roy. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 111 ++++++-------

Are the build instructions out of date? I've been following them but when I get to "make update-app" I get make: *** No rule to make target `update-app'. Stop. I took a look in the Makefile and sure enough there's no updated-app target or update-host for that matter... What's the procedure now? Cheers, Justin.

I created a new VM today and it ran for a while before mysteriously disappearing. I logged in to the node it was running on to take a look at the logs and it looks as though the VM was shut down because the node ran out of memory. This particular node has 8GB in it and was running 4 VMs (including the crashed one). The memory assigned to each VM was 4G, 1.5G, 512M, 256M. It was the 256M VM

After running for a while the node becomes "unavailable" in the server UI. All VMs running on that node also become unavailable. The node is still running fine as are all the VMs, they're just no longer manageable. I looked on the node and everything appeared to be running fine. Looked on the server and ovirt-taskomatic was stopped (this seems to happen quite a bit).

Hi, I'm having some problems building ovirt. The build fails during the final ovirt build stage in the instructions. The failure is because it can't find "/usr/share/ovirt-node-tools/ovirt-node-recipe.ks". I've checked and sure enough it's not there. Has anyone else come across this problem? Building on FC13 using the instructions found here:

Hi， I tried QEMU on ARM/PPC platforms. If running poweroff command on guest, it should also shutoff the VM. But it shows the VM status still be 'running' instead of 'shutoff'. I guess it should be qemu issue, is it right? Best Regards, Olivia

Hi, I had to reboot my management server today and when it comes back up the node machine has a status of "unavailable (enabled)". I saw this the last time I rebooted the management server and rebooting the node fixed the problem. What is the expected behaviour in this instance? My expectation would be that when the management server is reset, the nodes keep running (which they

I'm using a bunch of SPA942's, and I'm trying to provision them mostly by DHCP (and what I can't set that way, I try to provision via HTTP interface into the phone). I changed the domain in my AstLinux config from "astlinux" to redfish-solutions.com, and set that in my sip.conf file as well: context=incoming

Signed-off-by: Arthur Clement <aclement at linagora.com> --- src/host-browser/host-register.rb | 16 ++++++++++++---- 1 files changed, 12 insertions(+), 4 deletions(-) diff --git a/src/host-browser/host-register.rb b/src/host-browser/host-register.rb index 693a6f2..5ff6a90 100755 --- a/src/host-browser/host-register.rb +++ b/src/host-browser/host-register.rb @@ -393,13 +393,18 @@ class

This patch includes one small change: the Processors::get_load_average() method is now const since it does not change the object's state.

After some feedback from Slow, mainly about the load_average API being a method rather than an ongoing statistic. So I've converted the code over to instead update the load average statistic on a regular basis.

Refactoring the previous patch ended up creating two deltas. This patch pushes them both together into a single commit.

Hi, Fantastic that Samba 4.0 has been released, I've just installed and joined it to an existing AD (single Win2k8R2 server running Exchange). The installation seemed to go well but I'm seeing odd messages when I show the replication status on both the Samba server and the Win2k8R2 server. Is there something I missed in the install? I followed the instructions outlined at

Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- src/db-omatic/db_omatic.rb | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index da11bfa..79f29d2 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -195,6 +195,9 @@ class DbOmatic < Qmf::ConsoleHandler end