[Devtools] CDK fails under QEMU. Have we seen this one before?

[Rick Wagner]

Thanks for that, Robert.

We'll run it down with the customer to see if these are applicable.*

Rick

* Interesting side note:  In most of our middleware support arenas, support
involves pinning down a bug that is replicated on the JVM and mitigated
with a framework code change.   Thus far, CDK support is turning out to be
more about environmental issues.  CEE will look for ways to recognize best
practices and optimize....

On Wed, Jul 27, 2016 at 10:39 AM, Robert Kratky <rkratky at redhat.com> wrote:

> On 27. 7. 2016 09:01:17, Rick Wagner wrote:
>
> > Hello DevTools SMEs,
> >
> > We have a customer with a failing CDK installation.  They appear (we are
> > asking for validation) to be running RHEL 7.2 under QEMU.
> >
> > When they try 'vagrant up', they get the following:
> > "Error while creating domain: Error saving the server: Call to
> > virDomainDefineXML failed: invalid argument: could not find capabilities
> > for domaintype=kvm"
> >
> > Google suggests this error is telling us kvm isn't recognized as a
> > supported feature of the guest o/s.  (There are a couple of suggested
> > workarounds, with mixed results.)
> >
> > Before we start poking at it in the customer's environment, we'd like to
> > ask if we have encountered this before ourselves (and if we have a known
> > good remedy).
>
> Hi Rick,
>
> Could it be that the customer forgot to enable nested virtualization? See
> [1] for how to check for it and set it up.
>
> Also, they need to have a host OS that supports it. Fedora does, RHEL does
> too but only as a TP [2].
>
> Robert
>
> [1]
> https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM
> [2] https://access.redhat.com/solutions/58204
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20160727/f2446d2e/attachment.htm>