Question about not starting guests

[Perryg]

Something is not happy and it may be the version of VirtualBox. If I was having this issue I would upgrade to the latest build which has plenty of new code and fixes. Newest version is 5.1.6 and available here

[Abrugal]

Something is not happy and it may be the version of VirtualBox. If I was having this issue I would upgrade to the latest build which has plenty of new code and fixes. Newest version is 5.1.6 and available here

I've been gradually upgrading to every new version coming up since this started and nothing changed.

[dwarsligger]

Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

Did you have the OSE version installed at some point? If so the OSE version should have been purged before you install the official version of VirtualBox.

Fix is to purge and install again.

Hello Perryg,

What exactly is the issue with the OSE and PUEL versions , many users will have started Vbox from a repository such as Ubuntu (which is the OSE version)
so did I my version was 5.0.24 ( current in Ubuntu) which is en OSE version
After I managed to get 5.0.24 removed ( iḿ not sure about purge) and 5.1.6 installed , I cannot start my Vbox environments I also get the 1912 error mention in the beginning of this thread
what would be the most suitable course of action ?
a- shoudl I remove/purge the PUEL version and revert to 5.0.24 the OSE version ?
b- I removed and purge the installation virtualbox-5.1 , then purged the 5.0.25 virtualbox and then re installed the 5.1 and extensions , But my VBox environments will not work under 5.1.6 they keep on giving the 1912 errror >==> (edited)
c- what does/ is supposed to do the sbin/vbox config tool ? in my case it rebuild the kernel

PS In my Case the Vboxmanag -v returns 5.1.6r110634

[Perryg]

OSE or open source edition is available to all and can be and usually is modified by the maintainer of the specific distro. The PUEL or public use edition license version is pre-compiled and can not be modified.

Since the OSE version can and usually is modified the two can not be trusted together as calls and package location and even packages that are not included in both. As far as using the OSE version I usually don't specify that you should not use them, just that you have to remove one before you install the other. I myself have not used the PUEL version for years. I build a custom release of my own and guess what? I don't get support either beyond basic which I don't need, but that is an exception to the rule.

One thing to keep in mind. Without actually working on your system all anyone can do is make suggestions as to what needs to be done unless they can replicate your issue and know what it took to repair it. Given the only indication of what the issue could be is a warning of not mixing the OSE and PUEL version ( in this thread ) no one knows what the exact issue might be if it is something else than what is posted. It could be a conflict on the host of a package that needs to be replaced or upgraded but I would think the error message would be different.

You can always raise a ticket at bugtracker if you are sure you have removed all of the OSE before you installed the official ( PUEL ) version and still see the same error.

You might also try one of the latest test builds to see if a known issue has been fixed. https://www.virtualbox.org/wiki/Testbuilds

[dwarsligger]

So in other words If I want to use the latest version 5.1.6 PUEL version from Vbox rather the from the rpository
I will need to rebuild every single Vbox environment that i previously build under OSE versions 5.0.24 or before

not quite the answer i epxected

[dwarsligger]

OSE or open source edition is available to all and can be and usually is modified by the maintainer of the specific distro. The PUEL or public use edition license version is pre-compiled and can not be modified.

Since the OSE version can and usually is modified the two can not be trusted together as calls and package location and even packages that are not included in both. As far as using the OSE version I usually don't specify that you should not use them, just that you have to remove one before you install the other. I myself have not used the PUEL version for years. I build a custom release of my own and guess what? I don't get support either beyond basic which I don't need, but that is an exception to the rule.

One thing to keep in mind. Without actually working on your system all anyone can do is make suggestions as to what needs to be done unless they can replicate your issue and know what it took to repair it. Given the only indication of what the issue could be is a warning of not mixing the OSE and PUEL version ( in this thread ) no one knows what the exact issue might be if it is something else than what is posted. It could be a conflict on the host of a package that needs to be replaced or upgraded but I would think the error message would be different.

You can always raise a ticket at bugtracker if you are sure you have removed all of the OSE before you installed the official ( PUEL ) version and still see the same error.

You might also try one of the latest test builds to see if a known issue has been fixed. https://www.virtualbox.org/wiki/Testbuilds

BTW would this also mean that if i reverted to the 5.0.24 version downloaded from the vbox site the guests build under a 5.0.24 installed form the ubuntu repository ??

[Perryg]

If you use the software center anything is possible. I have found it to be more than a little headache, even to the point of being total junk IMHO. I would suggest you remove with apt-get, aptitude, or synaptic ( usually requires you to install it first ), then use dpkg to install the proper package.

[socratis]

So in other words If I want to use the latest version 5.1.6 PUEL version from Vbox rather the from the repository I will need to rebuild every single Vbox environment that i previously build under OSE versions 5.0.24 or before

Where did you get that idea from? If you install the official LibreOffice as opposed to the Fedora repository LibreOffice, do you have to re-create your spreadsheets? Of course not! And by "every single Vbox environment that i previously build" I take it that you mean your VMs.

[dwarsligger]

I've noticed this before with VBOX : if I stick to the UBUNTU repository (OSE) versions and manage to get the extension and guest additions correct ( correct versions) the VMś will contiinue to work also as i progress through automatic repository updates
once i remove the old version a start using either the downloaded version ( from the vbox website, PUEL version) then the VMś will cease to work with this 1912 error the initiator complained about and nobody can help getting the VM to work again until i revert back to the OSE version in the ubuntu repository , so my conclusion is that contrary to libreoffce documents , the ose version prevents user of exisiting VM to migrate to newer versions whcih might deal with issues they have , so I think I will have to rebuild the VMś from scratch ...

[socratis]

Look, it's not worth beating a dead horse. You have two options:

• Stick with the Ubuntu fork. Seek help at the Ubuntu forums.
• Install the official VirtualBox. We continue the discussion here.

It's your call. Let me know if/when you have the official version installed.

[z hopa]

So in other words If I want to use the latest version 5.1.6 PUEL version from Vbox rather the from the repository I will need to rebuild every single Vbox environment that i previously build under OSE versions 5.0.24 or before

Where did you get that idea from? If you install the official LibreOffice as opposed to the Fedora repository LibreOffice, do you have to re-create your spreadsheets? Of course not! And by "every single Vbox environment that i previously build" I take it that you mean your VMs.

Those are apples and oranges.
Open Office, even though I consider it untested code soup that barely functions, does not require rebuilding all spreadsheets if uninstalled and re-installed.

VirtualBox on the contrary, appears totally blank after that with no machines surviving.
And I do not know of any method to import the existing machines, if those were not exported as appliances before hand.
Of course, Oracle deeply cares for the user's safety (or whatever they have in mind) and does not allow to simply point at the .vbox file and treat it as a new machine.
So he is right - after purging and reinstalling, we have to rebuild all machines from scratch, losing the snapshots.

[Perryg]

Totally not true. You can always use the add feature if they become lost, which should never happen if done correctly.
Main manager -> machine -> add.

[socratis]

VirtualBox on the contrary, appears totally blank after that with no machines surviving.

Then you're doing something wrong. Most probably you're running as a user that did not create the machines. How exactly are you installing VirtualBox? The EXACT procedure please. And tell me the location of your VMs, plus the location of your VirtualBox.xml.

Just because you're not doing it correctly, you can't blame VirtualBox for that...

[dwarsligger]

Totally not true. You can always use the add feature if they become lost, which should never happen if done correctly.
Main manager -> machine -> add.

Which is what I said before

So in other words If I want to use the latest version 5.1.6 PUEL version from Vbox rather the from the repository I will need to rebuild every single Vbox environment that i previously build under OSE versions 5.0.24 or before

Where did you get that idea from? If you install the official LibreOffice as opposed to the Fedora repository LibreOffice, do you have to re-create your spreadsheets? Of course not! And by "every single Vbox environment that i previously build" I take it that you mean your VMs.

Those are apples and oranges.
Open Office, even though I consider it untested code soup that barely functions, does not require rebuilding all spreadsheets if uninstalled and re-installed.

VirtualBox on the contrary, appears totally blank after that with no machines surviving.
And I do not know of any method to import the existing machines, if those were not exported as appliances before hand.
Of course, Oracle deeply cares for the user's safety (or whatever they have in mind) and does not allow to simply point at the .vbox file and treat it as a new machine.
So he is right - after purging and reinstalling, we have to rebuild all machines from scratch, losing the snapshots.

I do agree with Hoppa : you guys are pointing to some unknown ubuntu distro whatever as if there was infoboot in teh basement of Ubuntu with a guy that answers questions and does all kinds of fancy things to Virtual Box what makes it no longer Virtual box
If wokring on a standard Ubuntu 16.04 desktop and type in a terminalwindow "apt-get install Virtualbox" then I don know if I get an OSE or an PUEL version
Yes ( the Vbox manager does respond 5.024___ubuntu___) but when queried the about scren of virutla box I get 5.0.24 and a buidl number which concurs with the version on the oracle website and is the same for the OSE amd PUEL version

if working in the same enviroment and I type "apt-get install Virtualbox-5.1" then I don know if I get an OSE or an PUEL version
the about box says 5.1.6 ( and after consultins here so does the vboxmanager ... ) wihch seems to be a PUEL version

You might want to consider changing build if not version numbers like say Virtula box makes 5.0.24 build 123456 and an distor distributes an OSE version then that shoudl be named 5.0.25 build 123456

But what I'm saying is that since ever I have been using Virtual box there has been a problem with VM not laoding when upgrade by force installing another later versuion of virutal box which turns out t be a OSE version and the problem is always teh above 1912 error

Conclusion
so my conclusion is valid :
= private users (iḿ not talking about profesiionals) start always using Virtual box with the version they get from the Ubuntu software installer ( or theor distro provider) and create one or more VM's
= when they want to move to newer versions offered on the Virtual box website their VM will not function ( like spreadsheets in libre office do after you installed another version)
= and when starting a VM created on a OSE version the the PUEL version is made to reject it what the 1912 error message is all about babbing about wrappers and drivers ...
= the User is forced to rebuild his VM ś using the new Vitrual box distro
= and I suspect the needs to make sure later updates are not installed automatiscally but must update manually from the virotualbox website other wise the whole thing crashes again

more over the reports on different Unix websites that Virtualbox does have problems with USB support ( that flash drives don't work and wil never work ... ) seems to be valid because other connected USB devices do work ( if the definiton is correct)

Iǘe started testing VMware and i must say it does seem to be more reliable in creating VMś and on the USB front ... Unless this can be solved in a satisfactory manner instead of goint hrough the pain for rebuilding my Vbox - VM I might just rebuild it in VMware ...

[socratis]

You have so many mistaken assumptions in your post, that it's going to be a long reply. Let me start trying to cover them one by one:

1. "type in a terminalwindow "apt-get install Virtualbox" then I don know if I get an OSE or an PUEL version"
   If you're using 'apt-get', you are getting the OSE Ubuntu fork of VirtualBox. Unless you manually added the VirtualBox repository, you are using the Ubuntu repository.
2. Yes ( the Vbox manager does respond 5.024___ubuntu___)
   That's the proof that you're using the Ubuntu version, not the VirtualBox one.
3. get 5.0.24 and a buidl number which concurs with the version on the oracle website and is the same for the OSE amd PUEL version
   Which is perfectly fine. The only thing that the VirtualBox team asks is for the distros to mark their fork. But even if they don't mark it, I haven't heard of any lawsuits yet.
4. You might want to consider changing build if not version numbers like say Virtula box makes 5.0.24 build 123456 and an distor distributes an OSE version then that shoudl be named 5.0.25 build 123456
   You should talk to the distros about this.
5. there has been a problem with VM not laoding when upgrade by force installing another later versuion of virutal box which turns out t be a OSE version and the problem is always teh above 1912 error
   Because there is a driver conflict. VirtualBox warns you about this when you install it. It's kind of hard to miss. You have to uninstall the fork before you install the original. You have to do this, not VirtualBox.
6. private users (iḿ not talking about profesiionals) start always using Virtual box with the version they get from the Ubuntu software installer ( or theor distro provider) and create one or more VM's
   That's fine. As long as they seek support from wherever they got their VirtualBox from, I don't think I see a problem.
7. when they want to move to newer versions offered on the Virtual box website their VM will not function ( like spreadsheets in libre office do after you installed another version)
   I'm afraid that this is simply not true. You're the only one I've seen complaining about this, so please do not say "users", say "I".
8. the User is forced to rebuild his VM ś using the new Vitrual box distro
   Again, this is not true. You (again) are the only one reporting this, so you must be doing something that is not right. Either a mistake in, or a misunderstanding of the process.
9. and I suspect the needs to make sure later updates are not installed automatiscally but must update manually from the virotualbox website other wise the whole thing crashes again
   The official VirtualBox does not update itself automatically. It pops up a message if there is a newer version available, but you can turn it off in the preferences.
10. more over the reports on different Unix websites that Virtualbox does have problems with USB support ( that flash drives don't work and wil never work ... ) seems to be valid because other connected USB devices do work ( if the definiton is correct)
    Unfounded, unsubstantiated rumors do nothing to persuade me. So far, for every user that has been a USB complaint, 90% of them they were doing it wrong. If you have a problem with USB, then please open a new, appropriate thread because the title "Question about not starting guests" might be misleading.
11. Unless this can be solved in a satisfactory manner instead of goint hrough the pain for rebuilding my Vbox - VM I might just rebuild it in VMware
    It's your computer, your VMs, your choice.