blob: 1d7cb3647d0736ddbb4a2e83324c4eea50053a6c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
Ideas for the Python bindings:
https://www.redhat.com/archives/fedora-virt/2009-April/msg00114.html
----------------------------------------------------------------------
We badly need to actually implement the FTP server mentioned in the
documentation.
Or: Implement a FUSE-based filesystem. See the FUSE mountlo
project which does something similar, albeit only to single
filesystems:
http://sourceforge.net/project/showfiles.php?group_id=121684&package_id=150116
----------------------------------------------------------------------
BufferIn and BufferOut should turn into <char *, int> and simple
strings in other languages that can handle 8 bit clean strings.
Limit on transfers would still be 2MB for these types.
- then implement write-file properly
- and implement read-file
----------------------------------------------------------------------
Implement febootstrap command.
----------------------------------------------------------------------
Complete the Haskell bindings (see discussion on haskell-cafe).
----------------------------------------------------------------------
Complete the bindings tests - must test the return values and
error cases.
----------------------------------------------------------------------
For virt-inspector:
- Make a libvirt XML config
- Test over available OSes
- Add 'reged' / NT registry support.
----------------------------------------------------------------------
Use virtio_blk by default. It's faster and more natural.
Unfortunately it seems like this will rename all devices - see next
item.
Note: virtio_blk *IS* supported by all our minimum platforms,
ie. CentOS 5.3, Fedora 11, Debian.
----------------------------------------------------------------------
"Standalone/local mode"
Instead of running guestfsd (the daemon) inside qemu, there should be
an option to just run guestfsd directly.
The architecture in this mode would look like:
+------------------+
| main program |
|------------------|
| libguestfs |
+--------^---------+
| | reply
cmd | |
+----v-------------+
| guestfsd |
+------------------+
Notes:
(1) This only makes sense if we are running as root.
(2) There is no console / kernel messages in this configuration, but
we might consider capturing stderr from the daemon.
(3) guestfs_config and guestfs_add_drive become no-ops.
Obviously in this configuration, commands are run directly on the
local machine's disks. You could just run the commands themselves
directly, but libguestfs provides a convenient API and language
bindings. Also deals with tricky stuff like parsing the output of the
LVM commands. Also we get to leverage other code such as
virt-inspector.
This is mainly useful from live CDs, ie. virt-p2v.
Should we bother having the daemon at all and just link the guestfsd
code directly into libguestfs?
----------------------------------------------------------------------
PPC problems:
ppc (32 bit) works with qemu from git, however there is no serial console
ppc64 requires extra parameters:
-M mac99 -cpu ppc64
however it still fails:
invalid/unsupported opcode: 01 - 01 - 1a (06301e83) 00000000018c2738 1
invalid bits: 00400000 for opcode: 0b - 19 - 15 (2d746572) 0000000000009230
no serial console in ppc or ppc64 because no one can tell us what
console=ttyXX option to use
----------------------------------------------------------------------
Supermin appliance should be moved into febootstrap.
|
