> On Dec 21, 2016, at 10:11 AM, Nicolas Ecarnot <nico...@ecarnot.net> wrote:
> Le 21/12/2016 à 16:04, Tom Gamull a écrit :
>> Are there any events in the event log (usually Application Log entries
> With a test server, I'm trying to forcibly reproduce the
nsider reporting this to Microsoft, I am unaware of 2008 R2 having
this behavior (I have seen 2008 R2 used on KVM and libvirt for openstack
without issue and be migrated).
> On Dec 21, 2016, at 9:48 AM, Nicolas Ecarnot <nico...@ecarnot.net> wrote:
> Le 21/12/201
Under Edit Virtual Machine -> System -> (Advanced Parameters) there is a Custom
CPU Type you may be able to set, are all the hosts in the same cluster?
> On Dec 21, 2016, at 9:16 AM, Nicolas Ecarnot <nico...@ecarnot.net> wrote:
> Thank you f
what kind of activation keys are you using? Do you have KMS server?
> On Dec 21, 2016, at 8:27 AM, Nicolas Ecarnot <nico...@ecarnot.net> wrote:
> Most of our virtual machines are Linux, but an increasing number of windows
> VMs are being
I'm not going to lie I never had much luck. I end up using qemu-img convert on
the command line to convert a vmdk to a raw file. The ova should just be a
compressed file. Plenty of blogs on this.
I know that's not the answer you're looking for but if you run out of options
you can do this.
I had some similar issues (also with IPV6 which I haven’t retried lately). I
ended up double checking /etc/resolv.conf and just dropping an entry there and
also ensuring the name servers were present in the ifcfg files. This did the
trick. Depending on how you configure LACP, sometimes the
This is pointing to network connectivity issues
You can look at logs under /var/logs/ovirt-*
Check your dns and make sure the hosts can connect to each other. You can
restart the host, mark it as restarted in the manager and then activate it.
Worst case, you can remove it using hosted-engine
What does gluster peer status say on each host?
Red Hat | Solutions Architect
(404) 494-0280 | @magicalyak
> On Oct 26, 2016, at 8:55 PM, Tom Gamull <tgam...@redhat.com> wrote:
> This is pointing to network connectivity issues
> You can look at logs
I’ve done the same. You may get some shutdown issues with this approach on
sanlock so if this is more of a home lab and you shutdown a lot sometimes the
systemctl stop ovirt-ha-agent ovirt-ha-broker
systemctl stop vdsmd
systemctl stop sanlock
systemctl stop nfs
if that resolves the issue?
It may be a bug.
> On Oct 12, 2016, at 9:27 AM, Николаев Алексей <alexeynikolaev.p...@yandex.ru>
> 12.10.2016, 15:53, "Tom Gamull" <tgam...@redhat.com
>> Can you se
Can you set it to permissive and run
sealart -a /var/log/audit/audit.log
you may need to install selinux tools
> On Oct 12, 2016, at 4:49 AM, Краснобаев Михаил wrote:
> Good day,
> had a similar problem, disabling selinux helped.
> 11.10.2016, 09:55,
Can you eliminate the switch or port config as the issue? I’m a little unclear
as to how you configured the nodes I have basically use a single NIC (some are
LACP bonds) with a GENERAL link type (not TRUNK or ACCESS) where there is a
default VLAN (which I don’t tag) and the rest of the VLANs
started helping in
little bits on some projects.
If you can fork the documents, change them to include your notes, I’d be happy
to hand hold or explain how to do the pull request (think merging your changes
back). you can even email me direct if needed.
> On Sep 4, 2016, at 4:26
Mail list logo