Xen 8 & 9 DomU kernel panic with 2 or more virtual CPU

2010-03-31 Thread Guillaume Seigneuret
Dear all, When I try to make FreeBSD work in Xen domU with multiple vcups, I got a kernel panic. If someone have a clue . I got the following error : WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (

Re: Xen 8 & 9 DomU kernel panic with 2 or more virtual CPU

2010-03-31 Thread Adrian Chadd
The last time I checked, FreeBSD/DomU was highly buggy, and this includes SMP support. I never managed to get around to figuring out what wasn't being locked correctly. :/ Adrian On 1 April 2010 00:49, Guillaume Seigneuret wrote: > Dear all, > > > > When I try to make FreeBSD work in Xen domU

Re: Xen 8 & 9 DomU kernel panic with 2 or more virtual CPU

2010-05-14 Thread masterito
Hello. I have the same problem, but other error. When I create machine with 1 CPU (vcpus=1) - all work fine, but when I create machine with 4 CPU (vcpus=4) I see kernel panic on console: APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) SMP: Added CPU 1 (AP) SMP: Added CPU 2 (AP) SMP:

Re: Xen 8 & 9 DomU kernel panic with 2 or more virtual CPU

2010-05-14 Thread John Prather
This seems to affect most people trying to use FreeBSD on xen i386 paravirt. I was trying it on Linode, and got 8.0-RELEASE to actually boot by hacking MAXCPU to 1 in sys/i386/include/param.h but even then, when it was under load (building world or lots of ports) it would occasionally panic. 8-ST

Re: Xen 8 & 9 DomU kernel panic with 2 or more virtual CPU

2010-05-16 Thread K. Macy
I'll take a look this week. On Fri, May 14, 2010 at 4:47 PM, John Prather wrote: > This seems to affect most people trying to use FreeBSD on xen i386 paravirt. > > I was trying it on Linode, and got 8.0-RELEASE to actually boot by > hacking MAXCPU to 1 in sys/i386/include/param.h but even then, w