virtualizationtodo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
virtualizationtodo [2011/08/25 21:38] – More virtualisation todo RobertWatsonvirtualizationtodo [2021/04/26 10:02] (current) – Remove static last edit date intro, we got history KubilayKocak
Line 5: Line 5:
 ===== Cross-Platform ===== ===== Cross-Platform =====
  
-  * "make release" generates template VM file system images (not specific to a particular VM platform)+  * <del>%%VirtIO%% drivers in the base tree (for KVM, bhyve, VirtualBox, possibly others)</del>  (**//9/21//**, initial commit of virtio drivers to projects/virtio branch:  http://lists.freebsd.org/pipermail/svn-src-projects/2011-September/004361.html ) 
 +  * Support for hot adding/removing of CPUs (mainly for bare metal and VMware so far) 
 +  * "make release" generates template disk / file system images (not specific to a particular VM platform) 
 +  * "make release" extensions that allow qemu-tools (or similar external or new internal tools) to convert file system images into VM images that can be loaded with minimal work (i.e., VMDK, etc).
   * makefs(1) support for UFS2   * makefs(1) support for UFS2
   * GEOM "resize" event to allow device drivers to notify the storage stack of growth   * GEOM "resize" event to allow device drivers to notify the storage stack of growth
   * Live-growable UFS   * Live-growable UFS
 +  * Shrinkable UFS (for reducing "cloud" costs)
   * Reorder partitions so that swap is first   * Reorder partitions so that swap is first
   * Possibly a /boot with pivotroot twiddle model   * Possibly a /boot with pivotroot twiddle model
Line 17: Line 21:
 ===== Xen ===== ===== Xen =====
  
 +  * See: [[Xen]]
   * kldloadable PV drivers without having to compile in "options XENHVM"   * kldloadable PV drivers without having to compile in "options XENHVM"
   * Break out various Xen PV drivers into separate modules so they can be loaded independently -- i.e., front drivers without back drivers   * Break out various Xen PV drivers into separate modules so they can be loaded independently -- i.e., front drivers without back drivers
Line 22: Line 27:
   * dom0 (but lots to do here -- especially, grant tables, but also general stability work for "options XEN")   * dom0 (but lots to do here -- especially, grant tables, but also general stability work for "options XEN")
  
-===== bHyve =====+===== bhyve =====
  
 +  * See the [[bhyve|dedicated bhyve page]]
   * Suspend/resume   * Suspend/resume
   * Live migration   * Live migration
-  * %%VirtIO%% drivers in the base tree+  * Support for older CPUs without nested paging virtualization (there are still a lot of them) 
 + 
 +===== Jails ===== 
 + 
 +  * Make more filesystems jail friendly (audit individual filesystem code so that VFCF_JAIL can be set) 
 + 
 +===== EC2 (Amazon Cloud) ===== 
 + 
 +  * Provide AMI files as part of the release process 
 + 
 +===== VMware ===== 
 + 
 +==== VMware Studio ==== 
 + 
 +  * See: http://www.vmware.com/products/studio and http://communities.vmware.com/thread/312289 
 + 
 +  * Add a %%FreeBSD%% VM vApp template. See /opt/vmware/etc/new_os/TODO_new_os in the VMWare Studio 2.6 image. 
 + 
 +  * Port the Provisioning Agent to %%FreeBSD%%. This is just a shell script run once after first boot, which provisions a VM from template fillout hosted in a custom ISO image. /etc/rc integration is needed. See /opt/vmware/www/provagent/.build/etc/vmware-studio in the VMWare Studio 2.6 image. 
 + 
 +---- 
 + 
 +{{tag>Virtualization}} 
 +{{tag>Todo}} 
 +{{tag>Stale}}
  
  • virtualizationtodo.1314308330.txt.gz
  • Last modified: 2011/08/25 21:38
  • by RobertWatson