I don't sleep well if I know that my dear VPS has some error on boot...
My VPS is money and I can not afford to have downtime or other problem...

This really is not a problem. I just did a fresh install of CentOS and it does not have /dev/tty0.

'Fixing' it will involve messing with your udev config and/or the contents of /etc/rc.d. You run the risk of introducing errors or unforeseen results by changing things.

It ain't broke, so don't fix it.

_________________
/ Peter

I'm using linux for more than 12 years now and this "new theory" is quite strange for me but I can admit that it can work well...
You told me that you have the same problem with a fresh install of CentOS 5.3? Do you have the same error on boot???
I mean this error:
Starting udev: [ OK ]
Loading default keymap (us): /etc/rc.d/rc.sysinit: line 396: /dev/tty0: No such file or directory
[FAILED]

Yes, and other errors caused by Xen virtualisation / lack of physical hardware / stuff that's just not there, e.g.

Applying Intel CPU microcode update: FATAL: Module microcode not found.
/etc/rc3.d/S00microcode_ctl: microcode device /dev/cpu/microcode doesn't exist?

and

Loading additional iptables modules: ip_conntrack_netbios_ns [FAILED]

_________________
/ Peter

ok, since I hate see to error I can give you a tip for the last two error
for the first one, simply
disable the service cpu_microcode.
for the second one, edit /etc/sysconfig/iptables-config
and change this two lines from:
IPTABLES_MODULES="ip_conntrack_netbios_ns"
IPTABLES_MODULES_UNLOAD="yes"

to

IPTABLES_MODULES=""
IPTABLES_MODULES_UNLOAD="no"

If someone, will find a solution to the tty0 problem, will be really much appreciated.

You could just change the script to use /dev/tty1 instead of /dev/tty0 wherever it appears: sed -i.orig 's#/dev/tty0#/dev/tty1#g' /etc/rc.d/rc.sysinit

Don't know what unintended effects that might have, though...

I don't know too what it could create, so I'll not change it...