Custom Query (16363 matches)
Results (805 - 807 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15881 | invalid | After upgrading from 5.0.26 to 5.1.x VM does not boot; boot0: GPT | ||
| Description |
Windows 10 host I've been running a virtual machine with OS-X guest on V4.x and V5.0.x succesfully. After upgrading to 5.1.x (used the latest to date, V5.1.4) I get during boot: boot0: GPT boot0: test boot0: test boot0: done boot0: /boot That's all. No booting up of the VM. HOWEVER, when downgrading to 5.0.26 all works fine again. |
|||
| #6316 | duplicate | After upgrading kernel to 2.6.32-15-generic 64bit VMs run very slowly | ||
| Description |
Host is using VirtualBox 3.1.4 r57640 on Ubuntu Lucid Lynx Development, on 64bit OS with CPU-virtualization, previously created 64bit VM are not usable. Moments prior to the reboot into the new kernel, all VMs where running smoothly. I stopped the boot of a 64bit Guest when 3 minutes had past and the Plymouth progress bar had not completed. 32bit VMs seems to be running fine. Is this a duplicate of ticked 5501? http://www.virtualbox.org/ticket/5501 |
|||
| #3017 | fixed | After upgrading to 2.1.0 (Linux 64bit) network doesn't work between Host and Guests (Host interface) | ||
| Description |
Until version 2.0.6 I could run my VMs (Windows XP, Slackware linux, Netbsd, Openbsd, etc) and make them connect to the Host OS over the network (I always used Host Interface). So I could use ssh, ftp, http, samba shares, etc from the Guest to Host (and vice versa). Now that I upgraded to version 2.1.0 (linux 64bit) I just can't do it. It is like there is something blocking the network between Host and Guests. My firewall rules are the same before and after the upgrade, so that shouldn't be the problem. The Kernel is the same too. It should be noted that my VMs can access my network (other computers) or the Internet. They just can't comunicate to the Host. What can be done to fix this? |
|||

