From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 8 Jul 2008 15:03:45 -0500 From: "Eric Van Hensbergen" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <5a03888bc4077fcac1298b2e80fc34aa@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5a03888bc4077fcac1298b2e80fc34aa@quanstro.net> Subject: Re: [9fans] why not Lvx for Plan 9? Topicbox-Message-UUID: df187ebc-ead3-11e9-9d60-3106f5b1d025 On Tue, Jul 8, 2008 at 12:49 PM, erik quanstrom wrote: >>> in this model, all plan 9 does is add an extra layer of goo >>> on top of linux. it's not like you can avoid admining >>> linux by hiding on a vm running on linux. >>> >> >> That's not entirely true depending on the virtualization layer used. >> I'm not experienced yet with vx32, but for example, lguest/kvm/xen can >> be setup to pass-through device access to network, disk, audio, >> whatever. The logical partition running Plan 9 can be essentially >> pinned to a processor (or processors) and on that processor it rules >> the roost. Linux just deals with device access. > > you didn't explain the part where you avoid admining the > linux host. > I setup every machine on my network to tftpboot (BIOS), and they all tftpboot a kernel+ramdisk which has everything necessary to startup lguest/kvm plan9 and passthrough I/O requests to the disk/network. Admin done. Alternatively I could do something clever like kvmfs or xcpu or some combination thereof an boot arbitrary images on partitions on the cluster of drones -- but the most simple example is the one given above. -eric