[Pkg-libvirt-maintainers] Bug#578173: xen and libvirt

[IAN DELANEY]

Guido, thanks for your prompt reply.  So I provide the requested info.

* the full install log from virt-manager --debug

The log has a number of entries, finding it difficult to isolate the karmic install.  
Changed ~/.virt-manager/virt-manager.log .to ~/.virt-manager/virt-manager.log-old, re-doing the install with the vm setup
to get a single proper log for you.  I'm going to compromise a little here.  See my comment in the attached virt-manager log.


* the versions of xen, virt-manager/virtinst and libvirt0 you're actually using.

xen 3.2.1-2, standard lenny 5,
virt-manager 0.6.0-6
libvirt0 0.7.6-1-bp050+1

> 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.
> 

You're kidding. 
 -- Guido

I just don't get you, but maybe best not to dwell on it.  I don't want a contest of egos.  You're the developer.
I just want to see virt-manager and virtinst finally get to install and manage vms primarily in xen.
Suse has it nailed.  That's my main refernce point.  I've pursued libvirt and virtinst quite a bit.  More entries to come

You might note my other bug entry, it's the prequel to this.

* the versions of xen, virt-manager/virtinst and libvirt0 you're actually using.

xen 3.2.1-2, standard lenny 5,
virt-manager 0.6.0-6
libvirt0 0.7.6-1-bp050+1

> 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.
> 

You're kidding. 
 -- Guido

I just don't get you, but maybe best not to dwell on it.  I don't want a contest of egos.  You're the developer.
I just want to see virt-manager and virtinst finally get to install and manage vms primarily in xen.
Suse has it nailed.  That's my main refernce point.  I've pursued libvirt and virtinst quite a bit.  More entries to come

You might note my other bug entry, it's the prequel to this.



 		 	   		  
_________________________________________________________________
Need a new place to live? Find it on Domain.com.au
http://clk.atdmt.com/NMN/go/157631292/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20100418/5d9bcc54/attachment-0001.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: syslog-Sat-17.txt
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20100418/5d9bcc54/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: virt-manager.log-for karmic.txt
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20100418/5d9bcc54/attachment-0003.txt>