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.
+
----------------------------------------------------------------------
-"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.
+
+The architecture in this mode would look like:
+
+ +------------------+
+ | main program |
+ |------------------|
+ | libguestfs |
+ +--------^---------+
+ | | reply
+ cmd | |
+ +----v-------------+
+ | guestfsd |
+ +------------------+
-With a Fedora-based appliance, using libata driver, devices have
-"SCSI" names like /dev/sda.
+Notes:
-With an EPEL-based appliance, using old ide driver, devices have names
-like /dev/hda.
+(1) This only makes sense if we are running as root.
-If we use virtio_blk, devices will have names like /dev/vda.
+(2) There is no console / kernel messages in this configuration, but
+we might consider capturing stderr from the daemon.
-What a mess.
+(3) guestfs_config and guestfs_add_drive become no-ops.
-So the idea would be to add a device independent naming scheme, such
-as the one used by grub:
+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.
- "(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).
+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
+
+----------------------------------------------------------------------
-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.
+Supermin appliance should be moved into febootstrap.
-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.
+----------------------------------------------------------------------
+
+Extra commands / functionality:
+
+ General glibc / core programs:
+ chgrp
+ grep (do it locally using pipe?)
+ dd (?)
+ ln / ln -s
+ readlink
+ utime / utimes / futimes / futimens / l..
+ more mk*temp calls
+ some sort of alloc/fallocate/posix_fallocate call to create empty space
+ realpath
+ trunc[ate??]
+
+ ext2 properties:
+ chattr
+ lsattr
+ badblocks
+ blkid
+ debugfs
+ dumpe2fs
+ e2image
+ e2undo
+ filefrag
+ findfs
+ logsave
+ mklost+found
+
+ SELinux:
+ chcat
+ restorecon
+ ch???
+
+ Oddball:
+ pivot_root
+ fts(3) / ftw(3)
+
+----------------------------------------------------------------------
+
+Allow swap space from the guest to be used. Is it a good idea?
+
+----------------------------------------------------------------------
+
+Need a way to query a binary or library file for its architecture.
+Using objdump or readelf?
+What about non-ELF files (eg. Windows, BSD).
+
+To do this properly requires some serious logic, eg. to cover Linux
+and Windows we'd need objdump and i686-pc-mingw32-objdump, and more to
+cover a.out, COFF and 64 bit Windows. Therefore this cannot be done
+inside the daemon, and should be done by a separate, external program
+similar to virt-inspector.
+
+Probably we should go all the way and have virt-inspector able to
+determine kernel and userspace architectures of guests.
+
+----------------------------------------------------------------------
-Note there's a lot of hackery that currently exists in tests.c which
-could be *removed* if we made this change.
+Other initrd-* commands, such as:
-Open: Should the substitution be done in the library layer or in the
-daemon?
+initrd-extract
+initrd-replace
git.annexia.org / libguestfs.git / blobdiff