[libvirt] MinGW environment for libvirt (at this moment))
Hi, This is a current memo for building MinGW environment for libvirt. (up to run src/.libs/virsh.exe) Of course this Windows path is opened by Rich. this is another way to build this. Ref. http://www.redhat.com/archives/libvir-list/2008-January/msg00017.html Compares to Rich one, 2 different point exists 1)GCC version is keeps 3.x not 4.x. 2)libxml2 is using GTK one. Any suggestions are welcome. Since I want to simplify this complicated procedure. 1.Install MinGW-5.1.4.exe 2.Install MSYS-1.0.11-2004.04.30-1.exe 3.Install msysDTK-1.0.1.exe Above files are taken from following http://sourceforge.net/project/showfiles.php?group_id=2435 4.Install gtk-dev-2.12.9-win32-2.exe (This is for using pkg-config/gettext/libxml2) Taken from http://gladewin32.sourceforge.net/ 5.expand m4-1.4.7-MSYS.tar.bz2 from root directory (we need 1.4.5 or later but msysDTK installs 1.4) Taken from http://sourceforge.net/project/showfiles.php?group_id=2435 6.Install autoconf-2.62.tar.gz ./configure --prefix=/usr make make install Taken from http://www.gnu.org/software/autoconf/ 7.Install automake-1.10.1.tar.gz ./configure --prefix=/usr make make install (create /usr/share/aclocal-1.10) Taken from http://www.gnu.org/software/automake/ 8.Install libtool-1.5.18.tar.gz ./configure --prefix=/usr make make install Taken from http://www.gnu.org/software/libtool/ 9.Add m4 script for aclocal cp /mingw/lib/GTK/share/aclocal/* /usr/share/aclocal (This is for running autogen.sh) 10..Install GNUTLS expand gnutls-2.3.13.exe to c:\msys\1.0 (it goes to /usr)(This is for /usr/share/aclocal) cp -r /usr/include/gnutls /mingw/include cp /usr/lib/libgnutls* /mingw/lib cp /usr/lib/libgpg-error* /mingw/lib cp /usr/lib/libgcrypt* /mingw/lib cp /usr/lib/tasn1.* /mingw/lib rewrite dependency_libs on /mingw/lib/libgnutls.la from /home/jas/gnutls4win/inst to /mingw Taken from http://josefsson.org/gnutls4win/ 11.expand xdr Install xdr-4.0-mingw5.tar.gz(see Rich Page) rpc = /mingw/include lib*.a = /mingw/lib http://www.annexia.org/tmp/xdr-4.0-mingw5.tar.gz 12.get libvirt code from CVS repository comment out siginfo_t (currently this problem is assigned to me) ftp://libvirt.org/libvirt/ 13.create virsh ./autogen.sh (tgz file lacks this. you should get CVS repository) ./configure --without-xen --without-qemu --without-sasl --without-libvirtd make (Ignore compile stops at testutils.c) (this problem is also assigned to me.) 14.execute src/.libs/virsh.exe Thanks Atsushi SAKAI -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Fix qemudParseVMDeviceDef() to check for proper network device tag name
On Thu, Jun 12, 2008 at 09:22:20AM -0700, Kaitlin Rupert wrote: Is it too late to get this change in? Sorry, off by a couple of hours ! Instead of net, the tag name should be interface. Previously, attempting to attach a network device to a KVM guest would return: libvir: QEMU error : XML description for unknown device type is not well formed or invalid error: Failed to attach device from attach-disk.xml With this fix, it returns: libvir: QEMU error test_domain: this function is not supported by the hypervisor: only CDROM disk devices can be attached libvir: QEMU error : this function is not supported by the hypervisor: only CDROM disk devices can be attached error: Failed to attach device from attach-disk.xml Hum, right a network device description uses interface, not net that's clear from both the doc and qemudParseXML(), so applied and commited, but infortunately it didn't made into 0.4.3 :-\ thanks ! Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Release of libvirt-0.4.3
On Thu, Jun 12, 2008 at 09:38:14PM +0100, Richard W.M. Jones wrote: Daniel, really, thanks for doing this. The two virDomain*Peek APIs are what make virt-df the virt-mem toolbox work. On Thu, Jun 12, 2008 at 03:19:30PM -0400, Daniel Veillard wrote: Two months since the last release and a lot of changes had accumulated in the meantime. So it was really time for a release, 0.4.3 is available at ftp://libvirt.org/pub/libvirt This URL is actually wrong. The FTP URL is: ftp://libvirt.org/libvirt/ or by HTTP: http://libvirt.org/sources/ Humpf, i hope I didn't got too much stuff wrong, thanks for raising this. It containns a some new features, bug fixes and improvements, but the largest part is actually code cleanups: * New features: [...] - new virDomainBlockPeek API (Richard Jones) And don't forget virDomainMemoryPeek API :-) I think I got confused and associated the two :-\ Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] where is autogen.sh on libvirt?
On Fri, Jun 13, 2008 at 02:47:06PM +0900, Atsushi SAKAI wrote: Hi, I am looking thorough the package on ftp://libvirt.org/libvirt/ but cannot find autogen.sh files on 0.4.3 and snapshot package. Is there any reason? Of course cvs package have autogen.sh. Basically autogen.sh is used to bootstrap the configuration and building process, it has more dependancies than the resulting configure script. For that reason people which are not the developpers but rather users of the software simply run ./configure which itself is part of the releases. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Fix qemudParseVMDeviceDef() to check for proper network device tag name
On Fri, Jun 13, 2008 at 03:57:05AM -0400, Daniel Veillard wrote: On Thu, Jun 12, 2008 at 09:22:20AM -0700, Kaitlin Rupert wrote: Is it too late to get this change in? Sorry, off by a couple of hours ! Instead of net, the tag name should be interface. Previously, attempting to attach a network device to a KVM guest would return: libvir: QEMU error : XML description for unknown device type is not well formed or invalid error: Failed to attach device from attach-disk.xml With this fix, it returns: libvir: QEMU error test_domain: this function is not supported by the hypervisor: only CDROM disk devices can be attached libvir: QEMU error : this function is not supported by the hypervisor: only CDROM disk devices can be attached error: Failed to attach device from attach-disk.xml Hum, right a network device description uses interface, not net that's clear from both the doc and qemudParseXML(), so applied and commited, but infortunately it didn't made into 0.4.3 :-\ That's not critical - this function is only called from the device hotplug driver API, and we only implement that for changing CDROM media in QEMU at the moment. So nothing we actually use for real is broken. Regards, Daniel. -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] where is autogen.sh on libvirt?
On Fri, Jun 13, 2008 at 04:05:12AM -0400, Daniel Veillard wrote: On Fri, Jun 13, 2008 at 02:47:06PM +0900, Atsushi SAKAI wrote: Hi, I am looking thorough the package on ftp://libvirt.org/libvirt/ but cannot find autogen.sh files on 0.4.3 and snapshot package. Is there any reason? Of course cvs package have autogen.sh. Basically autogen.sh is used to bootstrap the configuration and building process, it has more dependancies than the resulting configure script. For that reason people which are not the developpers but rather users of the software simply run ./configure which itself is part of the releases. We should still include autogen.sh in the tar.gz, because people might be wanting to do patches against the tar.gz whcih involve the configure.ac or Makefile.am scripts. Dan -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] where is autogen.sh on libvirt?
On Fri, Jun 13, 2008 at 10:02:22AM +0100, Daniel P. Berrange wrote: On Fri, Jun 13, 2008 at 04:05:12AM -0400, Daniel Veillard wrote: On Fri, Jun 13, 2008 at 02:47:06PM +0900, Atsushi SAKAI wrote: Hi, I am looking thorough the package on ftp://libvirt.org/libvirt/ but cannot find autogen.sh files on 0.4.3 and snapshot package. Is there any reason? Of course cvs package have autogen.sh. Basically autogen.sh is used to bootstrap the configuration and building process, it has more dependancies than the resulting configure script. For that reason people which are not the developpers but rather users of the software simply run ./configure which itself is part of the releases. We should still include autogen.sh in the tar.gz, because people might be wanting to do patches against the tar.gz whcih involve the configure.ac or Makefile.am scripts. Okay, I added autogen.sh to EXTRA_DIST, that should do it, still it may be more useful to understand why configure doesn't work on MinGW out of the box (or rather tarball). Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] MinGW environment for libvirt (at this moment))
On Fri, Jun 13, 2008 at 03:23:36PM +0900, Atsushi SAKAI wrote: 5.expand m4-1.4.7-MSYS.tar.bz2 from root directory (we need 1.4.5 or later but msysDTK installs 1.4) Taken from http://sourceforge.net/project/showfiles.php?group_id=2435 I wonder if this is a bug in our use of m4 macros? Anyway, thanks for this. An easier way to solve this whole problem would be to add the mingw32 cross compiler to Fedora. See discussion here: http://www.redhat.com/archives/rhl-devel-list/2008-April/msg01224.html If we had this, we could relatively easily build libvirt DLLs / EXEs on our Fedora boxes and ship them through the main site. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my OCaml programming blog: http://camltastic.blogspot.com/ Fedora now supports 59 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Fix qemudParseVMDeviceDef() to check for proper network device tag name
libvir: QEMU error test_domain: this function is not supported by the hypervisor: only CDROM disk devices can be attached libvir: QEMU error : this function is not supported by the hypervisor: only CDROM disk devices can be attached error: Failed to attach device from attach-disk.xml Hum, right a network device description uses interface, not net that's clear from both the doc and qemudParseXML(), so applied and commited, but infortunately it didn't made into 0.4.3 :-\ That's not critical - this function is only called from the device hotplug driver API, and we only implement that for changing CDROM media in QEMU at the moment. So nothing we actually use for real is broken. Right, since attaching a network device isn't supported, you'd get an error either way. I tracked down this issue because I saw the following error when I attempted to attach a network device: libvir: QEMU error : XML description for unknown device type is not well formed or invalid I originally thought I wasn't formatting the XML properly. Once I looked at the code, I realized that the action wasn't supported. So, this change just saves some potential confusion. -- Kaitlin Rupert IBM Linux Technology Center [EMAIL PROTECTED] -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Fix qemudParseVMDeviceDef() to check for proper network device tag name
KR I originally thought I wasn't formatting the XML properly. Once I KR looked at the code, I realized that the action wasn't supported. KR So, this change just saves some potential confusion. It also helps generalized layers above libvirt handle the error. In the CIM providers, we can ignore (or handle) not supported properly, but XML not well-formed is a more fatal error, indicating a problem with the providers. The fewer this-is-kvm-so-only-cdroms-are-dynamic special cases we have, the better :) -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: [EMAIL PROTECTED] pgpnXH4UQGCRi.pgp Description: PGP signature -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
