Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Roman Kravchuk
Hello bugs@, I'm have problem with run OpenBSD current amd64 as guest in KVM hypervisor on Ubuntu server with AMD CPU. Host OS: Ubuntu 12.04 TLS Host CPU: AMD Phenom(tm) II X4 975 Processor stepping 03 Host kernel: Linux M720-US3 3.2.0-43-generic #68-Ubuntu SMP Wed May 15 03:33:33 UTC 2013

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Roman Kravchuk
patch_amd64errata.diff Index: amd64/amd64/amd64errata.c === RCS file: /cvs/src/sys/arch/amd64/amd64/amd64errata.c,v retrieving revision 1.3 diff -u -p -u -p -r1.3 amd64errata.c --- amd64/amd64/amd64errata.c27 Mar 2012 05:59:46

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Roman Kravchuk
$ cat patch_amd64errata.diff Index: amd64/amd64/amd64errata.c === RCS file: /cvs/src/sys/arch/amd64/amd64/amd64errata.c,v retrieving revision 1.3 diff -u -p -u -p -r1.3 amd64errata.c --- amd64/amd64/amd64errata.c27 Mar 2012

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Jonathan Gray
That is quite a large hammer. It would be preferable to find out which msr it objects to and guard it with a specific cpuid check, and/or fix the hypervisor. On Mon, May 20, 2013 at 10:34:43AM +0300, Roman Kravchuk wrote: patch_amd64errata.diff Index: amd64/amd64/amd64errata.c

Re: your mail

2013-05-20 Thread Cédric TESSIER
Hi, Using this patch, I still receive a `pckbc: command timeout' when starting X. And synaptics initialization fails. Cédric Monday 20 May 2013, 13:53:34 (+0600), Alexandr Shadchin: On Tue, May 14, 2013 at 03:01:03PM +0200, NeZetiC wrote: Synopsis: Elantech touchpad v2 detected but

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Jonathan Gray
On Mon, May 20, 2013 at 01:50:39PM +, Alexey E. Suslikov wrote: Jonathan Gray jsg at jsg.id.au writes: That is quite a large hammer. It would be preferable to find out which msr it objects to and guard it with a specific cpuid check, and/or fix the hypervisor. From NetBSD PR/47677

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Alexey E. Suslikov
Jonathan Gray jsg at jsg.id.au writes: Filling the kernel full of if not really running on hardware do something else paths is asking for trouble. If a hypervisor claims to be a specific model of a processor it should not be surprised when it gets msrs that processor can handle. FreeBSD

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Brynet
On Mon, May 20, 2013 at 09:16:21AM +0300, Roman Kravchuk wrote: I'm have problem with run OpenBSD current amd64 as guest in KVM hypervisor on Ubuntu server with AMD CPU. .. cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Phenom(tm) 9550 Quad-Core Processor, 3600.53 MHz cpu0:

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Alexey E. Suslikov
Mike Larkin mlarkin at azathoth.net writes: You're kidding, right? Could you guys tell what exactly wrong with FreeBSD/NetBSD approach?

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Theo de Raadt
You're kidding, right? Could you guys tell what exactly wrong with FreeBSD/NetBSD approach? So basically, we're told that these VM's are emulating real machines. Except when we try to manage the hardware -- in the specific way that the specific hardware must be handled -- the VM fails to

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread David Coppa
On Mon, May 20, 2013 at 6:15 PM, Alexey E. Suslikov alexey.susli...@gmail.com wrote: Mike Larkin mlarkin at azathoth.net writes: You're kidding, right? Could you guys tell what exactly wrong with FreeBSD/NetBSD approach? Adding some silly workarounds to the kernel for a bug that is a *KVM

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Alexey E. Suslikov
Theo de Raadt deraadt at cvs.openbsd.org writes: If these VM's are real VM's the should start emulating the machines they claim to be emulating correctly, or they should start advertising that they are something different, so that we can isolate the bullshit factor. Ok. I see. Could we trim

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Alexey Suslikov
On Mon, May 20, 2013 at 8:42 PM, Mike Larkin mlar...@azathoth.net wrote: On Mon, May 20, 2013 at 05:11:35PM +, Alexey E. Suslikov wrote: Theo de Raadt deraadt at cvs.openbsd.org writes: If these VM's are real VM's the should start emulating the machines they claim to be emulating

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Theo de Raadt
On Mon, May 20, 2013 at 8:42 PM, Mike Larkin mlar...@azathoth.net wrote: On Mon, May 20, 2013 at 05:11:35PM +, Alexey E. Suslikov wrote: Theo de Raadt deraadt at cvs.openbsd.org writes: If these VM's are real VM's the should start emulating the machines they claim to be emulating

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Theo de Raadt
On Mon, May 20, 2013 at 8:59 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: On Mon, May 20, 2013 at 8:42 PM, Mike Larkin mlar...@azathoth.net wrote: On Mon, May 20, 2013 at 05:11:35PM +, Alexey E. Suslikov wrote: Theo de Raadt deraadt at cvs.openbsd.org writes: If these

Re: Kernel panic on current amd64 running under Ubuntu KVM (patch included)

2013-05-20 Thread Ted Unangst
On Tue, May 21, 2013 at 00:32, Alexey Suslikov wrote: Sometimes we warn users, sometimes not (but we aware of the problem). What is the criteria? Is it a device we claim to support? (Or are interested in supporting?)