Since VPS has become quite an affordable option these days to shared hosting, I'm looking to move to a Linux-based VPS so that I can benefit from features like using my own choice of server software (I plan to use nginx instead of Apache) and also for SSL for some parts of my site, and full configuration control.

Is unmanaged VPS the way to go? I am a fairly experienced *nix user and know a bit about system configuration, but I haven't really managed a full server system.

Does managing a VPS require a lot of time ? I ask, because I have a full time job and I cannot devote a lot of time and energy for this.

Also what amount of dedicated memory and processor resources would be recommended at minimum for a simple personal website/blog?

If all you need is a web-server then I'd say it doesn't take a lot of time to keep it running. Go for a minimal install of OS, then only install packages absolutely needed.
Now you should really update the system at least once a month - but of course it depends on what risks you are willing to take. Updating doesn't take much time normally as it's done via package manager.
But beware, it might happen that an update breaks things, you need to make a plan how to handle that. I always recommend to install only the OS via package management tool, then the services you rely on you should ínstall manually. Why? Simple: you will not risk surprises, like when Ubuntu switched from apache-2.2 to apache-2.4 and no site was accessible (happened to a friend once).
I do this:
Install apache, php & mysql/mariadb in directory /private/apps/. Then symlink them, so apache-2.2 points to apache-2.2.29 etc. When you update, just install next version in /private/apps/, change the symlink to point to new installation. Test it - if something is wrong just change symlink back.

Hmm I'm getting a bit OT now I think. Well then, to your last question:
For a small webserver I usually choose 1 CPU and 1 GB ram. Check resource usage carefully, especially the database could require more.

One important thing: Some VPS providers gives you a firewall with a webgui together with your VPS, some don't. If not you'll have to configure iptables on your server. Not necessarily bad, but if you're not familiar with iptables it could be a hassle.

... or hire me to keep your server secured & updated! :-) That's what I do for a living, and I dare say I'm pretty good at it!

Current Rates

pingu, thanks for the tips. I will probably base the VPS on a stable version of Debian. I've seen some providers that use OpenVZ virtualization. This generally seems cheaper and provides for more efficient usage of (shared) resources than full virtualized containers. But of course, that limits some of my configurable options. What would be the benefits and disadvantages of forgoing full virtualization? I am not looking to tweak the system configuration much, if at all.

If I go the OpenVZ route, what should be the minimum dedicated resources I should choose, CPU-wise and RAM-wise?

(Oh, am I am not planning to run MySQL/MariaDB or any other database server. My simple blog is served by SQLite and other pages are served either by simple PHP or plain static HTML).

what VPS providers offer natively routed IPv6?

all i need in a web server is the ability to do an HTTP redirect. not even DNS. so i need even less. can a web hoster do that? i do need it to work on IPv6.