Custom Query (16363 matches)
Results (2287 - 2289 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5453 | obsolete | BSOD on staring VirtualBox in Windows Vista. | ||
| Description |
Hi, I am trying to install Ubuntu 9.10 (32bit i386 edition) in VirtualBox 3.0.10. I am running Windows Vista. Whenever I open VirtualBox and start Ubuntu for installing, my system crashes and I see BSOD. Can insights and suggestions to solve this will be greatly appreciated. The reason mentioned on the blue screen was: "A clock interrupt was not received on a secondary processor within the allocated time interval". I did ran Windows degugger to debug the reason for the memory dumb. (I am using Windows Vista SP 2, AMD Turion 64 X@ TL-69, 2.00Ghz, 2.00GB Ram, 32 bit Vista. I am trying to install Ubuntu 9.10 in VirtualBox 3.0.10.) This is what I found (see attached windbg file): |
|||
| #735 | fixed | Bridging in Windows XP does not work properly with Wireless adapters | ||
| Description |
Users of Windows XP are unable to create a proper bridge against a VirtualBox Host Interface when a wireless adapter is involved. Windows XP will show that the bridge was created successfully but connectivity is not present. This is due to lack of support for promiscuous mode in the majority of wireless adapters on the market.
A workaround has been identified that will resolve the issue but is not guaranteed to work for everyone.
And documentation in the Technet that mentions how network bridging works in Windows XP |
|||
| #1507 | fixed | internalcommands createrawvmdk fails to register with -register option if destination vmdk is not a full path | ||
| Description |
If you do not specify the full pathname of the destination vmdk file then the -register parameter will fail to actually do the registration. It completes the pathname based on the default location rather than the current location that you are actually at. The vmdk file does get created however and can be registered manually. OS is Windows XP. Output below: E:\DD-WRT>"c:\Program Files\Sun\xVM VirtualBox\VBoxManage.exe" internalcommands createrawvmdk -filename Debian_Raw.vmdk -rawdisk \.\PhysicalDrive1 -partitions 1,5 -register VirtualBox Command Line Management Interface Version 1.6.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. RAW host disk access VMDK file Debian_Raw.vmdk created successfully. [!] FAILED calling aVirtualBox->OpenHardDisk(filename, hardDisk.asOutParam()) at line 1045! [!] Primary RC = E_FAIL (0x80004005) - Unspecified error [!] Full error info present: true , basic error info present: true [!] Result Code = E_FAIL (0x80004005) - Unspecified error [!] Text = VD: error opening image file 'G:\VirtualBox\Debian_Raw.vmdk' (VERR_PATH_NOT_FOUND) [!] Component = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916} [!] Callee = IVirtualBox, {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667} |
|||

