Verr main config constructor com error

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Google [Bot] and 34 guests

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

[Solved] VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

[Solved] VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by Griezmann911 » 19. Nov 2019, 09:59

I am trying to create a session in my Windows 10 Pro using Virtual Box but getting below error once I select the Ubuntu ISO to start.

Failed to open a session for the virtual machine Ubuntu.

The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole <872da645-4a9b-1727-bee2-5585105b9eed>

Is this a common issue? Any idea on how we can resolve this?

Re: VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by scottgus1 » 19. Nov 2019, 15:18

To help you get underway getting a solution quick you can try searching for the error text (the CAPITALIZED_UNDERSCORE_SPACED_WORDS) in a web browser with the text «site:forums.virtualbox.org» added to restrict searching to this forum, like this:

There’s several causes, many of which indicate a need to reinstall Virtualbox (right-click the installer and choose Run As Administrator, even if you already are an admin) or check that Virtualbox version and Extension Pack version match.

If either of these do not get your guest running, zip and post a guest log, using the forum’s Upload Attachment tab.

Re: VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by Griezmann911 » 27. Nov 2019, 06:58

Thank you scottgus1. Like you said, I reinstalled VBox again and it is working now. I noticed they released a new version and decided to go for it. I am not sure if that was the issue — using an old version of VBox without updating the same.

Thank you for your kind help!

Re: VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by socratis » 27. Nov 2019, 08:43

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

[Solved] VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

[Solved] VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by Griezmann911 » 19. Nov 2019, 09:59

I am trying to create a session in my Windows 10 Pro using Virtual Box but getting below error once I select the Ubuntu ISO to start.

Failed to open a session for the virtual machine Ubuntu.

The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole <872da645-4a9b-1727-bee2-5585105b9eed>

Is this a common issue? Any idea on how we can resolve this?

Re: VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by scottgus1 » 19. Nov 2019, 15:18

To help you get underway getting a solution quick you can try searching for the error text (the CAPITALIZED_UNDERSCORE_SPACED_WORDS) in a web browser with the text «site:forums.virtualbox.org» added to restrict searching to this forum, like this:

There’s several causes, many of which indicate a need to reinstall Virtualbox (right-click the installer and choose Run As Administrator, even if you already are an admin) or check that Virtualbox version and Extension Pack version match.

If either of these do not get your guest running, zip and post a guest log, using the forum’s Upload Attachment tab.

Re: VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by Griezmann911 » 27. Nov 2019, 06:58

Thank you scottgus1. Like you said, I reinstalled VBox again and it is working now. I noticed they released a new version and decided to go for it. I am not sure if that was the issue — using an old version of VBox without updating the same.

Thank you for your kind help!

Re: VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR

by socratis » 27. Nov 2019, 08:43

Источник

Качество ПО

Основано на реальных событиях.

вторник, 14 декабря 2010 г.

Странный баг в VirtualBox и способ его решения

Вчера меня впервые подвела утилита VirtualBox. Думаю, не стоит расписывать для чего она нужна — слишком она известна).
В общем случилась следующая проблема. Для одной из виртуальных машин дал команду сохранить состояние и завершить ее работу.
При последующем старте VirtualBox обнаружил , что завершенную виртуальную машину запустить нельзя из-за следующей ошибки:

Runtime error opening ‘D:Userswill.VirtualBoxMachinesXP1XP1.xml’ for reading: -102 (File not found.).
D:tinderboxwin-3.2srcVBoxMainMachineImpl.cpp[679] (Machine::registeredInit).
Код ошибки:
E_FAIL (0x80004005)
Компонент:
VirtualBox
Интерфейс:
IVirtualBox <3f36e024-7fed-4f20-a02c-9158a82b44e6>

Если кто столкнется с подобным, не торопитесь удалять и пересоздавать виртуальную машину. Чтобы решить проблему надо перейти в директорию с настройками проблемной виртуалки. Там будет два файла: .xml-prev и .xml-tmp. То есть при сохранении состояния машины и завершении работы почему-то не был создан файл .xml и именно из-за его остутствия и возникала указанная выше проблема.
В общем, берем и переименовываем -prev Или -tmp в .xml и пользуемся созданной ранее машиной.

Вот такое сообщение об ошибке говорит о том, что скорее всего не найден файл ,
эмулирующий диск для виртуалки (например, vdi-файл)

Не удалось открыть сессию для виртуальной машины
No error info
Код ошибки:
E_FAIL (0x80004005)
Компонент:
ProgressProxy
Интерфейс:
IProgress

What was The Command Used To Provision?

vagrant up --provision

I followed the Thoroughly Updating VVV instructions here: https://varyingvagrantvagrants.org/docs/en-US/installation/keeping-up-to-date/

What Kind of VVV Provision Was This?

This was an attempt to upgrade to a new version of VVV

Logs/What Broke?

C:UsersAsusvagrant-local>vagrant up --provision
__ __ __ __
 V V V / Varying Vagrant Vagrants
 _/_/_/  v3.1.1
-git::master

Platform:   platform-mingw32 windows HasWinAdminPriv vagrant-hostsupdater NoColour shared_db_folder_disabled
Vagrant:    v2.2.5,     VirtualBox: v6.0.10r132072
VVV Path:   "C:/Users/Asus/vagrant-local"

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> 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", "20a5c4cf-b1c5-47ae-a0a7-4801cf73a90b", "--type", "headless"]

Stderr: VBoxManage.exe: error: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

If I try to start the VM in VirtualBox, I get this:

The virtual machine 'vagrant-local_1b36869d1c2' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:UsersAsusVirtualBox VMsvagrant-local_1b36869d1c2LogsVBoxHardening.log'.

Result Code: | E_FAIL (0x80004005)
-- | --
Component: | MachineWrap
Interface: | IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

VBoxHardening.log

Also, your vvv-custom.yml would be super handy —>

# IMPORTANT !!!!!!!!!
# Copy this file to vvv-custom.yml so your changes don't get overwritten when you update


# This file is a YAML formatted file. YAML indenting is done in spaces not
# tabs, and whitespace is significant. If you don't stick to this, it will
# fail on provision

#
# IMPORTANT, if you change this file, you have to reprovision,  no exceptions
# vagrant reload --provision
#

# These are your websites, and their names map on to the folders they're
# located in. See the docs for how to define these, and what all the keys
# and options are
sites:
  # The wordpress-default configuration provides an installation of the
  # latest version of WordPress.
  wordpress-default:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - local.wordpress.test

  # The wordpress-develop configuration is useful for contributing to WordPress.
  wordpress-develop:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop.git
    hosts:
      - src.wordpress-develop.test
      - build.wordpress-develop.test

  # The following commented out site configuration will create a standard WordPress
  # site in www/example-site/ available at http://my-example-site.dev.
  # Remember, whitespace is significant! Tabs and spaces mean different things

  #example-site:
  #  repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
  #  hosts:
  #    - my-example-site.test

  # The following commented out site configuration will create a environment useful
  # for contributions to the WordPress meta team:
  
  #wordpress-meta-environment:
  #  repo: https://github.com/WordPress/meta-environment.git


# Utilities are system level items rather than sites, that install tools or packages
# the core utilities install tools such as phpmyadmin
utilities:
  core:
    - memcached-admin
    - opcache-status
    - phpmyadmin
    - webgrind
    - trusted-hosts
    - tls-ca

# vm_config controls how Vagrant provisions the virtual machine, and can be used to
# increase the memory given to VVV and the number of CPU cores. For WP core development
# we recommend at least 2GB ( 2048 )
# It can also be used to override the default provider being used within Vagrant.
# Due to a limitation within Vagrant, the specified provider is only respected on a clean `vagrant up`
# as Vagrant currently restricts you to one provider per machine
# https://www.vagrantup.com/docs/providers/basic_usage.html#vagrant-up
vm_config:
  memory: 2048
  cores: 1
  # provider: vmware_workstation)

Possible Solution

No clue, but I have had a similar error with VirtualBox recently when using Local by Flywheel. See this thread:
https://localbyflywheel.com/community/t/local-machine-wont-start-various-errors/13778

Steps to Reproduce (for bugs)

See above.

Your Environment

Operating System: Windows 10 64-bit
8 GB RAM
VirtualBox 6.0.1.0
Vagrant 2.2.5