Apologies for the premature submission for #0 :

It looks like some bots are not properly exposing the KVM virtual device:

From https://chromium-swarm.appspot.com/user/task/3ce8aae548ef7810 :

"833.771944046:DEBUG:ssh:ssh exec: ssh -F /b/s/w/ir/out/repro/ssh_config localhost -p 32946 true
Could not access KVM kernel module: No such file or directory"

That bot has dimension kvm:0, did we lose a thing somewhere?

Re #1: Can you provide the link to the bot rather than the task? It's not clear [to me] what it was that requested that task in the first place.

And another...

https://chromium-swarm.appspot.com/task?id=3ce90a42995f1e10&refresh=10&show_raw=1

I'll see if we lost a dimension.

FYI: Kevin clarified offline that these are tasks from local manual runs of "swaring.py".

I triggered these locally using dimensions copied from a bot's swarming trigger step. Let me trace these back to the bot.

I believe this is working as intended. If you want to run a task on a bot with kvm, you need to add it to the dimensions you request explicitly w/

  swarming.py trigger ... -d kvm 1 ...

or something along those lines.

Feel free to reopen if you disagree w/ more details about what exactly you ran locally.