News for hackers. Stuff that matters.
Re:VirtualBox 6.0 released by robert_foss on Thursday December 20, 2018 @07:03AM (#18724174)
Avoid VirtualBox and becoming trapped in the non-free & personal use only extension by using one of the very decent open source alternatives Boxes[1] or virt-manager[2]

[1] https://wiki.gnome.org/action/show/Apps/Boxes

[2] https://virt-manager.org/

Re:VirtualBox 6.0 released by organsnyder on Thursday December 20, 2018 @10:05AM (#18725451)
Even worse: Oracle is going around and threatening to sue enterprises that show traffic to the extensions download site from their IP blocks. Happened recently at a previous employer of mine.
Re:VirtualBox 6.0 released by danmg on Thursday December 20, 2018 @11:53AM (#18726533)
Solution: null route *.oracle.com.
Re:VirtualBox 6.0 released by setquk on Thursday December 20, 2018 @10:14AM (#18725526)
Any public references for this anywhere?
Re:VirtualBox 6.0 released by chomp on Thursday December 20, 2018 @10:58AM (#18725973)
Personal anecdote: They came after us, since the extension phones home and they could track it to our ASN. Asked us for an audit of all installs of VB. The idea was that they wanted to then charge us big money for a corporate license.

Instead, IT banned it enterprise-wide. Which is sad, because we like it for Vagrant. We've since started moving all of our developer stuff to OpenShift, so we're not totally up a creek.

Re:VirtualBox 6.0 released by lambda on Thursday December 20, 2018 @01:03PM (#18727305)
Oh, wow. They've also changed the license a couple of times in 2016 and 2017 to make it more restrictive.

Early 2016: https://web.archive.org/web/20160411070811/https://www.virtu... Late 2016: https://web.archive.org/web/20161208112443/https://www.virtu... Current, last changed July 2017: https://www.virtualbox.org/wiki/VirtualBox_PUEL

In the earlier licenses, "personal use" was just defined as the person using it being the same person as who installed it, and only one person remotely accessing the desktop at a time. So I had interpreted this as being OK for developer VMs in which the developer installs it themselves and uses it for their own development purposes. It also contained an "evaluation use" with a vaguely defined period.

The current license now defines "personal use" as explicitly non-commercial use, and adds more restrictions on client access that applies to any type of clients and not just remote desktop access, as well as explicitly defining the evaluation use period to being 30 days.

So while I didn't really have a concern about developers using VirtualBox with the extension pack previously, given the new license and the fact that they seem to be enforcing it via phoning home, it looks like it's time to set a policy of no one using it.

Luckily, we've already pretty much transitioned everything over to libvirt/KVM on Linux hosts, and people have generally been using VMWare or VMWare Fusion on Windows and Mac hosts.

Re:VirtualBox 6.0 released by arminiusreturns on Thursday December 20, 2018 @11:07AM (#18726059)
I have a devops guy trying to push me to use Vagrant at the moment, but I am aware of these issues with virtualbox. I was thinking about using one of the lxc shims, but now you have me curious, how useful is openshift in that "I want to spin local vms up for testing" approach? I thought it was much more geared to server and not workstation, as opposed to vagrant.

Of course others are right, virt-manager is probably a better replacement I think.

Re:VirtualBox 6.0 released by chomp on Thursday December 20, 2018 @12:30PM (#18726969)
So OpenShift (or OKD) is just Redhat's Kubernetes platform. If your dev team isn't already in a docker-like workflow, it's going to be a hard sell. I've found many devops-y people love to be able to SSH into the environment to change code as it runs, and that's not possible with an environment like this.

You can spin up KVMs in OpenShift, but I have the feeling it's not going to be quite what you're looking for. I suppose it's all going to be a matter of what workflow is most comfortable for your devops people. If you have an OpenStack install, Vagrant can control those AND they can login and poke around.

Also FYI virt-manager is deprecated in RHEL 8, and is superceded by Cockpit.

Re:VirtualBox 6.0 released by nullify88 on Thursday December 20, 2018 @02:29PM (#18728216)
Out of curiosity, what feature in the extension pack are you using with Vagrant?
Re:VirtualBox 6.0 released by setquk on Saturday December 22, 2018 @01:06PM (#18741691)
USB pass through support to drive hardware debuggers here.
Re:VirtualBox 6.0 released by arminiusreturns on Friday December 21, 2018 @08:26PM (#18738274)
PXE booting mostly.
Re:VirtualBox 6.0 released by plq on Thursday December 20, 2018 @12:39PM (#18727065)
Why not use KVM via vagrant-libvirt? It's pretty easy to set up and works like a charm. See https://news.ycombinator.com/item?id=18727059
Re:VirtualBox 6.0 released by chomp on Thursday December 20, 2018 @01:27PM (#18727571)
So one problem with that is not all of our team uses Linux, we're a Mac/Linux hybrid team. Our workflow was to edit the puppet manifests locally and then Vagrant up, and we wanted something that would work across different dev machines. However, the fussiness of environment setup started to go higher the further we got from VBox; our team didn't really want to invest time into a workflow that was supposed to be an intermediate step to our "end game" development pipeline, so we just left it. Thanks for the link though!
Re:VirtualBox 6.0 released by ergo14 on Thursday December 20, 2018 @03:29PM (#18728821)
You can have mixed provider vagrant files.
Re:VirtualBox 6.0 released by alpinewinter on Thursday December 20, 2018 @10:50AM (#18725887)
I don't know of any public references, but I can confirm this is happening to government entities as well. Oracle is being extremely aggressive and mounting what is essentially a phishing campaign against organizations that it sees accessing the extension download page. They are e-mailing employees directly and asking them to contact Oracle.
Re:VirtualBox 6.0 released by gruez on Thursday December 20, 2018 @11:10AM (#18726091)
>Oracle is being extremely aggressive and mounting what is essentially a phishing campaign against organizations that it sees accessing the extension download page. They are e-mailing employees directly and asking them to contact Oracle.

You have a very broad definition of "phishing".

Re:VirtualBox 6.0 released by jstarfish on Thursday December 20, 2018 @01:11PM (#18727384)
Spamming employees with officious emails and hoping one of them is dumb enough to respond with pertinent information that subverts them or their organization is the textbook definition of phishing. What does it mean to you?
Re:VirtualBox 6.0 released by gruez on Thursday December 20, 2018 @01:39PM (#18727697)
from wikipedia:

>Phishing is the fraudulent attempt to obtain sensitive information such as usernames, passwords and credit card details by disguising as a trustworthy entity in an electronic communication

"using virtualbox" isn't sensitive information. I haven't read the emails, but I doubt Oracle is disguising themselves as the company's IT department or something.

Re:VirtualBox 6.0 released by jstarfish on Thursday December 20, 2018 @02:33PM (#18728278)
If you don't think information that subjects an entity to massive legal liability is sensitive, then I really don't understand where you're coming from.

The entire point of these emails is to bypass established channels by getting random employees to leak information. If they want licensing information, there's an IT point of contact for that. Or Contracts. Or Legal. They are literally fishing for information leakage that would give them grounds to sue.

> I doubt Oracle is disguising themselves as the company's IT department or something.

They wouldn't. At this stage the point is to convey a false sense of authority without being outright fraud. You have to wrap everything in vague but threatening insinuations-- "help us or you could face fines of up to a bazillion dollars, and/or you might go to JAIL."

Re:VirtualBox 6.0 released by Dylan16807 on Thursday December 20, 2018 @04:18PM (#18729212)
The key words are fraudulently and by disguising as a trustworthy entity. If they clearly identify themselves as oracle, asking about virtualbox usage, then it's not phishing.

> They are literally fishing

You can "fish for info" in a hundred ways. Only a small subset of that is "phishing".

Re:VirtualBox 6.0 released by gruez on Thursday December 20, 2018 @03:01PM (#18728579)
>If you don't think information that subjects an entity to massive legal liability is sensitive, then I really don't understand where you're coming from.

The employees were already subjecting their company to legal liability when they were using unlicensed software.

>The entire point of these emails is to bypass established channels by getting random employees to leak information. If they want licensing information, there's an IT point of contact for that. Or Contracts. Or Legal. They are literally fishing for information leakage that would give them grounds to sue.

So if I'm Oracle and I'm trying to find unlicensed enterprise users, what am I supposed to do? Call up their IT/legal department and hope that they'll investigate for me, and respond with a truthful response? Is Oracle not allowed to investigate on their own for licensing infractions? I feel like the only reason people are up in arms about this is because Oracle is doing it. If some startup was doing this to discover that some big corp was not paying their licensing fees, no one would blink an eye.

>They wouldn't. At this stage the point is to convey a false sense of authority without being outright fraud. You have to wrap everything in vague but threatening insinuations-- "help us or you could face fines of up to a bazillion dollars, and/or you might go to JAIL."

Sure, but cops do the same thing (if not more). I'm not saying either is okay, but both are not "phishing".

Re:VirtualBox 6.0 released by phamilton on Thursday December 20, 2018 @12:30PM (#18726968)
> They are e-mailing employees directly and asking them to contact Oracle

That would certainly look a lot like phishing

Re:VirtualBox 6.0 released by tracker1 on Thursday December 20, 2018 @01:07PM (#18727337)
In this case, I think it's actual fishing...
Re:VirtualBox 6.0 released by gruez on Thursday December 20, 2018 @01:41PM (#18727711)
So 90% of cold-call recruiting/sales is also "phishing"?
Re:VirtualBox 6.0 released by TeMPOraL on Thursday December 20, 2018 @02:46PM (#18728434)
I'd say "yes". If a cold-call results in anything than blacklisting the company that called you, you're setting yourself up for failure.
Re:VirtualBox 6.0 released by mynameisvlad on Thursday December 20, 2018 @01:49PM (#18727776)
Those are completely different.

One is "Hi my name is XYZ at company ABC. Do you want to talk about our product DEF?" to which you instantly know it's a sales call and how to respond.

The other is specifically emailing employees asking about their use in order to build a case against their employer in the hopes of getting an enterprise agreement or lawsuit out of it. It's far more shady and the actual nature of the communication is not revealed until after the fact. For all the developer knows, it's just a support email from Oracle asking them about how they use their product.

Re:VirtualBox 6.0 released by Dylan16807 on Thursday December 20, 2018 @04:20PM (#18729222)
Whether the intent is positive or negative is unrelated to whether it's phishing. You could phish someone's info and then send them a gift basket.
Re:VirtualBox 6.0 released by mynameisvlad on Thursday December 20, 2018 @06:12PM (#18730099)
Let me clear it up for you:

"Hello my name is X I would like to sell you Y" is not phishing. It's not asking for any information. It's annoying, sure, but you know how to deal with it and they won't bother continuing when they know you're not interested (ie. by saying no)

"Hello my name is X, I work at Oracle, do you have a few minutes to talk about your use of VirtualBox" followed by asking questions about how you use it in order to build a case against your employer can be perceived as phishing. They are either outright not representing or misrepresenting the purpose of the conversation, and asking for information for purposes other than what you'd expect. It doesn't fit the exact definition in the dictionary, but it's close enough and uses the same sort of tactics that it can easily be considered another example of it.

Re:VirtualBox 6.0 released by Dylan16807 on Thursday December 20, 2018 @06:46PM (#18730298)
I don't think the purpose of the conversation matters. It's about if/how you fake your identity and what information/access you collect.

That's why I bring up phishing personal info to send a gift basket. Despite flipping the purpose on its head, it's still phishing.

Re:VirtualBox 6.0 released by mynameisvlad on Thursday December 20, 2018 @07:18PM (#18730470)
The misrepresentation of the purpose is what brings it into phishing territory. By misrepresenting the purpose, you're also misrepresenting who you are and what your intentions are.

Something that's already phishing will still be phishing even if the purpose is misrepresented. Something that isn't otherwise phishing, however, can be made into something akin to phishing by misrepresenting the purpose.

Re:VirtualBox 6.0 released by jasonlotito on Friday December 21, 2018 @12:19PM (#18734738)
> The misrepresentation of the purpose

Incorrect. It's not about purpose. It's about misrepresenting who you are. Oracle is saying they are Oracle. If Oracle is pretending to be someone else, than it's phishing.

What you are describing is not phishing. It's just regular old fishing.

Re:VirtualBox 6.0 released by Dylan16807 on Thursday December 20, 2018 @07:22PM (#18730487)
> By misrepresenting the purpose, you're also misrepresenting who you are

Wha?

Re:VirtualBox 6.0 released by mynameisvlad on Thursday December 20, 2018 @07:59PM (#18730660)
Maybe this got lost halfway down this comment thread, but the whole point of this being considered phishing-like is that Oracle was emailing individual developers, asking questions about their use. The developers didn't realize so that Oracle can build a case against their employer and accidentally gave away details that Oracle would then use to pressure the employer to get licenses or would outright sue.

Developers likely thought they were speaking to Support, or responding to some kind of survey/questionnaire about their use cases and how they use VirtualBox, when in reality were being misled as to the actual purpose of the conversation.

Just because they were speaking to someone from Oracle as opposed to a third party scammer does not mean that the person they were speaking with didn't misrepresent/fake who they were.

Re:VirtualBox 6.0 released by alpinewinter on Thursday December 20, 2018 @12:55PM (#18727206)
Probably not the strict definition, but they are looking for information from employees they can use as leverage or in a lawsuit against the organization.
Re:VirtualBox 6.0 released by paulie_a on Thursday December 20, 2018 @11:19AM (#18726184)
I would definitely contact them. But they would not appreciate the reply.
Re:VirtualBox 6.0 released by mattferderer on Thursday December 20, 2018 @03:27PM (#18728802)
My last enterprise I worked at sent out an announcement that anyone with VirtualBox had to remove it.

What amazed me was when I first started there & asked if I could install it, most everyone was clueless what it even was. So Oracle had to have done some audit that found it, because I don't believe more than 1 or 2 other people would have been using it.

Re:VirtualBox 6.0 released by zaphirplane on Friday December 21, 2018 @02:24AM (#18731922)
Wow so those enterprises are paying massive money for consultants, Realestate, ms-office/windows, databases, CMS, ERP ... etc But don’t want to pay for using the VB extensions. The horror of it. No sympathy today
Re:VirtualBox 6.0 released by badsectoracula on Thursday December 20, 2018 @11:16AM (#18726160)
I do not understand, Virtual Box is free software, the versions distributed through most common Linux distributions does not contain any non-free components and the binaries on the site are released under the GPLv2. The extensions you mention are a separate download that you explicitly have to download and it is mentioned around the download that they are under a different license.

How exactly are you trapped by using GPL software?

Re:VirtualBox 6.0 released by tlrobinson on Thursday December 20, 2018 @11:34AM (#18726329)
From another comment it sounds like it's the Extension Pack they're going after.

> The VirtualBox Extension Pack is available under the VirtualBox Extension Pack Personal Use and Evaluation License, which is a free license for personal, educational or evaluation use, or an Enterprise License, which is a for-fee license that allows most commercial, non-distribution uses restricted by the PUEL.

Re:VirtualBox 6.0 released by NullPrefix on Thursday December 20, 2018 @11:30AM (#18726282)
Without the extension VirtualBox VMs are pretty much shit.
Re:VirtualBox 6.0 released by jstarfish on Thursday December 20, 2018 @01:28PM (#18727577)
Extensions add "support for USB 2.0 and USB 3.0 devices, VirtualBox RDP, disk encryption, NVMe and PXE boot for Intel cards."

I'd argue the added features themselves are mostly shit. If you need hypervisor RDP or FDE there are much better solutions than VirtualBox.

Re:VirtualBox 6.0 released by Drdrdrq on Thursday December 20, 2018 @02:47PM (#18728441)
I don't care much about other features either, but accessing USB devices is often invaluable.
Re:VirtualBox 6.0 released by Dylan16807 on Thursday December 20, 2018 @04:23PM (#18729251)
Often? For what kind of device? Input devices don't need to be fast, and storage is usually better off with a shared folder anyway.
Re:VirtualBox 6.0 released by tsomctl on Thursday December 20, 2018 @07:35PM (#18730562)
There’s lots of other hardware that people use. For example, the usb cable to connect to my BMW needs usb 2.0, and the software only works under Windows XP, so I have a virtual machine for that.
Re:VirtualBox 6.0 released by rbanffy on Thursday December 20, 2018 @11:37AM (#18726357)
For tools like Vagrant, not at all. They are very useful if you want to attach USB devices directly to the VM, use the built-in webcam and so on, but I've used VirtualBox for years without installing the extension once.
Re:VirtualBox 6.0 released by torstenvl on Thursday December 20, 2018 @11:45AM (#18726449)
USB 2.0 and 3.0 are not fully supported without the extension pack.
Re:VirtualBox 6.0 released by koolba on Thursday December 20, 2018 @12:20PM (#18726865)
Which again are irrelevant for the common “just for Vagrant” use case.
Re:VirtualBox 6.0 released by rbanffy on Friday December 21, 2018 @05:58AM (#18732610)
I have used it for testing on different Windows browsers, to check whether https://github.com/rbanffy/3270font would install correctly, and running some Windows software from my bank. The only time I needed the extensions was when I needed to reflash my Blackberry 10 DevAlpha (whose battery, sadly, is dead - I loved that phone)
Re:VirtualBox 6.0 released by noselasd on Thursday December 20, 2018 @01:21PM (#18727499)
How so ? (don't confuse the extension pack with the guest addons though)
Re:VirtualBox 6.0 released by robin_reala on Thursday December 20, 2018 @07:27AM (#18724313)
Linux only by the looks of things though.
Re:VirtualBox 6.0 released by lloeki on Thursday December 20, 2018 @08:04AM (#18724539)
The equivalent on macOS would leverage Hypervisor.framework, like xhyve or Veertu.

https://github.com/machyve/xhyve

https://veertu.com/anka-technology/#hypervisor

Re:VirtualBox 6.0 released by wlesieutre on Thursday December 20, 2018 @11:39AM (#18726383)
I gather that Veertu has (had?) a product called Veertu Desktop and it was open sourced, but they've wiped any mention of it from their website in favor of Anka Flow/Device/Build (commercial license only).

This looks like the source, found in a github repo of someone who works for Cisco. Maybe a former Veertu employee, or just someone who happened to fork a copy before Veertu deleted it? At any rate, I can't find an official Veertu repo anymore. https://github.com/tithomas1/vdhh

Last updates were 2 years ago and the installation instructions say "To Install Veertu Desktop on Mac, please visit veertu.com" which has deleted everything related to Veertu Desktop down to the knowledge base articles with release notes https://twitter.com/veertu_labs/status/818584467954495488

Seems like a pretty thoroughly dead product. Haven't heard of xhyve before, but between the two that's the one worth looking at.

Re:VirtualBox 6.0 released by regularfry on Thursday December 20, 2018 @11:45AM (#18726455)
Not only open sourced, but GPLv2'd. Ripe for forking, if one felt so inclined.
Re:VirtualBox 6.0 released by wlesieutre on Thursday December 20, 2018 @11:53AM (#18726528)
Sure but GPLv2 doesn't help you if all copies of the source code are gone, so be sure to grab a copy of that vdhh repo now in case tithomas1 removes his.

I imagine it's not in a working state on current versions of macOS, what with the security changes that Apple makes pretty much every year. But if someone wanted to try to get it going again they certainly could.

Re:VirtualBox 6.0 released by rbanffy on Thursday December 20, 2018 @12:08PM (#18726717)
Docker for Mac has moved from VirtualBox to the built-in hypervisor.

I have the impression that causes some pain when it starts eating away battery faster than the monitor can charge the laptop.

Re:VirtualBox 6.0 released by nine_k on Thursday December 20, 2018 @12:14PM (#18726800)
Hmm, never noticed that; to the contrary, in my practice, Docker's VM eats CPU less aggressively than VirtualBox's.
Re:VirtualBox 6.0 released by lloeki on Friday December 21, 2018 @04:39AM (#18732304)
Indeed, it's called HyperKit[0][1], and it's based straight off xhyve[2].

Also, there's docker-machine-driver-xhyve for people that prefer using docker-machine (like I do) instead of DfM.

[0]: https://github.com/moby/hyperkit

[1]: https://blog.docker.com/2016/05/docker-unikernels-open-sourc...

[2]: https://github.com/moby/hyperkit/tree/master/src/

Re:VirtualBox 6.0 released by nine_k on Thursday December 20, 2018 @12:16PM (#18726814)
Last time I tried, reasonably recent kernels (like 4.15 or so) failed to boot under Veertu, for no apparent reason.

Have they improved?

Re:VirtualBox 6.0 released by mr_toad on Thursday December 20, 2018 @08:19PM (#18730746)
Xhyve looks promising, but it’s really new and at this stage it lacks all but the most basic documentation.
Re:VirtualBox 6.0 released by teekert on Thursday December 20, 2018 @08:31AM (#18724701)
Exactly, I'm upvoting this to prevent poor souls stuck on Windows from looking for these nice solutions...
Re:VirtualBox 6.0 released by cm2187 on Thursday December 20, 2018 @09:20AM (#18725046)
But can't the poor souls stuck on windows use hyper-v and RDP into the vm?
Re:VirtualBox 6.0 released by cpach on Thursday December 20, 2018 @10:28AM (#18725667)
I tried Hyper-V for a while but I found the network configuration really cumbersome. Therefore I went back to Virtualbox but I should probably request my employer to buy a license for Vmware.
Re:VirtualBox 6.0 released by cm2187 on Thursday December 20, 2018 @11:11AM (#18726111)
Is it because you switched frequently from one adapter to another (like wifi to ethernet)? Otherwise I don't think I ever had any problem with the network configuration.
Re:VirtualBox 6.0 released by jstarks on Thursday December 20, 2018 @11:19AM (#18726189)
In Windows 10, we provide a NAT network option by default. This should work seamlessly even if you switch between WiFi and Ethernet. So even this problem should go away for most people now.
Re:VirtualBox 6.0 released by cm2187 on Thursday December 20, 2018 @11:51AM (#18726510)
Didn't the NAT get pulled from hyper-V?
Re:VirtualBox 6.0 released by jstarks on Thursday December 20, 2018 @11:20PM (#18731386)
I don’t think so. It’s only there by default on client, not server, though.
Re:VirtualBox 6.0 released by vbezhenar on Thursday December 20, 2018 @09:25AM (#18725089)
You need Windows Pro as a guest to RDP.
Re:VirtualBox 6.0 released by candiodari on Thursday December 20, 2018 @11:07AM (#18726063)
Not if you use the Virtualbox extension pack to VNC (that's the free/GPL extension pack, not the Oracle one). That will work with anything. Hell, it'll work with a DOS 1.0 guest.

(and yes, it's VNC, not RDP, I believe the oracle extension pack actually allows for Virtualbox to do RDP as well. But you can stay GPL-only and still support headless VNC. I believe phpVirtualbox uses it with beautiful results)

https://forums.virtualbox.org/viewtopic.php?f=7&t=85886

Re:VirtualBox 6.0 released by akulbe on Thursday December 20, 2018 @09:57AM (#18725382)
Can't you only RDP (and here is the qualifier) out-of-the-box with an "Enhanced Guest" VM, like what comes with some of the later Windows 10 builds, like 1809?

Otherwise, don't you have to do everything by hand to configured xrdp on the Linux guest?

Re:VirtualBox 6.0 released by cm2187 on Thursday December 20, 2018 @10:05AM (#18725456)
Well technically hyper-v comes with its own terminal, but granted it kind of sucks and I wouldn't use continuously.
Re:VirtualBox 6.0 released by Silhouette on Thursday December 20, 2018 @03:14PM (#18728675)
I think Hyper-V is Windows 8+ (or similar generations of Windows Server), isn't it?

Much of the Windows world is still on Windows 7, and it would be rather ironic if they were updating because of concerns about software phoning home...

Re:VirtualBox 6.0 released by mr_toad on Thursday December 20, 2018 @08:21PM (#18730757)
Hyper V requires a Windows Pro license last time I checked. That’s significantly more expensive that VirtualBox.
Re:VirtualBox 6.0 released by jki275 on Thursday December 20, 2018 @09:21AM (#18725056)
I use hyper-v and rdp every day, very happy with both. I even run Linux VMs in hyper-v.
Re:VirtualBox 6.0 released by border43 on Thursday December 20, 2018 @11:01AM (#18726013)
I've had nothing but issues trying to run Ubuntu in Hyper-V. Even the Windows Ubuntu LTS image that comes with the quick-create didn't work for very long.

Not sure what I'm doing wrong, but I've never has success with non-windows OS's.

Re:VirtualBox 6.0 released by jki275 on Thursday December 20, 2018 @11:29AM (#18726277)
What host version? I'm running 18.04 on Server 2016, for reference, did absolutely nothing special or unique, downloaded the iso, built the machine and loaded it and it's up running dns & unifi controller 24/7 for my home network with no issues.
Re:VirtualBox 6.0 released by novaRom on Thursday December 20, 2018 @09:49AM (#18725314)
Can you run singularity-container or docker in your Linux guest?
Re:VirtualBox 6.0 released by jki275 on Thursday December 20, 2018 @10:19AM (#18725574)
I haven't had reason to try, but I can't imagine a good reason why one couldn't.
Re:VirtualBox 6.0 released by coredog64 on Thursday December 20, 2018 @10:40AM (#18725790)
I would hope so, as that is what the Win10 version of Docker-for-Windows does.
Re:VirtualBox 6.0 released by codereflection on Thursday December 20, 2018 @10:43AM (#18725817)
Yes
Re:VirtualBox 6.0 released by Narishma on Thursday December 20, 2018 @04:29PM (#18729308)
Hyper-V only works on the Pro versions of Windows.
Re:VirtualBox 6.0 released by gaius on Thursday December 20, 2018 @10:12AM (#18725511)
WSL has supplanted VirtualBox for actually all of my use cases.
Re:VirtualBox 6.0 released by jweir on Thursday December 20, 2018 @01:00PM (#18727260)
To be clear, VirtualBox and Guest Additions are open source. It is only the Extension Pack which is licensed. No?

Until today I had never even heard of the Extension pack, and have never had any need to use it.

Re:VirtualBox 6.0 released by kop316 on Thursday December 20, 2018 @01:40PM (#18727706)
You are correct. It is of note that the extesions pack has a lot of useful add-ons, but you did have to explicitly install it.
Re:VirtualBox 6.0 released by bayindirh on Thursday December 20, 2018 @07:25AM (#18724306)
We use virt-manager to virtualize servers on servers with joy, however I use VBox to virtualize Windows hosts with hardware acceleration if possible.

How is the state of KVM's support about 3D acceleration, sound, drag'n drop and like?

Re:VirtualBox 6.0 released by znpy on Thursday December 20, 2018 @08:25AM (#18724666)
If you have on the host system a graphics card that you can fully dedicate to the guest system, you can then do pci-passthrough and let the guest system have nearly-full access to that graphic card with nearly full performances.

Also, kvm has some nice features that AFAIK virtual box does not have. For example you can have gnu/linux and windows guests use the balloon memory driver, that basically allocates and deallocates memory from the host system. Imagine having a guest vm where you can say "this vm should have 2GB ram, but it might burst up to 24GB if needed, and then go back to 2GB when the need is satisfied". Can't do that with VBox (AFAIK - and it works on windows too!)

Regarding sound, if you are virtualizing windows, imho you're better off connecting via rdp (avoid remmina, use rdesktop) and using local speakers as audio output.

Re:VirtualBox 6.0 released by pizza234 on Thursday December 20, 2018 @11:06AM (#18726053)
> you can then do pci-passthrough and let the guest system have nearly-full access to that graphic card with nearly full performances.

It is possible, but when it works and works well, which is not always the case. In addition, one may have to lock the card for usage with the guest only, since drivers may not be compatible with intermittent (=on/off) vfio usage.

I've had mixed experiences, depending on the hardware. my current system is 100% stable, however, I don use the card on the host (it causes instability). My previous system worked badly, and it was essentially not usable.

Re:VirtualBox 6.0 released by bayindirh on Thursday December 20, 2018 @11:36AM (#18726337)
> If you have on the host system a graphics card that you can fully dedicate to the guest system.

Which implies a special-build system to play some odd Windows games ocassionally, akin to building an Hackintosh. For my use case it's a definitive overkill :D

> ...do pci-passthrough and let the guest system have nearly-full access to that graphic card with nearly full performances.

Again which requires a CPU and system which supports vT-d (in intel jargon), which is the only feature which my 3770K doesn't support :D

VirtualBox supports memory balooning. The interface is same with VirtIO's ballooning drivers AFAIK. The commands can be found in [0].

Since I want to virtualize Windows to play my simpler games only, rdp is not a very attractive choice. Using local speakers and sound virtualization is alright. I don't want crystal clear, high end sound. However, I'm not aware of the support level.

[0]: https://www.virtualbox.org/manual/ch09.html

Re:VirtualBox 6.0 released by robin_reala on Thursday December 20, 2018 @08:54AM (#18724862)
How is pci-passthrough for hypervisor security? I’m speaking from a layman’s perspective, but there have been successful escapes through the GPU / GPU memory in the past right?
Re:VirtualBox 6.0 released by Hello71 on Thursday December 20, 2018 @09:01AM (#18724905)
Somewhat better than OpenGL passthrough, whose security can be summarized as between "basically none" and "absolutely none".
Re:VirtualBox 6.0 released by deadcow on Thursday December 20, 2018 @03:18PM (#18728717)
For sound I would recommend scream: https://github.com/duncanthrax/scream

I've been using it in my KVM PCI passthrough VM for some months and it works well.

Re:VirtualBox 6.0 released by robert_foss on Thursday December 20, 2018 @09:05AM (#18724939)
Virgil3D enables host-gpu based acceleration for KVM, and Boxes ships with it enabled I think.
Re:VirtualBox 6.0 released by bayindirh on Thursday December 20, 2018 @11:37AM (#18726354)
Virgil 3D is a KVM feature. Boxes is just a frontend. Fedora, CentOS and RH enables it, but it's not landed on Debian yet AFAIK.
Re:VirtualBox 6.0 released by nailer on Thursday December 20, 2018 @07:17AM (#18724249)
From Boxes site:

> While virt-manager does a very good job as a virtual machine management software, it's very much tailored for system administration.

Exactly! Boxes looks really polished.

Re:VirtualBox 6.0 released by bubblethink on Thursday December 20, 2018 @10:43AM (#18725818)
It's anything but. It's utterly useless. Just use virt-manager while it lasts. It is being deprecated though, after which you will be forced to use boxes or the other virt-manager replacement.
Re:VirtualBox 6.0 released by DrPhish on Thursday December 20, 2018 @11:30AM (#18726281)
Having never used Boxes before, I was excited for a better VM management tool than virt-manager.

However, I just tried using it (on Debian stretch), and unfortunately I have to agree that it doesn't do much beyond look pretty.

afaict you could only go to consoles, check a few resource usage graphs, send power commands and manage snapshots. There were very few configuration options and no ability to manipulate virtual hardware on existing machines. Also, there was no way to add remote libvirt instances from the GUI, and adding them into the config file (qemu+ssh) just made boxes crash.

If virt-manager really is going to be deprecated, is there a good replacement out there?

edit: Holy crap, it also managed to hibernate all the running VMs on my dev box when it crashed!?! Glad I didn't have anything too important running on it!

Re:VirtualBox 6.0 released by pseudalopex on Friday December 21, 2018 @02:01AM (#18731865)
It looks like Red Hat intends Cockpit (a web interface) to replace virt-manager eventually.[1]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1659477

Re:VirtualBox 6.0 released by pizza234 on Friday December 21, 2018 @03:32AM (#18732096)
This is somewhat excessive. There are still valid use cases where Virtualbox comes for free - private users or professional users/companies with a relatively small number of workstations (Oracle's going after companies who use a large number of unlicensed installations).

Also, it is still possible to build a free extension pack; it would be a great project. After all, Virtualbox is GPL, and it shouldn't be underestimated the amount of work that has been, and is being, put into it.

Re:VirtualBox 6.0 released by jancsika on Thursday December 20, 2018 @04:11PM (#18729149)
I'll try that.

I use Virtualbox to compile CI artifacts for Ubuntu, Debian, OSX (homebrew), and Windows (msys2) by using the virtualbox executor of gitlab.

The other available gitlab-runner executors to build these artifacts cross-flatform are: virtualbox, parallels, docker, kubernetes.

Boxes and virt-manager aren't on that list, so they are out.

Parallels isn't FLOSS.

Can I use docker or kubernetes to build my desired artifacts?

Re:VirtualBox 6.0 released by caycep on Thursday December 20, 2018 @11:06AM (#18726058)
I think the advantage of VB is its installer and ease of creating and spinning up desktop VMs. The last time I tried using virt manager, I decided it wasn't for me, at its then-level of polish, but this was probably back in 2011 or 2012 or something. Boxes seems promising in this regard...hopefully it gets some momentum behind it.
Re:VirtualBox 6.0 released by nunez on Thursday December 20, 2018 @03:35PM (#18728871)
Thank you for providing these links. I've been looking for an alternative to VBox for quite some time (I don't like anything that Oracle touches, as Oracle is a law firm with a tech problem); these help.
Re:VirtualBox 6.0 released by lmedinas on Thursday December 20, 2018 @07:29AM (#18724331)
Sorry but it could be (even remotely closely) to a Linux only solution.
Re:VirtualBox 6.0 released by juststeve on Thursday December 20, 2018 @07:24AM (#18724294)
from memory boxes has limited networking functionality though?
Re:VirtualBox 6.0 released by veeableful on Thursday December 20, 2018 @08:18PM (#18730743)
What VM should I use if I’m on macOS?
Re:VirtualBox 6.0 released by ianai on Thursday December 20, 2018 @08:14AM (#18724592)
You make a good point, but not a good recommendation. This is a Mac OS virtualization app, and your options are Linux only. Its an oversight, at best. I get that Apples messed up their evosystem, but that’s not this conversation.
Re:VirtualBox 6.0 released by watersb on Thursday December 20, 2018 @08:19AM (#18724634)
VirtualBox is a cross-platform app. The user interface looks like Java to me.
Re:VirtualBox 6.0 released by moondowner on Thursday December 20, 2018 @08:33AM (#18724718)
The UI is written in Qt. E.g. for older VirtualBox versions, the virtualbox-qt package was required to be installed in order to have the GUI.
Re:VirtualBox 6.0 released by Quekid5 on Thursday December 20, 2018 @08:33AM (#18724717)
The UI is Qt-based, I believe.
Re:VirtualBox 6.0 released by tatref on Thursday December 20, 2018 @08:20AM (#18724640)
No, VirtualBox is Windows, Linux, MacOS
Re:VirtualBox 6.0 released by ianai on Thursday December 20, 2018 @08:45AM (#18724790)
Whoops, I forgot.