Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Black Screen / Doesn't boot? #52

Closed
syntaxerror opened this issue Jan 3, 2017 · 13 comments
Closed

Black Screen / Doesn't boot? #52

syntaxerror opened this issue Jan 3, 2017 · 13 comments

Comments

@syntaxerror
Copy link

syntaxerror commented Jan 3, 2017

I wonder if anyone has been able to run this on a computer with a AMD CPU (and 64 bit Ubuntu Linux)?
On my system I just get a black screen (in VirtualBox), it doesn't seem to boot properly.

My system:
AMD Phenom(tm) II X4 965 Processor × 4
GeForce GT 640/PCIe/SSE2
32 GB RAM

I would recall I've read something some time ago, that it's easier to get Mac up running on Intel, even in VirtualBox etc.

@syntaxerror
Copy link
Author

Using vagrant up, and waiting for a long time:

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

@AndrewDryga
Copy link
Owner

Did you tried to turn GUI mode on and look whats happening? Can you provide your Vagrantfile?

@syntaxerror
Copy link
Author

syntaxerror commented Jan 3, 2017

Yes, the problem is nothing seems to happen. Starting directly from VirtualBox or Vagrant with GUI seems to do the same:
vb_mac

Haven't changed anything in Vagrantfile, and honestly, I don't know if I should. :)
Vagrantfile.zip

@syntaxerror
Copy link
Author

The log file
VBox.log.zip

But I also noticed in https://www.virtualbox.org/manual/ch03.html#intro-macosxguests

This allows you to install and execute unmodified versions of Mac OS X on supported host hardware.

  • wondering about this "supported hardware" ...

@WayneBuckhanan
Copy link

FYI, you may need more vb.customize fields if you are pushing the boundaries on what is "supported hardware"...
See this gist for a Vagrant file that worked on a previous version of this box (haven't tested recently).

HTH

@syntaxerror
Copy link
Author

syntaxerror commented Jan 8, 2017

OK, thanks for the info. Seems like there is need for quite much searching, reading, customisation and testing to get this up running on a system like mine. Maybe I'll just find a used Mac to do the web testing on instead. :)

Btw! I tested the Vagranfile from @WayneBuckhanan with the previous version of the box too (0.2.1), and it just freeze the whole computer then.

@AndrewDryga
Copy link
Owner

I think it would help if you will submit issue on VirtualBox forums/support, because it can affect other users.
Maybe they will be able to fix it in next releases or suggest you what is going on.

@syntaxerror
Copy link
Author

syntaxerror commented Jan 12, 2017

You're probably right. I also tested adding a Mac guest on a Windows host, it doesn't freez, but beyond that it seems to be same issues - meaning there is something about VirtualBox and Mac guests (maybe related to AMD etc, but have no Intel to verify).

@xoogu
Copy link

xoogu commented Jun 26, 2017

Can confirm this is an AMD specific problem. Doesn't work on my AMD based PC, but boots OK on my Intel laptop. Since OSX is only designed to work on Macs (which have Intel processors), not too surprising I guess.

@adhikjoshi
Copy link

I have same issue, Not working on AMD Cpu

@rkitover
Copy link

Any chance someone could use some of the AMD hackintosh magic to make things work?

@syntaxerror
Copy link
Author

Personally I gave up the hole Vagrant thing long time ago, bought a cheap used MacBook Pro instead for web testing ...

@vanishtachangea
Copy link

Did anyone solve this issue?
I have Ubuntu 18.04.1 LTS and I am using a Virtual Box with Linux 16.04 with Vagrant because Hyperledger is not supported on Ubuntu 18.
But now, Ubuntu does not appear to be loading in the virtual Box, I'm gettng the black screen.
I can do Vagrant ssh into the VM etc... But I cannot use the Virtual Box at all apart from running commands.
Any help please?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants