Bug#578186: closed by Guido Günther (Re: [Pkg-libvirt-maintainers] Bug#578186: libvirt0: Installation of a new vm within xen still fails to connect to a console)
From: ow...@bugs.debian.org To: john...@hotmail.com Subject: Bug#578186 closed by Guido Günther (Re: [Pkg-libvirt-maintainers] Bug#578186: libvirt0: Installation of a new vm within xen still fails to connect to a console) Date: Sat, 17 Apr 2010 18:21:10 + This is an automatic notification regarding your Bug report which was filed against the libvirt0 package: #578186: libvirt0: Installation of a new vm within xen still fails to connect to a console It has been closed by Guido Günther . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Guido Günther by replying to this email. -- 578186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --Forwarded Message Attachment-- Date: Sat, 17 Apr 2010 20:17:16 +0200 From: a...@sigxcpu.org To: 578186-d...@bugs.debian.org Subject: Re: [Pkg-libvirt-maintainers] Bug#578186: libvirt0: Installation of a new vm within xen still fails to connect to a console On Sun, Apr 18, 2010 at 01:47:34AM +, IAN DELANEY wrote: > The point I wish to express is that the fix was to leave this package broken, > and to backport to the later package. Well, a year later, I installed lenny > and acquired the broken package. > It took me days and days of trouble shooting and investigating virt-manager > and the error messages before finally finding the bug report, not the usual > activity for a regular user. > I happen to be a keen linux user and figured out enough to find the bug. Ian, please stop that. There's #578173 already open that describes this issue. Please add the requested further information there. The package is by no means unusuable - in fact lots of people are using it witk xen and kvm. Cheers, -- Guido Ian, please stop that. yep, ok. No problem with that. I made the point, so it's done. kvm and qemu are ok. My interest is in getting xen to work. _ View photos of singles in your area! Looking for a hot date? http://clk.atdmt.com/NMN/go/150855801/direct/01/
Bug#578186: libvirt0: Installation of a new vm within xen still fails to connect to a console
Package: libvirt0 Version: 0.7.6-1~bpo50+1 Severity: serious Justification: 2 Take a system on a cdrom or dvd e.g. hardy or karmic, invoke virt-manager to manage vms, select new to invoke the wizzard installer bringing virtinst to the table, enter required info to install, full virt for a cdrom or dvd. Pre enter to begin install, now it faulters. The vnc console comes up with the eroor message Console is not active for guest. This brings the package to its knees, totally unusable. Now, this is in fact 519809, March 2009. I find myself reporting a bug that was found a year ago. The point to make is that the package is still not fixed and reproduced all the difficulty and frustration that goes with this bug in place. To give this report a little more substance, the bug has two separate faces or parts; 1 - the console is not active for guest in the vnc console, & 2 - Attempting to attach to a tty console results in a second failure; Invoke xm console guestname live...@xenalive:~$ sudo xm console karmic xenconsole: Could not open tty : No such file or directory or close. This I tihnk is related to the choice of hvm to create the guest vm. The point is that the regular tty console can also not be connected, making a double failure. Now citing the bug number 519809, "I can confirm - I backported libvirt 0.6.1-1 from squeeze to lenny. The VNC console immediately works with virt-manager 0.6.0-6 after passing the wizard for creating a new guest." The point I wish to express is that the fix was to leave this package broken, and to backport to the later package. Well, a year later, I installed lenny and acquired the broken package. It took me days and days of trouble shooting and investigating virt-manager and the error messages before finally finding the bug report, not the usual activity for a regular user. I happen to be a keen linux user and figured out enough to find the bug. The report cites packages version number 0.6.0-6. suggesting a series of broken packages were never fixed. My lenny came supplied with 0.4.6-10, even earlier. I just wanted to see xen work. I also acquired live xen cd, which features lenny as a host. This gave me the impresiion that the supplied packages in lenny dom0 worked and were worthy to showcase management of xen. Oh, is this so not the case. On acquiring lenny, my first trouble came with the kernel, misfiring and failing to reach gnome. It still warrants a separate bug report. I only booted into xen in lenny by importing a gentoo xen kernel, as I also follow gentoo. As a user of lenny, could I suggest that leaving these broken packages in place is not helpful to your users. Could these packages either be fixed or withdrawn and replaced with upstream updated fixed versions that are supplied as standard packages to be used by the debian followers.Lenny is still the current release for debian, so it's the public face of debian standards and capabilities. Can lenny be relied upon to utilsise xen as a virtualisation option, or is it a case of declaring lenny a lemon, abandoning it and relying upon squeeze as a capable debian option? -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libvirt0 depends on: ii libc6 2.7-18GNU C Library: Shared libraries ii libgcrypt111.4.1-1 LGPL Crypto library - runtime libr ii libgnutls262.4.2-6 the GNU TLS library - runtime libr ii libgpg-error0 1.4-2 library for common error values an ii libsasl2-2 2.1.22.dfsg1-23 Cyrus SASL - authentication abstra ii libtasn1-3 1.4-1 Manage ASN.1 structures (runtime) ii libxenstore3.0 3.2.1-2 Xenstore communications library fo ii libxml22.6.32.dfsg-5 GNOME XML library ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages libvirt0 recommends: ii lvm2 2.02.39-6 The Linux Logical Volume Manager libvirt0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578173: virtinst or libvirt loses contact with console during installation
Package: virtinst Version: 0.400.0-7 Severity: serious Justification: 1 ok, the fiasco of installing in lenny continues. Boot into xen, take a system such as hardy or karmic on cd or dvd, put it in the drive, invole virt-manager, invoke new vm bringing virtinst into play, use the provided wizzard screens and setup install of a new vm using the cd drive, begin an install of the new vm. The problem WAS bug number 519809. We've progressed from there, bringing in the backport versions of libvirt0 and libvirt-bin, version 0.7.6-1~bp. Citing a late entry of that bug, "can confirm - I backported libvirt 0.6.1-1 from squeeze to lenny. The VNC console immediately works with virt-manager 0.6.0-6 after passing the wizard for creating a new guest." Well the reporter stopped at that point. Continuing the install we find a separate new bug. Initially, the install produces an effective vnc console. Half way through the install, the vnc console faults, producing the error message along the lines, TCP/IP error: Console lost contact or got disconnected from the console. Selecting the Hardware tab of the console, the selection Serial 0 initially reported Source path:/dev/pts0 (or 2) Some how the packages changed their mind about what to allocate the console to under /dev. Once faulted, it reads Serial 0: Source path:/dev/pts/1, a non existant char file! So this is the cause of the bug. The developer's place to fix it. In addition, as an attempt to salvage the install, I got the vm to be saved, hoping to restore it from the point on reboot. The save began to take place, then hangs, preventing the vm to be shutdown or paused, becomes frozen. A reboot is required to acess the vm again. Rationale, if a save can be made, at may be able to be restored on an existing /dev/pts/ file, and the install of the vm may perhaps then be completed. My take on this, seeing the content of the bug number 519809, libvirt had to be fixed to get past this point. The problem may again be libvirt, however, the nature of the problem is a missing char device file. On beginning the install, the packages concerned call upon an existing /dev/pts file, then switch to a new one which need be created. This suggests kernel involvement, or some feature that invokes udev to dynamically create a file with makedev or mknod. I hope to see a reply to the bug in due course -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages virtinst depends on: ii python 2.5.2-3 An interactive high-level object-o ii python-libvirt 0.4.6-10 libvirt Python bindings ii python-libxml2 2.6.32.dfsg-5 Python bindings for the GNOME XML ii python-support 0.8.4 automated rebuilding support for P ii python-urlgrabber 3.1.0-4 A high-level cross-protocol url-gr Versions of packages virtinst recommends: pn qemu (no description available) ii virt-viewer 0.0.3-2Displaying the graphical console o virtinst suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
