head	1.8;
access;
symbols
	netbsd-11-0-RC5:1.8
	netbsd-11-0-RC4:1.8
	netbsd-11-0-RC3:1.8
	netbsd-11-0-RC2:1.8
	netbsd-11-0-RC1:1.8
	perseant-exfatfs-base-20250801:1.8
	netbsd-11:1.8.0.2
	netbsd-11-base:1.8
	netbsd-10-1-RELEASE:1.6
	perseant-exfatfs-base-20240630:1.6
	perseant-exfatfs:1.6.0.12
	perseant-exfatfs-base:1.6
	netbsd-8-3-RELEASE:1.5
	netbsd-9-4-RELEASE:1.6
	netbsd-10-0-RELEASE:1.6
	netbsd-10-0-RC6:1.6
	netbsd-10-0-RC5:1.6
	netbsd-10-0-RC4:1.6
	netbsd-10-0-RC3:1.6
	netbsd-10-0-RC2:1.6
	netbsd-10-0-RC1:1.6
	netbsd-10:1.6.0.10
	netbsd-10-base:1.6
	netbsd-9-3-RELEASE:1.6
	cjep_sun2x-base1:1.6
	cjep_sun2x:1.6.0.8
	cjep_sun2x-base:1.6
	cjep_staticlib_x-base1:1.6
	netbsd-9-2-RELEASE:1.6
	cjep_staticlib_x:1.6.0.6
	cjep_staticlib_x-base:1.6
	netbsd-9-1-RELEASE:1.6
	phil-wifi-20200421:1.6
	phil-wifi-20200411:1.6
	is-mlppp:1.6.0.4
	is-mlppp-base:1.6
	phil-wifi-20200406:1.6
	netbsd-8-2-RELEASE:1.5
	netbsd-9-0-RELEASE:1.6
	netbsd-9-0-RC2:1.6
	netbsd-9-0-RC1:1.6
	phil-wifi-20191119:1.6
	netbsd-9:1.6.0.2
	netbsd-9-base:1.6
	phil-wifi-20190609:1.5
	netbsd-8-1-RELEASE:1.5
	netbsd-8-1-RC1:1.5
	pgoyette-compat-merge-20190127:1.5
	pgoyette-compat-20190127:1.5
	pgoyette-compat-20190118:1.5
	pgoyette-compat-1226:1.5
	pgoyette-compat-1126:1.5
	pgoyette-compat-1020:1.5
	pgoyette-compat-0930:1.5
	pgoyette-compat-0906:1.5
	netbsd-7-2-RELEASE:1.5
	pgoyette-compat-0728:1.5
	netbsd-8-0-RELEASE:1.5
	phil-wifi:1.5.0.40
	phil-wifi-base:1.5
	pgoyette-compat-0625:1.5
	netbsd-8-0-RC2:1.5
	pgoyette-compat-0521:1.5
	pgoyette-compat-0502:1.5
	pgoyette-compat-0422:1.5
	netbsd-8-0-RC1:1.5
	pgoyette-compat-0415:1.5
	pgoyette-compat-0407:1.5
	pgoyette-compat-0330:1.5
	pgoyette-compat-0322:1.5
	pgoyette-compat-0315:1.5
	netbsd-7-1-2-RELEASE:1.5
	pgoyette-compat:1.5.0.38
	pgoyette-compat-base:1.5
	netbsd-7-1-1-RELEASE:1.5
	matt-nb8-mediatek:1.5.0.36
	matt-nb8-mediatek-base:1.5
	netbsd-8:1.5.0.34
	netbsd-8-base:1.5
	prg-localcount2-base3:1.5
	prg-localcount2-base2:1.5
	prg-localcount2-base1:1.5
	prg-localcount2:1.5.0.32
	prg-localcount2-base:1.5
	pgoyette-localcount-20170426:1.5
	bouyer-socketcan-base1:1.5
	pgoyette-localcount-20170320:1.5
	netbsd-7-1:1.5.0.30
	netbsd-7-1-RELEASE:1.5
	netbsd-7-1-RC2:1.5
	netbsd-7-nhusb-base-20170116:1.5
	bouyer-socketcan:1.5.0.28
	bouyer-socketcan-base:1.5
	pgoyette-localcount-20170107:1.5
	netbsd-7-1-RC1:1.5
	pgoyette-localcount-20161104:1.5
	netbsd-7-0-2-RELEASE:1.5
	localcount-20160914:1.5
	netbsd-7-nhusb:1.5.0.26
	netbsd-7-nhusb-base:1.5
	pgoyette-localcount-20160806:1.5
	pgoyette-localcount-20160726:1.5
	pgoyette-localcount:1.5.0.24
	pgoyette-localcount-base:1.5
	netbsd-7-0-1-RELEASE:1.5
	netbsd-7-0:1.5.0.22
	netbsd-7-0-RELEASE:1.5
	netbsd-7-0-RC3:1.5
	netbsd-7-0-RC2:1.5
	netbsd-7-0-RC1:1.5
	netbsd-5-2-3-RELEASE:1.2.12.1
	netbsd-5-1-5-RELEASE:1.2.12.1
	netbsd-6-0-6-RELEASE:1.5
	netbsd-6-1-5-RELEASE:1.5
	netbsd-7:1.5.0.20
	netbsd-7-base:1.5
	yamt-pagecache-base9:1.5
	yamt-pagecache-tag8:1.4.6.1
	netbsd-6-1-4-RELEASE:1.5
	netbsd-6-0-5-RELEASE:1.5
	tls-earlyentropy:1.5.0.18
	tls-earlyentropy-base:1.5
	riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.5
	riastradh-drm2-base3:1.5
	netbsd-6-1-3-RELEASE:1.5
	netbsd-6-0-4-RELEASE:1.5
	netbsd-5-2-2-RELEASE:1.2.12.1
	netbsd-5-1-4-RELEASE:1.2.12.1
	netbsd-6-1-2-RELEASE:1.5
	netbsd-6-0-3-RELEASE:1.5
	netbsd-5-2-1-RELEASE:1.2.12.1
	netbsd-5-1-3-RELEASE:1.2.12.1
	netbsd-6-1-1-RELEASE:1.5
	riastradh-drm2-base2:1.5
	riastradh-drm2-base1:1.5
	riastradh-drm2:1.5.0.10
	riastradh-drm2-base:1.5
	netbsd-6-1:1.5.0.16
	netbsd-6-0-2-RELEASE:1.5
	netbsd-6-1-RELEASE:1.5
	khorben-n900:1.5.0.14
	netbsd-6-1-RC4:1.5
	netbsd-6-1-RC3:1.5
	agc-symver:1.5.0.12
	agc-symver-base:1.5
	netbsd-6-1-RC2:1.5
	netbsd-6-1-RC1:1.5
	yamt-pagecache-base8:1.5
	netbsd-5-2:1.2.12.1.0.10
	netbsd-6-0-1-RELEASE:1.5
	yamt-pagecache-base7:1.5
	netbsd-5-2-RELEASE:1.2.12.1
	netbsd-5-2-RC1:1.2.12.1
	matt-nb6-plus-nbase:1.5
	yamt-pagecache-base6:1.5
	netbsd-6-0:1.5.0.8
	netbsd-6-0-RELEASE:1.5
	netbsd-6-0-RC2:1.5
	tls-maxphys:1.5.0.6
	tls-maxphys-base:1.5
	matt-nb6-plus:1.5.0.4
	matt-nb6-plus-base:1.5
	netbsd-6-0-RC1:1.5
	yamt-pagecache-base5:1.5
	yamt-pagecache-base4:1.5
	netbsd-6:1.5.0.2
	netbsd-6-base:1.5
	netbsd-5-1-2-RELEASE:1.2.12.1
	netbsd-5-1-1-RELEASE:1.2.12.1
	yamt-pagecache-base3:1.4
	yamt-pagecache-base2:1.4
	yamt-pagecache:1.4.0.6
	yamt-pagecache-base:1.4
	cherry-xenmp:1.4.0.4
	cherry-xenmp-base:1.4
	bouyer-quota2-nbase:1.4
	bouyer-quota2:1.4.0.2
	bouyer-quota2-base:1.4
	matt-mips64-premerge-20101231:1.4
	matt-nb5-mips64-premerge-20101231:1.2.12.1
	matt-nb5-pq3:1.2.12.1.0.8
	matt-nb5-pq3-base:1.2.12.1
	netbsd-5-1:1.2.12.1.0.6
	netbsd-5-1-RELEASE:1.2.12.1
	netbsd-5-1-RC4:1.2.12.1
	matt-nb5-mips64-k15:1.2.12.1
	netbsd-5-1-RC3:1.2.12.1
	netbsd-5-1-RC2:1.2.12.1
	netbsd-5-1-RC1:1.2.12.1
	netbsd-5-0-2-RELEASE:1.2.12.1
	matt-nb5-mips64-premerge-20091211:1.2.12.1
	matt-premerge-20091211:1.4
	matt-nb5-mips64-u2-k2-k4-k7-k8-k9:1.2.12.1
	matt-nb4-mips64-k7-u2a-k9b:1.2.12.1
	matt-nb5-mips64-u1-k1-k5:1.2.12.1
	matt-nb5-mips64:1.2.12.1.0.4
	netbsd-5-0-1-RELEASE:1.2.12.1
	jym-xensuspend-nbase:1.3
	netbsd-5-0:1.2.12.1.0.2
	netbsd-5-0-RELEASE:1.2.12.1
	netbsd-5-0-RC4:1.2.12.1
	netbsd-5-0-RC3:1.2.12.1
	netbsd-5-0-RC2:1.2.12.1
	jym-xensuspend:1.3.0.2
	jym-xensuspend-base:1.3
	netbsd-5-0-RC1:1.2.12.1
	netbsd-5:1.2.0.12
	netbsd-5-base:1.2
	matt-mips64-base2:1.2
	wrstuden-revivesa-base-3:1.2
	wrstuden-revivesa-base-2:1.2
	wrstuden-revivesa-base-1:1.2
	yamt-pf42-base4:1.2
	yamt-pf42-base3:1.2
	hpcarm-cleanup-nbase:1.2
	yamt-pf42-baseX:1.2
	yamt-pf42-base2:1.2
	wrstuden-revivesa:1.2.0.10
	wrstuden-revivesa-base:1.2
	yamt-pf42:1.2.0.6
	yamt-pf42-base:1.2
	keiichi-mipv6-base:1.2
	keiichi-mipv6:1.2.0.4
	matt-armv6:1.2.0.2
	matt-armv6-nbase:1.2;
locks; strict;
comment	@# @;


1.8
date	2025.05.19.18.02.53;	author nia;	state Exp;
branches;
next	1.7;
commitid	KKoQigwL34GNNxVF;

1.7
date	2024.09.08.09.36.45;	author rillig;	state Exp;
branches;
next	1.6;
commitid	rdsoFf00hj9B9ZoF;

1.6
date	2019.06.17.18.22.41;	author sevan;	state Exp;
branches
	1.6.12.1;
next	1.5;
commitid	BQ5rsXKga4HxszrB;

1.5
date	2012.01.15.02.45.42;	author agc;	state Exp;
branches
	1.5.40.1;
next	1.4;

1.4
date	2009.09.15.21.07.58;	author agc;	state Exp;
branches
	1.4.6.1;
next	1.3;

1.3
date	2009.01.26.05.09.25;	author agc;	state Exp;
branches;
next	1.2;

1.2
date	2008.03.19.20.34.34;	author jmmv;	state Exp;
branches
	1.2.2.1
	1.2.4.1
	1.2.12.1;
next	1.1;

1.1
date	2008.03.19.20.12.53;	author agc;	state Exp;
branches;
next	;

1.6.12.1
date	2025.08.02.05.20.42;	author perseant;	state Exp;
branches;
next	;
commitid	23j6GFaDws3O875G;

1.5.40.1
date	2020.04.13.07.45.37;	author martin;	state Exp;
branches;
next	;
commitid	X01YhRUPVUDaec4C;

1.4.6.1
date	2012.04.17.00.02.56;	author yamt;	state Exp;
branches;
next	;

1.2.2.1
date	2008.03.19.20.34.34;	author matt;	state dead;
branches;
next	1.2.2.2;

1.2.2.2
date	2008.03.23.00.23.07;	author matt;	state Exp;
branches;
next	;

1.2.4.1
date	2008.03.19.20.34.34;	author keiichi;	state dead;
branches;
next	1.2.4.2;

1.2.4.2
date	2008.03.24.07.14.40;	author keiichi;	state Exp;
branches;
next	;

1.2.12.1
date	2009.01.26.05.17.44;	author snj;	state Exp;
branches;
next	;


desc
@@


1.8
log
@doc: Update roadmaps for 2025.

- Support for arm64 is pretty advanced now and not the biggest problem
  with supporting phone hardware. (yay, progress!)
- ZFS was updated to be based on FreeBSD's version, and "works", but
  more stabilization, optimization, and updating is always needed.
- NVME's been supported for several major releases now, but more
  optimization work is always needed.
- Our scheduler is now topology-aware (yay, progress!)
- Mention aarch64 support in nvmm.
@
text
@$NetBSD: virtualization,v 1.7 2024/09/08 09:36:45 rillig Exp $

NetBSD Virtualization Roadmap
=============================

This is a small roadmap document, and deals with the virtualization
side of the operating system.

Features that will be in 6.0:
1. NetBSD/usermode
5. Xen domU migration, suspend and resume

Features which may make future releases:
2. virtualization jails via secmodel
3. iSCSI booting
4. iSCSI device cloning
5. Arm64 (aarch64) support in NVMM

We'll continue to update this roadmap as features and dates get firmed up.


Some explanations
=================

1. NetBSD/usermode
------------------

NetBSD/usermode is a port of NetBSD to a POSIX-compatible user-space,
with the intention that it should be possible to run the usermode
version of NetBSD on any POSIX-compatible operating system.  This code
has been committed to the repository by jmcneill, and updated by reinoud
and jmcneill. usermode can now boot up to X11, can use a vnc console,
and is under active development now. This is most definitely in 6.0.

Responsible: jmcneill, reinoud

2. Virtualization Jails via secmodel
------------------------------------

One novel way of creating jails for virtualization is to use a new
secmodel (part of the kauth framework), to isolate processes into
jail-based virtual machines. This is the basis of a paper given by
bad@@ at AsiaBSDcon in March 2008. This will not make 6.0

Responsible: bad

3. iSCSI booting
----------------

In order to make Xen domains migration-friendly, the storage that the
domain uses must be based on some form of network-centric storage, either
NFS, or a SAN or IP-SAN. For IP-SANs, iSCSI booting will be used. This
is dependent on the in-kernel iSCSI initiator project completing. This will not make 6.0

Responsible: agc

4. iSCSI device cloning
-----------------------

To minimise the storage requirements for multiple domU booting, using
a standard root filesystem or block device for the domU is required, along
with some form of copy-on-write mechanism to preserve any modifications
that are made. This will not make 6.0

Responsible: agc

5. Xen domU migration, suspend and resume
-----------------------------------------

Xen domU migration is where a domU domain is moved from one dom0 to
another dom0 on the same vlan (to avoid networking problems, the
virtual arp address migrates with the domU itself). jym has committed
this code, and it will be in 6.0

Responsible: jym, bouyer

6. Arm64 (aarch64) support in NVMM
----------------------------------

Initial work was done on porting nvmm(4) to ARMv8.0 by Ryo Shimizu
and presented at 2023 AsiaBSDCon. Due to his very sad passing, the
port is now without a maintainer. It would be amazing if someone
picked up and finished this work.

https://github.com/IIJ-NetBSD/netbsd-src/compare/master...ryo:netbsd-src:wip/aarch64_el2

Alistair Crooks
Sat Jan 14 11:38:50 PST 2012
@


1.7
log
@fix a/an grammar in obvious cases
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.6 2019/06/17 18:22:41 sevan Exp $
d17 1
d77 10
@


1.6
log
@balloon(4) is in
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.5 2012/01/15 02:45:42 agc Exp $
d27 1
a27 1
NetBSD/usermode is an port of NetBSD to a POSIX-compatible user-space,
@


1.6.12.1
log
@Sync with HEAD
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.8 2025/05/19 18:02:53 nia Exp $
a16 1
5. Arm64 (aarch64) support in NVMM
d27 1
a27 1
NetBSD/usermode is a port of NetBSD to a POSIX-compatible user-space,
a75 10
6. Arm64 (aarch64) support in NVMM
----------------------------------

Initial work was done on porting nvmm(4) to ARMv8.0 by Ryo Shimizu
and presented at 2023 AsiaBSDCon. Due to his very sad passing, the
port is now without a maintainer. It would be amazing if someone
picked up and finished this work.

https://github.com/IIJ-NetBSD/netbsd-src/compare/master...ryo:netbsd-src:wip/aarch64_el2

@


1.5
log
@bring the virtualization roadmap up to date.
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.4 2009/09/15 21:07:58 agc Exp $
a11 1
6. Xen balloon driver support
a75 11
6. Xen balloon driver support
-----------------------------

The balloon driver allows more memory to be added to a running Xen domU
instance; this allows extra memory to be used by the domU for resource
peak needs. cherry has made a preliminary balloon driver and this has been
further updated and tested by jym. This will be in 6.0.

Responsible: jym, cherry


@


1.5.40.1
log
@Mostly merge changes from HEAD upto 20200411
@
text
@d1 1
a1 1
$NetBSD$
d12 1
d77 11
@


1.4
log
@Update the NetBSD roadmaps to reflect recent changes.

Please contact core if you have other major projects and requirements
that you would like to see included.
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.3 2009/01/26 05:09:25 agc Exp $
d9 1
d11 4
a17 5
5. Xen domU migration, suspend and resume
6. Xen balloon driver support

We currently expect to branch 6.0 in the March 2010 timeframe, with a view
to a 6.0 release later in 2010.
d31 3
a33 1
has been committed to the repository, but more work is needed.
d35 1
a35 1
Responsible: jmcneill
d43 1
a43 1
bad@@ at AsiaBSDcon in March 2008.
d53 1
a53 1
is dependent on the in-kernel iSCSI initiator project completing.
d63 1
a63 1
that are made.
d72 2
a73 2
virtual arp address migrates with the domU itself). jym is actively
working on this, and preliminary results are good.
d82 2
a83 2
peak needs. cherry has made a preliminary balloon driver - some testing
is needed before it can be committed.
d85 1
a85 1
Responsible: cherry
d89 1
a89 1
Tue 15 Sep 2009 08:06:34 PDT
@


1.4.6.1
log
@sync with head
@
text
@d1 1
a1 1
$NetBSD$
a8 1
Features that will be in 6.0:
d10 3
d16 2
a17 4
Features which may make future releases:
2. virtualization jails via secmodel
3. iSCSI booting
4. iSCSI device cloning
d31 1
a31 3
has been committed to the repository by jmcneill, and updated by reinoud
and jmcneill. usermode can now boot up to X11, can use a vnc console,
and is under active development now. This is most definitely in 6.0.
d33 1
a33 1
Responsible: jmcneill, reinoud
d41 1
a41 1
bad@@ at AsiaBSDcon in March 2008. This will not make 6.0
d51 1
a51 1
is dependent on the in-kernel iSCSI initiator project completing. This will not make 6.0
d61 1
a61 1
that are made. This will not make 6.0
d70 2
a71 2
virtual arp address migrates with the domU itself). jym has committed
this code, and it will be in 6.0
d80 2
a81 2
peak needs. cherry has made a preliminary balloon driver and this has been
further updated and tested by jym. This will be in 6.0.
d83 1
a83 1
Responsible: jym, cherry
d87 1
a87 1
Sat Jan 14 11:38:50 PST 2012
@


1.3
log
@Various updates to the roadmaps for features we are looking to develop
over the next few years
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.2 2008/03/19 20:34:34 jmmv Exp $
d9 6
a14 2
NetBSD 5.0 will ship with the following virtualization elements in
place:
d16 2
a17 16
1. Xen 3 Dom0		[i386/amd64]
2. Xen 3 DomU		[i386/amd64]
3. Xen 3 PAE DomU	[i386]

The following projects are expected to be included in NetBSD 6.0

4. NetBSD/usermode
5. virtualization jails via secmodel
6. iSCSI booting
7. iSCSI device cloning
8. Xen domU migration, suspend and resume
9. Xen balloon driver support

The timescales for 6.0 are not known at the present time, but we would
expect to branch 6.0 late in 2009, with a view to a 6.0 release in
early 2010.
d25 1
a25 1
4. NetBSD/usermode
d28 4
a31 3
NetBSD/usermode is an port of NetBSD to a POSIX-compatible user-space, with
the intention that it should be possible to run the usermode version of
NetBSD on any POSIX-compatible operating system.
d35 1
a35 1
5. Virtualization Jails via secmodel
d40 2
a41 2
jail-based virtual machines. This is the basis of a paper to appear
in the AsiaBSDcon proceedings in March 2008.
d45 1
a45 1
6. iSCSI booting
d50 2
a51 1
NFS, or a SAN or IP-SAN. For IP-SANs, iSCSI booting will be used.
d55 1
a55 1
7. iSCSI device cloning
d65 1
a65 1
8. Xen domU migration, suspend and resume
d70 2
a71 1
virtual arp address migrates with the domU itself).
d73 1
a73 1
Responsible: bouyer
d75 1
a75 1
9. Xen balloon driver support
d80 2
a81 1
peak needs.
d83 1
a83 1
Responsible: bouyer, cherry?
d87 1
a87 1
Sun 25 Jan 2009 21:07:42 PST
@


1.2
log
@Formatting fixes:
- Fix underlining of titles.
- Separate subsections by one blank line only (this seemed to be the most
  common style among the four documents).
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.1 2008/03/19 20:12:53 agc Exp $
d16 1
a16 2
The following elements and projects are pencilled in for 5.0, but
please do not rely on them being there.
a19 3

The following projects are expected to be included in NetBSD 6.0

d25 3
a27 14
We expect to branch for the 5.0 release in April or May 2008, which would
put a NetBSD 5.0 Release date in Q4 2008. An annual release cycle would
thus mean that 6.0 would be branched in April or May 2009.

Pictorially, this looks like:

 2008                                        2009
 Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug
|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|

                | ------- 5.0 --------- |                       | ------- 6.0
              branch                  release                 branch

 1-3     4,5                  6      7       8          9
d89 1
a89 1
Responsible: bouyer
d93 1
a93 1
Thu Mar  6 22:36:19 GMT 2008
@


1.2.12.1
log
@Pull up following revision(s) (requested by agc in ticket #322):
	doc/roadmaps/networking: revision 1.6
	doc/roadmaps/storage: revision 1.4
	doc/roadmaps/system: revision 1.5
	doc/roadmaps/virtualization: revision 1.3
Various updates to the roadmaps for features we are looking to develop
over the next few years
@
text
@d1 1
a1 1
$NetBSD: virtualization,v 1.2 2008/03/19 20:34:34 jmmv Exp $
d16 2
a17 1
The following projects are expected to be included in NetBSD 6.0
d21 3
d29 14
a42 3
The timescales for 6.0 are not known at the present time, but we would
expect to branch 6.0 late in 2009, with a view to a 6.0 release in
early 2010.
d104 1
a104 1
Responsible: bouyer, cherry?
d108 1
a108 1
Sun 25 Jan 2009 21:07:42 PST
@


1.2.4.1
log
@file virtualization was added on branch keiichi-mipv6 on 2008-03-24 07:14:40 +0000
@
text
@d1 108
@


1.2.4.2
log
@sync with head.
@
text
@a0 108
$NetBSD: virtualization,v 1.2 2008/03/19 20:34:34 jmmv Exp $

NetBSD Virtualization Roadmap
=============================

This is a small roadmap document, and deals with the virtualization
side of the operating system.

NetBSD 5.0 will ship with the following virtualization elements in
place:

1. Xen 3 Dom0		[i386/amd64]
2. Xen 3 DomU		[i386/amd64]
3. Xen 3 PAE DomU	[i386]

The following elements and projects are pencilled in for 5.0, but
please do not rely on them being there.

4. NetBSD/usermode
5. virtualization jails via secmodel

The following projects are expected to be included in NetBSD 6.0

6. iSCSI booting
7. iSCSI device cloning
8. Xen domU migration, suspend and resume
9. Xen balloon driver support

We expect to branch for the 5.0 release in April or May 2008, which would
put a NetBSD 5.0 Release date in Q4 2008. An annual release cycle would
thus mean that 6.0 would be branched in April or May 2009.

Pictorially, this looks like:

 2008                                        2009
 Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug
|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|

                | ------- 5.0 --------- |                       | ------- 6.0
              branch                  release                 branch

 1-3     4,5                  6      7       8          9

We'll continue to update this roadmap as features and dates get firmed up.


Some explanations
=================

4. NetBSD/usermode
------------------

NetBSD/usermode is an port of NetBSD to a POSIX-compatible user-space, with
the intention that it should be possible to run the usermode version of
NetBSD on any POSIX-compatible operating system.

Responsible: jmcneill

5. Virtualization Jails via secmodel
------------------------------------

One novel way of creating jails for virtualization is to use a new
secmodel (part of the kauth framework), to isolate processes into
jail-based virtual machines. This is the basis of a paper to appear
in the AsiaBSDcon proceedings in March 2008.

Responsible: bad

6. iSCSI booting
----------------

In order to make Xen domains migration-friendly, the storage that the
domain uses must be based on some form of network-centric storage, either
NFS, or a SAN or IP-SAN. For IP-SANs, iSCSI booting will be used.

Responsible: agc

7. iSCSI device cloning
-----------------------

To minimise the storage requirements for multiple domU booting, using
a standard root filesystem or block device for the domU is required, along
with some form of copy-on-write mechanism to preserve any modifications
that are made.

Responsible: agc

8. Xen domU migration, suspend and resume
-----------------------------------------

Xen domU migration is where a domU domain is moved from one dom0 to
another dom0 on the same vlan (to avoid networking problems, the
virtual arp address migrates with the domU itself).

Responsible: bouyer

9. Xen balloon driver support
-----------------------------

The balloon driver allows more memory to be added to a running Xen domU
instance; this allows extra memory to be used by the domU for resource
peak needs.

Responsible: bouyer


Alistair Crooks
Thu Mar  6 22:36:19 GMT 2008
@


1.2.2.1
log
@file virtualization was added on branch matt-armv6 on 2008-03-23 00:23:07 +0000
@
text
@d1 108
@


1.2.2.2
log
@sync with HEAD
@
text
@a0 108
$NetBSD: virtualization,v 1.2 2008/03/19 20:34:34 jmmv Exp $

NetBSD Virtualization Roadmap
=============================

This is a small roadmap document, and deals with the virtualization
side of the operating system.

NetBSD 5.0 will ship with the following virtualization elements in
place:

1. Xen 3 Dom0		[i386/amd64]
2. Xen 3 DomU		[i386/amd64]
3. Xen 3 PAE DomU	[i386]

The following elements and projects are pencilled in for 5.0, but
please do not rely on them being there.

4. NetBSD/usermode
5. virtualization jails via secmodel

The following projects are expected to be included in NetBSD 6.0

6. iSCSI booting
7. iSCSI device cloning
8. Xen domU migration, suspend and resume
9. Xen balloon driver support

We expect to branch for the 5.0 release in April or May 2008, which would
put a NetBSD 5.0 Release date in Q4 2008. An annual release cycle would
thus mean that 6.0 would be branched in April or May 2009.

Pictorially, this looks like:

 2008                                        2009
 Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug
|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|===|

                | ------- 5.0 --------- |                       | ------- 6.0
              branch                  release                 branch

 1-3     4,5                  6      7       8          9

We'll continue to update this roadmap as features and dates get firmed up.


Some explanations
=================

4. NetBSD/usermode
------------------

NetBSD/usermode is an port of NetBSD to a POSIX-compatible user-space, with
the intention that it should be possible to run the usermode version of
NetBSD on any POSIX-compatible operating system.

Responsible: jmcneill

5. Virtualization Jails via secmodel
------------------------------------

One novel way of creating jails for virtualization is to use a new
secmodel (part of the kauth framework), to isolate processes into
jail-based virtual machines. This is the basis of a paper to appear
in the AsiaBSDcon proceedings in March 2008.

Responsible: bad

6. iSCSI booting
----------------

In order to make Xen domains migration-friendly, the storage that the
domain uses must be based on some form of network-centric storage, either
NFS, or a SAN or IP-SAN. For IP-SANs, iSCSI booting will be used.

Responsible: agc

7. iSCSI device cloning
-----------------------

To minimise the storage requirements for multiple domU booting, using
a standard root filesystem or block device for the domU is required, along
with some form of copy-on-write mechanism to preserve any modifications
that are made.

Responsible: agc

8. Xen domU migration, suspend and resume
-----------------------------------------

Xen domU migration is where a domU domain is moved from one dom0 to
another dom0 on the same vlan (to avoid networking problems, the
virtual arp address migrates with the domU itself).

Responsible: bouyer

9. Xen balloon driver support
-----------------------------

The balloon driver allows more memory to be added to a running Xen domU
instance; this allows extra memory to be used by the domU for resource
peak needs.

Responsible: bouyer


Alistair Crooks
Thu Mar  6 22:36:19 GMT 2008
@


1.1
log
@Add roadmap files, outlining the directions, projects and rough indicative
timescales for new development within the

	networking
	storage
	system
	virtualization

More roadmaps will be forthcoming.

The dates in these documents may well change, and are provided for guidance
on relative, not absolute, timescales.
@
text
@d1 1
a1 1
$NetBSD$
a68 1

@
