On Sun, Jul 30, 2017 at 4:24 PM, Maor Lipchuk wrote:
> Hi David,
Sorry, I meant Johan
> I'm not sure how it got to that character in the first place.
> Nir, Is there a safe way to fix that while there are running VMs?
> On Sun, Jul 30, 2017 at 11:58
I'm not sure how it got to that character in the first place.
Nir, Is there a safe way to fix that while there are running VMs?
On Sun, Jul 30, 2017 at 11:58 AM, Johan Bernhardsson wrote:
> (First reply did not get to the list)
> From sanlock.log:
On this one node, it happened from 3.6 -> 4.0. It persisted after 4.0->4.1.
In systemd override I now have to have:
Jul 29 01:19:21 systemd: Starting Auxiliary vdsm service for
running helper functions as
RHEL - 7 - 3.1611.el7.centos
CentOS Linux 7
3.10.0 - 514.16.1.el7.x86_64
0.12.4 - 20.el7_3
Can please you provide the versions of vdsm, qemu, libvirt?
On Sun, Jul 30, 2017 at 1:01 PM, Johan Bernhardsson wrote:
> We get this error message while moving or copying some of the disks on
> our main cluster running 4.1.2 on centos7
> This is shown in the
If you are referring to a plain OS to run the laptops from on, I'm not
aware of any specific OS. maybe DSL (http://www.damnsmalllinux.org/)?
On Sun, Jul 30, 2017 at 1:01 PM, Maor Lipchuk wrote:
> What about ovirt-live?
I believe it depends on the version of Ovirt that you use, the Yanir
solution can be relevant only for the 3.5 version. Started from version 3.6
you can edit HE VM memory via UI without any troubles, the only thing that
you must be aware of under 4.1 you will need to wait for some time, until
What about ovirt-live?
On Sun, Jul 30, 2017 at 12:40 PM, Andy Michielsen
> Hi Maor,
> Thanks for pitching in. I have to admit it isn't really an oVirt issue but
> more on how to allow users working with it.
We get this error message while moving or copying some of the disks on
our main cluster running 4.1.2 on centos7
This is shown in the engine:
VDSM vbgkvm02 command HSMGetAllTasksStatusesVDS failed: low level Image
I can copy it inside the host. And i can use dd to copy.
Thanks for pitching in. I have to admit it isn't really an oVirt issue but more
on how to allow users working with it.
I do use the pool methode to provide the virtual servers and dektops.
For developers and support services I just let them use rdp for windows or even
(First reply did not get to the list)
2017-07-30 10:49:31+0200 1766275 : s310751 lockspace 0924ff77-
2017-07-30 10:49:31+0200 1766275 :
Might be a selinux related issue, similar threads suggest either to disable
selinux completely or run on host:
# setenforce 0
# yum clean expire-cache
# yum update selinux-policy\*
# setenforce 1
keeping an eye out for other reasons/solutions.
On Thu, Jul 27, 2017 at 5:32
As far as it goes for RHEV:
- Virtual machine migration will fail if migrating from a hypervisor with
SELinux enabled to one with SELinux disabled
- A virtual machine previously started on a hypervisor with SELinux enabled
will not start on a hypervisor with SELinux disable.
RHEV manages the
Can you please elaborate more regarding the requirements and what you
are trying to achieve.
Have you tried to use vm-pool? Those VMs should be configured as
stateless and acquire minimal storage capacity.
On Fri, Jul 28, 2017 at 10:19 PM, Andy Michielsen
In order to increase the memory allocation or the cpu cores of the hosted
engine VM, the VM must be brought down and the vm.conf configuration file
must be edited on every hypervisor:
Set global maintenance mode from the hypervisor the VM is currently running
Can you please share the vdsm and engine logs.
Also, it won't harm to also get the sanlock logs just in case sanlock
was configured to save all debugging in a log file (see
Try to share the sanlock ouput by running 'sanlock
On Fri, Jul 28, 2017 at 8:37 PM, Richard Chan
> After an upgrade to 4.0 I have a single host that cannot start supervdsmd
> because of IOError on /dev/stdout. All other hosts upgraded correctly.
Upgrade from which version? 3.6? Did you stay on 4.0 or
Mail list logo