Changes between Version 1 and Version 2 of Ticket #22059, comment 19
- Timestamp:
- May 28, 2024 1:58:47 AM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #22059, comment 19
v1 v2 4 4 Thank you very much. I mean if nobody sees it and nobody replies to it after multiple days, except users panicking why their VMs are suddenly have stopped working and Oracle and the VBox Team is silent... 5 5 6 Also the SEO of the bug tracker is so crappy that I decided to post it separately, to link the affected versions and to make google index it properly, as well as giving users' the opportunity to see and read it, as nobody looks into the old versions in a bug tracker (under normal circumstances). 7 8 6 Also the SEO of the bug tracker is so crappy that I decided to post it separately, to link the affected versions and to make google index it properly, as well as giving users' the opportunity to see and read it, nobody looks into the old versions in a bug tracker under normal circumstances. 9 7 10 8 … … 15 13 > Rather than downgrading a workaround is to configure the VM to use a USB 3.0 (xHCI) controller. 16 14 17 Does n't that only work with your vbox extension pack ?15 Does not that only work with your vbox extension pack ? 18 16 19 As far as I know there is no option for USB 3.0 by default, and I even tried thisin my first runs, which did not work. But maybe it works now idk.17 As far as I know, there is no option for USB 3.0 by default. I even tried playing around with the USB Controller (enabling, disabling, switching between the availabe options) in my first runs, which did not work. But maybe it works now idk. 20 18 21 I will not trust new versions of vbox for now. They just break things and sucking performance for such "features". Causing unnecessary efforts.19 **Lessons learned:** I will not trust new versions of vbox for now. They just break things and suck performance for such "features", causing unnecessary efforts. 22 20 23 21 A nice warning popup for the users' would be nice, when their machine can be possibly affected by this issue. Or a auto-fix deployed by VBox.
