Custom Query (16363 matches)
Results (619 - 621 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19717 | fixed | Storage IO Erros With virtio-scsi Controller When Host I/O Cache is Enabled => fixed in SVN/next 7.0.x and 6.1.x maintenance | ||
| Description |
On Ubuntu Server 20.04 guest in Virtualbox 6.1.2 on a Win10 (2004) host: I've selected the virtio-scsi controller and enabled the host I/O cache option to maximize performance. With this configuration, I see multiple I/O related errors in the guest's shell and dmesg log ("Buffer I/O error on device sda2, logical block xxxxxxx", "I/O error, dev sda, sector yyyyyy op 0x0:(READ) flags 0x80700 phys_seg 20 prio class 0", and many others). On the host's log I see multiple messages like "SCSI#0: Read at offset xxxxxxxxx (4096 bytes left) returned rc=VERR_NOT_IMPLEMENTED". All above errors disappear when host I/O cache is disabled. This seems to have started with Virtualbox 6.1.2. When downgrading to Virtuabox 6.1.0 There are no problems when cache is enabled. Attached are 2 logs for the same machine (created and running on Virtualbox 6.1.2), one with the cache enabled and the other disabled. Any help will be much appreciated. I have reported the problem in the Virtualbox forums:https://forums.virtualbox.org/viewtopic.php?f=3&t=98962, no responses. |
|||
| #19711 | fixed | VB GAs are taking over the guest clipboard even with VB clipboard functionality disabled. => Fixed in SVN | ||
| Description |
Although this issue is literally driving our team nuts I'm afraid we are out of time to invest in it right now. I am therefore providing the closing status of the virtual box forum discussion in the hope that the Oracle VB Dev team agree that it is a serious issue and resolve it. (further detail and uploaded information can be found on the virtual box forum discussion here: https://forums.virtualbox.org/viewtopic.php?f=3&t=97718&start=15) Closing status from my perspective:
My closing observations to the Virtual Box development team should they ever read this:
Again @scottgus1 - thank you so much for your efforts and help on this topic, I can only hope Oracle put the effort in to correct this. |
|||
| #19706 | fixed | MacOS hosts no longer able to run VBoxHeadless as of 6.0.18 and 6.1.4 => fixed in svn/6.1.x x>12 | ||
| Description |
It is impossible to launch a VM in headless mode because of a problem of setugid which is not allowed. It works fine with VirtualBox 6.1.2 but not with the following versions. The error message seen is: $ /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless -s solaris Oracle VM VirtualBox Headless Interface 6.1.4 (C) 2008-2020 Oracle Corporation All rights reserved. 2020-07-24 09:40:25.798 VBoxHeadless[2026:18559] The application with bundle ID org.virtualbox.app.VirtualBox is running setugid(), which is not allowed. |
|||

