Terminal Window bBlank

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
mickiepitts
Posts: 2
Joined: 5. Jan 2019, 16:18

Terminal Window bBlank

Post by mickiepitts »

I installed VitualBox on my MAC and everything seams to work find. In my VMB Window it always blank. Any Suggestions how I can get HASSOS on it?
Attachments
Screen Shot 2019-01-05 at 9.22.39 AM.jpg
Screen Shot 2019-01-05 at 9.22.39 AM.jpg (33.44 KiB) Viewed 1274 times
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Terminal Window bBlank

Post by socratis »

For future reference, next time please downsize your attached PNG (not JPG) images by 50% (at least), or simply change the DPI to 72. Not everyone has the luxury of a HiDPI display. And preview the message; does the pic look big? You're not doing something right then... ;)

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
mickiepitts
Posts: 2
Joined: 5. Jan 2019, 16:18

Re: Terminal Window Blank

Post by mickiepitts »

Attached is the log, I do see an error, but have no idea what ti means.

Thank you for looking a this.
Attachments
Home_Assistant-2019-01-06-06-42-58.log.zip
(20.42 KiB) Downloaded 22 times
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Terminal Window bBlank

Post by socratis »

Do you mind sharing some details about what is this thing? What is HASSOS, what's supposed to be doing, what's it running on, where did you get it from, what do you expect. You know, some basic introductory stuff, so we won't have all of us to go hunting around for information?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
andyp73
Volunteer
Posts: 1631
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: Terminal Window bBlank

Post by andyp73 »

I am presuming that it is HassOS which is some kind of home assistant talk to your IoT device type platform. To quote from the linked page...
Download the appropriate install option:
...
As a virtual appliance:

VMDK (VMWare Workstation)
VHDX (beta)
VDI (beta)
OVA (not available at this time!)
Given the VDI is labelled as beta and the OVA as not available I wouldn't be surprised if there are issues.

-Andy.
Last edited by socratis on 7. Jan 2019, 10:26, edited 1 time in total.
Reason: Modified URL.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Terminal Window bBlank

Post by socratis »

  • Install the Extension Pack on the host.
  • Change the VM template to "Linux 2.4/2.6 (64 bit)" from "Ubuntu (64)".
  • Enable PAE.
  • Change the USB to USB 2.
  • Change the vGPU from VMSVGA to VBoxVGA. This is your main problem; UEFI and VMSVGA don't mix well. At all actually, see https://www.virtualbox.org/ticket/18282
  • Increase the VRAM to 128 MB.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply