Nope no luck :(
Been tryin to get it working for a few months, even opened a case (01376573)
and was told it was broken, that's why I was asking if anyone else has been
able to get it working. Seems strange to me if the feature is completely
broken since it was one of the main features
- Original Message -
From: Diego Remolina dijur...@gmail.com
To: Users@ovirt.org
Sent: Thursday, July 16, 2015 7:45:43 AM
Subject: [ovirt-users] Cannot run specific VM in one node
Hi,
Was wondering if I can get some help with this particular situation. I
have two ovirt cluster
- Original Message -
From: Miguel Angel Costas migacos2...@gmail.com
To: users@ovirt.org
Sent: Monday, July 13, 2015 3:00:33 PM
Subject: [ovirt-users] Problem to start VMs on ovirt
Dear,
I have implemented the lastest version of Ovirt (Centos 6), and every time I
want to start
Hello oVirt users,
I am facing a serious problem regarding my GlusterFS storage and virtual
machines that have *bootable* disks on this storage.
All my VMs that have GlusterFS disks are occasionally (1-2 times/hour)
becoming paused with the following Error: VM vm02.mytld has been paused
due
oVirt 3.6 will be released soon.
Deep dive sessions on various features / aspects of this release will be
scheduled In the upcoming several weeks.
You have a chance to take a look into this new exciting release.
Stay tuned and join these sessions.
Thanks
Barak Azulay
On Thu, Jul 16, 2015 at 12:29:32AM +0200, Adam Popik wrote:
Hello;
I have 2 ovirt nodes (v3.5.3, all on centos 7) with ovirt engine on separate
machine, few vlans, shared storage etc. Installation is mostly standard.
Virtual machines with ipv4 only works well without problems. But I have lot
Hi Joop,
There is currently no split brain in my gluster file systems. The
virtualization setup is a two node hypervisor (ysmha01 and ysmha02),
but I have a 3 node gluster where one node has no bricks
(10.0.1.6-ysmha01, 10.0.1.7-ysmha02 and 10.0.1.5 no bricks), but
helps define quorum, see below:
Hi again Konstantinos.
Can you please attach the full VDSM Engine logs so we can understand the
reason for your problem?
Thanks.
- Original Message -
From: Konstantinos Christidis kochr...@ekt.gr
To: users@ovirt.org
Sent: Thursday, July 16, 2015 11:29:26 AM
Subject: [ovirt-users] VM
On 16-7-2015 14:20, Diego Remolina wrote:
I have two virtualization/storage servers, ysmha01 and ysmha02 running
Ovirt hosted engine on top of glusterfs storage. I have two Windows
server vms called ysmad01 and ysmad02. The current problem is that
ysmad02 will *not* start on ysmha02 any more.
Report available at:
http://dougsland.livejournal.com/124552.html
--
Cheers
Douglas
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Check your vdsm Logs on your nodes. I bet you find something about I/O
errors i guess...
Also check your glusterfs logs. Maybe you can find some problems, too.
Mario
Am 16.07.15 um 10:29 schrieb Konstantinos Christidis:
Hello oVirt users,
I am facing a serious problem regarding my
Hi,
seems like the Setting EnableMACAntiSpoofingFilterRules only applies to
the main IP of a VM, additional IP Adresses on Alias Interfaces (eth0:x)
are not included in the generated ebtables ruleset.
Is there any Workaround / Setting / whatever to allow more than one IP
without completly
These are the links to the files, if there is other better/preffered
way to post them, let me know:
https://www.dropbox.com/s/yziky6f9nk3e8aw/engine.log.xz?dl=0
https://www.dropbox.com/s/qsweiizwxk37qzg/vdsm.log.4.xz?dl=0
A bit more of an explanation on the infrastructure:
I have two
Due to a moment of idiocy I accidentally upgraded my hosted-engine vm to
Fedora 22 and now ovirt-engine will not start, I was able to get postgesql
up an running so I was able to make a backup of the engine. As far as I
know Ovirt 3.5 is not supported on F22, so my options seem limited.
1,
Hello Mario,
On 16/07/2015 04:12 μμ, m...@ohnewald.net wrote:
Check your vdsm Logs on your nodes. I bet you find something about I/O
errors i guess...
Yes there are many IO errors
libvirtEventLoop::INFO::2015-07-16
22:30:02,237::vm::3609::virt.vm::(onIOError)
martirosov.d писал 2015-07-14 17:24:
Николаев Алексей писал 2015-07-10 10:45:
Ovirt больше не поддерживает CentOS 6 для
гипервизоров. CentOS 6 поддерживается
только для Ovirt Engine.
Считаю, что сначало надо
воспроизвести проблему на CentOS 7.1. Если
она сохранится, то будут нужны логи с
16 matches
Mail list logo