On Thu, Dec 18, 2014 at 01:21:47PM -0600, Adam Thompson wrote: > On 14-12-18 12:57 PM, Mike Larkin wrote: > >On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: > >>On 14-12-18 12:06 PM, andrew fabbro wrote: > >>>In short - the list of VPS providers who can support OpenBSD is actually > >>>very big. > >>I have to take issue with that statement... > >> > >>The list of VPS providers where OpenBSD will run, more or less > >>correctly, more or less all of the time, is actually very big. It > >>will even run correctly all of the time on a fairly large list of > >>providers. > >> > >>However, the list of VPS providers who are willing to *support* > >>OpenBSD is extremely small. > >> > >>What do you do if one day you're only getting 100kbps throughput? > >>Call support, who - as soon as they learn you're running OpenBSD - > >>tell you "that's not supported, sorry" and hang up. When ACPI goes > >>haywire (normal under KVM so far)... same thing. Not naming names, > >And your bug report for this is ... where? > > > >-ml > The last time I filed a bugreport on OpenBSD in a virtualized > environment, I got flamed for not running it on real hardware. > Haven't bothered since. However, that was a few years ago, and the > ACPI shutdown issue is a big enough PITA that I'll file again soon. > Difficult to debug, though, since the all I/O except wscons just > freezes upon receipt of the ACPI signal. > > -- > -Adam Thompson > [email protected] >
It would be useful to at least see if this is a real ACPI issue or if this some problem KVM is causing. The former will elicit more sympathy than the latter. -ml
