Custom Query (16363 matches)
Results (1240 - 1242 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18079 | obsolete | Incorrect CPU cores detection | ||
| Description |
I have a AMD FX-4100. It's a quad core CPU. I've created new VM for Live Linux. GUI detects only 2 cores. If I try to setup more than 2 cores for VM, GUI says that I've setup more cores, that physically available. I tried to downgrade and gone down all way to somewhere around 4.2.20. GUI there detects cores normally, but when starting VMS it fails with "AMD-V is disabled in the BIOS. (VERR_SVM_DISABLED)." which is not true. Is it possible to fix cores detection by GUI? VM itself seems using all 4 cores. |
|||
| #18078 | fixed | VBox 5.2.20: Linux guest not remembering window size -> fixed after (not in) 5.2.20 | ||
| Description |
Hello, I'm recently upgraded to VBox from 5.2.18 to 5.2.20 on my MacOS X laptop. The laptop is running OS X 10.14 (Mojave). I have both a Linux guest (CentOS 7.5, fully updated) and a Windows guest (Windows 10) that I use regularly for development. As part of updating VBox, I also updated the guest additions on both guests. After the upgrade, I noticed that the Linux guest no longer remembers its windows size when starting from the off state. If I resize the window and reboot the guest, it comes back up with the expected size; however, if I shutdown the guest and start it back up, the window takes a "default" (very small) size. Note that this does not happen with the Windows 10 guest. The Windows 10 guest window is always the expected size whether I reboot it or start it from the off state. This is a regression from 5.2.18, where the guest window for both guest VMs always had the expected size. I did try uninstalling and reinstalling the guest additions on the Linux guest, but that made no difference. I've attached the log from a session where the VM was started from the off state and the guest window came up with the wrong (small) size. |
|||
| #18077 | fixed | Repository 'VirtualBox for Fedora 28 - x86_64' update imposible -> fixed | ||
| Description |
Can't update to 5.2.20 on Fedora 28. Seems to be similar to ticket 18057 but for Fedora instead of opensuse dnf -v --refresh upgrade Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync, system-upgrade DNF version: 2.7.5 cachedir: /var/cache/dnf reviving: 'updates' can be revived - repomd matches. updates: using metadata from Tue 23 Oct 2018 01:55:29 PM MST. reviving: 'fedora' can be revived - repomd matches. not found deltainfo for: Fedora 28 - x86_64 not found updateinfo for: Fedora 28 - x86_64 fedora: using metadata from Tue 24 Apr 2018 09:27:32 PM MST. reviving: failed for 'virtualbox', mismatched repomd. Cannot download 'http://download.virtualbox.org/virtualbox/rpm/fedora/28/x86_64': Yum repo downloading error: Downloading error(s): repodata/8797acb2bdc4a098c1ebade2f11ff827324fddb42bd09973fef46490574f617f-primary.xml.gz - Cannot download, all mirrors were already tried without success. Failed to synchronize cache for repo 'virtualbox', disabling. Last metadata expiration check: 0:00:00 ago on Wed 24 Oct 2018 11:20:56 AM MST. Missing file *modules.yaml in metadata cache dir: /var/cache/dnf/updates-3da4dabc82b8d7a0 Missing file *modules.yaml in metadata cache dir: /var/cache/dnf/fedora-f538a89832a62144 --> Starting dependency resolution --> Finished dependency resolution Dependencies resolved. Nothing to do. Complete! |
|||

