mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-09-09 09:14:57 +00:00
+ + * TODO: Added a note about requiring C++ compiler because of a + possible problem with libtool autoconf macros. + * docs/examples/Makefile.am, proxy/Makefile.am, qemud/Makefile.am, + src/Makefile.am, tests/Makefile.am: Pass $(WARN_CFLAGS) when + linking, so if -fstack-protector is there, gcc will link to + the stack protector library. + * tests/xencapstest.c: Allow this test to compile when Xen + libraries are not enabled. +
30 lines
925 B
Plaintext
30 lines
925 B
Plaintext
TODO:
|
|
- libvirt_virDomainSetMemory should check memory is > 0
|
|
- check how to better handle renaming of domains (xm rename and cache)
|
|
|
|
- UUID lookup in hash.c
|
|
|
|
Other environment:
|
|
- support for UML
|
|
|
|
+ UML control layer should be easy at least for one user but incomplete
|
|
|
|
Probable TODOs:
|
|
- event on big domain state change (create, crashed, paused, shutdown, destroy)
|
|
- bindings for more languages
|
|
|
|
Would-be-nice TODO:
|
|
- man page for virsh and the libraries entry points
|
|
- more documentation and examples on using the toolkit
|
|
- examples for the error handling code
|
|
|
|
Cleanup:
|
|
- now that libxml2 is linked in, drop hash.[ch] and get back to libxml2 ones ?
|
|
same for the buffers
|
|
|
|
Autoconf:
|
|
- On Debian and other platforms, C++ compiler is required because
|
|
autoconf macros to detect libtool depend on it. (This is probably
|
|
an autoconf or libtool m4 macro bug, and the fact that it happens
|
|
on Debian is a red herring).
|