The strange thing is to connect to the Guest console according to the official RHEL file, but the system is like a dead fish, no response !! Check the/var/log/message of Guest and find that there is no console. After one afternoon, it seems that the security permission cannot allow the console to log on !! However, this should be caused by no response from the Guest console to the root user.
The strange thing is to connect to the Guest console according to the official RHEL file, but the system is like a dead fish, no response !! Check the/var/log/message of Guest and find that there is no console. After one afternoon, it seems that the security permission cannot allow the console to log on !! However, this should be because the console of the root user should not respond to the Guest. Check whether the Guest still needs to be set. Otherwise, the command xm console alone cannot be logged in !!
1. In/boot/grub. conf
Specify the console value "console = tty0 console = xvc0"
[Root @ benjr ~] #Vi/boot/grub. conf Title Red Hat Enterprise Linux ES (2.6.9-78. ELxenU) Root (hd0, 0) Kernel/boot/vmlinuz-2.6.9-78.ELxenU ro root = LABEL =/Console = tty0 console = xvc0 Initrd/boot/initrd-2.6.9-78.ELxenU.img |
2./etc/inittabYou cannot use comport to log on to the system by default. Therefore, modify/etc/inittab,
[Root @ benjr ~] #Vi/etc/inittab Co: 2345: respawn:/sbin/agetty xvc0 9600 vt100-nav |
3./etc/securettyDue to PAM restrictions, root cannot use comport to log on to the system. Therefore, modify/etc/securetty:
[Root @ benjr ~] #Vi/etc/securetty Xvc0 [Root @ benjr ~] #Xm list Name ID Mem (MiB) VCPUs State Time (s) Domain-0 0 1231 4 r ----- 150.1 Rhel4.6 2 255 1-B ---- 0.1 Rhel5 4 511 1-B ---- 2.2 |
You will see all the Guest currently in the running status.
[Root @ benjr ~] #Xm console rhel4.6 |
If the settings are correct, you can see the console screen !!
This problem can be solved as described above.