Skip to main content

Access a KVM VM's console when all hope is lost

It's pretty simple for the Linux gurus I'm sure...but I ran into the following scenario with one of my clients.

Longtime Linux admin leaves - he built all the systems - and a temp admin takes over (part of a takeover).  New management decrees security policies, so he resets all of the old ssh account passwords - the changes are not documented.  The takeover falls apart, the temp admin is no longer an employee, and control is handed back to the original company.  They are left with no admin, and no passwords.

The original admin did a great (maybe slightly paranoid) job of setting up and hardening the servers, so of course root has no ssh.  This can be overcome by logging on to the console, no problem.

One of the other projects the original admin set up was a couple of KVM clusters - they worked great, but one cluster had weird issues (probably hardware/networking, but the original admin left before it could be resolved), and since the temp Linux admin couldn't figure them out, the original management team said forget it...move all the VMs over to our VMware clusters.

With the temp admin gone, I was contracted on to help out.  Going back to the KVM issue...the problem is that there was no console method to access the KVM VMs.  No console, no ssh...no access.  Bad news bears, right?

Well, there is of course a way to get console access, but you have to be a Linux admin/power user to get that.  (I am neither, really)  SSH forwarding!  You forward the X11 session back to your computer, run virt-manager, and bam!  Access!  Unfortunately, this is super easy if you're using Linux as your workstation OS...and of course super not-easy if you're using Windows.

Google (lots...and lots...of google) to the rescue!

  1. Configure Putty to use X11 forwarding
  2. Install Xming on your Windows workstation (without this you get connection rejected errors in your putty log - CTRL + right-click on your session window!!!)
  3. Ensure the KVM hosts themselves have functional X11 forwarding (sshd_config, ssh_config) - without this you get authentication/authorization errors
  4. When you connect with Putty, if things are good you should get a 'localhost' line if you run this: echo $DISPLAY (if you're not running xming on your workstation, you'll get a blank line, among other errors)
  5. Run virt-manager (you'll need the root password, too)
  6. It'll pop up - job done!
Of course, this only worked because we had console access to the KVM hosts.

Side note: Some would say, oh, but there is a console access method for KVM VMs!  You set up a serial TTY port and whatnot, you can directly connect from the KVM host console!  Very much so...but you have to first configure something inside the VM (via ssh, of course), and if you don't have SSH access or console access...well...ya.

Another side note:  I had to bypass a lot of security stuff to get this far, so don't forget to turn all that back on once you're done!




Comments

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…