Custom Query (16363 matches)
Results (2377 - 2379 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11181 | obsolete | Similar Name of Network Card not showing to DropDown List | ||
| Description | ||||
| #11184 | obsolete | Novell OES v6.5 Does Not Boot Correctly With VirtualBox 4.2.4, Works with 4.1.22 | ||
| Description |
Good day,
1) Utilizing VirtualBox version 4.1.22 my Novell VirtualBox System boots correctly and can be shutdown correctly when sent the "shutdown signal". 2) Upgraded my VirtualBox software to version 4.2.4 and installed the VirtualBox extensions for VirtualBox 4.2.4. 3) Starting this VirtualBox instance with VirtualBox 4.2.4 encounters the following as one of the messages in the boot-up process when acessing the System Console (Esc+Ctrl and Select 1. System Console): "The running process will be returned to the safe state" 4) The system will not finish booting even after leaving sit for an extended period of time, such as 15 minutes or longer and no other output goes to the console. An incorrect shutdown is required to process anything different which also causes a disk check after every boot. 5) Removed VirtualBox 4.2.4 and reinstalled VirtualBox 4.1.22, and downgraded the VirtualBox extension pack to 4.1.22, and the VirtualBox machine works as normal before the upgrade with the same result as (1). I have confirmed that this an issue with the new upgrade and I have not seen this issue with other Operating System (OS) instances that I run in VirtualBox, such as Windows XP or Windows 7 x64.
|
|||
| #11185 | obsolete | Virtual Box install hangs - appears to be conflict with VPN network driver | ||
| Description |
When trying to install Virtual Box on my Dell Win7 64-bit laptop, the install process got near the end and just hung. I checked Process Explorer and the hung thread call stack was the below. ntoskrnl.exeKeWaitForMultipleObjects+0xc0a ntoskrnl.exeKeAcquireSpinLockAtDpcLevel+0x732 ntoskrnl.exeKeWaitForMultipleObjects+0x26a ntoskrnl.exeNtWaitForSingleObject+0x41f ntoskrnl.exeIoReportTargetDeviceChange+0xe6d ntoskrnl.exeKeSynchronizeExecution+0x3a23 wow64cpu.dllTurboDispatchJumpAddressEnd+0x6c0 wow64cpu.dllTurboDispatchJumpAddressEnd+0xf5 wow64.dll!Wow64SystemServiceEx+0x1ce wow64.dll!Wow64LdrpInitialize+0x429 ntdll.dllRtlUniform+0x6e6 ntdll.dllRtlCreateTagHeap+0xa7 ntdll.dllLdrInitializeThunk+0xe ntdll.dllZwWaitForMultipleObjects+0x15 kernel32.dllWaitForMultipleObjectsEx+0x8e msi.dll!MsiEnumProductsW+0x2bf0 msi.dll!MsiReinstallFeatureW+0x2a4 msi.dll!MsiInstallProductA+0xcc VirtualBox-4.2.4-81684-Win.exe+0x1fcf VirtualBox-4.2.4-81684-Win.exe+0x27f4 kernel32.dllBaseThreadInitThunk+0x12 ntdll.dllRtlInitializeExceptionChain+0x63 ntdll.dllRtlInitializeExceptionChain+0x36 I killed the installer and rebooted. I checked device manager and noticed my VPN client network adapter in the list, "NCP Secure Client Virtual NDIS6 Adapter". This is the adapter created by my VPN client. I tried disabling that adapter in device manager and rebooted. After the reboot I tried again to install Virtual Box and this time it worked without hanging. After installing, I re-enabled the VPN network adapter and rebooted again and all appears to be working now. |
|||

