1 Ideas for the Python bindings:
2 https://www.redhat.com/archives/fedora-virt/2009-April/msg00114.html
4 ----------------------------------------------------------------------
6 We badly need to actually implement the FTP server mentioned in the
9 Or: Implement a FUSE-based filesystem. See the FUSE mountlo
10 project which does something similar, albeit only to single
13 http://sourceforge.net/project/showfiles.php?group_id=121684&package_id=150116
15 ----------------------------------------------------------------------
17 BufferIn and BufferOut should turn into <char *, int> and simple
18 strings in other languages that can handle 8 bit clean strings.
19 Limit on transfers would still be 2MB for these types.
20 - then implement write-file properly
21 - and implement read-file
23 ----------------------------------------------------------------------
25 Implement febootstrap command.
27 ----------------------------------------------------------------------
29 Complete the Haskell bindings (see discussion on haskell-cafe).
31 ----------------------------------------------------------------------
33 Complete the bindings tests - must test the return values and
36 ----------------------------------------------------------------------
40 - Make a libvirt XML config
42 - Test over available OSes
44 - Add 'reged' / NT registry support.
46 ----------------------------------------------------------------------
48 Use virtio_blk by default. It's faster and more natural.
49 Unfortunately it seems like this will rename all devices - see next
52 Note: virtio_blk *IS* supported by all our minimum platforms,
53 ie. CentOS 5.3, Fedora 11, Debian.
55 ----------------------------------------------------------------------
57 "Standalone/local mode"
59 Instead of running guestfsd (the daemon) inside qemu, there should be
60 an option to just run guestfsd directly.
62 The architecture in this mode would look like:
77 (1) This only makes sense if we are running as root.
79 (2) There is no console / kernel messages in this configuration, but
80 we might consider capturing stderr from the daemon.
82 (3) guestfs_config and guestfs_add_drive become no-ops.
84 Obviously in this configuration, commands are run directly on the
85 local machine's disks. You could just run the commands themselves
86 directly, but libguestfs provides a convenient API and language
87 bindings. Also deals with tricky stuff like parsing the output of the
88 LVM commands. Also we get to leverage other code such as
91 This is mainly useful from live CDs, ie. virt-p2v.
93 Should we bother having the daemon at all and just link the guestfsd
94 code directly into libguestfs?
96 ----------------------------------------------------------------------
100 ppc (32 bit) works with qemu from git, however there is no serial console
102 ppc64 requires extra parameters:
104 however it still fails:
105 invalid/unsupported opcode: 01 - 01 - 1a (06301e83) 00000000018c2738 1
106 invalid bits: 00400000 for opcode: 0b - 19 - 15 (2d746572) 0000000000009230
108 no serial console in ppc or ppc64 because no one can tell us what
109 console=ttyXX option to use
111 ----------------------------------------------------------------------
113 Supermin appliance should be moved into febootstrap.
115 ----------------------------------------------------------------------
117 Extra commands / functionality:
119 General glibc / core programs:
122 grep (do it locally using pipe?)
128 utime / utimes / futimes / futimens / l..
131 readdir / readdir-and-stat
132 some sort of alloc/fallocate/posix_fallocate call to create empty space
160 more/less (like cat, but pipes it through $PAGER)
162 cat file | pipe-cmd should have a generic form? like
163 'file | less' or 'file | sort'?
165 ----------------------------------------------------------------------
167 Allow swap space from the guest to be used. Is it a good idea?