Date: Wed, 3 Dec 2008 12:35:06 +0100 [ (text/plain, inline)] Package: libvirt-bin Version: 0.5.0-1 Severity: normal File: /usr/bin/virsh I have a test domain with and kvm properly starts it with -monitor pty and -serial pty. When I run 'virsh console' on it, virsh just hangs and cannot be stopped/interrupted with any of ctrl-c/z/. SIGTERM works. Strace is attached (search for 'HANGS HERE'). Date: Fri, 5 Dec 2008 10:09:10 +0100 tags 507650 + moreinfo On Wed, Dec 03, 2008 at 12:35:06PM +0100, martin f krafft wrote: > Package: libvirt-bin > Version: 0.5.0-1 > Severity: normal > File: /usr/bin/virsh > > I have a test domain with > > > > > > and kvm properly starts it with -monitor pty and -serial pty. The bhyve driver in libvirt is in its early stage and under active development. So it supports only limited number of features bhyve provides. Note: in older libvirt versions, only a single network device and a single disk device were supported per-domain. However, since 1.2.6 the libvirt bhyve driver supports up to 31 PCI devices. Virt-install is a command line tool for creating new KVM, Xen, or Linux container guests using the 'libvirt' hypervisor management library. See electrical v7r1. See the EXAMPLES section at the end of this document to quickly get started. When > I run 'virsh console' on it, virsh just hangs and cannot be > stopped/interrupted with any of ctrl-c/z/. SIGTERM works. Strace is > attached (search for 'HANGS HERE'). You can't terminate this with 'ctrl-alt-]'? Can you make sure your system really *has* output on the serial console by looking at the /dev/pts/X yourself? ![]() You can find out the pty by looking at /var/log/libvirt/qemu/.log - it should be the last second pty listed. The first one is the monitor pty. Cheers, -- Guido. Date: Sun, 7 Dec 2008 19:04:27 +0100 [ (text/plain, inline)] clone 507650 -1 severity -1 normal retitle -1 ctrl-alt-] does not terminate the console reopen -1 found -1 0.4.4-3 thanks also sprach martin f krafft [2008. +0100]: > Keygen php maker templates. No, ctrl-alt-] does not terminate the console. This problem stays, but. > I can use minicom like this: > > minicom -op /dev/pts/3 > > to connect to the monitor just fine, but connecting to /dev/pts/4 > doesn't do anything. There seems to be no output, and minicom does > not accept any input from me either. Yet, the guest is running. This is now solved. I forgot that we are talking serial console and that I would thus need to modify the kernel boot command line, as well as /etc/inittab. As soon as I changed the first to root=/dev/vda1 ro serial=tty0 console=ttyS0,115200n8 quiet and appended to inittab: T0:S12345:respawn:/sbin/getty -hL ttyS0 115200 vt100 it starts to work. Magic.:) PS: I wish qemu would just give me an easy access to tty0, like Xen does. Krafft Related projects:::': proud Debian developer `. `'` `- Debian - when you have better things to do than fixing systems * Overfiend came out of the womb complaining. -- #debian-devel [ (application/pgp-signature, inline)]. Date: Thu, 11 Dec 2008 20:44:23 +0100 [ (text/plain, inline)] reopen 507650 retitle 507650 virsh console just hangs, cannot connect remotely thanks Even though virsh console now works locally, doing the same via qemu+ssh from a remote system exhibits exactly the same behaviour when I try to connect to it via qemu+ssh. It seems that virsh tries to open the *local* /dev/pts/*, which is a little suboptimal.:) --.' Krafft Related projects:::': proud Debian developer `. `'` `- Debian - when you have better things to do than fixing systems never trust an operating system for which you do not have the source. -- source unknown [ (application/pgp-signature, inline)]. Date: Fri, 12 Dec 2008 09:14:26 +0100 [ (text/plain, inline)] retitle 507650 'virsh console should work for remote connections' severity 507650 wishlist On Thu, Dec 11, 2008 at 08:44:23PM +0100, martin f krafft wrote: > Even though virsh console now works locally, doing the same via > qemu+ssh from a remote system exhibits exactly the same behaviour > when I try to connect to it via qemu+ssh. > > It seems that virsh tries to open the *local* /dev/pts/*, which is > a little suboptimal.:) 'virsh console' is currently strictly local, it simply opens the pty specified in the XML config. It also assumes you have the permission to access the device (so while you can manage the vm as non root you might to be root to read the serial console). Ideally this would be routed to libvirtd itself for permission checking and remote console forwarding. Cheers, -- Guido [ (application/pgp-signature, inline)]. Bug archived. Request was from Debbugs Internal Request to [email protected].
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |