RE: port-amd64/51134: Random shutdown (power button pressed) inside VirtualBox 5 on Windows 7

[<Tomas.T.Bodzar%tieto.com@localhost>]

The following reply was made to PR port-amd64/51134; it has been noted by GNATS.

From: <Tomas.T.Bodzar%tieto.com@localhost>
To: <gnats-bugs%NetBSD.org@localhost>, <port-amd64-maintainer%netbsd.org@localhost>,
	<gnats-admin%netbsd.org@localhost>, <netbsd-bugs%netbsd.org@localhost>
Cc: 
Subject: RE: port-amd64/51134: Random shutdown (power button pressed) inside
 VirtualBox 5 on Windows 7
Date: Fri, 13 May 2016 13:21:04 +0000

 Hi,
 
 Yeah wonders of enterprise and Oracle worlds :-) Just for info NetBSD relas=
 e 7 runs here just fine.
 
 You are free to do whatever you find suitable with that "bug".=20
 
 S=A0pozdravem / Best regards,
 
 Tom=E1=B9 Bod=BE=E1r
 
 -----Original Message-----
 From: Robert Elz [mailto:kre%munnari.OZ.AU@localhost]=20
 Sent: Friday, May 13, 2016 2:35 PM
 To: port-amd64-maintainer%netbsd.org@localhost; gnats-admin%netbsd.org@localhost; netbsd-bugs@n=
 etbsd.org; Bodzar Tomas T <Tomas.T.Bodzar%tieto.com@localhost>
 Subject: Re: port-amd64/51134: Random shutdown (power button pressed) insid=
 e VirtualBox 5 on Windows 7
 
 The following reply was made to PR port-amd64/51134; it has been noted by G=
 NATS.
 
 From: Robert Elz <kre%munnari.OZ.AU@localhost>
 To: gnats-bugs%NetBSD.org@localhost
 Cc:=20
 Subject: Re: port-amd64/51134: Random shutdown (power button pressed) insid=
 e VirtualBox 5 on Windows 7
 Date: Fri, 13 May 2016 19:31:20 +0700
 
  For what it is worth, I gave up on Virtualbox 5, it just isn't  stable (bu=
 g free) enough yet to waste time on.  I went back to  Virtualbox 4 (whateve=
 r the latest one is 4.3.38 or something, though  that's at least one update=
  beyond when I reverted) which works much better.
 =20
  I do host it on linux though, not windows - I will sink quite low when  ne=
 eded, but not that low.
 =20
  But beware, vpox 5 changes the vm config format, so anything that  vpox 5 =
 has ever run on won't work again with vbox 4 - fortunately,  the disc image=
  formats are compat, so all that's needed is to delete  the screwed machine=
  config, and make a new vbox client using the same disc  images as before -=
  a bit tedious to redo all the virtualbox config  but better than running v=
 pox 5.
 =20
  The only problem I have now is that it keeps trying to convince me that  t=
 here's a newer better version (5.0.20 at the minute) that I should be
  upgrading to.    Blah!
 =20
  kre
 =20