You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the image in #34 , I was able to get as far as getting VirtualBox up and running. It does appear to be doing something (checking top shows the CPU going up quite a bit, and then falling off again), but whatever the create script is waiting for never happens.
I've verified this on my local Ubuntu machine and a cloud Ubuntu VM. Same behavior :/
~/src❯ t2-vm create
Initializing VM...
? Choose a bridge interface (or hit enter) em1
Downloading image...
.......... downloaded ...
Creating VM...
Attaching to serial port: /usr/local/google/home/cflewis/.tessel/vm.port
Configuring VM...
Opened serial connection to VirtualBox...
Awaiting hostname...
This seems to be taking way too long.
Perhaps CTRL+C and try again.
The text was updated successfully, but these errors were encountered:
From what I can tell, this will never work. It seems to me that the prompt (which you get if you boot the image and hit "Return" after it's finished) says test_ap whereas the script is looking for something with tessel in the name.
Hacking in test_ap to the script doesn't work though, as the initialize function fails to sed what it needs to either, and I don't know enough about TCP sockets to know how to begin debugging that :(
I had the same issue:
Awaiting hostname...
This seems to be taking way too long.
Perhaps CTRL+C and try again.
This is how I was able to get past this problem:
Launch vm console on virtualbox.
Edit file /etc/config/system. Change HOSTNAME from 'test_ap' to 'Tessel-XXXXXXXX'.
Reboot
Using the image in #34 , I was able to get as far as getting VirtualBox up and running. It does appear to be doing something (checking
top
shows the CPU going up quite a bit, and then falling off again), but whatever thecreate
script is waiting for never happens.I've verified this on my local Ubuntu machine and a cloud Ubuntu VM. Same behavior :/
The text was updated successfully, but these errors were encountered: