Custom Query (16363 matches)
Results (586 - 588 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4534 | duplicate | v2.2.0 vbox run under v3.0.2 but v3.0.2 vbox cause system lockup on solaris 10 | ||
| Description |
After upgrading to v3.0.2 all my existing VBox clients worked correctly (these include CentOS, RHat, SXDE b115, OpenSolaris 2009.06, Win XP) without causing system lock ups on Solaris 10 u5. I also increased the number of CPUs available for SXDE b115 from 1 to 2 without any problems. I then decided to upgrade Solaris Express Developer Edition b117 which would over write the existing b117. However, while attempting to install b117 (with 2 CPUs for the VBox) my desktop locked up and required a power cycle to recover. I tried again and the system locked up at the same point in the b117 installation (after completing 1586.50MB with 5532.08MB to complete). I then attempted to install b117 in the same VBox with 1 CPU, the same thing happen again but much quicker during the installation process, just after 72.11MB installed with 7046.46MB to go. So, I reverted back to SXDE b115 which been previously working under v3.0.2 having been created using v2.2.0. While the installation completed, booting the SXDE b115 VBox resulted in hanging my desktop again!!! What does v3.0.2 do differently when creating a new VBox that v2.2.0 does not? Why does a SXDE b115 Vbox previously created with v2.2.0 work reliably under v3.0.2? |
|||
| #2829 | duplicate | v2.1.0 host interface network crashes RHEL5 host | ||
| Description |
Virtual Box 2.1.0 crashes my RHEL5 host notebook when I start a VM with Host Interface selected.
The notebook crashes with CapsLck & ScrollLck LEDs flashing.
If the network is selected as "not attached", NAT or Internal then the VM starts with no problem. This happens with both a XP guest VM and also an "Other/Unknown" VM that I configure for an Embedded OS. |
|||
| #1177 | duplicate | v1.5.4: Incorrect text cursor colour in guest display when using Crimson editor | ||
| Description |
Guest: Windows XP sp2 Host: Slackware linux 12.0 Application: Crimson Editor v3.70 (freeware) http://www.crimsoneditor.com/ Steps to reproduce: *Install Crimson editor *Run Crimson *From the menu select View -> Set Colors *From the "Load color scheme" drop-down select 'reversed color scheme' *Click "Load" *Close the dialog *Type some text in the editor window Notice that when the mouse cursor is over the text, it is black instead of white, as it would be when running Windows natively. I have run Crimson on a few other machines (always reversed colour scheme and never had this problem. My display depth inside the guest is 32-bit, xorg is running at 24-bit. Unfortunately not being able to locate the cursor inside the editor window of Crimson makes this color scheme almost unusable. I never realised I relied on the mouse so much. |
|||

