Custom Query (16363 matches)
Results (1186 - 1188 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20731 | duplicate | Windows 10 Menu Not Displaying Properly | ||
| Description |
When I click the start button my Windows 10 menu is transparent. The Icons show up but none of the menu options that appear next are visible. For instance, when you click the Start button and then the Power icon, no options are visible. But, if I click the up arrow on my keyboard twice and hit enter, the computer shuts down. If I right click on an icon, no options appear. This started with VirtualBox-6.1.28-147628-Win and is still true in VirtualBox-6.1.30-148432-Win. I installed the latest GuestAddOns and the latest Expansion Pack during setup. There is also a Windows message about the system searching for a Display Driver. I have screen captures of the symptoms but don't know how to attach them to the case. Hopefully someone can help. |
|||
| #1107 | fixed | Segfault at trying to run a Virtual Machine | ||
| Description |
I'm using a Debian system (Lenny version) with the x86_64 based kernel 2.6.22-3-amd64. I've installed VirtualBox 1.5.4 and all seems to run fine until I try to open a Virtual Machine, then I get a flash and the status showed under the VM name change to "Aborted". The system is not installed yet. Locking the /var/log/messages file, I get the next:
Jan 19 14:58:00 Aragorn kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently... Curiosly, if I run VirtualBox as root, it works right, but the other user is member of "vboxusers" group. Any idea to solve the problem? Thank you Enhy |
|||
| #7526 | obsolete | VBox crashes within minutes of running | ||
| Description |
I'm almost afraid to start any virtual machine now for fear of vm corruption because VB seems to crash just doing anything on my computer. Be it Starting a vm, stopping a vm, the vm just running (any guest) or even just trying to open/close the Virtual Media Manager, VB will crash. It doesn't happen instantly, but it will always happen within a few minutes of VB being launched. I can't seem to pinpoint a single reason as to why this happens. My computer: MacBook Pro 5,5 (Mid-2009) 4GB of RAM Snow Leopard 10.6.4 with the 64-bit kernel activated VirtualBox 3.2.8 This has been happening since 3.1 (or whatever was recent in Jan. 2010) Guests do not have to be running. The VirtualBox program itself can crash, a vm can crash, or they'll both crash. Attached is a list of crashes from VirtualBox and VirtualBoxVM, along with the VBox.log of the last guest that crashed (Fedora 13 32-bit). Crashed happened when I tried to enter seamless mode. I can be doing anything to trigger a crash. |
|||

