[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4010:
--------------------------------
Sprint: devex #126 January 2017 (was: devex #125 December 2016)
> DevSuite installer should check if virtualization extension is enabled
> ----------------------------------------------------------------------
>
> Key: JBDS-4010
> URL: https://issues.jboss.org/browse/JBDS-4010
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Sudhir Verma
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows.
> {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr
> anslationExtensions"
> __GENUS : 2
> __CLASS : Win32_Processor
> __SUPERCLASS :
> __DYNASTY :
> __RELPATH :
> __PROPERTY_COUNT : 2
> __DERIVATION : {}
> __SERVER :
> __NAMESPACE :
> __PATH :
> SecondLevelAddressTranslationExtensions : True
> VirtualizationFirmwareEnabled : True
> PSComputerName :{code}
> *Update*
> Better to use systeminfo command. Here is example of output:
> {code}$ systeminfo
> Host Name: ESKIMO-ASUS
> OS Name: Microsoft Windows 10 Pro
> OS Version: 10.0.14393 N/A Build 14393
> OS Manufacturer: Microsoft Corporation
> OS Configuration: Standalone Workstation
> OS Build Type: Multiprocessor Free
> Registered Owner: eskimo
> Registered Organization:
> Product ID: 00330-80000-00000-AA020
> Original Install Date: 9/26/2016, 4:15:45 AM
> System Boot Time: 12/19/2016, 4:23:14 PM
> System Manufacturer: ASUSTeK Computer Inc.
> System Model: G53SX
> System Type: x64-based PC
> Processor(s): 1 Processor(s) Installed.
> [01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2201 Mhz
> BIOS Version: American Megatrends Inc. G53SX.203, 7/5/2011
> Windows Directory: C:\WINDOWS
> System Directory: C:\WINDOWS\system32
> Boot Device: \Device\HarddiskVolume1
> System Locale: en-us;English (United States)
> Input Locale: en-us;English (United States)
> Time Zone: (UTC-08:00) Pacific Time (US & Canada)
> Total Physical Memory: 16,361 MB
> Available Physical Memory: 10,150 MB
> Virtual Memory: Max Size: 32,745 MB
> Virtual Memory: Available: 23,976 MB
> Virtual Memory: In Use: 8,769 MB
> Page File Location(s): C:\pagefile.sys
> Domain: WORKGROUP
> Logon Server: \\ESKIMO-ASUS
> Hotfix(s): 7 Hotfix(s) Installed.
> [01]: KB3176935
> [02]: KB3176936
> [03]: KB3176937
> [04]: KB3199209
> [05]: KB3199986
> [06]: KB3209498
> [07]: KB3206632
> Network Card(s): 3 NIC(s) Installed.
> [01]: Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter
> Connection Name: Wi-Fi
> DHCP Enabled: Yes
> DHCP Server: 192.168.0.1
> IP address(es)
> [01]: 192.168.0.101
> [02]: Realtek PCIe GBE Family Controller
> Connection Name: Ethernet
> Status: Media disconnected
> [03]: Cisco Systems VPN Adapter for 64-bit Windows
> Connection Name: Ethernet 3
> DHCP Enabled: No
> IP address(es)
> [01]: 10.3.230.99
> [02]: fe80::e40c:d8f4:d1f6:5959
> Hyper-V Requirements: VM Monitor Mode Extensions: Yes
> Virtualization Enabled In Firmware: Yes
> Second Level Address Translation: Yes
> Data Execution Prevention Available: Yes
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3869:
--------------------------------
Sprint: devex #126 January 2017 (was: devex #125 December 2016)
> platform installer should check/warn if Hyper-V is already enabled.
> -------------------------------------------------------------------
>
> Key: JBDS-3869
> URL: https://issues.jboss.org/browse/JBDS-3869
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 10 Pro, 64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> The platform installer should check and warn if Hyper-V is already enabled on Windows systems.
> Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-23678:
-------------------------------
Attachment: (was: Screenshot 2017-01-10 18.20.38.png)
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-23678:
-------------------------------
Comment: was deleted
(was: My remediation dialog looks different: !Screenshot 2017-01-10 18.20.38.png!)
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-23678:
------------------------------------
My remediation dialog looks different: !Screenshot 2017-01-10 18.20.38.png!
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.4.3.AM2
>
> Attachments: Screenshot 2017-01-10 18.20.38.png, remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1015:
-----------------------------------
Sorry - see !b1.png|thumbnail! and !b2.png|thumbnail!
I'm using the local repo based on jbtistp-4.4.1.CR2-SNAPSHOT-base.zip using Eclipse Neon 1a on Linux FC24.
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png, b1.png, b2.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-23678:
-------------------------------
Attachment: Screenshot 2017-01-10 18.20.38.png
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.4.3.AM2
>
> Attachments: Screenshot 2017-01-10 18.20.38.png, remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months