4 ms·

VirtualBox is in maintenance mode. Nothing cool has happened in the past few years. This release is not noteworthy.

by tcrews 10y ago

mfisher87 10y ago
First thing I saw when I clicked the link: "This is a maintenance release." Second thing I noticed: "(released 2016-10-18)". It's not new nor noteworthy. :\
kyriakos 10y ago
what new features should it get? its a serious question, i cant think of anything
- tcrews 10y ago
  Better shared folders and 3D acceleration would be a good start. They are completely broken and/or missing important features. The community has no interest in maintaining VirtualBox, mostly because of Oracle. It's a dead project just like OpenOffice, OpenSolaris, etc. One day, enough customers will stop paying Oracle for it, they will look at community contributions (rare to nonexistent?) and will close the project down rationalizing it as they did all the work. The reality is, they don't know how to steer open source projects and have no desire to do that anyway (separate private bug tracker? write access to repository only to Oracle employees? harsh email replies and comments on bug reports?). It's on life support and will stay like that for a little while. Unfortunately, it's the only hypervisor that vagrant supports decently and it works on Mac OS X, Windows and Linux (as opposed to using KVM on Linux, xhyve on OSX and Hyper-V on Windows... for someone considering building vagrant boxes). It's sad but completely expected.
  - kyriakos 10y ago
    can it be forked or the license is too restrictive?
    - pmontra 10y ago
      GPL2 https://www.virtualbox.org/wiki/Licensing_FAQ https://www.virtualbox.org/wiki/Licensing_FAQ
    - cyphar 10y ago
      It's GPLv2 but I remember there was some license issue with some of the addons, or the build process (I can't remember).
  - oridecon 10y ago
    Is there a good article that explains why is so hard to properly do 3D acceleration in a VM? And why is it so hard to do GPU passthrough? And if there's any hope this might improve significantly, let's say 70~90% of native GPU performance. I understand you need compatible hardware and NVIDIA makes it harder just to sell cards that are more expensive. Maybe you have some insight. Off-topic: You go in one of those Linux boards and they all say it's so easy to do it. I mean, yes, I can follow instructions and make it work but it's so cumbersome for every day usage if you want to use a Windows guest. Death by a thousand paper cuts. I don't have the time or patience to use weird setups in my work desktop anymore. To think about it, I did some pretty crazy stuff a few years ago, I'm surprised I wasn't even fired back then. The Linux equivalent of betting your income on a Hackintosh. Kinda like anything Linux related. Don't get me wrong, all my servers are using some variation of it, but when it comes to UX (I'm not talking about GUI) and desktop stuff (not only games but anything GPU related) I wish some things were more mature.
    - pizza234 10y ago
      I've extensively tried and finally succesfully setup a VGA passthrough, so I'll chime in. > why is so hard to properly do 3D acceleration in a VM? I don't have a precisely informed answer to this, but I think it's simply because GPUs do not support/accelerate virtualization in hardware. > And why is it so hard to do GPU passthrough? Now the interesting bit! The core problem is that VGA passthrough requires an extensive collaboration of software and hardware parts, I believe significantly more than CPU virtualization. As a matter of fact, the term "GPU passthrough" is inappropriate/imprecise - you pass an entire card (hence, "VGA passthrough"). I'll enumerate a few critical examples: - in real world, you can't reliably transfer ownership of the VGA from the driver to VFIO¹; this means that if you want a stable VGA passthrough, you need to lock it at boot time, and renounce using it on the host - the software matured only very recently. around an year ago, QEMU had a bug which prevented Windows 7 (without a hack) to perform an installation; until Yakkety, the precompiled UEFI firmware had a bug which prevented Windows 10 to perform an installation; locking devices is something that has been introduced (I think, not sure) no early than an year ago in the kernel - there are many tweaks on the host which can radically affect the guest performance (eg. if you don't disable nested paging on [some] AMD systems, you will get CPU speed down to 30% of native; this will destroy the GPU performance) - nVidia blocks VGA passthrough on consumer machines (it can be worked around easily), and it blatantly lies about it - IOMMUs associated with their support in the BIOS may be buggy - not all the IOMMUs support the conditions required to make VGA passthrough work out of the box - even if all the factors apply, you may still have a system which severely underperforms without any understandable reason. There isn't a central, comprehensive, up to date, documentation, this is true. All of this factors are not really domain of the hypervisor; of course they could be integrated, but not in a consistent, safe way. Now the good part! If you have a proper system (both in HW and SW), VGA passthrough rocks; I get almost native performance (I can't distinguish native from virtual), it's perfectly stable (doesn't crash and I can execute it multiple times a day), and I launch it in a single command. As a matter of fact, I've entirely removed Windows from my disk (modern/high end motherboards support BIOS updating directly from a USB memory). I think it's important to clarify that the problems of VGA passthrough are radically different from the ones of Hackintosh. Mac O/S is not designed to run on hypervisors unless certain conditions are met (the absence of such conditions being defined as "Hackintosh"), and hypervisors can't officially support conditions other than those. In other words, Hackintosh is something that is not supposed to exist. VGA passthough on the other hand is something that is supposed to exist and work, it's just very much dependent on the hardware support, and both HW and SW just very recently matured. What people I think get wrong is that they think VGA passthrough as a function of the software. When the HW support is not there, like in your experience, you will die of a thousand paper cuts. If one thinks VGA passthrough as a matter of hardware instead, then it will work wonderfully. So if you really want to get rid of that nasty Windows partition (oh yeah!) you should start with the correct HW, then the SW will work butter smooth. ¹=on large scale. of course, there will be systems where one can.
- nwah1 10y ago
  Performance optimization, using the latest instruction sets. Wayland support. Improved 3D drivers with full Vulkan support and maybe DirectX via Gallium3D. Fully open source drivers for all common hardware, so no more need for the extension pack. Update to Python 3.
  - skeptic2718 10y ago
    Lack of Wayland support is going to hit Fedora 25 users hard very soon. It's completely unusable if Wayland is enabled.
- sixothree 10y ago
  I would like it to do something other than cut the power to my VMs when the host system shuts down or reboots.
- stonogo 10y ago
  Stability. Every maintenance release is filled with special-cased 'fixes' that wind up breaking something else, calling for the next round of special-cased 'fixes', ad infinitum. We've completely abandoned it for kvm and docker because we got tired of having our test platform broken with each patch release. Since we left virtualbox behind, all of our partners have had an easier time replicating our environment reliably.
- briansteffens 10y ago
  I'd like VMX passthrough for nested virtualization.
vic-traill 10y ago
Better USB device support. I've had to flip to VMWare for packaging usb-related software for deployment purposes. USB detection and function is hit and miss. This is just my own experience, but I will say that when you attempt to find solutions to this sort of issue, one encounters a lot of posts from folks looking for the same thing. And not many answers. I'd be happy for someone here to tell me I'm wrong and point me in the right direction. Edit: replied to a parent not the correct child. My bad.
deleted 10y ago
[deleted]

VirtualBox is in maintenance mode. Nothing cool has happened in the past few years. This release is not noteworthy.

by tcrews 10y ago

VirtualBox is in maintenance mode. Nothing cool has happened in the past few years. This release is not noteworthy.

First thing I saw when I clicked the link: "This is a maintenance release." Second thing I noticed: "(released 2016-10-18)". It's not new nor noteworthy. :\

kyriakos 10y ago

what new features should it get? its a serious question, i cant think of anything

tcrews 10y ago
Better shared folders and 3D acceleration would be a good start. They are completely broken and/or missing important features. The community has no interest in maintaining VirtualBox, mostly because of Oracle. It's a dead project just like OpenOffice, OpenSolaris, etc. One day, enough customers will stop paying Oracle for it, they will look at community contributions (rare to nonexistent?) and will close the project down rationalizing it as they did all the work. The reality is, they don't know how to steer open source projects and have no desire to do that anyway (separate private bug tracker? write access to repository only to Oracle employees? harsh email replies and comments on bug reports?). It's on life support and will stay like that for a little while. Unfortunately, it's the only hypervisor that vagrant supports decently and it works on Mac OS X, Windows and Linux (as opposed to using KVM on Linux, xhyve on OSX and Hyper-V on Windows... for someone considering building vagrant boxes). It's sad but completely expected.
- kyriakos 10y ago
  can it be forked or the license is too restrictive?
  - pmontra 10y ago
    GPL2 https://www.virtualbox.org/wiki/Licensing_FAQ https://www.virtualbox.org/wiki/Licensing_FAQ
  - cyphar 10y ago
    It's GPLv2 but I remember there was some license issue with some of the addons, or the build process (I can't remember).
- oridecon 10y ago
  Is there a good article that explains why is so hard to properly do 3D acceleration in a VM? And why is it so hard to do GPU passthrough? And if there's any hope this might improve significantly, let's say 70~90% of native GPU performance. I understand you need compatible hardware and NVIDIA makes it harder just to sell cards that are more expensive. Maybe you have some insight. Off-topic: You go in one of those Linux boards and they all say it's so easy to do it. I mean, yes, I can follow instructions and make it work but it's so cumbersome for every day usage if you want to use a Windows guest. Death by a thousand paper cuts. I don't have the time or patience to use weird setups in my work desktop anymore. To think about it, I did some pretty crazy stuff a few years ago, I'm surprised I wasn't even fired back then. The Linux equivalent of betting your income on a Hackintosh. Kinda like anything Linux related. Don't get me wrong, all my servers are using some variation of it, but when it comes to UX (I'm not talking about GUI) and desktop stuff (not only games but anything GPU related) I wish some things were more mature.
  - pizza234 10y ago
    I've extensively tried and finally succesfully setup a VGA passthrough, so I'll chime in. > why is so hard to properly do 3D acceleration in a VM? I don't have a precisely informed answer to this, but I think it's simply because GPUs do not support/accelerate virtualization in hardware. > And why is it so hard to do GPU passthrough? Now the interesting bit! The core problem is that VGA passthrough requires an extensive collaboration of software and hardware parts, I believe significantly more than CPU virtualization. As a matter of fact, the term "GPU passthrough" is inappropriate/imprecise - you pass an entire card (hence, "VGA passthrough"). I'll enumerate a few critical examples: - in real world, you can't reliably transfer ownership of the VGA from the driver to VFIO¹; this means that if you want a stable VGA passthrough, you need to lock it at boot time, and renounce using it on the host - the software matured only very recently. around an year ago, QEMU had a bug which prevented Windows 7 (without a hack) to perform an installation; until Yakkety, the precompiled UEFI firmware had a bug which prevented Windows 10 to perform an installation; locking devices is something that has been introduced (I think, not sure) no early than an year ago in the kernel - there are many tweaks on the host which can radically affect the guest performance (eg. if you don't disable nested paging on [some] AMD systems, you will get CPU speed down to 30% of native; this will destroy the GPU performance) - nVidia blocks VGA passthrough on consumer machines (it can be worked around easily), and it blatantly lies about it - IOMMUs associated with their support in the BIOS may be buggy - not all the IOMMUs support the conditions required to make VGA passthrough work out of the box - even if all the factors apply, you may still have a system which severely underperforms without any understandable reason. There isn't a central, comprehensive, up to date, documentation, this is true. All of this factors are not really domain of the hypervisor; of course they could be integrated, but not in a consistent, safe way. Now the good part! If you have a proper system (both in HW and SW), VGA passthrough rocks; I get almost native performance (I can't distinguish native from virtual), it's perfectly stable (doesn't crash and I can execute it multiple times a day), and I launch it in a single command. As a matter of fact, I've entirely removed Windows from my disk (modern/high end motherboards support BIOS updating directly from a USB memory). I think it's important to clarify that the problems of VGA passthrough are radically different from the ones of Hackintosh. Mac O/S is not designed to run on hypervisors unless certain conditions are met (the absence of such conditions being defined as "Hackintosh"), and hypervisors can't officially support conditions other than those. In other words, Hackintosh is something that is not supposed to exist. VGA passthough on the other hand is something that is supposed to exist and work, it's just very much dependent on the hardware support, and both HW and SW just very recently matured. What people I think get wrong is that they think VGA passthrough as a function of the software. When the HW support is not there, like in your experience, you will die of a thousand paper cuts. If one thinks VGA passthrough as a matter of hardware instead, then it will work wonderfully. So if you really want to get rid of that nasty Windows partition (oh yeah!) you should start with the correct HW, then the SW will work butter smooth. ¹=on large scale. of course, there will be systems where one can.
nwah1 10y ago
Performance optimization, using the latest instruction sets. Wayland support. Improved 3D drivers with full Vulkan support and maybe DirectX via Gallium3D. Fully open source drivers for all common hardware, so no more need for the extension pack. Update to Python 3.
- skeptic2718 10y ago
  Lack of Wayland support is going to hit Fedora 25 users hard very soon. It's completely unusable if Wayland is enabled.
sixothree 10y ago
I would like it to do something other than cut the power to my VMs when the host system shuts down or reboots.
stonogo 10y ago
Stability. Every maintenance release is filled with special-cased 'fixes' that wind up breaking something else, calling for the next round of special-cased 'fixes', ad infinitum. We've completely abandoned it for kvm and docker because we got tired of having our test platform broken with each patch release. Since we left virtualbox behind, all of our partners have had an easier time replicating our environment reliably.
briansteffens 10y ago
I'd like VMX passthrough for nested virtualization.

vic-traill 10y ago

Better USB device support. I've had to flip to VMWare for packaging usb-related software for deployment purposes. USB detection and function is hit and miss. This is just my own experience, but I will say that when you attempt to find solutions to this sort of issue, one encounters a lot of posts from folks looking for the same thing. And not many answers. I'd be happy for someone here to tell me I'm wrong and point me in the right direction. Edit: replied to a parent not the correct child. My bad.

deleted 10y ago

[deleted]