Hi
For long time I've been looking for proper support in ovirt for Open
vSwitch so I'm happy that it is moving in the right direction. However,
there seems to still be a dependency on a ovirtmgmt bridge and I'm
unable to move that to the OVN provider.
The hosting center where I rent hw
On Tue, 27 Dec 2016 20:04:23 +0100 ov...@timmi.org wrote:
OO> Hi all,
OO>
OO> please note that I have upgrade my oVirt 3.6.5 environment to 4.0.5
OO> without problems.
OO> I saw some network messages in my evens but I will post them later in a
OO> separate thread.
OO>
OO> Really great work how
Hi all,
please note that I have upgrade my oVirt 3.6.5 environment to 4.0.5
without problems.
I saw some network messages in my evens but I will post them later in a
separate thread.
Really great work how the upgrades are working.
Best regards
Christoph
Am 21.12.2016 um 19:30 schrieb
Hi,
The package starts with q, yet you pasted only ovirt and vdsm from yum update.
Can you paste complete output of yum update?
Also, the qemu package should be there when you go to 7.3
http://mirror.centos.org/centos-7/7.3.1611/virt/x86_64/kvm-common/
From:
Hello,
I set my hosts on ovirtmgmt with DHCP. It happened several times that
they lost their address for several reason, but never asked for a new
lease, so the hosts become unreacheable. What about adding the
|PERSISTENT_DHCLIENT=1 |option as default for DHCP attribution in ifcfg
files?
You create a nic on a network defined on a VLAN via the API\UI\SDK.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary
On Mon, Dec 26, 2016 at 5:45
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETTO:+0100
TZOFFSETFROM:+0200
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
Hi,
This pool is responsible for event processing. There are not so many events
that we send from vdsm. At the moment we send vm status changes. The
default value may be not enough when we provision, delete, stop etc many
vms at the same time. If your environment is static the default value
8 matches
Mail list logo