X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=TODO;h=ad9e6e9b37ab344b7bd57f5248c98cbeb79a1f11;hp=f3ee67913e1648b1cc564efc20a40173358f5d18;hb=65acb799d2c94e6628f647f2319eb8d16f29a0d5;hpb=3496c6c3dfb5ef4ab93f6aae86512665a37b23cf diff --git a/TODO b/TODO index f3ee679..ad9e6e9 100644 --- a/TODO +++ b/TODO @@ -49,38 +49,80 @@ 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. + +---------------------------------------------------------------------- + +Qemu options -- After discussion with the KVM developers, they have +recommended some flags which will improve the safety and reliability +of KVM. Need to test that these also work under qemu (or at least, do +no harm): + +-no-hpet HPET support is broken and should be disabled. + +-rtc-td-hack Keeps the rtc clock source track time correctly. + +-drive file=...,if=[ide|virtio],cache=off + cache=off is necessary to improve reliability in the + event of a system crash when writing. + ---------------------------------------------------------------------- -"Device independent" naming for devices. +"Standalone/local mode" + +Instead of running guestfsd (the daemon) inside qemu, there should be +an option to just run guestfsd directly. -With a Fedora-based appliance, using libata driver, devices have -"SCSI" names like /dev/sda. +The architecture in this mode would look like: -With an EPEL-based appliance, using old ide driver, devices have names -like /dev/hda. + +------------------+ + | main program | + |------------------| + | libguestfs | + +--------^---------+ + | | reply + cmd | | + +----v-------------+ + | guestfsd | + +------------------+ -If we use virtio_blk, devices will have names like /dev/vda. +Notes: -What a mess. +(1) This only makes sense if we are running as root. -So the idea would be to add a device independent naming scheme, such -as the one used by grub: +(2) There is no console / kernel messages in this configuration, but +we might consider capturing stderr from the daemon. - "(hdX)" X = 0 means 'a', X = 1 means 'b' and so on. - "(hdX,Y)" Device X, partition Y (in grub, this counts from 0 which is - deeply confusing). +(3) guestfs_config and guestfs_add_drive become no-ops. -There would have to be a very simple rule. If guestfsd was expecting -a /dev block device or partition name, then the alternate form can be -used, and we would just look it up using the normal output of -guestfs_list_devices. +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. -Maybe best is to use /dev/sda as the "standard" naming. That -shouldn't cause conflicts in the appliance because we tightly control -what drivers are available. +This is mainly useful from live CDs, ie. virt-p2v. -Note there's a lot of hackery that currently exists in tests.c which -could be *removed* if we made this change. +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 + +---------------------------------------------------------------------- -Open: Should the substitution be done in the library layer or in the -daemon? +Supermin appliance should be moved into febootstrap.