[jbosstools-issues] [JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not

[Aileen Cunningham (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13336653#comment-13336653 ] 

Aileen Cunningham commented on JBDS-4159:
-----------------------------------------

[~dgolovin] This has been highlighted as a usability issue for Fuse Integration Services as when users do hit this issues it takes time to figure out what went wrong.

Is this something you can look at for next release of the Installer?


> On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-4159
>                 URL: https://issues.jboss.org/browse/JBDS-4159
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Feature Request
>          Components: platform-installer
>    Affects Versions: 1.1.0.GA
>            Reporter: Aurélien Pupier
>            Assignee: Denis Golovin
>            Priority: Blocker
>
> On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases.
> here is the error:
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
>     default: Adapter 1: nat
>     default: Adapter 2: hostonly
> ==> default: Forwarding ports...
>     default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
> Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
> Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)