August 23, 201411 yr For those who will never run Xen or KVM there is no need to include hundreds of MB's of unneeded tools in root file system. Therefore include in the release both a 'bzroot-vm' and a 'bzroot' with appropriate changes to syslinux config file.
January 23, 201511 yr Yes please. As one who runs unRAID as a guest on VMware ESXi, I don't foresee adding another VM layer on my unRAID guest OS. John
February 22, 201511 yr Looks good to me, would be nice to cut out the excess cruft a lot of people will never use.
February 22, 201511 yr @limetech, Is there perhaps a means of treating the Xen/KVM items as an auxilary bzroot so everyone could be using the same barebones bzroot? Then if xen and if the xenzroot exist it gets augmented into it. Likewise with KVM items. Do those hundreds of MBs of uneeded tools have to be there before full boot up? If not, then could they simply be a plugin?
February 22, 201511 yr @limetech, Is there perhaps a means of treating the Xen/KVM items as an auxilary bzroot so everyone could be using the same barebones bzroot? Then if xen and if the xenzroot exist it gets augmented into it. Likewise with KVM items. Do those hundreds of MBs of uneeded tools have to be there before full boot up? If not, then could they simply be a plugin? That is our plan, yes. The kernel will be the same for all boot modes, but we will have two "bzroot" files: one with and one without all the extra VM tools. Both will include docker. Make sense? The net diff between the vm and non vm mode will be vm tools.
Archived
This topic is now archived and is closed to further replies.