blob: 26af2adb56ce75984ee7cefbacc8dffb73b0aae6 (
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
|
# Ideas
## Usability
* Docs (tutorial and manpage).
* Makefile and debian package.
* Patch for spice-client-gtk for menuless windows (spicec usecase).
* Systemd service for a single VM.
* Shell completions.
## Virtualization
* Config option to [disable
networking](https://wiki.qemu.org/Documentation/Networking#How_to_disable_network_completely),
passing `-net none`.
* [Nested virtualization](http://www.rdoxenham.com/?p=275)
([1](https://wiki.archlinux.org/index.php/KVM#Nested_virtualization),
[2](https://ladipro.wordpress.com/2017/02/24/running-hyperv-in-kvm-guest/)).
# Workflow
* Continuous Integration script (kvmx-ci):
* For schedule jobs (like cron).
* Pull from remote repository and check source integrity.
* Automatic VM (re-)creation and/or provisioning.
* Logging.
* Status report.
* Test suite for kvmx itself.
## Folder sharing
* Try to umount all sshfs volumes in the host.
* Remount 9p shared folders and reinitialize spice-vdagent upon resume from
disk [see possible bug](https://bugzilla.redhat.com/show_bug.cgi?id=1333072).
* Alternative folder sharing support:
* NFS, SMB.
* Or even [SSH to a server](https://superuser.com/questions/831659/mount-a-local-directory-to-a-remote-ssh-server)).
## Image handling
* Integration with [image-bootstrap](https://github.com/hartwork/image-bootstrap).
* LVM support at `kvmx-create`, with optional LUKS support for the whole volume.
* Non-superuser support for building images on `kvmx-create`, relying on a method like the following:
* https://unix.stackexchange.com/questions/32008/how-to-mount-an-image-file-without-root-permission
* https://wiki.debian.org/ManipulatingISOs
* https://github.com/libfuse/libfuse/wiki/Filesystems
* https://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=all&keywords=fuse
* Additional way to handle missing image on `kvmx up` by spawning `kvmx_install` instead of `kvmx-create`.
* Fix isolinux support:
* http://www.syslinux.org/wiki/index.php?title=Development/Testing
* http://linux-kernel-driver.blogspot.com.br/2009/06/linux-kernel-development-using.html
* https://bbs.archlinux.org/viewtopic.php?id=177299
* Image resize action, doing something like this, thanks to
https://ahelpme.com/linux/online-resize-of-a-root-ext4-file-system-increase-the-space/
# poweroff
kvmx poweroff $guest
# resize image
qemu-img resize `kvmx list_image $guest` +5G
# power up
kvmx up $guest
# resize virtual machine root fs - while the partition is mounted!
# this parted command currently need to be done manually
#echo resizepart 2 -1 | kvmx ssh $guest sudo parted /dev/vda
# See https://unix.stackexchange.com/questions/190317/gnu-parted-resizepart-in-script#202872
# https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1270203
# https://techtitbits.com/2018/12/using-parteds-resizepart-non-interactively-on-a-busy-partition/
# https://serverfault.com/questions/870594/resize-partition-to-maximum-using-parted-in-non-interactive-mode
kvmx ssh $guest sudo parted /dev/vda resizepart 2 -1 Yes
kvmx ssh $guest sudo resize2fs /dev/vda2
kvmx ssh $guest sudo touch /forcefsck
kvmx ssh $guest sudo poweroff
|
