No PXE involved for the hosts nor for the VMs.
On 26 October 2014 21:04, Matt . wrote:
> Tiemen,
>
> Are you PXE booting or are it normal installs ?
>
> Cheers,
>
> Matt
>
> 2014-10-26 14:43 GMT+01:00 Matt . :
> > Hi,
> >
> > Thanks for your reply!
> >
> > I think I just found out that it's a Fi
Tiemen,
Are you PXE booting or are it normal installs ?
Cheers,
Matt
2014-10-26 14:43 GMT+01:00 Matt . :
> Hi,
>
> Thanks for your reply!
>
> I think I just found out that it's a Firewall issue on CentOS 7. I
> have them normally off, but these were on as that should be setup
> right with ovirt
Hi,
Thanks for your reply!
I think I just found out that it's a Firewall issue on CentOS 7. I
have them normally off, but these were on as that should be setup
right with ovirt.
When I turn it off console seems to connect better and servers seem to
be able to boot from
their mounted disks over N
I have two CentOS 7 hosts in a 3.5 cluster, working fine. My storage domain
is iSCSI and I have only one logical network, no VLAN tagging. There's one
Centos 7 VM running in there and two Windows Server 2012 R2. Haven't tried
Centos 6 yet.
I have disabled firewalld, because otherwise the ovirt hos
Hi,
I have tested the 3.4 release also on CentOS7 as host which gave me
the same result.
It seems CentOS 7 is the killer here.
Matt
2014-10-26 2:14 GMT+01:00 Matt . :
> HI,
>
> I'm still struggeling here with the 3.5 hosts on CentOS 7, no booting
> servers as there is no disk found and connect
HI,
I'm still struggeling here with the 3.5 hosts on CentOS 7, no booting
servers as there is no disk found and connecting to Spice takes around
30 seconds.
FreeBSD VM's seem to boot without any issues, CentOS and Ubuntu don't
as described above.
The 3.4 hosts are still working perfectly on Cent
I cannot find the docs atm, but even with a upgraded engine to 3.5, same issue.
2014-10-20 16:07 GMT+02:00 Daniel Helgenberger :
>
> On 20.10.2014 15:49, Matt . wrote:
>> Hi,
>>
>> Sorry, I forgot a reply to all.
>>
>> As far as I understood 3.4 is supported as host on 7.0.
> Can you point me to
On 20.10.2014 15:49, Matt . wrote:
> Hi,
>
> Sorry, I forgot a reply to all.
>
> As far as I understood 3.4 is supported as host on 7.0.
Can you point me to that documentation? As I understood it this was a
feature of 3.5 (though I can mix this up with hosted engine).
> As I'm
> deploying new hos
Hi,
Sorry, I forgot a reply to all.
As far as I understood 3.4 is supported as host on 7.0. As I'm
deploying new hosts I thought this was nice, also as it fixes some
issues on networking at my side.
So to be clear:
ovirt 3.4.1
Engine = CentOS 6.5
Hosts = CentOS 6.5
NewHosts = CentOS 7.0
That
On 20.10.2014 15:01, Matt . wrote:
> Hi Daniel,
Hi Mat,
please do not forget the list in your reply.
>
> The engine is 6.5 and the host is 7.0
>
> Thats should be supported I thought.
IIRC *not* with =<3.4.x - support for EL7 hosts started with the release
of 3.5. Note, even there it is not recomm
On 20.10.2014 13:48, Matt . wrote:
> Hi guys,
>
> I have installed a new host with Centos 7 on a 3.4.1 engine.
Hi Mat,
can you clarify? Is the engine running on EL7 or the hypervisor host?
In any case, I had troubles running either 3.4 (host / engine) on EL7
and reverted back to EL6.
Also, note
Hi guys,
I have installed a new host with Centos 7 on a 3.4.1 engine.
I have attached the right networks for the VM and strorage is attached
an mounted well.
When I start the VM, connecting to the graphical console takes very
long and when I finally get it my PXEboot is done and wants to boo
loc
12 matches
Mail list logo