On Tue, Jul 12, 2016 at 10:22 AM, Yaniv Kaul wrote:
>
>
> On Mon, Jul 11, 2016 at 7:10 PM, Rafael Almeida
> wrote:
>>
>> Hello, i need secure my hosts runining ovirt (vdsm-4.18.4.1-0) over centos
>> 7, this because oVirt installed on a minimal install of centos 7x, could
>> helpme by sending all
I just found out that Carp also not works on a mode=4 Bond with LACP
on the switch.
I think it's just the linux bond with multiple VLAN's on top of it. a
single vlan on it goes well it seems.
2016-07-12 20:58 GMT+02:00 Matt . :
> Hi guys,
>
> I have been testing bonding with a vm connected to the
On 07/12/2016 07:26 PM, Sebastien Fuchs wrote:
> This works fine with sdk4. Thanks.
> Unfortunately I couldn't find away to update cpu_shares config: can't
> set any update option to update it now or later and no error from the API.
>
In order to perform the update using version 4 of the SDK you
Hi guys,
I have been testing bonding with a vm connected to the network on this
bond mode=1 (vlans on top of it) where the vm uses a carp IP for
failover.
It seems that when the VM which holds the Carp IP and so is Master you
can ping both IP's, so interface IP and Carp IP, but you cannot
throw/r
This works fine with sdk4. Thanks.
Unfortunately I couldn't find away to update cpu_shares config: can't set
any update option to update it now or later and no error from the API.
On Mon, Jul 11, 2016 at 1:07 PM, Juan Hernández wrote:
> On 07/08/2016 04:09 PM, Sebastien Fuchs wrote:
> > Hi,
> >
Hi Ariel,
On 07/12/2016 10:49 AM, Ariel Pérez Rodríguez wrote:
Hi guys!
I want to upgrade my oVirt nodes from oVirt Node - 3.6 -
0.999.201607061021.el7.centos to
ovirt-node-ng-installer-ovirt-4.0-2016062412. I want to use the
ovirt-engine GUI for it. I already installed oVirrt-engine version
Hi guys!
I want to upgrade my oVirt nodes from oVirt Node - 3.6 -
0.999.201607061021.el7.centos to ovirt-node-ng-installer-ovirt-4.0-2016062412.
I want to use the ovirt-engine GUI for it. I already installed
oVirrt-engine version 4.0 and the ovirt-node-ng-image squashfs image
version 4.0.0. I don't
> On Jul 6, 2016, at 2:23 PM, Alexis HAUSER
> wrote:
>
> This is what happens when I try to start the ovirt-guest-agent in Ubuntu-Mate
> 16.04 Xenial, any ideas ?
The problem is here that the log file has not the correct access rights. it
needs to be rw for the ovirtagent user. Long story sh
Hi guys,
I'm investigating which bond mode is best for Vrrp.
Mode=1 is always OK, that stated.
When I try to set mode=6 or mode=5 (where I prefer mode=6) it limits
back in the bond file to mode=4 which is lacp and which I can't use in
this case.
Anyone some testing with this ? mode=2 gives flap
It's the ovirt guest tools iso.
Please note there is a warning message at the import dialog – «You have
selected windows OS and have not selected VirtIO drivers. This may cause the
system not boot up». However selecting the ovirt guest tools iso doesn't help.
Looks like the only solution is to
Alexis HAUSER writes:
> Is there a way to change it for all os in a row ? something like
> "os.all.devices.display.vramMultiplier.value = 2"
Try `os.other.devices.display.vramMultiplier.value'.
> How is that memory used on the hypervisor ? Will this use the physical vram
> for
> the same amoun
> On Jul 12, 2016, at 11:13 AM, Pavel Gashev wrote:
>
> Vinzenz.
>
> I double checked, system matches the configuration. Cluster is running on
> Intel Westmere Family.
>
> Also I tried to boot into the repair mode. After loading viostor driver from
> the CD I was able to see the drive. Pro
> That's right. You can add similar lines for other OSes as needed.
Is there a way to change it for all os in a row ? something like
"os.all.devices.display.vramMultiplier.value = 2"
How is that memory used on the hypervisor ? Will this use the physical vram for
the same amount or will it use
Vinzenz.
I double checked, system matches the configuration. Cluster is running on Intel
Westmere Family.
Also I tried to boot into the repair mode. After loading viostor driver from
the CD I was able to see the drive. Probable the issue is that there are no
vio* drivers in /Windows/System32/d
Alexis HAUSER writes:
>> Look for vramMultiplier in osinfo-defaults.properties file.
>> The following formula applies: vram_size = vramMultiplier * vgamem
>> You must restart Engine to apply the new setting.
>
> The only thin I found about it in that file is :
> os.rhel_7x64.devices.display.vram
> Look for vramMultiplier in osinfo-defaults.properties file.
> The following formula applies: vram_size = vramMultiplier * vgamem
> You must restart Engine to apply the new setting.
The only thin I found about it in that file is :
os.rhel_7x64.devices.display.vramMultiplier.value = 2
I am not
On Mon, Jul 11, 2016 at 7:10 PM, Rafael Almeida <
ralme...@prefecturaloja.gob.ec> wrote:
> Hello, i need secure my hosts runining ovirt (vdsm-4.18.4.1-0) over centos
> 7, this because oVirt installed on a minimal install of centos 7x, could
> helpme by sending all required ports enabled for hosts.
I encountered similar if not exact same issue.
Exploring KVM with oVirt. Testing on Nested Virtualization (KVM on VMWare)
I was able to solve this issue by setting on each node.
brctl setageing 0
I do not have access to the switching infrastructure to easily troubleshoot.
I'm not sure of the
18 matches
Mail list logo