Task #2840 (closed)
Opened 9 years ago
Closed 9 years ago
Bug: VM does not start up. | ssh to vm on 10.*.148 fails
| Reported by: | jamoore | Owned by: | atarkowska |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-Beta4.2.1 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | cxallan, dzmacdonald |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | 2010-09-09 (16) |
Description
The following which works locally fails on 10.*.148, both with the open source virtualbox-ose as well as the proprietary package:
$ sh createVM.sh ... $ VBoxManage startvm SEPT1 --type headless $ ssh -vvvv omero@localhost -p 2222 OpenSSH_5.3p1 Debian-3ubuntu4, OpenSSL 0.9.8k 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to localhost [::1] port 2222. debug1: connect to address ::1 port 2222: Connection refused debug1: Connecting to localhost [127.0.0.1] port 2222. debug1: Connection established. debug1: identity file /home/hudson/.ssh/identity type -1 debug1: identity file /home/hudson/.ssh/id_rsa type -1 debug1: identity file /home/hudson/.ssh/id_dsa type -1 ...HANGS HERE...
Change History (9)
comment:1 Changed 9 years ago by jburel
- Sprint changed from 2010-08-26 (15) to 2010-09-09 (16)
comment:2 Changed 9 years ago by atarkowska
comment:3 Changed 9 years ago by atarkowska
- Summary changed from Bug: ssh to vm on 10.*.148 fails to Bug: VM does not start up. | ssh to vm on 10.*.148 fails
comment:4 Changed 9 years ago by atarkowska
comment:5 Changed 9 years ago by atarkowska
The problem is with hardware "VT-x/AMD-V hardware acceleration is not available on your system..." - VT-x/AMD-V hardware acceleration is not available on the 10.2.1.148
comment:6 Changed 9 years ago by dzmacdonald
Linux: egrep -c '(vmx|svm)' /proc/cpuinfo returns 1 if supported
MacOSX: sysctl machdep.cpu.features | egrep -c VMX returns 1 if supported
comment:7 Changed 9 years ago by atarkowska
- Status changed from new to assigned
comment:8 Changed 9 years ago by atarkowska
- Owner changed from dzmacdonald to atarkowska
comment:9 Changed 9 years ago by cxallan
- Resolution set to invalid
- Status changed from assigned to closed
First of all the output does not match the script. Second, the problem is not with ssh, but with the VM it self. You could not create because it did not start.
The error is: