virtualization revision 1.4 
11.4Sagc$NetBSD: virtualization,v 1.4 2009/09/15 21:07:58 agc Exp $
21.1Sagc
31.1SagcNetBSD Virtualization Roadmap
41.1Sagc=============================
51.1Sagc
61.1SagcThis is a small roadmap document, and deals with the virtualization
71.1Sagcside of the operating system.
81.1Sagc
91.4Sagc1. NetBSD/usermode
101.4Sagc2. virtualization jails via secmodel
111.4Sagc3. iSCSI booting
121.4Sagc4. iSCSI device cloning
131.4Sagc5. Xen domU migration, suspend and resume
141.4Sagc6. Xen balloon driver support
151.1Sagc
161.4SagcWe currently expect to branch 6.0 in the March 2010 timeframe, with a view
171.4Sagcto a 6.0 release later in 2010.
181.1Sagc
191.1SagcWe'll continue to update this roadmap as features and dates get firmed up.
201.1Sagc
211.1Sagc
221.1SagcSome explanations
231.1Sagc=================
241.1Sagc
251.4Sagc1. NetBSD/usermode
261.1Sagc------------------
271.1Sagc
281.4SagcNetBSD/usermode is an port of NetBSD to a POSIX-compatible user-space,
291.4Sagcwith the intention that it should be possible to run the usermode
301.4Sagcversion of NetBSD on any POSIX-compatible operating system.  This code
311.4Sagchas been committed to the repository, but more work is needed.
321.1Sagc
331.1SagcResponsible: jmcneill
341.1Sagc
351.4Sagc2. Virtualization Jails via secmodel
361.1Sagc------------------------------------
371.1Sagc
381.1SagcOne novel way of creating jails for virtualization is to use a new
391.1Sagcsecmodel (part of the kauth framework), to isolate processes into
401.4Sagcjail-based virtual machines. This is the basis of a paper given by
411.4Sagcbad@ at AsiaBSDcon in March 2008.
421.1Sagc
431.1SagcResponsible: bad
441.1Sagc
451.4Sagc3. iSCSI booting
461.1Sagc----------------
471.1Sagc
481.1SagcIn order to make Xen domains migration-friendly, the storage that the
491.1Sagcdomain uses must be based on some form of network-centric storage, either
501.4SagcNFS, or a SAN or IP-SAN. For IP-SANs, iSCSI booting will be used. This
511.4Sagcis dependent on the in-kernel iSCSI initiator project completing.
521.1Sagc
531.1SagcResponsible: agc
541.1Sagc
551.4Sagc4. iSCSI device cloning
561.1Sagc-----------------------
571.1Sagc
581.1SagcTo minimise the storage requirements for multiple domU booting, using
591.1Sagca standard root filesystem or block device for the domU is required, along
601.1Sagcwith some form of copy-on-write mechanism to preserve any modifications
611.1Sagcthat are made.
621.1Sagc
631.1SagcResponsible: agc
641.1Sagc
651.4Sagc5. Xen domU migration, suspend and resume
661.1Sagc-----------------------------------------
671.1Sagc
681.1SagcXen domU migration is where a domU domain is moved from one dom0 to
691.1Sagcanother dom0 on the same vlan (to avoid networking problems, the
701.4Sagcvirtual arp address migrates with the domU itself). jym is actively
711.4Sagcworking on this, and preliminary results are good.
721.1Sagc
731.4SagcResponsible: jym, bouyer
741.1Sagc
751.4Sagc6. Xen balloon driver support
761.1Sagc-----------------------------
771.1Sagc
781.1SagcThe balloon driver allows more memory to be added to a running Xen domU
791.1Sagcinstance; this allows extra memory to be used by the domU for resource
801.4Sagcpeak needs. cherry has made a preliminary balloon driver - some testing
811.4Sagcis needed before it can be committed.
821.1Sagc
831.4SagcResponsible: cherry
841.1Sagc
851.1Sagc
861.1SagcAlistair Crooks
871.4SagcTue 15 Sep 2009 08:06:34 PDT
88