Verr main config constructor com error

virtualbox.org

End user forums for VirtualBox

  • Board indexGeneralVirtualBox 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 indexGeneralVirtualBox 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.

Читайте также:  Network error please check and retry

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:\Users\will\.VirtualBox\Machines\XP1\XP1.xml’ for reading: -102 (File not found.).
D:\tinderbox\win-3.2\src\VBox\Main\MachineImpl.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

Читайте также:  Error loading operating system что делать если на компьютере надпись

Источник

virtualbox.org

End user forums for VirtualBox

  • Board indexGuest systemsWindows Guests
  • Change font size
  • Print view
  • FAQ
  • Login

error help

error help

by cowman » 24. Aug 2016, 03:01

I need some help with this error

Failed to open a session for the virtual machine SAS University Edition.

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

thanks in advance

Re: error help

by socratis » 24. Aug 2016, 07:54

Re: error help

by mpack » 24. Aug 2016, 11:33

This seems like the VirtualBox software is not properly installed. Use «Run as administrator», and install for the the correct final user.

I’m not sure what «release log of the VM» means. VMs have run logs, not release logs. A screenshot of the error might help.

Re: error help

by Elizine » 24. Aug 2016, 12:47

VirtualBox is throwing this error for a number of reasons. It’s the same requirement it’s just that the root cause is different.

1. You haven’t enabled VT-x in VirtualBox and it’s required for the VM.
To enable: open vbox, click the VM, click Settings. System->Acceleration->VT-x check box.
2. You haven’t enabled VT-x in BIOS and it’s required.
Check your motherboard manual but you basically want to enter your BIOS just after the machine turns on (usually DEL key, F2, F12 etc) and find «Advanced» tag, enter «CPU configuration», then enable «Intel Virtualization Technology».
3. Your processor doesn’t support VT-x (eg a Core i3).
In this case your BIOS and VirtualBox shouldn’t allow you to try and enable VT-x (but if they do, you’ll likely get a crash in the VM).
4. Your trying to install or boot a 64 bit guest OS.
I think 64 bit OS requires true CPU pass-through which requires VT-x. (A VM expert can comment on this point).
5. You are trying to allocate >3GB of RAM to the VM.
Similar to the previous point, this requires: (a) a 64 bit host system; and (b) true hardware pass-through ie VT-x.
I got success after installing: 32 bit version of linux, allocating 2.5GB RAM.

Oh, and wherever I say «VT-x» above, that obviously applies equally to AMD’s «AMD-V» virtualization tech.

Источник

virtualbox.org

End user forums for VirtualBox

  • Board indexGeneralVirtualBox on Linux Hosts
  • Change font size
  • Print view
  • FAQ
  • Login

Can’t start VM after pciattach command

Can’t start VM after pciattach command

by Ziru » 13. Sep 2015, 21:46

Читайте также:  Zte c s325 прошивка

I have working virtualbox, i can create windows vm or linux vm, but when i do: «VBoxManage modifyvm «VM-Name» —pciattach XX:XX.X@XX:XX.X and i try to start the vm i get this error:
Code: Select all Expand viewCollapse view 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: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interfaz: IConsole <872da645-4a9b-1727-bee2-5585105b9eed>

dmesg | grep iommu
Code: Select all Expand viewCollapse view [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6ee4f064-0bcb-4294-a413-544f4c0b0467 rw quiet pci-stub.ids=1002:68f9,1002:aa68 iommu=1 amd_iommu=on

[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6ee4f064-0bcb-4294-a413-544f4c0b0467 rw quiet pci-stub.ids=1002:68f9,1002:aa68 iommu=1 amd_iommu=on

dmesg | grep IOMMU
Code: Select all Expand viewCollapse view [ 1.793993] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[ 12.512656] vboxpci: IOMMU found

dmesg | grep AMD-Vi
Code: Select all Expand viewCollapse view [ 1.793993] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[ 1.793994] AMD-Vi: Interrupt remapping enabled
[ 1.794202] AMD-Vi: Initialized for Passthrough Mode

lspci -nn | grep 04:00
Code: Select all Expand viewCollapse view 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] [1002:aa68]

dmesg | grep pci-stub
Code: Select all Expand viewCollapse view [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6ee4f064-0bcb-4294-a413-544f4c0b0467 rw quiet pci-stub.ids=1002:68f9,1002:aa68 iommu=1 amd_iommu=on
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6ee4f064-0bcb-4294-a413-544f4c0b0467 rw quiet pci-stub.ids=1002:68f9,1002:aa68 iommu=1 amd_iommu=on

[ 1.964440] pci-stub: add 1002:68F9 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 1.964458] pci-stub 0000:04:00.0: claimed by stub
[ 1.964466] pci-stub: add 1002:AA68 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 1.964473] pci-stub 0000:04:00.1: claimed by stub

pciattach command used:
Code: Select all Expand viewCollapse view VBoxManage modifyvm «LadyMalwil» —pciattach 04:00.0@01:05.0
VBoxManage modifyvm «LadyMalwil» —pciattach 04:00.1@01:05.1

I’ve tested on other VM the command without @01:05.0, but i get same results.
Code: Select all Expand viewCollapse view «VBoxManage modifyvm «TestVM» —pciattach 04:00.0″

IOMMU Capable CPU, Motherboard,
IOMMU enabled in grub,
VirtualBox modules enabled,
pci-stub enabled.

the —pciattach command adds to (vm-name).vbox file, the error that i get say » The configuration constructor in main failed » may be the added section is wrong?

Code: Select all Expand viewCollapse view VBoxManage modifyvm «LadyMalwil» —pciattach 04:00.0@01:05.0
VBoxManage modifyvm «LadyMalwil» —pciattach 04:00.1@01:05.1

Note: I can do PCI Passthrough on QEMU+KVM, XEN 4.5, XenServer, VMWare ESXi 5.0/5.1/5.5/6.0
Note2: I don’t have other hypervisor installed on this os installation.
Note3: The linux distro don’t matter, i’ve tested on Fedora22, Ubuntu14.04, ArchLinux, and i’m now at Chakra-os, exactly same results.
Note4: if i remove the » » section from (vm-name).vbox file, then the VM works again.

Источник

Smartadm.ru
Adblock
detector