Custom Query (16363 matches)
Results (544 - 546 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19909 | fixed | macOS:VM crashes after upgrade to 6.1.14 => fixed in svn/6.1.x x>14 | ||
| Description |
OS :macOS 10.15.6 VirtualBox:6.1.14 VM OS : Ubuntu 18.04 LTS When upgraded to 6.1.14, virtualbox will start up normally, but VM crash after startup. After downgrading to 6.1.12, vm can be started. |
|||
| #19904 | invalid | v6.1.14 fails to open for os/2 guest | ||
| Description |
opensuse tumbleweed 20200917 Vbox failed to restore an os/2 4.52 instance after a repo update of Virtualbox from an interim version 6.1.13 (or 6.1.97). The error is shown below. The Display settings are disabled for the guest. Windows guests start normally. Unsupported version 22 of data unit 'vga' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION). I did try to install the 6.1.14 distribution from the Vbox site. It had a dependency failure: "libvpx.so.4()(64bit)". Libvpx6 is installed on this host; adding the devel package made no difference. |
|||
| #19903 | fixed | VBoxService CPU hotplug brings always cpu1 online regardless of plugged CPU => fixed in SVN/next maintenance | ||
| Description |
The code to bring a newly plugged CPU online is seriously wrong, textual description of what is done there:
Actual code is here: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/common/VBoxService/VBoxServiceCpuHotPlug.cpp#L449 Assuming (?) that the directory listing is sorted by name, this will always put cpu1 (and only that!) online. --- Stumbled over this while trying to find out why my CPU (cpu2 ... cpu1 comes before that in the directory listing) isn't online prior to getting it back offline (https://www.virtualbox.org/ticket/19902) |
|||

