Custom Query (16363 matches)
Results (1891 - 1893 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15392 | fixed | Virtualbox interprets commented lines in resolv.conf | ||
| Description |
When installing 5.0.18 (and then 5.0.20) I found that I couldn't use DNS from an installed Debian client (it couldn't access the repos). I tracked the internet traffic with Wireshark, and found it was using DNS IPs I had commented in the host's resolv.conf long ago. The lines were commented with semi-colons (;) as instructed in the resolv.conf man-page. Sure enough, changing the order of lines, changed the order of the lines, changed the order of DNS requests. Putting valid IPs in front, made the appear, and made the Debian install work correctly. I also confirmed this by cat /etc/resolv.conf in the client. (It's necessary to disconnect/reconnect the network to read the re-read the host's resolv.conf. |
|||
| #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. |
|||
| #15346 | worksforme | Windows 8.1 guest boot failure after Microsoft 4/14 update | ||
| Description |
After a Windows 8.1 guest takes the April 14 updates from Microsoft and restarts it fails during boot: Your PC needs to restart. Please hold down the power button. Error Code: 0x00000100 Parameters: 0x0000000000000006 0x0000000000000003 0x0000000000000128 0x0000000000000988 |
|||

