Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

veewee build error, controlvm keyboardputscancode 01 returns fails. #415

Closed
editstudio opened this Issue · 11 comments

5 participants

@editstudio

I have been trying to package a default ubuntu box but getting an error from the second these two commands:

[bundle exec] veewee vbox define 'test-box' 'ubuntu-12.10-server-amd64'
[bundle exec] veewee vbox build 'test-box'

The result of the second is:

Received port hint - 7222
Found port 7222 available
Creating vm test-box : 2048M - 1 CPU - Ubuntu_64
Creating new harddrive of size 10140, format VDI, variant Standard 
Attaching disk: /stage/lab/VirtualBox VMs/test-box/test-box.vdi
Mounting cdrom: /stage/lab/projects/vm-test/veewee/iso/ubuntu-12.10-server-amd64.iso
Mounting guest additions: /stage/lab/projects/vm-test/veewee/iso/VBoxGuestAdditions_4.2.4.iso
Received port hint - 7222
Found port 7222 available
Changing ssh port from 22 to 7222
Waiting 4 seconds for the machine to boot
Received port hint - 7122
Found port 7122 available

Typing:[1]: <Esc><Esc><Enter>
Error: We executed a shell command and the exit status was not 0
- Command :VBoxManage controlvm "test-box" keyboardputscancode 01.
- Exitcode :139.
- Output   :
Segmentation fault (core dumped)

Wrong exit code for command VBoxManage controlvm "test-box" keyboardputscancode 01

Anyone had a similar experience?

Oh, I am running Virtualbox 4.2.4 on Ubuntu 12.10 64bit.

@jedi4ever
Owner

@editstudio what happens if you type the command " VBoxManage controlvm "test-box" keyboardputscancode 01" manually ?

@lukewpatterson
Collaborator

not sure how helpful this is - but at least the error is reproducible - https://travis-ci.org/veewee-community/proof-of-concept/builds/3394763/#L380

headless veewee has been giving me fits (still haven't found a way), and it was during a tweak to xvfb settings that the error appeared

like I said, not much to go on but maybe someone can see a pattern

@jedi4ever
Owner
@editstudio

I managed to get it working. The problem was that Intel VT was disabled, which is apparently required for using 64bit VMs. Perhaps its a similiar issue?

@jedi4ever
Owner
@editstudio
@lukewpatterson
Collaborator

Or am I mistaking here and it used to work on travisci before?

@jedi4ever - I thrashed around a few months ago trying to get veewee running in travis. I could get virtualbox running (e.g. https://travis-ci.org/veewee-community/travis-vagrant-up/builds/3427898/#L297), but never veewee. Actually, even if I can get past the keyboard inputs, I'll probably still be fighting the clock with the 25 minute travis build timeout. If I can ever get it going, the next step is box upload to the github repo's 'download' section. Then consumers will have complete open-source and transparent build all the way through, and it will be easier to trust the box downloads.

both my main user and test user (with extra group *vboxusers) could build boxes

@editstudio - do you have any scripts snippets you can share? Did you ever get it working completely headless, without virtual display? I guess I wouldn't care even if it did require virtual display, as long as I could get it going on travis.

@jedi4ever
Owner
@heymishy

actually was related to architecture, i'd accidently selected an x86 image rather than amd64. was obviously crashing instantly upon firing the VM. switching to amd64 worked fine.

now im getting stuck waiting for the winrm service to connect to the windows guest, as per: hh/windows-fromscratch#1

@yeukhon

Okay. I think the issue has to do with gui display. If you are like me working via ssh and hates -X option,
try again with:
veewee vbox build 'mybox' -a --nogui --force

output:

The isofile ubuntu-12.04.1-server-i386.iso already exists.
VBoxManage unregistervm  "myubuntubox" --delete
Deleting vm myubuntubox
Creating vm myubuntubox : 400M - 1 CPU - Ubuntu
Creating new harddrive of size 10140, format VDI, variant Standard 
Attaching disk: /home/glasslab/VirtualBox VMs/myubuntubox/myubuntubox.vdi
Mounting cdrom: /home/glasslab/veewee/iso/ubuntu-12.04.1-server-i386.iso
Mounting guest additions: /home/glasslab/veewee/iso/VBoxGuestAdditions_4.2.0.iso
Received port hint - 7222
Found port 7222 available
Received port hint - 7222
Found port 7222 available
Changing ssh port from 22 to 7222
Waiting 4 seconds for the machine to boot
Received port hint - 7122
Found port 7122 available

Typing:[1]: <Esc><Esc><Enter>
Typing:[2]: /install/vmlinuz noapic preseed/url=http://10.0.2.2:7122/preseed.cfg 
Typing:[3]: debian-installer=en_US auto locale=en_US kbd-chooser/method=us 
Typing:[4]: hostname=myubuntubox 
Typing:[5]: fb=false debconf/frontend=noninteractive 
Typing:[6]: keyboard-configuration/layout=USA keyboard-configuration/variant=USA console-setup/ask_detect=false 
Typing:[7]: initrd=/install/initrd.gz -- <Enter>
Done typing.

Starting a webserver :7122

Now common issues may arise:

hangs on starting a webserver for a long time
I suggest change :boot_wait => "10", to a larger number. On a really slow machine (I am still testing this on a P4 CPU), try 120 seconds.

I also had to wait 8 minutes before passing ssh.

We should compile a doc with common Q&A.

@jedi4ever
Owner

closing as this ticket was created because of problem with X display and not specifying --no-gui.

I can't check more in veewee.

@jedi4ever jedi4ever closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.