Sorry, got away from this for a while attending to other work, but back at it
now... Anyone have any ideas on how I may further troubleshoot this issue?
Thanks
-Original Message-
From: Will Dennis
Sent: Wednesday, May 18, 2016 11:39 AM
To: 'Michal Skrivanek'; 'Yedidyah Bar David'
Cc:
> On Jun 6, 2016, at 1:59 AM, Fabrice Bacchella
> wrote:
> I'm surprised, because in my mind, the default value are the least usefull
> version of each options. Why don't set them to good, useful values and let
> the user changed them to the opposite if there is
On 06/06/16 16:15 +0300, Дмитрий Глушенок wrote:
So, libvirt behaves differently with custom partition? My assumption was that
it will perform the same changes. I will have in mind in case oVirt 4 will be
released too late.
May be I wrote incorrectly - in oVirt 4.0 RC1 scsi pass-through
So, libvirt behaves differently with custom partition? My assumption was that
it will perform the same changes. I will have in mind in case oVirt 4 will be
released too late.
May be I wrote incorrectly - in oVirt 4.0 RC1 scsi pass-through already working.
--
Dmitry Glushenok
Jet Infosystems
It looks fine, thanks.
Looking at the oVirt log I see IPA server FQDN:
auth02.intern.customer-virt.eu.intern.customer-virt.eu
Looking at krb realm, I guess this should be -
auth02.intern.customer-virt.eu
Do you use SRV records or did you pass --ldap-servers to manage-domains?
If SRV, then
On 06/06/16 13:26 +0300, Дмитрий Глушенок wrote:
Hello Martin,
Thank you for your time. It is clear how to create partition and assign it to a
VM. But libvirt manipulates with contents of devices.list and I didn't find a
way to put my devices into devices.list and stop libvirt from removing
Hello Martin,
Thank you for your time. It is clear how to create partition and assign it to a
VM. But libvirt manipulates with contents of devices.list and I didn't find a
way to put my devices into devices.list and stop libvirt from removing them.
Anyway, it looks like that the best solution
On 03/06/16 14:05 +0300, Дмитрий Глушенок wrote:
Thank you Martin!
Actually I tried the workaround hook, provided in [2], but then VDSM (oVirt
3.6.6) tries to interpret hostdev in XML as PCI device, which leads to:
::The vm start process failed
Traceback (most recent call last):
File
Hello,
here is the krb5kdc log from IPA2:
###
Jun 03 17:18:22 auth02.intern.customer-virt.eu krb5kdc[1283](info): AS_REQ (1
etypes {23}) 192.168.210.45: NEEDED_PREAUTH: kr...@intern.customer-virt.eu for
krbtgt/intern.customer-virt...@intern.customer-virt.eu, Additional
pre-authentication
When I'm looking the RHEV's documentation about the API class in the python
SDK, I see :
persistent_auth
Specifies whether persistent authentication is enabled for this connection.
Valid values are True and False. This parameter is optional and defaults to
False.
filter
Specifies whether or
Le 5 juin 2016 à 13:22, Michal Skrivanek a écrit :
On 05 Jun 2016, at 12:37, nico...@devels.es wrote:
Hi,
On user portal, when users click on the "Connect" link of a VM that is
configured to be run with "Native client" and SPICE protocol, a .vv file is
On 06/03/2016 05:44 PM, Kilian Ries wrote:
Hi,
i have two free-IPA directories setup in multi-master replication. Both
are running on CentOS 7.2 with latest Software installed. Replication
between both IPAs is setup correctly and i am able to authenticate
against each of the two manually.
12 matches
Mail list logo