Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
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.
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.
Try going into the BIOS and make sure that the Virtualization Technology is 'enabled'-
Hi
Thanks for your advice.
Whether you meant "Intel Virtualization Technology"?
I'm running AMD CPU
sudo lshw
Code:
.....
Description: Motherboard
product: M5A97 LE R2.0
vendor: ASUSTeK COMPUTER INC.
physical id: 0
version: Rev 1.xx
serial: 141235722500456
slot: To be filled by O.E.M.
.....
Just looked at the BIOS -> Advanced Mode
No such an item found
There are 2 VMs, say VM1 and VM2, which haven't been running for prolonged time;
Normal booting
VM-1 only a black screen without login screen popup nor I can input command
VM-2 after login without menu bar displayed.
Booting headless mode with same result.
I wonder whether the command "VBoxheadless -s xxxxx" is working properly. I tried other VMs, some booting up headless mode where I can input commands and others booting straight to login screen.
I also tried "VBoxHeadless --startvm xxx.xxxx.xxxx." with same result.
Actually I can delete them. Just for curiosity I continue.
Whether you meant "Intel Virtualization Technology"?
I'm running AMD CPU
sudo lshw
Code:
.....
Description: Motherboard
product: M5A97 LE R2.0
vendor: ASUSTeK COMPUTER INC.
physical id: 0
version: Rev 1.xx
serial: 141235722500456
slot: To be filled by O.E.M.
.....
Just looked at the BIOS -> Advanced Mode
No such an item found
There are 2 VMs, say VM1 and VM2, which haven't been running for prolonged time;
Normal booting
VM-1 only a black screen without login screen popup nor I can input command
VM-2 after login without menu bar displayed.
Booting headless mode with same result.
I wonder whether the command "VBoxheadless -s xxxxx" is working properly. I tried other VMs, some booting up headless mode where I can input commands and others booting straight to login screen.
I also tried "VBoxHeadless --startvm xxx.xxxx.xxxx." with same result.
Actually I can delete them. Just for curiosity I continue.
Regards
satimis
You're Welcome.
Ok, thanks for letting us know it's an AMD CPU:-
I've tried to run a handful of distro's myself in a VM and got the black screen too.
I'm not entirely sure what that's all about.
Quote:
I wonder whether the command "VBoxheadless -s xxxxx" is working properly.
That's certainly something to think about.
Look in the Virtual Box Forum. Might find a thread concerning that.
When you get the time read the documentation that TB0ne linked for you.
Often what's going on is something we didn't read up on thus leading us to not knowing things.
The very thing that you may not know at the moment could be the thing that fixes the issue.
Yeah, I know manuals are boring but I had to read the VBox manual twice and I'm glad I did.
I've tried to run a handful of distro's myself in a VM and got the black screen too.
I'm not entirely sure what that's all about.
That's certainly something to think about.
Look in the Virtual Box Forum. Might find a thread concerning that.
When you get the time read the documentation that TB0ne linked for you.
Often what's going on is something we didn't read up on thus leading us to not knowing things.
The very thing that you may not know at the moment could be the thing that fixes the issue.
Yeah, I know manuals are boring but I had to read the VBox manual twice and I'm glad I did.
I couldn't start Headless as root. I suspect whether there are some problem on Headless mode here.
On
VirtualBox Manager (graphic interface mode)
select VM -> right click
Code:
Start
-> Normal Start
-> Headless Start
-> Detachable Start
On some VMs no difference between Normal and Headless Start the VM boots as Normal
On some VMs Headless Start boots to a black screen only without cursor blinking
On some VMs Headless boots to a login screen as Normal Start and after login no desktop displayed
etc.
I suppose the easier way to rescue a problematic VM is booting it with LiveCD i.e. attaching a Ubuntu16.04 ISO to IDE Controller on Settings -> Storage -> Controller:IDE
I'll stop my testing here. Again lot of thanks for your support and effort
I couldn't start Headless as root. I suspect whether there are some problem on Headless mode here.
On VirtualBox Manager (graphic interface mode) select VM -> right click
Code:
Start
-> Normal Start
-> Headless Start
-> Detachable Start
On some VMs no difference between Normal and Headless Start the VM boots as Normal
On some VMs Headless Start boots to a black screen only without cursor blinking
On some VMs Headless boots to a login screen as Normal Start and after login no desktop displayed etc.
I suppose the easier way to rescue a problematic VM is booting it with LiveCD i.e. attaching a Ubuntu16.04 ISO to IDE Controller on Settings -> Storage -> Controller:IDE I'll stop my testing here. Again lot of thanks for your support and effort
The easiest thing to do would be to pay attention. The Virtualbox documentation has covered this plenty, and you have been asking about things like this for MANY years...why are you unable to apply anything you've been told previously, or learn on your own??
You were given the answer: you started headless, which AGAIN, is covered in the documentation which I handed to you in my first reply. It HAS nothing to show you on the screen...it is HEADLESS. It's waiting for you to connect to it via RDE...AGAIN, as is told to you plainly in the documentation. If you don't want to read/learn/research things on your own, or even acknowledge you get answers, there's little point in posting questions.
Quote:
Originally Posted by Ztcoracat
The first 2 hits in this search look like a start.
...and the second one, from their documentation, is what I handed the OP to start with, in the very first reply. Apparently, he doesn't want to read it.
Don't run Virtuablbox as root. 15 years here and you run as root? What has that ever fixed?
Yep...the OP has posted NUMEROUS times about Virtualbox over the past 14 years. I've asked the same question before, and have given info too..OP doesn't seem to answer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.