I am not saying at all that it should be a show stopper: it's been there since 3.6 and has gone unnoticed. If at all it can be fixed later. Most people are probably not using a UFS system and neither am I except sometimes for virtual machines. I have 20GB disk space for testing purposes and can put two or four UFS machines there, hammer is not even supported for less than 10GB.
Peeter -- On Thu, May 29, 2014 at 4:35 PM, Zachary Crownover <[email protected]> wrote: > Not that I'm defending an error, but why use UFS when you can use HAMMER? > I'm just curious. > > > On Thu, May 29, 2014 at 12:24 AM, karu.pruun <[email protected]> wrote: >> >> On Wed, May 28, 2014 at 4:51 PM, Zenny wrote: >> > Confirmation that iso works fine in VirtualBox 4.3.8 OSE with ACPI >> > disabled. But the img file didn't. >> > >> > On 5/28/14, Justin Sherrill <[email protected]> wrote: >> >> "Hey this boots strangely oh wait it is just this particular version of >> >> VirtualBox that has the problem" has been a reported problem at what >> >> feels >> >> like every release for years. I'm starting to think that if anyone >> >> reports >> >> issues in VirtualBox, the first step should always be "try a different >> >> version of VirtualBox, or a different virtual system". >> >> >> Point taken, suppose it's a good idea to test on different machines. >> >> However, now it looks again like a DFly problem. I tested on >> Virtualbox 4.1, 4.2, 4.3 and finally reproduced it on a physical >> machine too. It only concerns installations where all partitions are >> UFS. It does not show for a hammer system (ie root HAMMER and /boot >> UFS). >> >> I used the partition layout: >> >> --- >> / UFS >> swap >> /usr UFS >> --- >> >> when booting the system from hdd, the acpi/ehci error shows for DFly >> 3.6.x and 3.8.0RC where both are x86_64. So it appeared already in >> 3.6.x. >> >> Peeter >> >> -- > > > > > -- > Sincerely, > > Zachary Crownover > mobile (310) 487-5573
