I've built amd64 unstable HVM image. It successfully started on m3.xlarge. On cg1.4xlarge it starts but I cannot connect via ssh - it looks like previous attempts (before Anders fixed HVM). SSH just timeouts, and I got: System status Checks: System reachability check passed Instance Status Checks: nstance reachability check failed at January 21, 2014 7:20:00 PM UTC+1 (9 minutes ago) I cannot even start my image on g1.2xlarge - i get message: Instances of type 'g2.2xlarge' may not be launched from AMI 'ami-f91f2d90' Hide launch log Creating security group Successful (sg-4797af2c) Authorizing inbound rules Successful Initiating launch FailureRetry The same situation is with images you gave, from account 379101102735, debian-wheezy-amd64-hvm-2014-01-20-ebs - ami-31d0e258 > > > James > [1] g2 is based on the nvidia Keplar GK104 > (http://aws.amazon.com/ec2/instance-types/#instance-details). See > also > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using_cluster_computing.html. Perhaps we should test out nouveau? -- Tomasz Rybak GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak
Attachment:
signature.asc
Description: This is a digitally signed message part