[Pkg-libvirt-maintainers] Bug#578173: Bug#578173: virtinst or libvirt loses contact with console during installation

Guido Günther agx at sigxcpu.org
Sat Apr 17 17:20:23 UTC 2010


Hi Ian,
On Sun, Apr 18, 2010 at 12:35:10AM +0000, IAN DELANEY wrote:
> 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.
If this does affect only lenny it's not serious since this is from bpo
(at least that's what I read from your post).

Please add:
	* the full install log from virt-manager --debug
	* the versions of xen, virt-manager/virtinst and libvirt0 you're actually
	  using.
	* any output from libvirt in syslog

[..snip..] 
> 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
You're kidding. 
 -- Guido





More information about the Pkg-libvirt-maintainers mailing list