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

Already on GitHub? Sign in to your account

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

Closed
editstudio opened this Issue Oct 29, 2012 · 11 comments

Comments

Projects
None yet
5 participants

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.

Owner

jedi4ever commented Nov 5, 2012

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

Collaborator

lukewpatterson commented Nov 28, 2012

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

Owner

jedi4ever commented Nov 28, 2012

Interesting! You're running veewee on travisci.

But isn't travisci using virtualbox itself? So you'll get virtualbox in
virtualbox?
Or am I mistaking here and it used to work on travisci before?

On 28/11/12 06:39, Luke Patterson wrote:

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
https://github.com/veewee-community/proof-of-concept/commit/85a7d07741ccc471879ba16bddaae0432fd58b23
settings that the error appeared

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


Reply to this email directly or view it on GitHub
#415 (comment).

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?

Owner

jedi4ever commented Nov 28, 2012

Ha, that might be a good thing to investigate. Wonder how we can check
if it is enabled or not.

Those who had the problem , were you running linux as a host (not guest) ?

On 28/11/12 08:30, editstudio wrote:

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?


Reply to this email directly or view it on GitHub
#415 (comment).

It is normally set in the bios, but exactly where depends on you
motherboard maker I guess.

Originally, I tested building a box as a separate user. This led to the
output I posted previously. However, since that new user did not have
xconf/ui setup, I did not know VirtualBox was popping up a message warning
me about virtualisation for 64bit boxes, which I discovered after trying
the same procedure with my user with xconf setup. After I enabled VT, both
my main user and test user (with extra group vboxusers) could build boxes.

I use linux (Ubuntu 12.10, 64bit) as the host machine.

On Wed, Nov 28, 2012 at 8:33 AM, Patrick Debois notifications@github.comwrote:

Ha, that might be a good thing to investigate. Wonder how we can check
if it is enabled or not.

Those who had the problem , were you running linux as a host (not guest) ?

On 28/11/12 08:30, editstudio wrote:

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?


Reply to this email directly or view it on GitHub
#415 (comment).


Reply to this email directly or view it on GitHubhttps://github.com/jedi4ever/veewee/issues/415#issuecomment-10793202.

Collaborator

lukewpatterson commented Nov 30, 2012

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.

Owner

jedi4ever commented Jan 6, 2013

hi , it seems it's the vboxmanage command that seg-faulted.
not a lot veewee can do about that.

can you try creating a vm manually with vboxmanage and see if that works?
you might get some clue via the vbox logging?

On 05 Jan 2013, at 22:08, Hamish King notifications@github.com wrote:

Im trying to build a basebox whilst already in a VM (windows host, Ubuntu VM) and Im getting same error code. Have VT enabled in the bios

I would built it locally but currently not dual-booting with linux and was trying to keep it within a VM.

vagrant@lucid32:~/veewee$ vagrant basebox build win2k8
[win2k8] Downloading vbox guest additions iso v 4.2.6 - http://download.virtualbox.org/virtualbox/4.2.6/VBoxGuestAdditions_4.2.6.iso
[win2k8] Checking if isofile VBoxGuestAdditions_4.2.6.iso already exists.
[win2k8] Full path: /home/vagrant/veewee/iso/VBoxGuestAdditions_4.2.6.iso
[win2k8]
[win2k8] The isofile VBoxGuestAdditions_4.2.6.iso already exists.
[win2k8] Building Box win2k8 with Definition win2k8:
[win2k8]
[win2k8] The isofile 6001.18000.080118-1840_x86fre_ServerWeb_en-us-KRMWFRE_EN_DVD.iso already exists.
[win2k8] Creating vm win2k8 : 384M - 1 CPU - Windows2008
[win2k8] Creating new harddrive of size 20280, format VDI, variant Standard
[win2k8] Attaching disk: /home/vagrant/VirtualBox VMs/win2k8/win2k8.vdi
[win2k8] Mounting cdrom: /home/vagrant/veewee/iso/6001.18000.080118-1840_x86fre_ServerWeb_en-us-KRMWFRE_EN_DVD.iso
[win2k8] Mounting guest additions: /home/vagrant/veewee/iso/VBoxGuestAdditions_4.2.6.iso
[win2k8] Received port hint - 7235
[win2k8] Found port 7235 available
[win2k8] Received port hint - 7235
[win2k8] Found port 7235 available
[vagrant] Changing ssh port from 22 to 7235
[win2k8] Waiting 50 seconds for the machine to boot
[win2k8]
[win2k8] Typing:[1]:
[win2k8] Error: We executed a shell command and the exit status was not 0
[win2k8] - Command :VBoxManage controlvm "win2k8" keyboardputscancode 0f.
[win2k8] - Exitcode :139.
[win2k8] - Output :
Segmentation fault

Wrong exit code for command VBoxManage controlvm "win2k8" keyboardputscancode 0f
vagrant@lucid32:~/veewee$

Any ideas?


Reply to this email directly or view it on GitHub.

heymishy commented Jan 7, 2013

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 commented Jan 21, 2013

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.

Owner

jedi4ever commented Feb 20, 2013

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 Feb 20, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment