Re: XENHVM on -curent useless

[Roger Pau Monné]

On 10/07/13 18:41, Sean Bruno wrote:
 On Wed, 2013-07-10 at 18:15 +0200, Roger Pau Monné wrote:
 On 10/07/13 17:54, Sean Bruno wrote:
 Just got a rootbsd.net instance and the 9.1r XENHVM that they provided
 me works great.

 Attempted to boot -current on their systems and the XENHVM kernel
 panic'd when it could find any hardware timers.  This is a pretty
 serious regression that I'll bisect this weekend if nobody is looking at
 it.

 Could you post the boot log and the panic with a backtrace?

 
 
 Yeah, I'll do that in a bit. I'm doing a testcompile on my instance at
 the moment, but the panic string was:
 
 panic: No usable event timer found
 
 I'm rebuilding world/kernel at the moment, so it'll be a couple of hours
 before I can fire it up.

That's strange, I've just compiled a recent XENHVM kernel and it seems 
to work just fine, the tip commit is:

commit e42a32794c6657516febef7a44fad00ddb24f2fa
Author: theraven thera...@freebsd.org
Date:   Wed Jul 10 10:57:09 2013 +

Report error for out-of-range numerical inputs.  Requested by brooks.

Are you using i386 or amd64? Also, could you post the Xen version you 
are using and the config file for the guest?

Here is my boot log:

Booting...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
SMAP type=01 base= len=0009fc00
SMAP type=02 base=0009fc00 len=0400
SMAP type=02 base=000f len=0001
SMAP type=01 base=0010 len=7f6ff000
SMAP type=02 base=7f7ff000 len=1000
SMAP type=02 base=fc00 len=0400
Table 'FACP' at 0xfc009a20
Table 'APIC' at 0xfc009b20
APIC: Found table at 0xfc009b20
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 0: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 2 ACPI ID 1: enabled
SMP: Added CPU 2 (AP)
MADT: Found CPU APIC ID 4 ACPI ID 2: enabled
SMP: Added CPU 4 (AP)
MADT: Found CPU APIC ID 6 ACPI ID 3: enabled
SMP: Added CPU 6 (AP)
MADT: Found CPU APIC ID 8 ACPI ID 4: enabled
SMP: Added CPU 8 (AP)
MADT: Found CPU APIC ID 10 ACPI ID 5: enabled
SMP: Added CPU 10 (AP)
MADT: Found CPU APIC ID 12 ACPI ID 6: enabled
SMP: Added CPU 12 (AP)
MADT: Found CPU APIC ID 14 ACPI ID 7: disabled
MADT: Found CPU APIC ID 16 ACPI ID 8: disabled
MADT: Found CPU APIC ID 18 ACPI ID 9: disabled
MADT: Found CPU APIC ID 20 ACPI ID 10: disabled
MADT: Found CPU APIC ID 22 ACPI ID 11: disabled
MADT: Found CPU APIC ID 24 ACPI ID 12: disabled
MADT: Found CPU APIC ID 26 ACPI ID 13: disabled
MADT: Found CPU APIC ID 28 ACPI ID 14: disabled
MADT: Found CPU APIC ID 30 ACPI ID 15: disabled
MADT: Found CPU APIC ID 32 ACPI ID 16: disabled
MADT: Found CPU APIC ID 34 ACPI ID 17: disabled
MADT: Found CPU APIC ID 36 ACPI ID 18: disabled
MADT: Found CPU APIC ID 38 ACPI ID 19: disabled
MADT: Found CPU APIC ID 40 ACPI ID 20: disabled
MADT: Found CPU APIC ID 42 ACPI ID 21: disabled
MADT: Found CPU APIC ID 44 ACPI ID 22: disabled
MADT: Found CPU APIC ID 46 ACPI ID 23: disabled
MADT: Found CPU APIC ID 48 ACPI ID 24: disabled
MADT: Found CPU APIC ID 50 ACPI ID 25: disabled
MADT: Found CPU APIC ID 52 ACPI ID 26: disabled
MADT: Found CPU APIC ID 54 ACPI ID 27: disabled
MADT: Found CPU APIC ID 56 ACPI ID 28: disabled
MADT: Found CPU APIC ID 58 ACPI ID 29: disabled
MADT: Found CPU APIC ID 60 ACPI ID 30: disabled
MADT: Found CPU APIC ID 62 ACPI ID 31: disabled
MADT: Found CPU APIC ID 64 ACPI ID 32: disabled
MADT: Found CPU APIC ID 66 ACPI ID 33: disabled
MADT: Found CPU APIC ID 68 ACPI ID 34: disabled
MADT: Found CPU APIC ID 70 ACPI ID 35: disabled
MADT: Found CPU APIC ID 72 ACPI ID 36: disabled
MADT: Found CPU APIC ID 74 ACPI ID 37: disabled
MADT: Found CPU APIC ID 76 ACPI ID 38: disabled
MADT: Found CPU APIC ID 78 ACPI ID 39: disabled
MADT: Found CPU APIC ID 80 ACPI ID 40: disabled
MADT: Found CPU APIC ID 82 ACPI ID 41: disabled
MADT: Found CPU APIC ID 84 ACPI ID 42: disabled
MADT: Found CPU APIC ID 86 ACPI ID 43: disabled
MADT: Found CPU APIC ID 88 ACPI ID 44: disabled
MADT: Found CPU APIC ID 90 ACPI ID 45: disabled
MADT: Found CPU APIC ID 92 ACPI ID 46: disabled
MADT: Found CPU APIC ID 94 ACPI ID 47: disabled
MADT: Found CPU APIC ID 96 ACPI ID 48: disabled
MADT: Found CPU APIC ID 98 ACPI ID 49: disabled
MADT: Found CPU APIC ID 100 ACPI ID 50: disabled
MADT: Found CPU APIC ID 102 ACPI ID 51: disabled
MADT: Found CPU APIC ID 104 ACPI ID 52: disabled
MADT: Found CPU APIC ID 106 ACPI ID 53: disabled
MADT: Found CPU APIC ID 108 ACPI ID 54: disabled
MADT: Found CPU APIC ID 110 ACPI ID 55: disabled
MADT: Found CPU APIC ID 112 ACPI ID 56: disabled
MADT: Found CPU APIC ID 114 ACPI ID 57: disabled
MADT: Found CPU APIC ID 116 ACPI ID 58: disabled
MADT: Found CPU APIC ID 118 ACPI ID 59: disabled
MADT: Found CPU APIC ID 120 ACPI ID 60: disabled
MADT: Found CPU APIC ID 122 ACPI ID 61: disabled
MADT: Found CPU APIC ID 124 ACPI ID 62: disabled
MADT: Found CPU APIC ID 126 ACPI ID 63: disabled
MADT: Found CPU APIC ID 

Re: XENHVM on -curent useless [VERY USEFUL TODAY]

[Sean Bruno]

On Wed, 2013-07-10 at 18:15 +0200, Roger Pau Monné wrote:
 On 10/07/13 17:54, Sean Bruno wrote:
  Just got a rootbsd.net instance and the 9.1r XENHVM that they provided
  me works great.
  
  Attempted to boot -current on their systems and the XENHVM kernel
  panic'd when it could find any hardware timers.  This is a pretty
  serious regression that I'll bisect this weekend if nobody is looking at
  it.
 
 Could you post the boot log and the panic with a backtrace?
 

Today, sync'd to head at svn r253159, head works *just fine* and is
fantastic.  :-)

sean


signature.asc
Description: This is a digitally signed message part

XENHVM on -curent useless

[Sean Bruno]

Just got a rootbsd.net instance and the 9.1r XENHVM that they provided
me works great.

Attempted to boot -current on their systems and the XENHVM kernel
panic'd when it could find any hardware timers.  This is a pretty
serious regression that I'll bisect this weekend if nobody is looking at
it.

For the record I did *try* to compile the PVHVM tree in git, and it did
not build for me on 9.x because of some stupid unlreated yyparse error
that made me table flip and go back to 9.1r



Sean




signature.asc
Description: This is a digitally signed message part

Re: XENHVM on -curent useless

[Outback Dingo]

On Wed, Jul 10, 2013 at 12:15 PM, Roger Pau Monné roger@citrix.comwrote:

 On 10/07/13 17:54, Sean Bruno wrote:
  Just got a rootbsd.net instance and the 9.1r XENHVM that they provided
  me works great.
 
  Attempted to boot -current on their systems and the XENHVM kernel
  panic'd when it could find any hardware timers.  This is a pretty
  serious regression that I'll bisect this weekend if nobody is looking at
  it.

 Could you post the boot log and the panic with a backtrace?


it builds and runs fine on 9/STABLE as of today for me under XEN XCP

FreeBSD  9.1-STABLE FreeBSD 9.1-STABLE #1 r253149M: Wed Jul 10 15:48:40 UTC
2013 root@:/usr/obj/usr/src/sys/XENHVM  amd64


 ___
 freebsd-xen@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-xen
 To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org

Re: XENHVM on -curent useless

[Sean Bruno]

On Wed, 2013-07-10 at 18:15 +0200, Roger Pau Monné wrote:
 On 10/07/13 17:54, Sean Bruno wrote:
  Just got a rootbsd.net instance and the 9.1r XENHVM that they provided
  me works great.
  
  Attempted to boot -current on their systems and the XENHVM kernel
  panic'd when it could find any hardware timers.  This is a pretty
  serious regression that I'll bisect this weekend if nobody is looking at
  it.
 
 Could you post the boot log and the panic with a backtrace?
 


Yeah, I'll do that in a bit. I'm doing a testcompile on my instance at
the moment, but the panic string was:

panic: No usable event timer found

I'm rebuilding world/kernel at the moment, so it'll be a couple of hours
before I can fire it up.

Sean

p.s. thanks for your work on PVHVM.  I look forward to testing it soon.




signature.asc
Description: This is a digitally signed message part