[Libvir] [PATCH] typo
Hi, I finally succeed for building libvirt on windows(MinGW/MSYS). Thank you for coopration. During that work I found several typo in libvirt document. Thanks Atsushi SAKAI
Atsushi SAKAI wrote:
Hi,
I finally succeed for building libvirt on windows(MinGW/MSYS). Thank you for coopration.
During that work I found several typo in libvirt document.
Thanks, applied. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Atsushi SAKAI wrote:
I finally succeed for building libvirt on windows(MinGW/MSYS).
So you built it, but did it work? A couple of basic tests you can do to check: (1) virsh.exe -c test:///default list (should list the test domain) (2) virsh.exe -c xen+tcp://somehost/ list Assuming that 'somehost' has a libvirtd configured to listen over TCP, this should list the Xen domains on the remote host. Test (2) is good because it exercises the remote driver, XDR, sockets, etc. FWIW both of the above worked for me, and I can also get virt-ctrl to display remote domains from a Windows box, although I didn't go into any great detail. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Hi, I succeed test (2) but failed (1). I think this is reasonable for virsh on Windows. Anyway currently(from 1/21) pthread is used on hash.c It requires pthread-win32 for windows platform. http://sourceware.org/pthreads-win32/ But I am not familiar with autoconf. I hope someone would write configuration file for pthread in autoconf. Thanks Atsushi SAKAI "Richard W.M. Jones" <rjones@redhat.com> wrote:
Atsushi SAKAI wrote:
I finally succeed for building libvirt on windows(MinGW/MSYS).
So you built it, but did it work?
A couple of basic tests you can do to check:
(1) virsh.exe -c test:///default list
(should list the test domain)
(2) virsh.exe -c xen+tcp://somehost/ list
Assuming that 'somehost' has a libvirtd configured to listen over TCP, this should list the Xen domains on the remote host.
Test (2) is good because it exercises the remote driver, XDR, sockets, etc.
FWIW both of the above worked for me, and I can also get virt-ctrl to display remote domains from a Windows box, although I didn't go into any great detail.
Rich.
-- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Atsushi SAKAI wrote:
Hi,
I succeed test (2) but failed (1). I think this is reasonable for virsh on Windows.
Interesting ... what was the error message when you did: virsh.exe -c test:///default list
Anyway currently(from 1/21) pthread is used on hash.c It requires pthread-win32 for windows platform. http://sourceware.org/pthreads-win32/ But I am not familiar with autoconf. I hope someone would write configuration file for pthread in autoconf.
Sounds like this is a regression. Previously we used the xmlMutex abstractions from libxml, but we have now moved to using pthread directly, so that needs to be reflected in the configure.in. As I said in another message, I need to boot up Windows ... Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Hi, Rich Thank you for your suggestion. Now I found, I switched off test utils since compilation failed with --with-test on MinGW. Since testutils failes compilation. I attach the failure log Thanks Atsushi SAKAI "Richard W.M. Jones" <rjones@redhat.com> wrote:
Atsushi SAKAI wrote:
Hi,
I succeed test (2) but failed (1). I think this is reasonable for virsh on Windows.
Interesting ... what was the error message when you did:
virsh.exe -c test:///default list
participants (2)
-
Atsushi SAKAI -
Richard W.M. Jones