What factor can protect against console result from "virsh -c qemu:/// system console guest1"?

I'm running KVM on a Ubuntu 10.04 host. The visitor OS is additionally Ubuntu 10.04.

I am trying to connect to the visitor making use of the 'console' command. It appears I can develop a link, yet I get no result.

$ sudo virsh -c qemu:///system console guest1
Connected to domain guest1
Escape character is ^]
(NOTHING HERE)
^]
$

I do not have a 'serial' tool set up, yet I do have these 'console' tools.

<console type='pty' tty='/dev/pts/2'>
  <source path='/dev/pts/2'/>
  <target port='0'/>
</console>
<console type='pty' tty='/dev/pts/2'>
  <source path='/dev/pts/2'/>
  <target port='0'/>
</console>

Are these enough for a console, or do I require a serial tool too?

What do I require to do so as to get the KVM console to function?

0
2019-05-05 18:41:54
Source Share
Answers: 2

I'm rather certain you do require to set up the visitor to make use of a serial console. You require 3 points for this to function :

  1. offer the visitor a digital serial tool of type pty (as an example by including one in the virt-manager vm details web page)

  2. inform the kernel to make use of that for its result, by including boot parameters like serial=tty0 console=ttyS0,115200n8 right into GRUB_CMDLINE_LINUX in /etc/default/grub ; after that run sudo update-grub

  3. (optional) put a getty on ttyS0 to make sure that you get a login punctual

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507650 for extra.

0
2019-05-08 17:14:58
Source

One opportunity is that your digital equipment does not have a serial console set up.

virsh dumpxml guest1

will certainly show if there is a serial console set up or otherwise. There need to be something comparable as

<serial type='pty'>
<target port='0'/>
</serial>
0
2019-05-08 10:17:12
Source