Return to Answer

Any planned usage of virtualbox is offtopic.

Any use to estinguish a fire for a temporary case or a question to migrate off virtualbox would be ontopic IMO

As such for myself I would state a similar opinion as John told in 2011. It depend in the use, but keep in mind John answer didnt aged well, as back in 2011 hyperv support was limited unlike now.

I used virtualbox in some limited context as an admin. In my toolkit I used vmware vserver, but its now EOL (last build 2.02 in 2009), thus virtualbox took over that part. (my limited use to give an example was to save a failing DC, did a dcpromo in a quick setupped vm on a secretary pc, to give time to order a new server). Honnestly I didnt used that tool for year for the reason I told you for the hyperv support. It was mainly virtual pc vs virtualbox a while back, now hyperv put the virtualbox usage a alot narrower.

Any planned usage of virtualbox is offtopic. SuperUser is more suited for almost all VirtualBox questions.

Any use to estinguish a fire for a temporary case or a question to migrate off virtualbox would be ontopic IMO, but it’s really rare case.

As such for myself I would state a similar opinion as John told in 2011. It depend in the use, but keep in mind John answer didnt aged well, as back in 2011 hyperv support was limited unlike now.

I used virtualbox in some limited context as an admin. In my toolkit I used vmware vserver, but its now EOL (last build 2.02 in 2009), thus virtualbox took over that part. (my limited use to give an example was to save a failing DC, did a dcpromo in a quick setupped vm on a secretary pc, to give time to order a new server). Honnestly I didnt used that tool for year for the reason I told you for the hyperv support. 

It was mainly virtual pc vs virtualbox a while back, now hyperv put the virtualbox usage a alot more narrower. For that reason I can see the tag used in the past a lot more than today, as enterprise product is more accessible now for the same task.

Any planned usage of virtualbox is offtopic.

Any use to estinguish a fire for a temporary case or a question to migrate off virtualbox would be ontopic IMO

As such for myself I would state a similar opinion as John told in 2011. It depend in the use, but keep in mind John answer didnt aged well, as back in 2011 hyperv support was limited unlike now.

I used virtualbox in some limited context as an admin. In my toolkit I used vmware vserver, but its now EOL (last build 2.02 in 2009), thus virtualbox took over that part. (my limited use to give an example was to save a failing DC, did a dcpromo in a quick setupped vm on a secretary pc, to give time to order a new server). Honnestly I didnt used that tool for year for the reason I told you for the hyperv support. It was mainly virtual pc vs virtualbox, now hyperv put the virtualbox usage a alot narrower.

Any planned usage of virtualbox is offtopic.

Any use to estinguish a fire for a temporary case or a question to migrate off virtualbox would be ontopic IMO

As such for myself I would state a similar opinion as John told in 2011. It depend in the use, but keep in mind John answer didnt aged well, as back in 2011 hyperv support was limited unlike now.

I used virtualbox in some limited context as an admin. In my toolkit I used vmware vserver, but its now EOL (last build 2.02 in 2009), thus virtualbox took over that part. (my limited use to give an example was to save a failing DC, did a dcpromo in a quick setupped vm on a secretary pc, to give time to order a new server). Honnestly I didnt used that tool for year for the reason I told you for the hyperv support. It was mainly virtual pc vs virtualbox a while back, now hyperv put the virtualbox usage a alot narrower.

Any planned usage of virtualbox is offtopic.

Any use to estinguish a fire for a temporary case or a question to migrate off virtualbox would be ontopic IMO

As such for myself I would state a similar opinion as John told in 2011. It depend in the use, but keep in mind John answer didnt aged well, as back in 2011 hyperv support was limited unlike now.

I use virtualbox in some limited context as an admin. In my toolkit I used vmware vserver, but its now EOL (last build 2.02 in 2009), thus virtualbox took over that part. (my limited use to give an example was to save a failing DC, did a dcpromo in a quick setupped vm on a secretary pc, to give time to order a new server). Honnestly I didnt used that tool for year for the reason I told you.

Any planned usage of virtualbox is offtopic.

Any use to estinguish a fire for a temporary case or a question to migrate off virtualbox would be ontopic IMO

As such for myself I would state a similar opinion as John told in 2011. It depend in the use, but keep in mind John answer didnt aged well, as back in 2011 hyperv support was limited unlike now.

I used virtualbox in some limited context as an admin. In my toolkit I used vmware vserver, but its now EOL (last build 2.02 in 2009), thus virtualbox took over that part. (my limited use to give an example was to save a failing DC, did a dcpromo in a quick setupped vm on a secretary pc, to give time to order a new server). Honnestly I didnt used that tool for year for the reason I told you for the hyperv support. It was mainly virtual pc vs virtualbox, now hyperv put the virtualbox usage a alot narrower.