Hide Forgot
If I enter and exit the console of a domain multiple times in one interactive virsh session, I see garbled console output that's consistent with multiple consoles being open at the same time. 0.9.4-4
Dave , would you please help confirm if the following stuff is the exact reproducer for this bug ? tested with libvirt-0.9.4-4 steps : 1. configure guest grub with "console=tty0 console=ttyS0,115200n8" appended in the kernel command line 2. configure guest with serial device added <serial type='pty'> <source path='/dev/pts/5'/> <target port='0'/> <alias name='serial0'/> </serial> 3. start guest 4. enter interactive mode of virsh # virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # console test1 Connected to domain test1 Escape character is ^] � Welcome to Red Hat Enterprise Linux Client Starting udev: virsh # console test1 Connected to domain test1 Escape character is ^] [/sbin/fsck untin quotas: virsh # console test1 Connected to domain test1 Escape character is ^] 6_64 on an x86_646_64 on an x86_64x86_64 on an x86_64 After times of Enter-Exit loop , we get the garbled console output in interactive virsh session . Additional info: This can be only seen in virsh interactive mode .
Yes, that's exactly it.
tested with libvirt-0.9.4-9.el6 qemu-kvm-0.12.1.2-2.185.el6 kernel-2.6.32-193.el6 steps : 1. configure guest grub with "console=tty0 console=ttyS0,115200n8" appended in the kernel command line 2. configure guest with serial device added <serial type='pty'> <source path='/dev/pts/5'/> <target port='0'/> <alias name='serial0'/> </serial> 3. start guest 4. enter interactive mode of virsh # virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # console test1 Connected to domain test1 Escape character is ^] connect-disconnect loop won't make a garbled console output. So set bug status to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1513.html