Details
-
Bug
-
Resolution: Unresolved
-
Trivial
-
None
-
None
-
None
Description
ReactOS version: 0.4.15-dev-5159-g2e56c3b
Arch: 32 bits
Compiler tested: GCC
Software tested: VirtualBox 2.0.X (all the versions suffer that issue, but it goes worse after 2.0.10).
Description of the bug:
Open VBox 2.0.0. You have to create a new VM, with an attached Virtual HDD. Once you have it created, you can start it and the configurations of every parameter is in the C:\Documents and Settings\Administrator\.VirtualBox\Virtualbox.xml file and visually in the software. Close the VirtualBox software. Once you have done this, you will never be able to start the this VM because it's shown as "inaccessible", error code: Unknown status 0x8012D850 (0x0012D850). I think it's an problem loading the XML file itself.
In 2.0.10 or posterior versions, like 2.1.0, 3.X.X. or 4.X.X are taking this issue loading the xml creating the VM or the HDD. Forgets almost the configuration it's using.
Screenshot
vbox1.png vbox2.png
It won't give the opportunity to delete the virtualmachine
Log
Vbox bug.log
fixme:(dll/win32/shell32/shlexec.cpp:1934) flags ignored: 0x00104000 |
(dll/ntdll/ldr/ldrinit.c:1889) Applying LOAD_CONFIG |
(drivers/ksfilter/ks/connectivity.c:281) ZwOpenKey() failed with status 0xc0000034 |
(sdk/lib/drivers/sound/mmixer/controls.c:481) MMixerCountMixerControls PinId 11 is not connected by any node |
(dll/win32/kernel32/client/loader.c:386) LoadLibraryExW(wintab32) failing with status c0000135 |
(dll/win32/kernel32/client/loader.c:386) LoadLibraryExW(wintab32.dll) failing with status c0000135 |
(dll/ntdll/ldr/ldrinit.c:1889) Applying LOAD_CONFIG |
fixme:(dll/win32/ole32/compobj.c:4128) (00000000,-1,00000000,00000000,1,3,00000000,0,00000000) - stub! |
fixme:(dll/win32/ole32/compobj.c:3290) stub |
err:(dll/win32/ole32/compobj.c:3195) class {c71566f2-561e-11d1-ad87-00c04fd8fdff} not registered |
err:(dll/win32/ole32/compobj.c:3274) no class object {c71566f2-561e-11d1-ad87-00c04fd8fdff} could be created for context 0x1 |
(drivers/usb/usbport/ioctl.c:430) USBPORT_FdoDeviceControl: IOCTL_GET_HCD_DRIVERKEY_NAME |
(drivers/usb/usbport/ioctl.c:430) USBPORT_FdoDeviceControl: IOCTL_GET_HCD_DRIVERKEY_NAME |
(drivers/usb/usbport/ioctl.c:425) USBPORT_FdoDeviceControl: IOCTL_USB_GET_NODE_INFORMATION |
(drivers/usb/usbport/ioctl.c:425) USBPORT_FdoDeviceControl: IOCTL_USB_GET_NODE_INFORMATION |
(drivers/usb/usbport/ioctl.c:430) USBPORT_FdoDeviceControl: IOCTL_GET_HCD_DRIVERKEY_NAME |
(drivers/usb/usbport/ioctl.c:430) USBPORT_FdoDeviceControl: IOCTL_GET_HCD_DRIVERKEY_NAME |
(drivers/usb/usbport/ioctl.c:425) USBPORT_FdoDeviceControl: IOCTL_USB_GET_NODE_INFORMATION |
(drivers/usb/usbport/ioctl.c:425) USBPORT_FdoDeviceControl: IOCTL_USB_GET_NODE_INFORMATION |
fixme:(dll/win32/oleaut32/usrmarshal.c:798) size interfaces |
fixme:(dll/win32/oleaut32/usrmarshal.c:919) marshal interfaces |
fixme:(dll/win32/oleaut32/usrmarshal.c:1096) marshal interfaces |
(dll/win32/kernel32/client/loader.c:386) LoadLibraryExW(wintab32) failing with status c0000135 |
(dll/win32/kernel32/client/loader.c:386) LoadLibraryExW(wintab32.dll) failing with status c0000135 |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
(win32ss/user/ntuser/window.c:1318) err: UserSetParent Bad Child! |
fixme:(dll/win32/oleaut32/usrmarshal.c:798) size interfaces |
fixme:(dll/win32/oleaut32/usrmarshal.c:919) marshal interfaces |
fixme:(dll/win32/oleaut32/usrmarshal.c:1096) marshal interfaces |
|
Attachments
Issue Links
- relates to
-
CORE-14507 Can't create a VM in VirtualBox 4.0.36 under ReactOS.
- Open
-
CORE-11254 Can't create a virtual machine in Virtualbox 1.6.0
- Untriaged
-
CORE-17980 VirtualBox 4.3.40: Unable to create a new HDD for a VM
- Untriaged
-
CORE-8418 empty input boxes in VirtualBox 3.1.0
- Open