Custom Query (16363 matches)
Results (421 - 423 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12371 | fixed | Empty password not accepted by VBoxManage in 4.3 => Fixed in SVN | ||
| Description |
The changes introduced in to GuestCtrlImpl.cpp by r47469 (https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-client/GuestCtrlImpl.cpp?rev=47469#L465) prevent VBoxManage from accepting an empty password. An empty password has always been allowed before, although possibly not supported by the guest OS. I saw no mention of this change in the change log. On a personal note, this change breaks most of ievms: http://git.io/ievms |
|||
| #2239 | fixed | Guru meditation when running a dos application | ||
| Description |
as you see in the .png file when i tried to execute the dos program that we wrote virtual box stops responding then stops running. i attached the .png and .log files. |
|||
| #11913 | fixed | AMD E-350 i686 error | ||
| Description |
My PC config: MB: GA-E350N WIN 8 (rev.1.0) CPU: AMD E-350D RAM: 8GB DDR3 1333 SSD: 120GB OS: Windows 7 Ultimate x64 SP1 When I try to start any VM to boot, I got this error: This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU. [!] SVM Mode is enabled from BIOS! I searched for any other virtualization settings in BIOS but I didn't found. I tried also to install ESXi and PROXMOX on my PC and I received some errors that says I haven't virtualization enabled in BIOS. It's weird! I checked CPU capabilities by typing egrep '(vmx|svm)' --color=always /proc/cpuinfo and I have SVM feature displayed. Please help me with this annoying problem. I bought this PC because I saw that this low consumption CPU supports virtualization. Thank You in advance! BR, Danny. |
|||

