Slashdot Mirror
NetBSD Adopts NetBSD/xen for Internal Use
agent dero writes "With NetBSD 2.0, the NetBSD Foundation also released support for a new port, NetBSD/xen.
A version of NetBSD meant to run on top of the Xen virtual machine monitor. In this press release the foundation has announced that it is using the port and Xen for much of its internal development, citing security, and ease of use as main reasons for its adoption."
Maybe I'll switch from using Qemu for my kernel sabotage. I would call it kernel hacking but that would indicate some proficiency :-(
Looks like you need to read harder: NetBSD/xen can run in both privileged and unprivileged virtual machines under Xen 1.2, and in unprivileged virtual machines under Xen 2.0. Perhaps that is the why of it?
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
... I could switch between a build world of netbsd, and Counter Strike real fast!!!.
That makes me wonder if I can share one nic between the OSes, or put in two NICs, assign one for each OS.
Apart from Zen, would be cool to do a complete replace-boot, as in the OS state is frozen and written to harddisk (some laptop bioses do this), and the state of another OS is read... making switching between OSes, as fast as reading the same amount of data as your used up ram.
Heck I'll just buy another machine and use a KVM switch.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Xen has been benchmarked to outperform VMWare in certain applications. In addition, Xen allows you to migrate a domain (instance of client OS) to another machine running Xen, live over the network.
Although, another difference is that the OS must be ported to run on Xen. But Linux, FreeBSD, NetBSD have been ported.