News for hackers. Stuff that matters.

A comment on Trigger a Kernel Panic to Diagnose Unresponsive EC2 Instances. Parent comment

Re:Trigger a Kernel Panic to Diagnose Unresponsive EC2 Insta... by technion on Thursday August 15, 2019 @07:15PM (#20710620)
That's only an output image though. The ability to interact with the console is always something I've missed from on-premises hypervisors.
[ Parent | on HN ]
Re:Trigger a Kernel Panic to Diagnose Unresponsive EC2 Insta... by andoma on Thursday August 15, 2019 @07:19PM (#20710650)
FWIW, GCE have console. Another thing I miss in AWS is the ability to change instance user-data while running (GCE also allows this, including the ability to long-poll for changes)
[ Parent | on HN ]
Re:Trigger a Kernel Panic to Diagnose Unresponsive EC2 Insta... by kornholi on Thursday August 15, 2019 @08:15PM (#20710989)
Yeah, I've used GCE's console many times with SysRq to debug frozen instances. Surprised that AWS doesn't have one.
[ Parent | on HN ]
Re:Trigger a Kernel Panic to Diagnose Unresponsive EC2 Insta... by deathanatos on Friday August 16, 2019 @04:21AM (#20713155)
Rackspace (at least, when I worked for a company that used them) has access to the console; their website has a link to a VNC page (running a Java applet) that connects to the console of the VM; you can even type into it, unlike AWS.

It was extremely handy, and I miss having it. Debugging issues in AWS is a bit trickier.

[ Parent | on HN ]