Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
06-20-2026, 04:57 PM
|
#736
|
|
Member
Registered: Nov 2003
Location: NY
Distribution: slackware
Posts: 771
|
Quote:
|
Oh, it will build and install, but won't start the "machine." The error message is simply,"Can't start machine."
|
Anything useful in the VBox logs?
I don't know it'll be useful in this case, but usually Virtualbox will provide output when it errors with "Can't start machine."
Anything useful?
I've found it (the output information) helpful in the past in resolving "start" errors.
Which in my case were usually due to something changing in the image config (name.vbox) file (Identifier, path, resource etc).
|
|
|
1 members found this post helpful.
|
06-26-2026, 01:33 PM
|
#737
|
|
LQ Veteran
Registered: Feb 2007
Distribution: Slackware64-current with KDE4Town.
Posts: 10,145
Original Poster
|
Quote:
Originally Posted by bitfuzzy
Anything useful in the VBox logs?
I don't know it'll be useful in this case, but usually Virtualbox will provide output when it errors with "Can't start machine."
Anything useful?
I've found it (the output information) helpful in the past in resolving "start" errors.
Which in my case were usually due to something changing in the image config (name.vbox) file (Identifier, path, resource etc).
|
thanks for the suggestion.
Found this,
Quote:
Failed to open virtual machine located in /home/VirtualBox VMs/Xp3-Scan/Xp3-Scan-1.19-linux.vbox.
Trying to open a VM config '/home/VirtualBox VMs/Xp3-Scan/Xp3-Scan-1.19-linux.vbox' which has the same UUID as an existing virtual machine.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {e36a5081-a82a-40bd-9e4e-42a44d6ce50f}
Callee:
IVirtualBox {2ce10519-3c09-45d8-a12d-e887786146b7}
|
|
|
|
|
06-26-2026, 04:15 PM
|
#738
|
|
Member
Registered: Nov 2003
Location: NY
Distribution: slackware
Posts: 771
|
Quote:
|
Trying to open a VM config '/home/VirtualBox VMs/Xp3-Scan/Xp3-Scan-1.19-linux.vbox' which has the same UUID as an existing virtual machine.
|
Yup! That's your culprit, should be simple enough to resolve
|
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 05:05 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|