Custom Query (16363 matches)
Results (799 - 801 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14012 | obsolete | After upgrade to 4.3.26 exception is raised if create second instance of VirtualBoxManager | ||
| Description |
Hello! After upgrade from virtualbox 4.3.20 to 4.3.26 my code generates errors. Small example to reproduce error: #!/usr/bin/env python from vboxapi import VirtualBoxManager VirtualBoxManager(None, None) VirtualBoxManager(None, None) Output of the script: init exception: 'NoneType' object has no attribute '__getitem__'
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/vboxapi/__init__.py", line 981, in __init__
self.vbox = self.platform.getVirtualBox()
File "/usr/lib/python2.7/dist-packages/vboxapi/__init__.py", line 735, in getVirtualBox
return xpcom.components.classes["@virtualbox.org/VirtualBox;1"].createInstance()
TypeError: 'NoneType' object has no attribute '__getitem__'
Traceback (most recent call last):
File "./test_script.py", line 5, in <module>
VirtualBoxManager(None, None)
File "/usr/lib/python2.7/dist-packages/vboxapi/__init__.py", line 992, in __init__
raise e
TypeError: 'NoneType' object has no attribute '__getitem__'
Also this exception is raised if create instances of VirtualBoxManager in different Python threads. Seems this error occurs because method "observe" of class "_ShutdownObserver" from module "xpcom.components" executes and set variable global xpcom.components.classes to None. |
|||
| #14541 | invalid | After upgrade to 5.02 error IP conflict with bridged network on wireless | ||
| Description |
Hi All, after upgrading to virtualbox 5.0.2 from 4.3.30 I have the error "IP conflict" on each VM with bridged network on wireless. Please note it happens only with wireless bridged and not with wired network. In the error VM says it conflicts with my physical network card. I recognize it from MAC address. I've already chaged mac address and hostname to all my VMs and their network card..but without solving. I've also tried 5.0.3.x in beta release! I downgraded to 4.3.30 and now it works fine again. I attach screenshot of error, vm log and ipconfig o my physical laptop. Thank you |
|||
| #21031 | worksforme | After upgrade to 6.1.36 on Windows 10, can't launch RHEL guest | ||
| Description |
I upgraded VB on my Windows 10 host to release 6.1.36, and now when I try to launch my RHEL guest, there is an error, and the guest won't run. The host is running Windows 10 Version 21H2 (OS Build 19044.1826) on a Dell XPS 8930 tower. The error message that is copied to the clipboard when I click "Copy" on the window that comes up when it fails, is: ===== Failed to open a session for the virtual machine RHEL first. The virtual machine 'RHEL first' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\paulc\VirtualBox VMs\RHEL first\Logs\VBoxHardening.log'. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} ===== The file VBoxHardening.log suggests to run a command, the output of that command is: C:\Users\paulc\VirtualBox VMs\RHEL first\Logs>sc.exe query vboxdrv [SC] EnumQueryServicesStatus:OpenService FAILED 1060: The specified service does not exist as an installed service. I don't see a way to attach files to this web interface, I'll see if I can attach them after posting |
|||

