I would judge that person more than someone who's not had any IT work at all in their lives.
With VM's, tech previews, evaluations and a ton more, I would worry about someone who's not only allowed themselves to get stuck in a rut and can't poke their head above, but also complains about lack of training when they aren't doing stuff themselves. And when you get into stuff like Linux, free Hyper-V hypervisors, etc. there's really no excuse for not having tinkered with something. That your employer didn't want to actually deploy it is neither here nor there.
I'm not saying that's you, I'm blowing up one comment to become a persona here, but I worked as a "roaming tech" (I hate the word consultant) for many years - zero equipment beyond what the place had already, no budget to get new stuff, emergency cases in dire situations, stuff I've never had to deal with before and need to learn "on the job", and then "oh, can you just make it do this" and I came through without any "training" of any kind. In fact, where offered I actively refused because it was unsuitable and/or only trained me on what I already do day-in, day-out.
I never expect anyone to have used a particular product, or feature, but I expect them to have an outline of what it is, have played with similar features and - even if it means clarification like "Hyper-V is a virtualisation hypervisor" - that they can then pick up on it and go "Oh, right, well, I've played about with some of the ESX / VMWare stuff and I've done a bit of Xen for my own stuff but I haven't touched Hyper-V personally".
The answer "Nope, I've never deployed it outside my personal test environments, but I think I have a grasp of what's involved because I've done a lot of tinkering on my personal test network at home" is actually VASTLY informative to an employer. It means you're happy to admit holes in your knowledge, happy to play and tinker, able to do these things off your own back, have some experience of the concept, have taken the time to learn on your own time, and are not scared to say "Never done it 'for real' but I'll have a go if you're okay with that".
I have to agree with your last paragraph. But if you've been in a position for 3 years and not progressed in some way, I judge that person just as much for not having stretched themselves, done things on their own time, etc. I'm not a "management" sort, except in job-title. I'm purely functional and hands-on. But I worry about people who need "training" to have booted up something in VMWare and played about with the new features. Hell, when a new OS comes out, I pretty much compete with those around me to find the holes and the problems in it as soon as the first public preview is available.
The best teams I've worked on, are basically competition over who's deployed some new technology before. Then you become the "virtualisation guru" of the team because you've done it a bit at home. Then someone else starts putting in some HA functions into your hypervisors to beef them up and "beats you" because they read something on Google and try it on the test network. I've had competitions over who could deploy a PHP-enabled web server first back when PHP was new to us, and one of us did it on Linux and one of us heard it was possible on Windows. The thing never went into service, but the curiosity was there.
Sure there are some dead-end jobs, but the point of IT is that like most other professions (as opposed to just "jobs") you HAVE to keep on top of it. A doctor who doesn't research a strange condition he comes across or a lawyer who doesn't bother to read the new legislations would be out of a job soon too. Or stuck doing only the stuff people tell them to do.
Please note, I have no industry certifications. I have a degree in mathematics. But I have had a career exclusively in IT for a decade and a half. Because when someone says "Our servers are a little overworked, there's a bottleneck here, what can we do?", I go research the answer.
Don't expect training in IT. It doesn't happen. Because those who need it you won't want to give it to them (a little knowledge is dangerous) and those who you might want to give it to don't need it.