Re: Mention vmd FFS boot support removal in current.html
Hi Josh, Just a quick note regarding - it is used only once in there - being the dominant tag. BTW is only about consistency, not about one vs the other. Cheers, Raf On Fri, Mar 19, 2021 at 08:08:26PM GMT, Josh Rickmar wrote: > On Fri, Mar 19, 2021 at 03:26:46PM -0400, Josh Rickmar wrote: > > I got some emails off list asking about the removal and if it affected > > them. Worth adding to current.html? > > sorry for the noise, missed a > > diff 0d7807046bcfacd3249f4c62031ac970d9b42ace /home/jrick/www > blob - 9452b3672627fb39fa0c7ec17a17e08f57406afa > file + faq/current.html > --- faq/current.html > +++ faq/current.html > @@ -274,6 +274,22 @@ RFC 8981 changed the terminology from privacy to tempo > temporary. > > > +2021/03/19 - FFS boot support removed in vmd > + > +Support in vmd(8) for booting OpenBSD guests installed to a FFS root > +filesystem, without using the BIOS firmware or another boot kernel, > +was removed. > +This had only been possible by using both the -b and > +-d flags to vmctl start, or boot and > +disk parameters in vm.conf, with each specifying the > +same disk image file. > +This feature had not been implemented for FFS2. > + > +The use of the BIOS firmware is now required to boot the kernel > +installed to a raw or qcow2 disk image, and will be used by default > +after removing a boot parameter from vm.conf. > + > + >
Re: Mention vmd FFS boot support removal in current.html
On Fri, Mar 19, 2021 at 03:26:46PM -0400, Josh Rickmar wrote: > I got some emails off list asking about the removal and if it affected > them. Worth adding to current.html? sorry for the noise, missed a diff 0d7807046bcfacd3249f4c62031ac970d9b42ace /home/jrick/www blob - 9452b3672627fb39fa0c7ec17a17e08f57406afa file + faq/current.html --- faq/current.html +++ faq/current.html @@ -274,6 +274,22 @@ RFC 8981 changed the terminology from privacy to tempo temporary. +2021/03/19 - FFS boot support removed in vmd + +Support in vmd(8) for booting OpenBSD guests installed to a FFS root +filesystem, without using the BIOS firmware or another boot kernel, +was removed. +This had only been possible by using both the -b and +-d flags to vmctl start, or boot and +disk parameters in vm.conf, with each specifying the +same disk image file. +This feature had not been implemented for FFS2. + +The use of the BIOS firmware is now required to boot the kernel +installed to a raw or qcow2 disk image, and will be used by default +after removing a boot parameter from vm.conf. + +
Mention vmd FFS boot support removal in current.html
I got some emails off list asking about the removal and if it affected them. Worth adding to current.html? diff 0d7807046bcfacd3249f4c62031ac970d9b42ace /home/jrick/www blob - 9452b3672627fb39fa0c7ec17a17e08f57406afa file + faq/current.html --- faq/current.html +++ faq/current.html @@ -274,6 +274,22 @@ RFC 8981 changed the terminology from privacy to tempo temporary. +2021/03/19 - FFS boot support removed in vmd + +Support in vmd(8) for booting OpenBSD guests installed to a FFS root +filesystem, without using the BIOS firmware or another boot kernel, +was removed. +This had only been possible by using both the -b and +-d flags to vmctl start, or boot and +disk parameters in vm.conf, with each specifying the +same disk image file. +This feature had not been implemented for FFS2. + +The use of the BIOS firmware is now required to boot the kernel +installed to a raw or qcow2 disk image, and will be used by default +after removing a boot parameter from vm.conf. + +
