virtualization revision 1.7
1 $NetBSD: virtualization,v 1.7 2024/09/08 09:36:45 rillig Exp $ 2 3 NetBSD Virtualization Roadmap 4 ============================= 5 6 This is a small roadmap document, and deals with the virtualization 7 side of the operating system. 8 9 Features that will be in 6.0: 10 1. NetBSD/usermode 11 5. Xen domU migration, suspend and resume 12 13 Features which may make future releases: 14 2. virtualization jails via secmodel 15 3. iSCSI booting 16 4. iSCSI device cloning 17 18 We'll continue to update this roadmap as features and dates get firmed up. 19 20 21 Some explanations 22 ================= 23 24 1. NetBSD/usermode 25 ------------------ 26 27 NetBSD/usermode is a port of NetBSD to a POSIX-compatible user-space, 28 with the intention that it should be possible to run the usermode 29 version of NetBSD on any POSIX-compatible operating system. This code 30 has been committed to the repository by jmcneill, and updated by reinoud 31 and jmcneill. usermode can now boot up to X11, can use a vnc console, 32 and is under active development now. This is most definitely in 6.0. 33 34 Responsible: jmcneill, reinoud 35 36 2. Virtualization Jails via secmodel 37 ------------------------------------ 38 39 One novel way of creating jails for virtualization is to use a new 40 secmodel (part of the kauth framework), to isolate processes into 41 jail-based virtual machines. This is the basis of a paper given by 42 bad@ at AsiaBSDcon in March 2008. This will not make 6.0 43 44 Responsible: bad 45 46 3. iSCSI booting 47 ---------------- 48 49 In order to make Xen domains migration-friendly, the storage that the 50 domain uses must be based on some form of network-centric storage, either 51 NFS, or a SAN or IP-SAN. For IP-SANs, iSCSI booting will be used. This 52 is dependent on the in-kernel iSCSI initiator project completing. This will not make 6.0 53 54 Responsible: agc 55 56 4. iSCSI device cloning 57 ----------------------- 58 59 To minimise the storage requirements for multiple domU booting, using 60 a standard root filesystem or block device for the domU is required, along 61 with some form of copy-on-write mechanism to preserve any modifications 62 that are made. This will not make 6.0 63 64 Responsible: agc 65 66 5. Xen domU migration, suspend and resume 67 ----------------------------------------- 68 69 Xen domU migration is where a domU domain is moved from one dom0 to 70 another dom0 on the same vlan (to avoid networking problems, the 71 virtual arp address migrates with the domU itself). jym has committed 72 this code, and it will be in 6.0 73 74 Responsible: jym, bouyer 75 76 Alistair Crooks 77 Sat Jan 14 11:38:50 PST 2012 78
Indexes created Sat Sep 27 22:09:54 GMT 2025