Custom Query (16363 matches)
Results (439 - 441 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2148 | wontfix | Problems with http://download.virtualbox.org and wget | ||
| Description |
When downloading from http://download.virtualbox.org via wget, files are saved/proposed with a different name, example for VirtualBox-1.6.6-Linux_x86.run:
url used: http://download.virtualbox.org/virtualbox/1.6.6/VirtualBox-1.6.6-Linux_x86.run this occurs only for all the files actually hosted on dlc-cdn-rd.sun.com. There is a way to fix this issue? under Gentoo wget is used by default from portage to retrieve all the files needed for the installation of a specific package (in this example for virtualbox-bin-1.6.6), and when the files are saved under with different name the digest verification fails. |
|||
| #12300 | fixed | NAT broken since VirtualBox 4.3 => Fixed in SVN | ||
| Description |
I first reported this bug to Arch Linux, here is the original link: https://bugs.archlinux.org/task/37575 Since this bug exists in both OSE (compiled by Arch Linux community) and binary version (compiled by Oracle), IMHO this is a "upstream bug", so I re-post the bug report here. Here is a copy-and-paste of the original bug report: Description: VirtualBox NAT function does not work any more after version 4.3. Instead, it just results in CPU 100% usage in host machine and the whole Qt interface becomes unreponsive. I've tested this on a 2011 HP laptop and a 2013 ThinkPad. The latter one was bought yesterday and had a fresh new installation of Arch Linux + VirtualBox. However, this problem exists regardless of host machine (different laptops) and guest machine (CentOS, Windows XP, Windows 8, etc). Additional info:
Steps to reproduce:
My (in vain) attempt to debug:
I am not very sure if this is a Arch Linux bug or an upstream bug. The changelog of VirtualBox 4.3 *did* mention something about new "NAT Network" function. Maybe the new function broke something... VBox.log (80.4 KiB) Please refer to the original bug report for VBox.log download and see also its comments for follow-up information. I've selected "VirtualBox 4.3.0" in "Version" field, but this bug still exists in 4.3.2. |
|||
| #21045 | invalid | Nested VT-x/AMD-v not working in Linux client | ||
| Description |
Even though I have enabled the Nested VT-x/AMD-v for the client, and my AMD 5800x Windows 11 PC's bios has the SVM feature turned on, but from the Linux client, grep svm from /proc/cpuinfo still return nothing. |
|||

