[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
- First Post
- Replies
- Stats
-
Go to
- ----- 2026 -----
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
[
https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin....
]
Len DiMaggio commented on JBDS-3766:
------------------------------------
This error was reported in response to "vagrant up" with the attempted
installation:
{code}
C:\DeveloperPlatform\cdk\components\rhel\rhel-ose>vagrant global-status
id name provider state directory
---------------------------------------------------------------------------------------
dd89029 default virtualbox poweroff C:/DeveloperPlatform/cdk/components/rhel/rhel-ose
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
C:\DeveloperPlatform\cdk\components\rhel\rhel-ose>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["modifyvm", "0a2f3c37-c477-4682-bb9b-41745b76dcea",
"--natpf1", "delete", "ssh"]
Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info
not available)
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at
line 493 of file VBoxManageModifyVM.cpp
{code}
Performing a system restart resolved the issue.
Installer - Seeing an intermittent issue where vagrant fails to start
- is a system restart needed as indicated in the log?
---------------------------------------------------------------------------------------------------------------------------
Key: JBDS-3766
URL: https://issues.jboss.org/browse/JBDS-3766
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Environment: Installer: Setup-bundled-0.0.2-20160401-33
Reporter: Len DiMaggio
Assignee: Denis Golovin
Attachments: install.log, vagrant.log, vbox.log
See attached log files.
After some install attempts, Vagrant fails to start. The vagrant install log reports the
following:
{code}
MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully.
MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name:
Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp.
Installation success or error status: 0.
MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product
Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp.
Type of System Restart: 2. Reason for Restart: 2.
MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or
update for the product required a restart for all changes to take effect. The restart was
deferred to a later time.
{code}
Is a system restart needed to ensure that the vagrant installation is successful on
Windows?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
3670
days inactive
3670
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
tags (0)
participants (1)
-
Len DiMaggio (JIRA)