Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. The main benefits of this changes are that Xen virtual interrupts (event channels) are now delivered to the guest using a vector callback injection, that is a per-cpu mechanism that allows each vCPU to have different interrupts assigned, so for example network and disk interrupts are delivered to different vCPUs in order to improve performance. With this changes FreeBSD also uses PV timers when running as an HVM guest, which should provide better time keeping and reduce the virtualization overhead, since emulated timers are no longer used. PV IPIs can also be used inside a HVM guest, but this will be implemented later. Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. The code is available in the following git repository, under the branch pvhvm_v5: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary Also, I''ve created a wiki page that explains how to set up a FreeBSD PVHVM for testing: http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. The main benefits of this changes are that Xen virtual interrupts (event channels) are now delivered to the guest using a vector callback injection, that is a per-cpu mechanism that allows each vCPU to have different interrupts assigned, so for example network and disk interrupts are delivered to different vCPUs in order to improve performance. With this changes FreeBSD also uses PV timers when running as an HVM guest, which should provide better time keeping and reduce the virtualization overhead, since emulated timers are no longer used. PV IPIs can also be used inside a HVM guest, but this will be implemented later. Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. The code is available in the following git repository, under the branch pvhvm_v5: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary Also, I''ve created a wiki page that explains how to set up a FreeBSD PVHVM for testing: http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
On Mon, May 13, 2013 at 11:32 AM, Roger Pau Monné <roger.pau@citrix.com> wrote:> Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. ...I think should be encouraged. We''re eagerly awaiting the ability to run FreeBSD in AWS in something other than t1.micro or cluster compute instances. Should we keep holding out hope, or will AWS make HVM available for all instance types before this happens? - M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, May 13, 2013 at 11:32 AM, Roger Pau Monné <roger.pau@citrix.com> wrote:> Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. ...I think should be encouraged. We''re eagerly awaiting the ability to run FreeBSD in AWS in something other than t1.micro or cluster compute instances. Should we keep holding out hope, or will AWS make HVM available for all instance types before this happens? - M _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 05/13/13 11:52, Michael Sierchio wrote:> I think should be encouraged. We''re eagerly awaiting the ability to run > FreeBSD in AWS in something other than t1.micro or cluster compute > instances. Should we keep holding out hope, or will AWS make HVM available > for all instance types before this happens?Err... my AMIs run on all EC2 instance types. On some you have to pay the Windows rate, that''s all. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 05/13/13 11:52, Michael Sierchio wrote:> I think should be encouraged. We''re eagerly awaiting the ability to run > FreeBSD in AWS in something other than t1.micro or cluster compute > instances. Should we keep holding out hope, or will AWS make HVM available > for all instance types before this happens?Err... my AMIs run on all EC2 instance types. On some you have to pay the Windows rate, that''s all. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
The Windoze tax is unacceptable for a number of reasons - the primary reason is that I''m not running Windows. I don''t think the licensing scheme is unfair for those actually running Windows, mind you. At the AWS Summit, an assertion was made that HVM support might be coming soon for all instance types for *NIX OSes. I hope that''s true. - M On Mon, May 13, 2013 at 11:59 AM, Colin Percival <cperciva@freebsd.org>wrote:> On 05/13/13 11:52, Michael Sierchio wrote: > > I think should be encouraged. We''re eagerly awaiting the ability to run > > FreeBSD in AWS in something other than t1.micro or cluster compute > > instances. Should we keep holding out hope, or will AWS make HVM > available > > for all instance types before this happens? > > Err... my AMIs run on all EC2 instance types. On some you have to pay the > Windows rate, that''s all. > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
The Windoze tax is unacceptable for a number of reasons - the primary reason is that I''m not running Windows. I don''t think the licensing scheme is unfair for those actually running Windows, mind you. At the AWS Summit, an assertion was made that HVM support might be coming soon for all instance types for *NIX OSes. I hope that''s true. - M On Mon, May 13, 2013 at 11:59 AM, Colin Percival <cperciva@freebsd.org>wrote:> On 05/13/13 11:52, Michael Sierchio wrote: > > I think should be encouraged. We''re eagerly awaiting the ability to run > > FreeBSD in AWS in something other than t1.micro or cluster compute > > instances. Should we keep holding out hope, or will AWS make HVM > available > > for all instance types before this happens? > > Err... my AMIs run on all EC2 instance types. On some you have to pay the > Windows rate, that''s all. > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 05/13/13 12:08, Michael Sierchio wrote:> The Windoze tax is unacceptable for a number of reasons - the primary reason is > that I''m not running Windows. I don''t think the licensing scheme is unfair for > those actually running Windows, mind you.Right, it''s definitely annoying having to pay more -- I just wanted to point out that the ability does exist, if you''re willing to pay the price.> At the AWS Summit, an assertion was made that HVM support might be coming soon > for all instance types for *NIX OSes. I hope that''s true.Was it indeed? I must not have been present for that... it certainly would be good news. Certainly all the new instance types they''ve released in the past few years have had UNIX HVM support. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 05/13/13 12:08, Michael Sierchio wrote:> The Windoze tax is unacceptable for a number of reasons - the primary reason is > that I''m not running Windows. I don''t think the licensing scheme is unfair for > those actually running Windows, mind you.Right, it''s definitely annoying having to pay more -- I just wanted to point out that the ability does exist, if you''re willing to pay the price.> At the AWS Summit, an assertion was made that HVM support might be coming soon > for all instance types for *NIX OSes. I hope that''s true.Was it indeed? I must not have been present for that... it certainly would be good news. Certainly all the new instance types they''ve released in the past few years have had UNIX HVM support. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On Mon, May 13, 2013 at 7:32 PM, Roger Pau Monné <roger.pau@citrix.com> wrote:> Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. > The main benefits of this changes are that Xen virtual interrupts (event > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when running > as an HVM guest, which should provide better time keeping and reduce the > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. > > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback.Is this something we should try to put on the Xen.org blog? -George
On mar, 2013-05-14 at 10:19 +0100, George Dunlap wrote:> On Mon, May 13, 2013 at 7:32 PM, Roger Pau Monné <roger.pau@citrix.com> wrote: > > Hello, > > > > Recently Justin T Gibbs, Will Andrews and myself have been working on > > improving the Xen support in FreeBSD. The main goal of this was to bring > > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > > interfaces for disk and network interfaces when running as a HVM guest. > > [..] > > > Right now the code is in a state where it can be tested by users, so we > > would like to encourage FreeBSD and Xen users to test it and provide > > feedback. >Cool! :-)> Is this something we should try to put on the Xen.org blog? >I think it definitely should... Whoever is up to write a blog post about it, please, get in touch to me. Soon we''ll have the new mailing lists and all the stuff, but for now, just drop me a line, and I can put the post in the pipeline. Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 05/13/13 11:32, Roger Pau Monné wrote:> Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. > > The code is available in the following git repository, under the branch > pvhvm_v5: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > > Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMI built a XENHVM kernel with this code on EC2, and it hanged after> xenbusb_front0: <Xen Frontend Devices> on xenstore0With a XENHVM kernel from FreeBSD HEAD the next line after that is> xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0Any ideas? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 05/13/13 11:32, Roger Pau Monné wrote:> Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. > > The code is available in the following git repository, under the branch > pvhvm_v5: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > > Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMI built a XENHVM kernel with this code on EC2, and it hanged after> xenbusb_front0: <Xen Frontend Devices> on xenstore0With a XENHVM kernel from FreeBSD HEAD the next line after that is> xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0Any ideas? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 16/05/13 19:55, Colin Percival wrote:> On 05/13/13 11:32, Roger Pau Monné wrote: >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. >> >> The code is available in the following git repository, under the branch >> pvhvm_v5: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary >> >> Also, I''ve created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > I built a XENHVM kernel with this code on EC2, and it hanged after >> xenbusb_front0: <Xen Frontend Devices> on xenstore0 > > With a XENHVM kernel from FreeBSD HEAD the next line after that is >> xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 > > Any ideas?Hello Colin, Thanks for testing this on EC2, could you post the full dmesg? So I can see the hypervisor version and if the PV timer is loaded or not. Roger.
On 16/05/13 19:55, Colin Percival wrote:> On 05/13/13 11:32, Roger Pau Monné wrote: >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. >> >> The code is available in the following git repository, under the branch >> pvhvm_v5: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary >> >> Also, I''ve created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > I built a XENHVM kernel with this code on EC2, and it hanged after >> xenbusb_front0: <Xen Frontend Devices> on xenstore0 > > With a XENHVM kernel from FreeBSD HEAD the next line after that is >> xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 > > Any ideas?Hello Colin, Thanks for testing this on EC2, could you post the full dmesg? So I can see the hypervisor version and if the PV timer is loaded or not. Roger.
On 05/16/13 17:43, Roger Pau Monné wrote:> Thanks for testing this on EC2, could you post the full dmesg? So I can > see the hypervisor version and if the PV timer is loaded or not.Here''s what I get on a cc2.8xlarge with boot_verbose=YES:> Booting [/boot/kernel/kernel]... > -\|/-\|GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > SMAP type=01 base=0000000000000000 len=000000000009fc00 > SMAP type=02 base=000000000009fc00 len=0000000000000400 > SMAP type=02 base=00000000000e0000 len=0000000000020000 > SMAP type=01 base=0000000000100000 len=00000000bff00000 > SMAP type=02 base=00000000fc000000 len=0000000004000000 > SMAP type=01 base=0000000100000000 len=0000000e63000000 > Table ''FACP'' at 0xfc005ee0 > Table ''APIC'' at 0xfc005fe0 > APIC: Found table at 0xfc005fe0 > 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: enabled > SMP: Added CPU 14 (AP) > MADT: Found CPU APIC ID 32 ACPI ID 8: enabled > SMP: Added CPU 32 (AP) > MADT: Found CPU APIC ID 34 ACPI ID 9: enabled > SMP: Added CPU 34 (AP) > MADT: Found CPU APIC ID 36 ACPI ID 10: enabled > SMP: Added CPU 36 (AP) > MADT: Found CPU APIC ID 38 ACPI ID 11: enabled > SMP: Added CPU 38 (AP) > MADT: Found CPU APIC ID 40 ACPI ID 12: enabled > SMP: Added CPU 40 (AP) > MADT: Found CPU APIC ID 42 ACPI ID 13: enabled > SMP: Added CPU 42 (AP) > MADT: Found CPU APIC ID 44 ACPI ID 14: enabled > SMP: Added CPU 44 (AP) > MADT: Found CPU APIC ID 46 ACPI ID 15: enabled > SMP: Added CPU 46 (AP) > MADT: Found CPU APIC ID 1 ACPI ID 16: enabled > SMP: Added CPU 1 (AP) > MADT: Found CPU APIC ID 3 ACPI ID 17: enabled > SMP: Added CPU 3 (AP) > MADT: Found CPU APIC ID 5 ACPI ID 18: enabled > SMP: Added CPU 5 (AP) > MADT: Found CPU APIC ID 7 ACPI ID 19: enabled > SMP: Added CPU 7 (AP) > MADT: Found CPU APIC ID 9 ACPI ID 20: enabled > SMP: Added CPU 9 (AP) > MADT: Found CPU APIC ID 11 ACPI ID 21: enabled > SMP: Added CPU 11 (AP) > MADT: Found CPU APIC ID 13 ACPI ID 22: enabled > SMP: Added CPU 13 (AP) > MADT: Found CPU APIC ID 15 ACPI ID 23: enabled > SMP: Added CPU 15 (AP) > MADT: Found CPU APIC ID 33 ACPI ID 24: enabled > SMP: Added CPU 33 (AP) > MADT: Found CPU APIC ID 35 ACPI ID 25: enabled > SMP: Added CPU 35 (AP) > MADT: Found CPU APIC ID 37 ACPI ID 26: enabled > SMP: Added CPU 37 (AP) > MADT: Found CPU APIC ID 39 ACPI ID 27: enabled > SMP: Added CPU 39 (AP) > MADT: Found CPU APIC ID 41 ACPI ID 28: enabled > SMP: Added CPU 41 (AP) > MADT: Found CPU APIC ID 43 ACPI ID 29: enabled > SMP: Added CPU 43 (AP) > MADT: Found CPU APIC ID 45 ACPI ID 30: enabled > SMP: Added CPU 45 (AP) > MADT: Found CPU APIC ID 47 ACPI ID 31: enabled > SMP: Added CPU 47 (AP) > Copyright (c) 1992-2013 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-CURRENT #0 r+7c97e5b: Fri May 17 02:38:29 UTC 2013 > root@ip-10-148-212-216:/usr/obj/usr/src/sys/XENHVM amd64 > FreeBSD clang version 3.3 (trunk 178860) 20130405 > WARNING: WITNESS option enabled, expect reduced performance. > XEN: Hypervisor version 3.4 detected. > XEN: Disabling emulated block and network devices > Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81912000. > Hypervisor: Origin = "XenVMMXenVMM" > Calibrating TSC clock ... TSC clock: 2593801200 Hz > CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2593.80-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 > Features=0x1781fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,MMX,FXSR,SSE,SSE2,HTT> > Features2=0x9c982201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,XSAVE,OSXSAVE,AVX,HV> > AMD Features=0x20100800<SYSCALL,NX,LM> > AMD Features2=0x1<LAHF> > real memory = 65011712000 (62000 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) > 0x0000000001972000 - 0x00000000bfffffff, 3194544128 bytes (779918 pages) > 0x0000000100000000 - 0x0000000efeb95fff, 60108136448 bytes (14674838 pages) > avail memory = 60563271680 (57757 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: <Xen HVM> > INTR: Adding local APIC 1 as a target > INTR: Adding local APIC 2 as a target > INTR: Adding local APIC 3 as a target > INTR: Adding local APIC 4 as a target > INTR: Adding local APIC 5 as a target > INTR: Adding local APIC 6 as a target > INTR: Adding local APIC 7 as a target > INTR: Adding local APIC 8 as a target > INTR: Adding local APIC 9 as a target > INTR: Adding local APIC 10 as a target > INTR: Adding local APIC 11 as a target > INTR: Adding local APIC 12 as a target > INTR: Adding local APIC 13 as a target > INTR: Adding local APIC 14 as a target > INTR: Adding local APIC 15 as a target > INTR: Adding local APIC 32 as a target > INTR: Adding local APIC 33 as a target > INTR: Adding local APIC 34 as a target > INTR: Adding local APIC 35 as a target > INTR: Adding local APIC 36 as a target > INTR: Adding local APIC 37 as a target > INTR: Adding local APIC 38 as a target > INTR: Adding local APIC 39 as a target > INTR: Adding local APIC 40 as a target > INTR: Adding local APIC 41 as a target > INTR: Adding local APIC 42 as a target > INTR: Adding local APIC 43 as a target > INTR: Adding local APIC 44 as a target > INTR: Adding local APIC 45 as a target > INTR: Adding local APIC 46 as a target > INTR: Adding local APIC 47 as a target > FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs > FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > cpu8 (AP): APIC ID: 8 > cpu9 (AP): APIC ID: 9 > cpu10 (AP): APIC ID: 10 > cpu11 (AP): APIC ID: 11 > cpu12 (AP): APIC ID: 12 > cpu13 (AP): APIC ID: 13 > cpu14 (AP): APIC ID: 14 > cpu15 (AP): APIC ID: 15 > cpu16 (AP): APIC ID: 32 > cpu17 (AP): APIC ID: 33 > cpu18 (AP): APIC ID: 34 > cpu19 (AP): APIC ID: 35 > cpu20 (AP): APIC ID: 36 > cpu21 (AP): APIC ID: 37 > cpu22 (AP): APIC ID: 38 > cpu23 (AP): APIC ID: 39 > cpu24 (AP): APIC ID: 40 > cpu25 (AP): APIC ID: 41 > cpu26 (AP): APIC ID: 42 > cpu27 (AP): APIC ID: 43 > cpu28 (AP): APIC ID: 44 > cpu29 (AP): APIC ID: 45 > cpu30 (AP): APIC ID: 46 > cpu31 (AP): APIC ID: 47 > x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 > x86bios: SSEG 0x001000-0x001fff at 0xffffff80003cc000 > x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 > x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 > APIC: CPU 0 has ACPI ID 0 > APIC: CPU 1 has ACPI ID 16 > APIC: CPU 2 has ACPI ID 1 > APIC: CPU 3 has ACPI ID 17 > APIC: CPU 4 has ACPI ID 2 > APIC: CPU 5 has ACPI ID 18 > APIC: CPU 6 has ACPI ID 3 > APIC: CPU 7 has ACPI ID 19 > APIC: CPU 8 has ACPI ID 4 > APIC: CPU 9 has ACPI ID 20 > APIC: CPU 10 has ACPI ID 5 > APIC: CPU 11 has ACPI ID 21 > APIC: CPU 12 has ACPI ID 6 > APIC: CPU 13 has ACPI ID 22 > APIC: CPU 14 has ACPI ID 7 > APIC: CPU 15 has ACPI ID 23 > APIC: CPU 16 has ACPI ID 8 > APIC: CPU 17 has ACPI ID 24 > APIC: CPU 18 has ACPI ID 9 > APIC: CPU 19 has ACPI ID 25 > APIC: CPU 20 has ACPI ID 10 > APIC: CPU 21 has ACPI ID 26 > APIC: CPU 22 has ACPI ID 11 > APIC: CPU 23 has ACPI ID 27 > APIC: CPU 24 has ACPI ID 12 > APIC: CPU 25 has ACPI ID 28 > APIC: CPU 26 has ACPI ID 13 > APIC: CPU 27 has ACPI ID 29 > APIC: CPU 28 has ACPI ID 14 > APIC: CPU 29 has ACPI ID 30 > APIC: CPU 30 has ACPI ID 15 > APIC: CPU 31 has ACPI ID 31 > random device not loaded; using insecure entropy > ULE: setup cpu 0 > ULE: setup cpu 1 > ULE: setup cpu 2 > ULE: setup cpu 3 > ULE: setup cpu 4 > ULE: setup cpu 5 > ULE: setup cpu 6 > ULE: setup cpu 7 > ULE: setup cpu 8 > ULE: setup cpu 9 > ULE: setup cpu 10 > ULE: setup cpu 11 > ULE: setup cpu 12 > ULE: setup cpu 13 > ULE: setup cpu 14 > ULE: setup cpu 15 > ULE: setup cpu 16 > ULE: setup cpu 17 > ULE: setup cpu 18 > ULE: setup cpu 19 > ULE: setup cpu 20 > ULE: setup cpu 21 > ULE: setup cpu 22 > ULE: setup cpu 23 > ULE: setup cpu 24 > ULE: setup cpu 25 > ULE: setup cpu 26 > ULE: setup cpu 27 > ULE: setup cpu 28 > ULE: setup cpu 29 > ULE: setup cpu 30 > ULE: setup cpu 31 > ACPI: RSDP 0xea020 00024 (v02 Xen) > ACPI: XSDT 0xfc006430 0004C (v01 Xen HVM 00000000 HVML 00000000) > ACPI: FACP 0xfc005ee0 000F4 (v04 Xen HVM 00000000 HVML 00000000) > ACPI: DSDT 0xfc002c40 0321F (v02 Xen HVM 00000000 INTL 20090220) > ACPI: FACS 0xfc002c00 00040 > ACPI: APIC 0xfc005fe0 00160 (v02 Xen HVM 00000000 HVML 00000000) > ACPI: SRAT 0xfc006140 00280 (v01 Xen HVM 00000000 HVML 00000000) > ACPI: SLIT 0xfc0063c0 00030 (v01 Xen HVM 00000000 HVML 00000000) > ACPI: HPET 0xfc0063f0 00038 (v01 Xen HVM 00000000 HVML 00000000) > MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 > ioapic0: Changing APIC ID to 1 > ioapic0: Routing external 8259A''s -> intpin 0 > MADT: Interrupt override: source 0, irq 2 > ioapic0: Routing IRQ 0 -> intpin 2 > MADT: Interrupt override: source 5, irq 5 > ioapic0: intpin 5 trigger: level > ioapic0: intpin 5 polarity: low > MADT: Interrupt override: source 10, irq 10 > ioapic0: intpin 10 trigger: level > ioapic0: intpin 10 polarity: low > MADT: Interrupt override: source 11, irq 11 > ioapic0: intpin 11 trigger: level > ioapic0: intpin 11 polarity: low > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0: intpin 9 polarity: low > ioapic0: intpin 9 trigger: level > ioapic0 <Version 1.1> irqs 0-47 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 > Event-channel device installed. > snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] > feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 > wlan: <802.11 Link Layer> > null: <null device, zero device> > nfslock: pseudo-device > random: <entropy source, Software, Yarrow> > VESA: INT 0x10 vector 0xc000:0x836e > VESA: information block > 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00 > 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83 > 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 > 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff > 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > VESA: 15 mode(s) found > VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80003ff040 (2000040) > VESA: VGABIOS Cirrus extension > VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0 > io: <I/O> > kbd: new array size 4 > kbd1 at kbdmux0 > mem: <memory> > hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 > hpt27xx: RocketRAID 27xx controller driver v1.0 > xen_et0: vector callbacks unavailable > acpi0: <Xen> on motherboard > ACPI: All ACPI Tables successfully acquired > ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > cpu0: Processor \_PR_.PR00 (ACPI ID 0) -> APIC ID 0 > cpu0: <ACPI CPU> on acpi0 > cpu0: switching to generic Cx mode > cpu1: Processor \_PR_.PR01 (ACPI ID 1) -> APIC ID 2 > cpu1: <ACPI CPU> on acpi0 > cpu2: Processor \_PR_.PR02 (ACPI ID 2) -> APIC ID 4 > cpu2: <ACPI CPU> on acpi0 > cpu3: Processor \_PR_.PR03 (ACPI ID 3) -> APIC ID 6 > cpu3: <ACPI CPU> on acpi0 > cpu4: Processor \_PR_.PR04 (ACPI ID 4) -> APIC ID 8 > cpu4: <ACPI CPU> on acpi0 > cpu5: Processor \_PR_.PR05 (ACPI ID 5) -> APIC ID 10 > cpu5: <ACPI CPU> on acpi0 > cpu6: Processor \_PR_.PR06 (ACPI ID 6) -> APIC ID 12 > cpu6: <ACPI CPU> on acpi0 > cpu7: Processor \_PR_.PR07 (ACPI ID 7) -> APIC ID 14 > cpu7: <ACPI CPU> on acpi0 > cpu8: Processor \_PR_.PR08 (ACPI ID 8) -> APIC ID 16 > cpu8: <ACPI CPU> on acpi0 > cpu9: Processor \_PR_.PR09 (ACPI ID 9) -> APIC ID 18 > cpu9: <ACPI CPU> on acpi0 > cpu10: Processor \_PR_.PR0A (ACPI ID 10) -> APIC ID 20 > cpu10: <ACPI CPU> on acpi0 > cpu11: Processor \_PR_.PR0B (ACPI ID 11) -> APIC ID 22 > cpu11: <ACPI CPU> on acpi0 > cpu12: Processor \_PR_.PR0C (ACPI ID 12) -> APIC ID 24 > cpu12: <ACPI CPU> on acpi0 > cpu13: Processor \_PR_.PR0D (ACPI ID 13) -> APIC ID 26 > cpu13: <ACPI CPU> on acpi0 > cpu14: Processor \_PR_.PR0E (ACPI ID 14) -> APIC ID 28 > cpu14: <ACPI CPU> on acpi0 > hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 > hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route > hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic > hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic > hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic > Timecounter "HPET" frequency 62500000 Hz quality 950 > attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 > atrtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) > ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50 > Event timer "RTC" frequency 32768 Hz quality 0 > ACPI timer: 1/7 1/5 1/8 1/9 1/7 1/7 1/7 1/7 1/19 1/8 -> 10 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1f48-0x1f4b on acpi0 > pci_link0: Index IRQ Rtd Ref IRQs > Initial Probe 0 5 N 0 5 10 11 > Validation 0 5 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pci_link1: Index IRQ Rtd Ref IRQs > Initial Probe 0 10 N 0 5 10 11 > Validation 0 10 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pci_link2: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 5 10 11 > Validation 0 11 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pci_link3: Index IRQ Rtd Ref IRQs > Initial Probe 0 5 N 0 5 10 11 > Validation 0 5 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 > pcib0: decoding 4 range 0-0xcf7 > pcib0: decoding 4 range 0xd00-0xffff > pcib0: decoding 3 range 0xa0000-0xbffff > pcib0: decoding 3 range 0xc0000000-0xf4ffffff > pci0: <ACPI PCI bus> on pcib0 > pci0: domain=0, physical bus=0 > found-> vendor=0x8086, dev=0x1237, revid=0x02 > domain=0, bus=0, slot=0, func=0 > class=06-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x7000, revid=0x00 > domain=0, bus=0, slot=1, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x7010, revid=0x00 > domain=0, bus=0, slot=1, func=1 > class=01-01-80, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 > pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 > pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 > pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 > map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled > pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1 > found-> vendor=0x8086, dev=0x7113, revid=0x01 > domain=0, bus=0, slot=1, func=3 > class=06-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > pcib0: matched entry for 0.1.INTA > pcib0: slot 1 INTA hardwired to IRQ 20 > found-> vendor=0x1013, dev=0x00b8, revid=0x00 > domain=0, bus=0, slot=2, func=0 > class=03-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type Prefetchable Memory, range 32, base 0xc0000000, size 25, enabled > pcib0: allocated type 3 (0xc0000000-0xc1ffffff) for rid 10 of pci0:0:2:0 > map[14]: type Memory, range 32, base 0xc3000000, size 12, enabled > pcib0: allocated type 3 (0xc3000000-0xc3000fff) for rid 14 of pci0:0:2:0 > found-> vendor=0x5853, dev=0x0001, revid=0x01 > domain=0, bus=0, slot=3, func=0 > class=ff-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=5 > map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled > pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 > map[14]: type Prefetchable Memory, range 32, base 0xc2000000, size 24, enabled > pcib0: allocated type 3 (0xc2000000-0xc2ffffff) for rid 14 of pci0:0:3:0 > pcib0: matched entry for 0.3.INTA > pcib0: slot 3 INTA hardwired to IRQ 28 > isab0: <PCI-ISA bridge> at device 1.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0 > ata0: <ATA channel> at channel 0 on atapci0 > ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51 > ata1: <ATA channel> at channel 1 on atapci0 > ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52 > pci0: <bridge> at device 1.3 (no driver attached) > vgapci0: <VGA-compatible display> mem 0xc0000000-0xc1ffffff,0xc3000000-0xc3000fff at device 2.0 on pci0 > xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xc2000000-0xc2ffffff irq 28 at device 3.0 on pci0 > ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53 > xenstore0: <XenStore> on xenpci0 > Grant table initialized > psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0061 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > kbd0 at atkbd0 > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 > ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54 > atkbd0: [GIANT-LOCKED] > psm0: current command byte:0061 > kbdc: TEST_AUX_PORT status:0000 > kbdc: RESET_AUX return code:00fa > kbdc: RESET_AUX status:00aa > kbdc: RESET_AUX ID:0000 > kbdc: RESET_AUX return code:00fa > kbdc: RESET_AUX status:00aa > kbdc: RESET_AUX ID:0000 > psm: status 00 02 64 > psm: status 00 00 64 > psm: status 00 03 64 > psm: status 00 03 64 > psm: data 08 00 00 > psm: status 00 02 64 > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons > psm0: config:00000000, flags:00000008, packet size:4 > psm0: syncmask:08, syncbits:00 > fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56 > uart0: fast interrupt > uart0: console (9600,n,8,1) > ppc0: using extended I/O port range > ACPI: Enabled 1 GPEs in block 00 to 1F > acpi0: wakeup code va 0xffffff9096fb5000 pa 0x4000 > ex_isa_identify() > pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 > pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 > ahc_isa_identify 0: ioport 0xc00 alloc failed > ahc_isa_identify 1: ioport 0x1c00 alloc failed > ahc_isa_identify 2: ioport 0x2c00 alloc failed > ahc_isa_identify 3: ioport 0x3c00 alloc failed > ahc_isa_identify 4: ioport 0x4c00 alloc failed > ahc_isa_identify 5: ioport 0x5c00 alloc failed > ahc_isa_identify 6: ioport 0x6c00 alloc failed > ahc_isa_identify 7: ioport 0x7c00 alloc failed > ahc_isa_identify 8: ioport 0x8c00 alloc failed > ahc_isa_identify 9: ioport 0x9c00 alloc failed > ahc_isa_identify 10: ioport 0xac00 alloc failed > ahc_isa_identify 11: ioport 0xbc00 alloc failed > ahc_isa_identify 12: ioport 0xcc00 alloc failed > ahc_isa_identify 13: ioport 0xdc00 alloc failed > ahc_isa_identify 14: ioport 0xec00 alloc failed > isa_probe_children: disabling PnP devices > atkbdc: atkbdc0 already exists; skipping it > atrtc: atrtc0 already exists; skipping it > attimer: attimer0 already exists; skipping it > sc: sc0 already exists; skipping it > uart: uart0 already exists; skipping it > isa_probe_children: probing non-PnP devices > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 > pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 > fdc0: No FDOUT register! > fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 > ppc0: cannot reserve I/O port range > ppc0 failed to probe at irq 7 on isa0 > pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 > uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 > wbwd0 failed to probe on isa0 > isa_probe_children: probing PnP devices > Device configuration finished. > procfs registered > lapic: Divisor 2, Frequency 50000453 Hz > Timecounters tick every 10.000 msec > vlan: initialized, using hash tables with chaining > tcp_init: net.inet.tcp.tcbhashsize auto tuned to 524288 > lo0: bpf attached > hptrr: no controller detected. > hpt27xx: no controller detected. > xenbusb_front0: <Xen Frontend Devices> on xenstore0 > ata0: reset tp1 mask=03 ostat0=00 ostat1=00 > ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 > ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > ata0: reset tp2 stat0=00 stat1=00 devices=0x0 > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 > ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > ata1: reset tp2 stat0=00 stat1=00 devices=0x0-- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 05/16/13 17:43, Roger Pau Monné wrote:> Thanks for testing this on EC2, could you post the full dmesg? So I can > see the hypervisor version and if the PV timer is loaded or not.Here''s what I get on a cc2.8xlarge with boot_verbose=YES:> Booting [/boot/kernel/kernel]... > -\|/-\|GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > SMAP type=01 base=0000000000000000 len=000000000009fc00 > SMAP type=02 base=000000000009fc00 len=0000000000000400 > SMAP type=02 base=00000000000e0000 len=0000000000020000 > SMAP type=01 base=0000000000100000 len=00000000bff00000 > SMAP type=02 base=00000000fc000000 len=0000000004000000 > SMAP type=01 base=0000000100000000 len=0000000e63000000 > Table ''FACP'' at 0xfc005ee0 > Table ''APIC'' at 0xfc005fe0 > APIC: Found table at 0xfc005fe0 > 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: enabled > SMP: Added CPU 14 (AP) > MADT: Found CPU APIC ID 32 ACPI ID 8: enabled > SMP: Added CPU 32 (AP) > MADT: Found CPU APIC ID 34 ACPI ID 9: enabled > SMP: Added CPU 34 (AP) > MADT: Found CPU APIC ID 36 ACPI ID 10: enabled > SMP: Added CPU 36 (AP) > MADT: Found CPU APIC ID 38 ACPI ID 11: enabled > SMP: Added CPU 38 (AP) > MADT: Found CPU APIC ID 40 ACPI ID 12: enabled > SMP: Added CPU 40 (AP) > MADT: Found CPU APIC ID 42 ACPI ID 13: enabled > SMP: Added CPU 42 (AP) > MADT: Found CPU APIC ID 44 ACPI ID 14: enabled > SMP: Added CPU 44 (AP) > MADT: Found CPU APIC ID 46 ACPI ID 15: enabled > SMP: Added CPU 46 (AP) > MADT: Found CPU APIC ID 1 ACPI ID 16: enabled > SMP: Added CPU 1 (AP) > MADT: Found CPU APIC ID 3 ACPI ID 17: enabled > SMP: Added CPU 3 (AP) > MADT: Found CPU APIC ID 5 ACPI ID 18: enabled > SMP: Added CPU 5 (AP) > MADT: Found CPU APIC ID 7 ACPI ID 19: enabled > SMP: Added CPU 7 (AP) > MADT: Found CPU APIC ID 9 ACPI ID 20: enabled > SMP: Added CPU 9 (AP) > MADT: Found CPU APIC ID 11 ACPI ID 21: enabled > SMP: Added CPU 11 (AP) > MADT: Found CPU APIC ID 13 ACPI ID 22: enabled > SMP: Added CPU 13 (AP) > MADT: Found CPU APIC ID 15 ACPI ID 23: enabled > SMP: Added CPU 15 (AP) > MADT: Found CPU APIC ID 33 ACPI ID 24: enabled > SMP: Added CPU 33 (AP) > MADT: Found CPU APIC ID 35 ACPI ID 25: enabled > SMP: Added CPU 35 (AP) > MADT: Found CPU APIC ID 37 ACPI ID 26: enabled > SMP: Added CPU 37 (AP) > MADT: Found CPU APIC ID 39 ACPI ID 27: enabled > SMP: Added CPU 39 (AP) > MADT: Found CPU APIC ID 41 ACPI ID 28: enabled > SMP: Added CPU 41 (AP) > MADT: Found CPU APIC ID 43 ACPI ID 29: enabled > SMP: Added CPU 43 (AP) > MADT: Found CPU APIC ID 45 ACPI ID 30: enabled > SMP: Added CPU 45 (AP) > MADT: Found CPU APIC ID 47 ACPI ID 31: enabled > SMP: Added CPU 47 (AP) > Copyright (c) 1992-2013 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-CURRENT #0 r+7c97e5b: Fri May 17 02:38:29 UTC 2013 > root@ip-10-148-212-216:/usr/obj/usr/src/sys/XENHVM amd64 > FreeBSD clang version 3.3 (trunk 178860) 20130405 > WARNING: WITNESS option enabled, expect reduced performance. > XEN: Hypervisor version 3.4 detected. > XEN: Disabling emulated block and network devices > Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81912000. > Hypervisor: Origin = "XenVMMXenVMM" > Calibrating TSC clock ... TSC clock: 2593801200 Hz > CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2593.80-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 > Features=0x1781fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,MMX,FXSR,SSE,SSE2,HTT> > Features2=0x9c982201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,XSAVE,OSXSAVE,AVX,HV> > AMD Features=0x20100800<SYSCALL,NX,LM> > AMD Features2=0x1<LAHF> > real memory = 65011712000 (62000 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) > 0x0000000001972000 - 0x00000000bfffffff, 3194544128 bytes (779918 pages) > 0x0000000100000000 - 0x0000000efeb95fff, 60108136448 bytes (14674838 pages) > avail memory = 60563271680 (57757 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: <Xen HVM> > INTR: Adding local APIC 1 as a target > INTR: Adding local APIC 2 as a target > INTR: Adding local APIC 3 as a target > INTR: Adding local APIC 4 as a target > INTR: Adding local APIC 5 as a target > INTR: Adding local APIC 6 as a target > INTR: Adding local APIC 7 as a target > INTR: Adding local APIC 8 as a target > INTR: Adding local APIC 9 as a target > INTR: Adding local APIC 10 as a target > INTR: Adding local APIC 11 as a target > INTR: Adding local APIC 12 as a target > INTR: Adding local APIC 13 as a target > INTR: Adding local APIC 14 as a target > INTR: Adding local APIC 15 as a target > INTR: Adding local APIC 32 as a target > INTR: Adding local APIC 33 as a target > INTR: Adding local APIC 34 as a target > INTR: Adding local APIC 35 as a target > INTR: Adding local APIC 36 as a target > INTR: Adding local APIC 37 as a target > INTR: Adding local APIC 38 as a target > INTR: Adding local APIC 39 as a target > INTR: Adding local APIC 40 as a target > INTR: Adding local APIC 41 as a target > INTR: Adding local APIC 42 as a target > INTR: Adding local APIC 43 as a target > INTR: Adding local APIC 44 as a target > INTR: Adding local APIC 45 as a target > INTR: Adding local APIC 46 as a target > INTR: Adding local APIC 47 as a target > FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs > FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > cpu8 (AP): APIC ID: 8 > cpu9 (AP): APIC ID: 9 > cpu10 (AP): APIC ID: 10 > cpu11 (AP): APIC ID: 11 > cpu12 (AP): APIC ID: 12 > cpu13 (AP): APIC ID: 13 > cpu14 (AP): APIC ID: 14 > cpu15 (AP): APIC ID: 15 > cpu16 (AP): APIC ID: 32 > cpu17 (AP): APIC ID: 33 > cpu18 (AP): APIC ID: 34 > cpu19 (AP): APIC ID: 35 > cpu20 (AP): APIC ID: 36 > cpu21 (AP): APIC ID: 37 > cpu22 (AP): APIC ID: 38 > cpu23 (AP): APIC ID: 39 > cpu24 (AP): APIC ID: 40 > cpu25 (AP): APIC ID: 41 > cpu26 (AP): APIC ID: 42 > cpu27 (AP): APIC ID: 43 > cpu28 (AP): APIC ID: 44 > cpu29 (AP): APIC ID: 45 > cpu30 (AP): APIC ID: 46 > cpu31 (AP): APIC ID: 47 > x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 > x86bios: SSEG 0x001000-0x001fff at 0xffffff80003cc000 > x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 > x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 > APIC: CPU 0 has ACPI ID 0 > APIC: CPU 1 has ACPI ID 16 > APIC: CPU 2 has ACPI ID 1 > APIC: CPU 3 has ACPI ID 17 > APIC: CPU 4 has ACPI ID 2 > APIC: CPU 5 has ACPI ID 18 > APIC: CPU 6 has ACPI ID 3 > APIC: CPU 7 has ACPI ID 19 > APIC: CPU 8 has ACPI ID 4 > APIC: CPU 9 has ACPI ID 20 > APIC: CPU 10 has ACPI ID 5 > APIC: CPU 11 has ACPI ID 21 > APIC: CPU 12 has ACPI ID 6 > APIC: CPU 13 has ACPI ID 22 > APIC: CPU 14 has ACPI ID 7 > APIC: CPU 15 has ACPI ID 23 > APIC: CPU 16 has ACPI ID 8 > APIC: CPU 17 has ACPI ID 24 > APIC: CPU 18 has ACPI ID 9 > APIC: CPU 19 has ACPI ID 25 > APIC: CPU 20 has ACPI ID 10 > APIC: CPU 21 has ACPI ID 26 > APIC: CPU 22 has ACPI ID 11 > APIC: CPU 23 has ACPI ID 27 > APIC: CPU 24 has ACPI ID 12 > APIC: CPU 25 has ACPI ID 28 > APIC: CPU 26 has ACPI ID 13 > APIC: CPU 27 has ACPI ID 29 > APIC: CPU 28 has ACPI ID 14 > APIC: CPU 29 has ACPI ID 30 > APIC: CPU 30 has ACPI ID 15 > APIC: CPU 31 has ACPI ID 31 > random device not loaded; using insecure entropy > ULE: setup cpu 0 > ULE: setup cpu 1 > ULE: setup cpu 2 > ULE: setup cpu 3 > ULE: setup cpu 4 > ULE: setup cpu 5 > ULE: setup cpu 6 > ULE: setup cpu 7 > ULE: setup cpu 8 > ULE: setup cpu 9 > ULE: setup cpu 10 > ULE: setup cpu 11 > ULE: setup cpu 12 > ULE: setup cpu 13 > ULE: setup cpu 14 > ULE: setup cpu 15 > ULE: setup cpu 16 > ULE: setup cpu 17 > ULE: setup cpu 18 > ULE: setup cpu 19 > ULE: setup cpu 20 > ULE: setup cpu 21 > ULE: setup cpu 22 > ULE: setup cpu 23 > ULE: setup cpu 24 > ULE: setup cpu 25 > ULE: setup cpu 26 > ULE: setup cpu 27 > ULE: setup cpu 28 > ULE: setup cpu 29 > ULE: setup cpu 30 > ULE: setup cpu 31 > ACPI: RSDP 0xea020 00024 (v02 Xen) > ACPI: XSDT 0xfc006430 0004C (v01 Xen HVM 00000000 HVML 00000000) > ACPI: FACP 0xfc005ee0 000F4 (v04 Xen HVM 00000000 HVML 00000000) > ACPI: DSDT 0xfc002c40 0321F (v02 Xen HVM 00000000 INTL 20090220) > ACPI: FACS 0xfc002c00 00040 > ACPI: APIC 0xfc005fe0 00160 (v02 Xen HVM 00000000 HVML 00000000) > ACPI: SRAT 0xfc006140 00280 (v01 Xen HVM 00000000 HVML 00000000) > ACPI: SLIT 0xfc0063c0 00030 (v01 Xen HVM 00000000 HVML 00000000) > ACPI: HPET 0xfc0063f0 00038 (v01 Xen HVM 00000000 HVML 00000000) > MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 > ioapic0: Changing APIC ID to 1 > ioapic0: Routing external 8259A''s -> intpin 0 > MADT: Interrupt override: source 0, irq 2 > ioapic0: Routing IRQ 0 -> intpin 2 > MADT: Interrupt override: source 5, irq 5 > ioapic0: intpin 5 trigger: level > ioapic0: intpin 5 polarity: low > MADT: Interrupt override: source 10, irq 10 > ioapic0: intpin 10 trigger: level > ioapic0: intpin 10 polarity: low > MADT: Interrupt override: source 11, irq 11 > ioapic0: intpin 11 trigger: level > ioapic0: intpin 11 polarity: low > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0: intpin 9 polarity: low > ioapic0: intpin 9 trigger: level > ioapic0 <Version 1.1> irqs 0-47 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 > Event-channel device installed. > snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] > feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 > wlan: <802.11 Link Layer> > null: <null device, zero device> > nfslock: pseudo-device > random: <entropy source, Software, Yarrow> > VESA: INT 0x10 vector 0xc000:0x836e > VESA: information block > 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00 > 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83 > 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 > 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff > 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > VESA: 15 mode(s) found > VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80003ff040 (2000040) > VESA: VGABIOS Cirrus extension > VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0 > io: <I/O> > kbd: new array size 4 > kbd1 at kbdmux0 > mem: <memory> > hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 > hpt27xx: RocketRAID 27xx controller driver v1.0 > xen_et0: vector callbacks unavailable > acpi0: <Xen> on motherboard > ACPI: All ACPI Tables successfully acquired > ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > cpu0: Processor \_PR_.PR00 (ACPI ID 0) -> APIC ID 0 > cpu0: <ACPI CPU> on acpi0 > cpu0: switching to generic Cx mode > cpu1: Processor \_PR_.PR01 (ACPI ID 1) -> APIC ID 2 > cpu1: <ACPI CPU> on acpi0 > cpu2: Processor \_PR_.PR02 (ACPI ID 2) -> APIC ID 4 > cpu2: <ACPI CPU> on acpi0 > cpu3: Processor \_PR_.PR03 (ACPI ID 3) -> APIC ID 6 > cpu3: <ACPI CPU> on acpi0 > cpu4: Processor \_PR_.PR04 (ACPI ID 4) -> APIC ID 8 > cpu4: <ACPI CPU> on acpi0 > cpu5: Processor \_PR_.PR05 (ACPI ID 5) -> APIC ID 10 > cpu5: <ACPI CPU> on acpi0 > cpu6: Processor \_PR_.PR06 (ACPI ID 6) -> APIC ID 12 > cpu6: <ACPI CPU> on acpi0 > cpu7: Processor \_PR_.PR07 (ACPI ID 7) -> APIC ID 14 > cpu7: <ACPI CPU> on acpi0 > cpu8: Processor \_PR_.PR08 (ACPI ID 8) -> APIC ID 16 > cpu8: <ACPI CPU> on acpi0 > cpu9: Processor \_PR_.PR09 (ACPI ID 9) -> APIC ID 18 > cpu9: <ACPI CPU> on acpi0 > cpu10: Processor \_PR_.PR0A (ACPI ID 10) -> APIC ID 20 > cpu10: <ACPI CPU> on acpi0 > cpu11: Processor \_PR_.PR0B (ACPI ID 11) -> APIC ID 22 > cpu11: <ACPI CPU> on acpi0 > cpu12: Processor \_PR_.PR0C (ACPI ID 12) -> APIC ID 24 > cpu12: <ACPI CPU> on acpi0 > cpu13: Processor \_PR_.PR0D (ACPI ID 13) -> APIC ID 26 > cpu13: <ACPI CPU> on acpi0 > cpu14: Processor \_PR_.PR0E (ACPI ID 14) -> APIC ID 28 > cpu14: <ACPI CPU> on acpi0 > hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 > hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route > hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic > hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic > hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic > Timecounter "HPET" frequency 62500000 Hz quality 950 > attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 > atrtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) > ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50 > Event timer "RTC" frequency 32768 Hz quality 0 > ACPI timer: 1/7 1/5 1/8 1/9 1/7 1/7 1/7 1/7 1/19 1/8 -> 10 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1f48-0x1f4b on acpi0 > pci_link0: Index IRQ Rtd Ref IRQs > Initial Probe 0 5 N 0 5 10 11 > Validation 0 5 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pci_link1: Index IRQ Rtd Ref IRQs > Initial Probe 0 10 N 0 5 10 11 > Validation 0 10 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pci_link2: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 5 10 11 > Validation 0 11 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pci_link3: Index IRQ Rtd Ref IRQs > Initial Probe 0 5 N 0 5 10 11 > Validation 0 5 N 0 5 10 11 > After Disable 0 255 N 0 5 10 11 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 > pcib0: decoding 4 range 0-0xcf7 > pcib0: decoding 4 range 0xd00-0xffff > pcib0: decoding 3 range 0xa0000-0xbffff > pcib0: decoding 3 range 0xc0000000-0xf4ffffff > pci0: <ACPI PCI bus> on pcib0 > pci0: domain=0, physical bus=0 > found-> vendor=0x8086, dev=0x1237, revid=0x02 > domain=0, bus=0, slot=0, func=0 > class=06-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x7000, revid=0x00 > domain=0, bus=0, slot=1, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x7010, revid=0x00 > domain=0, bus=0, slot=1, func=1 > class=01-01-80, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 > pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 > pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 > pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 > map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled > pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1 > found-> vendor=0x8086, dev=0x7113, revid=0x01 > domain=0, bus=0, slot=1, func=3 > class=06-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > pcib0: matched entry for 0.1.INTA > pcib0: slot 1 INTA hardwired to IRQ 20 > found-> vendor=0x1013, dev=0x00b8, revid=0x00 > domain=0, bus=0, slot=2, func=0 > class=03-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type Prefetchable Memory, range 32, base 0xc0000000, size 25, enabled > pcib0: allocated type 3 (0xc0000000-0xc1ffffff) for rid 10 of pci0:0:2:0 > map[14]: type Memory, range 32, base 0xc3000000, size 12, enabled > pcib0: allocated type 3 (0xc3000000-0xc3000fff) for rid 14 of pci0:0:2:0 > found-> vendor=0x5853, dev=0x0001, revid=0x01 > domain=0, bus=0, slot=3, func=0 > class=ff-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=5 > map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled > pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 > map[14]: type Prefetchable Memory, range 32, base 0xc2000000, size 24, enabled > pcib0: allocated type 3 (0xc2000000-0xc2ffffff) for rid 14 of pci0:0:3:0 > pcib0: matched entry for 0.3.INTA > pcib0: slot 3 INTA hardwired to IRQ 28 > isab0: <PCI-ISA bridge> at device 1.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0 > ata0: <ATA channel> at channel 0 on atapci0 > ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51 > ata1: <ATA channel> at channel 1 on atapci0 > ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52 > pci0: <bridge> at device 1.3 (no driver attached) > vgapci0: <VGA-compatible display> mem 0xc0000000-0xc1ffffff,0xc3000000-0xc3000fff at device 2.0 on pci0 > xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xc2000000-0xc2ffffff irq 28 at device 3.0 on pci0 > ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53 > xenstore0: <XenStore> on xenpci0 > Grant table initialized > psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0061 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > kbd0 at atkbd0 > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 > ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54 > atkbd0: [GIANT-LOCKED] > psm0: current command byte:0061 > kbdc: TEST_AUX_PORT status:0000 > kbdc: RESET_AUX return code:00fa > kbdc: RESET_AUX status:00aa > kbdc: RESET_AUX ID:0000 > kbdc: RESET_AUX return code:00fa > kbdc: RESET_AUX status:00aa > kbdc: RESET_AUX ID:0000 > psm: status 00 02 64 > psm: status 00 00 64 > psm: status 00 03 64 > psm: status 00 03 64 > psm: data 08 00 00 > psm: status 00 02 64 > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons > psm0: config:00000000, flags:00000008, packet size:4 > psm0: syncmask:08, syncbits:00 > fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56 > uart0: fast interrupt > uart0: console (9600,n,8,1) > ppc0: using extended I/O port range > ACPI: Enabled 1 GPEs in block 00 to 1F > acpi0: wakeup code va 0xffffff9096fb5000 pa 0x4000 > ex_isa_identify() > pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 > pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 > ahc_isa_identify 0: ioport 0xc00 alloc failed > ahc_isa_identify 1: ioport 0x1c00 alloc failed > ahc_isa_identify 2: ioport 0x2c00 alloc failed > ahc_isa_identify 3: ioport 0x3c00 alloc failed > ahc_isa_identify 4: ioport 0x4c00 alloc failed > ahc_isa_identify 5: ioport 0x5c00 alloc failed > ahc_isa_identify 6: ioport 0x6c00 alloc failed > ahc_isa_identify 7: ioport 0x7c00 alloc failed > ahc_isa_identify 8: ioport 0x8c00 alloc failed > ahc_isa_identify 9: ioport 0x9c00 alloc failed > ahc_isa_identify 10: ioport 0xac00 alloc failed > ahc_isa_identify 11: ioport 0xbc00 alloc failed > ahc_isa_identify 12: ioport 0xcc00 alloc failed > ahc_isa_identify 13: ioport 0xdc00 alloc failed > ahc_isa_identify 14: ioport 0xec00 alloc failed > isa_probe_children: disabling PnP devices > atkbdc: atkbdc0 already exists; skipping it > atrtc: atrtc0 already exists; skipping it > attimer: attimer0 already exists; skipping it > sc: sc0 already exists; skipping it > uart: uart0 already exists; skipping it > isa_probe_children: probing non-PnP devices > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 > pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 > fdc0: No FDOUT register! > fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 > ppc0: cannot reserve I/O port range > ppc0 failed to probe at irq 7 on isa0 > pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 > uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 > wbwd0 failed to probe on isa0 > isa_probe_children: probing PnP devices > Device configuration finished. > procfs registered > lapic: Divisor 2, Frequency 50000453 Hz > Timecounters tick every 10.000 msec > vlan: initialized, using hash tables with chaining > tcp_init: net.inet.tcp.tcbhashsize auto tuned to 524288 > lo0: bpf attached > hptrr: no controller detected. > hpt27xx: no controller detected. > xenbusb_front0: <Xen Frontend Devices> on xenstore0 > ata0: reset tp1 mask=03 ostat0=00 ostat1=00 > ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 > ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > ata0: reset tp2 stat0=00 stat1=00 devices=0x0 > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 > ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > ata1: reset tp2 stat0=00 stat1=00 devices=0x0-- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 17/05/13 05:07, Colin Percival wrote:> On 05/16/13 17:43, Roger Pau Monné wrote: >> Thanks for testing this on EC2, could you post the full dmesg? So I can >> see the hypervisor version and if the PV timer is loaded or not. > > Here''s what I get on a cc2.8xlarge with boot_verbose=YES:I''ve pushed a new branch to my repository, pvhvm_v7 that should work, there was a bug with PCI event channel interrupt set up. I''ve tested with 3.4 and seems OK, but of course it doesn''t support the vector callback injection. Regards, Roger.
On 17/05/13 05:07, Colin Percival wrote:> On 05/16/13 17:43, Roger Pau Monné wrote: >> Thanks for testing this on EC2, could you post the full dmesg? So I can >> see the hypervisor version and if the PV timer is loaded or not. > > Here''s what I get on a cc2.8xlarge with boot_verbose=YES:I''ve pushed a new branch to my repository, pvhvm_v7 that should work, there was a bug with PCI event channel interrupt set up. I''ve tested with 3.4 and seems OK, but of course it doesn''t support the vector callback injection. Regards, Roger.
On 05/18/13 02:50, Roger Pau Monné wrote:> On 17/05/13 05:07, Colin Percival wrote: >> On 05/16/13 17:43, Roger Pau Monné wrote: >>> Thanks for testing this on EC2, could you post the full dmesg? So I can >>> see the hypervisor version and if the PV timer is loaded or not. >> >> Here''s what I get on a cc2.8xlarge with boot_verbose=YES: > > I''ve pushed a new branch to my repository, pvhvm_v7 that should work, > there was a bug with PCI event channel interrupt set up. I''ve tested > with 3.4 and seems OK, but of course it doesn''t support the vector > callback injection.That seems to work. dmesg is attached. Are there any particular tests you''d like me to run? If anyone else wants to play with this, you can launch ami-e75c358e in the EC2 us-east-1 region. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 05/18/13 02:50, Roger Pau Monné wrote:> On 17/05/13 05:07, Colin Percival wrote: >> On 05/16/13 17:43, Roger Pau Monné wrote: >>> Thanks for testing this on EC2, could you post the full dmesg? So I can >>> see the hypervisor version and if the PV timer is loaded or not. >> >> Here''s what I get on a cc2.8xlarge with boot_verbose=YES: > > I''ve pushed a new branch to my repository, pvhvm_v7 that should work, > there was a bug with PCI event channel interrupt set up. I''ve tested > with 3.4 and seems OK, but of course it doesn''t support the vector > callback injection.That seems to work. dmesg is attached. Are there any particular tests you''d like me to run? If anyone else wants to play with this, you can launch ami-e75c358e in the EC2 us-east-1 region. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote:> Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. > The main benefits of this changes are that Xen virtual interrupts (event > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when running > as an HVM guest, which should provide better time keeping and reduce the > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. > > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. > > The code is available in the following git repository, under the branch > pvhvm_v5: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > > Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMI tried on my Linux box to do this: HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM Makefile:123: *** missing separator. Stop. As I thought it would compile the same way you can compile NetBSD - that is even on non-BSD distros. Is that not the case? Should I only do this under a FreeBSD guest?
On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote:> On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: >> Hello, >> >> Recently Justin T Gibbs, Will Andrews and myself have been working on >> improving the Xen support in FreeBSD. The main goal of this was to bring >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV >> interfaces for disk and network interfaces when running as a HVM guest. >> The main benefits of this changes are that Xen virtual interrupts (event >> channels) are now delivered to the guest using a vector callback >> injection, that is a per-cpu mechanism that allows each vCPU to have >> different interrupts assigned, so for example network and disk >> interrupts are delivered to different vCPUs in order to improve >> performance. With this changes FreeBSD also uses PV timers when running >> as an HVM guest, which should provide better time keeping and reduce the >> virtualization overhead, since emulated timers are no longer used. PV >> IPIs can also be used inside a HVM guest, but this will be implemented >> later. >> >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. >> >> The code is available in the following git repository, under the branch >> pvhvm_v5: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary >> >> Also, I''ve created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > I tried on my Linux box to do this: > > > HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces > konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM > Makefile:123: *** missing separator. Stop. > > > As I thought it would compile the same way you can compile NetBSD - that is > even on non-BSD distros. Is that not the case? Should I only do this under > a FreeBSD guest?I have never tried to run the FreeBSD build system under something different than FreeBSD, also keep in mind that installkernel will place a bunch of FreeBSD files on your Linux box if you manage to run it. The error itself can probably be fixed by installing and using BSD make (bmake), but anyway you need a FreeBSD HVM DomU in order to test the kernel, so why not do the compilation on it?
On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote:> On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: >> Hello, >> >> Recently Justin T Gibbs, Will Andrews and myself have been working on >> improving the Xen support in FreeBSD. The main goal of this was to bring >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV >> interfaces for disk and network interfaces when running as a HVM guest. >> The main benefits of this changes are that Xen virtual interrupts (event >> channels) are now delivered to the guest using a vector callback >> injection, that is a per-cpu mechanism that allows each vCPU to have >> different interrupts assigned, so for example network and disk >> interrupts are delivered to different vCPUs in order to improve >> performance. With this changes FreeBSD also uses PV timers when running >> as an HVM guest, which should provide better time keeping and reduce the >> virtualization overhead, since emulated timers are no longer used. PV >> IPIs can also be used inside a HVM guest, but this will be implemented >> later. >> >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. >> >> The code is available in the following git repository, under the branch >> pvhvm_v5: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary >> >> Also, I''ve created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > I tried on my Linux box to do this: > > > HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces > konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM > Makefile:123: *** missing separator. Stop. > > > As I thought it would compile the same way you can compile NetBSD - that is > even on non-BSD distros. Is that not the case? Should I only do this under > a FreeBSD guest?I have never tried to run the FreeBSD build system under something different than FreeBSD, also keep in mind that installkernel will place a bunch of FreeBSD files on your Linux box if you manage to run it. The error itself can probably be fixed by installing and using BSD make (bmake), but anyway you need a FreeBSD HVM DomU in order to test the kernel, so why not do the compilation on it?
On 18/05/13 17:44, Colin Percival wrote:> On 05/18/13 02:50, Roger Pau Monné wrote: >> On 17/05/13 05:07, Colin Percival wrote: >>> On 05/16/13 17:43, Roger Pau Monné wrote: >>>> Thanks for testing this on EC2, could you post the full dmesg? So I can >>>> see the hypervisor version and if the PV timer is loaded or not. >>> >>> Here''s what I get on a cc2.8xlarge with boot_verbose=YES: >> >> I''ve pushed a new branch to my repository, pvhvm_v7 that should work, >> there was a bug with PCI event channel interrupt set up. I''ve tested >> with 3.4 and seems OK, but of course it doesn''t support the vector >> callback injection. > > That seems to work. dmesg is attached. Are there any particular tests > you''d like me to run?I have not tested ZFS, that might be a good one. If you are running this on Xen 3.4 the behaviour should be the same as without this patches, so there shouldn''t be many differences. If you could try that on Xen 4.0 at least (if I remember correctly that''s when the vector callback was introduced), you should see the PV timer getting attached, and a performance increase.> If anyone else wants to play with this, you can launch ami-e75c358e in the > EC2 us-east-1 region. >
On 18/05/13 17:44, Colin Percival wrote:> On 05/18/13 02:50, Roger Pau Monné wrote: >> On 17/05/13 05:07, Colin Percival wrote: >>> On 05/16/13 17:43, Roger Pau Monné wrote: >>>> Thanks for testing this on EC2, could you post the full dmesg? So I can >>>> see the hypervisor version and if the PV timer is loaded or not. >>> >>> Here''s what I get on a cc2.8xlarge with boot_verbose=YES: >> >> I''ve pushed a new branch to my repository, pvhvm_v7 that should work, >> there was a bug with PCI event channel interrupt set up. I''ve tested >> with 3.4 and seems OK, but of course it doesn''t support the vector >> callback injection. > > That seems to work. dmesg is attached. Are there any particular tests > you''d like me to run?I have not tested ZFS, that might be a good one. If you are running this on Xen 3.4 the behaviour should be the same as without this patches, so there shouldn''t be many differences. If you could try that on Xen 4.0 at least (if I remember correctly that''s when the vector callback was introduced), you should see the PV timer getting attached, and a performance increase.> If anyone else wants to play with this, you can launch ami-e75c358e in the > EC2 us-east-1 region. >
On Wed, May 22, 2013 at 01:41:02PM +0200, Roger Pau Monné wrote:> On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote: > > On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: > >> Hello, > >> > >> Recently Justin T Gibbs, Will Andrews and myself have been working on > >> improving the Xen support in FreeBSD. The main goal of this was to bring > >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV > >> interfaces for disk and network interfaces when running as a HVM guest. > >> The main benefits of this changes are that Xen virtual interrupts (event > >> channels) are now delivered to the guest using a vector callback > >> injection, that is a per-cpu mechanism that allows each vCPU to have > >> different interrupts assigned, so for example network and disk > >> interrupts are delivered to different vCPUs in order to improve > >> performance. With this changes FreeBSD also uses PV timers when running > >> as an HVM guest, which should provide better time keeping and reduce the > >> virtualization overhead, since emulated timers are no longer used. PV > >> IPIs can also be used inside a HVM guest, but this will be implemented > >> later. > >> > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > >> > >> The code is available in the following git repository, under the branch > >> pvhvm_v5: > >> > >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > >> > >> Also, I''ve created a wiki page that explains how to set up a FreeBSD > >> PVHVM for testing: > >> > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > I tried on my Linux box to do this: > > > > > > HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces > > konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM > > Makefile:123: *** missing separator. Stop. > > > > > > As I thought it would compile the same way you can compile NetBSD - that is > > even on non-BSD distros. Is that not the case? Should I only do this under > > a FreeBSD guest? > > I have never tried to run the FreeBSD build system under something > different than FreeBSD, also keep in mind that installkernel will place > a bunch of FreeBSD files on your Linux box if you manage to run it. The > error itself can probably be fixed by installing and using BSD make > (bmake), but anyway you need a FreeBSD HVM DomU in order to test the > kernel, so why not do the compilation on it?Oh, sure. Just thought that the NetBSD method (which also allows one to build the kernel and the iso) was the same on FreeBSd. Will of course install first the HVM domU and do it again.>
Konrad Rzeszutek Wilk
2013-May-22 12:21 UTC
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Wed, May 22, 2013 at 01:41:02PM +0200, Roger Pau Monné wrote:> On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote: > > On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: > >> Hello, > >> > >> Recently Justin T Gibbs, Will Andrews and myself have been working on > >> improving the Xen support in FreeBSD. The main goal of this was to bring > >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV > >> interfaces for disk and network interfaces when running as a HVM guest. > >> The main benefits of this changes are that Xen virtual interrupts (event > >> channels) are now delivered to the guest using a vector callback > >> injection, that is a per-cpu mechanism that allows each vCPU to have > >> different interrupts assigned, so for example network and disk > >> interrupts are delivered to different vCPUs in order to improve > >> performance. With this changes FreeBSD also uses PV timers when running > >> as an HVM guest, which should provide better time keeping and reduce the > >> virtualization overhead, since emulated timers are no longer used. PV > >> IPIs can also be used inside a HVM guest, but this will be implemented > >> later. > >> > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > >> > >> The code is available in the following git repository, under the branch > >> pvhvm_v5: > >> > >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > >> > >> Also, I''ve created a wiki page that explains how to set up a FreeBSD > >> PVHVM for testing: > >> > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > I tried on my Linux box to do this: > > > > > > HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces > > konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM > > Makefile:123: *** missing separator. Stop. > > > > > > As I thought it would compile the same way you can compile NetBSD - that is > > even on non-BSD distros. Is that not the case? Should I only do this under > > a FreeBSD guest? > > I have never tried to run the FreeBSD build system under something > different than FreeBSD, also keep in mind that installkernel will place > a bunch of FreeBSD files on your Linux box if you manage to run it. The > error itself can probably be fixed by installing and using BSD make > (bmake), but anyway you need a FreeBSD HVM DomU in order to test the > kernel, so why not do the compilation on it?Oh, sure. Just thought that the NetBSD method (which also allows one to build the kernel and the iso) was the same on FreeBSd. Will of course install first the HVM domU and do it again.>
Hi,
I''ve just successfully run FreeBSD 9.1 based guest with
''pvhvm_v8'' based kernel under Xen 3.4.4.
Hypervisor details:
# xm info
host : *******
release : 2.6.18-348.2.1.el5xen
version : #1 SMP Tue Mar 5 17:05:33 EST 2013
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2128
hw_caps :
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 6135
free_memory : 262
node_to_cpu : node0:0-3
node_to_memory : node0:262
xen_major : 3
xen_minor : 4
xen_extra : .4
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)
cc_compile_by : root
cc_compile_domain : ******
cc_compile_date : Wed Sep 5 18:01:10 EEST 2012
xend_config_format : 4
DomU details:
# xm list --long h283bpm53f9rnx
(domain
(domid 61)
(on_crash restart)
(uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051)
(bootloader_args )
(vcpus 2)
(name h283bpm53f9rnx)
(on_poweroff destroy)
(on_reboot restart)
(cpus (() ()))
(bootloader )
(maxmem 1024)
(memory 1024)
(shadow_memory 10)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1369235607.92)
(cpu_time 31.914003553)
(online_vcpus 2)
(image
(hvm
(kernel )
(videoram 4)
(hpet 0)
(stdvga 0)
(loader /usr/lib/xen/boot/hvmloader)
(vncunused 1)
(xen_platform_pci 1)
(boot cd)
(rtc_timeoffset 7202)
(pci ())
(pae 1)
(vpt_align 1)
(hap 1)
(viridian 0)
(acpi 1)
(localtime 0)
(timer_mode 1)
(vnc 1)
(nographic 0)
(guest_os_type default)
(pci_msitranslate 1)
(apic 1)
(monitor 0)
(usbdevice tablet)
(device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0)
(usb 0)
(xauthority /root/.Xauthority)
(isa 0)
(notes (SUSPEND_CANCEL 1))
)
)
(status 2)
(state -b----)
(store_mfn 1044476)
(device
(vif
(bridge xnh5getjoj54ke)
(uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe)
(script /etc/xen/scripts/vif-bridge)
(ip 83.170.81.183)
(mac 00:16:3e:a4:02:5a)
(vifname t2vd5w22msrv5d)
(backend 0)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a)
(bootable 1)
(dev hda:disk)
(uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby)
(mode w)
(backend 0)
(bootable 1)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba)
(bootable 0)
(dev hdb:disk)
(uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd)
(mode w)
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 2b97ec8c-0cc5-7197-f510-63c272449680)
(bootable 0)
(dev hdc:disk)
(uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq)
(mode w)
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7)
(bootable 0)
(dev hdd:cdrom)
(uname file:/tools/freebsd/boot-freebsd-generic.iso)
(mode r)
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vfb
(vncunused 1)
(vnc 1)
(uuid b3defeea-4acc-1408-9b22-71547a64e705)
(location 0.0.0.0:5900)
)
)
(device
(console
(protocol vt100)
(location 4)
(uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da)
)
)
)
DomU from "inside":
# uname -a
FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed May 22
17:47:40 EEST 2013 root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64
I''ll also set up one (hope will have some time) under Xen 4.2.2
tomorrow.
---
Yura
On May 13, 2013, at 21:32 PM, Roger Pau Monné <roger.pau@citrix.com>
wrote:
> Hello,
>
> Recently Justin T Gibbs, Will Andrews and myself have been working on
> improving the Xen support in FreeBSD. The main goal of this was to bring
> full PVHVM support to FreeBSD, right now FreeBSD is only using PV
> interfaces for disk and network interfaces when running as a HVM guest.
> The main benefits of this changes are that Xen virtual interrupts (event
> channels) are now delivered to the guest using a vector callback
> injection, that is a per-cpu mechanism that allows each vCPU to have
> different interrupts assigned, so for example network and disk
> interrupts are delivered to different vCPUs in order to improve
> performance. With this changes FreeBSD also uses PV timers when running
> as an HVM guest, which should provide better time keeping and reduce the
> virtualization overhead, since emulated timers are no longer used. PV
> IPIs can also be used inside a HVM guest, but this will be implemented
> later.
>
> Right now the code is in a state where it can be tested by users, so we
> would like to encourage FreeBSD and Xen users to test it and provide
> feedback.
>
> The code is available in the following git repository, under the branch
> pvhvm_v5:
>
> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary
>
> Also, I''ve created a wiki page that explains how to set up a
FreeBSD
> PVHVM for testing:
>
> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to
"freebsd-xen-unsubscribe@freebsd.org"
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Hi,
I''ve just successfully run FreeBSD 9.1 based guest with
''pvhvm_v8'' based kernel under Xen 3.4.4.
Hypervisor details:
# xm info
host : *******
release : 2.6.18-348.2.1.el5xen
version : #1 SMP Tue Mar 5 17:05:33 EST 2013
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2128
hw_caps :
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 6135
free_memory : 262
node_to_cpu : node0:0-3
node_to_memory : node0:262
xen_major : 3
xen_minor : 4
xen_extra : .4
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)
cc_compile_by : root
cc_compile_domain : ******
cc_compile_date : Wed Sep 5 18:01:10 EEST 2012
xend_config_format : 4
DomU details:
# xm list --long h283bpm53f9rnx
(domain
(domid 61)
(on_crash restart)
(uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051)
(bootloader_args )
(vcpus 2)
(name h283bpm53f9rnx)
(on_poweroff destroy)
(on_reboot restart)
(cpus (() ()))
(bootloader )
(maxmem 1024)
(memory 1024)
(shadow_memory 10)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1369235607.92)
(cpu_time 31.914003553)
(online_vcpus 2)
(image
(hvm
(kernel )
(videoram 4)
(hpet 0)
(stdvga 0)
(loader /usr/lib/xen/boot/hvmloader)
(vncunused 1)
(xen_platform_pci 1)
(boot cd)
(rtc_timeoffset 7202)
(pci ())
(pae 1)
(vpt_align 1)
(hap 1)
(viridian 0)
(acpi 1)
(localtime 0)
(timer_mode 1)
(vnc 1)
(nographic 0)
(guest_os_type default)
(pci_msitranslate 1)
(apic 1)
(monitor 0)
(usbdevice tablet)
(device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0)
(usb 0)
(xauthority /root/.Xauthority)
(isa 0)
(notes (SUSPEND_CANCEL 1))
)
)
(status 2)
(state -b----)
(store_mfn 1044476)
(device
(vif
(bridge xnh5getjoj54ke)
(uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe)
(script /etc/xen/scripts/vif-bridge)
(ip 83.170.81.183)
(mac 00:16:3e:a4:02:5a)
(vifname t2vd5w22msrv5d)
(backend 0)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a)
(bootable 1)
(dev hda:disk)
(uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby)
(mode w)
(backend 0)
(bootable 1)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba)
(bootable 0)
(dev hdb:disk)
(uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd)
(mode w)
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 2b97ec8c-0cc5-7197-f510-63c272449680)
(bootable 0)
(dev hdc:disk)
(uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq)
(mode w)
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7)
(bootable 0)
(dev hdd:cdrom)
(uname file:/tools/freebsd/boot-freebsd-generic.iso)
(mode r)
(backend 0)
(bootable 0)
(VDI )
)
)
(device
(vfb
(vncunused 1)
(vnc 1)
(uuid b3defeea-4acc-1408-9b22-71547a64e705)
(location 0.0.0.0:5900)
)
)
(device
(console
(protocol vt100)
(location 4)
(uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da)
)
)
)
DomU from "inside":
# uname -a
FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed May 22
17:47:40 EEST 2013 root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64
I''ll also set up one (hope will have some time) under Xen 4.2.2
tomorrow.
---
Yura
On May 13, 2013, at 21:32 PM, Roger Pau Monné <roger.pau@citrix.com>
wrote:
> Hello,
>
> Recently Justin T Gibbs, Will Andrews and myself have been working on
> improving the Xen support in FreeBSD. The main goal of this was to bring
> full PVHVM support to FreeBSD, right now FreeBSD is only using PV
> interfaces for disk and network interfaces when running as a HVM guest.
> The main benefits of this changes are that Xen virtual interrupts (event
> channels) are now delivered to the guest using a vector callback
> injection, that is a per-cpu mechanism that allows each vCPU to have
> different interrupts assigned, so for example network and disk
> interrupts are delivered to different vCPUs in order to improve
> performance. With this changes FreeBSD also uses PV timers when running
> as an HVM guest, which should provide better time keeping and reduce the
> virtualization overhead, since emulated timers are no longer used. PV
> IPIs can also be used inside a HVM guest, but this will be implemented
> later.
>
> Right now the code is in a state where it can be tested by users, so we
> would like to encourage FreeBSD and Xen users to test it and provide
> feedback.
>
> The code is available in the following git repository, under the branch
> pvhvm_v5:
>
> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary
>
> Also, I''ve created a wiki page that explains how to set up a
FreeBSD
> PVHVM for testing:
>
> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to
"freebsd-xen-unsubscribe@freebsd.org"
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
On 05/22/13 04:45, Roger Pau Monné wrote:> On 18/05/13 17:44, Colin Percival wrote: >> That seems to work. dmesg is attached. Are there any particular tests >> you''d like me to run? > > I have not tested ZFS, that might be a good one. If you are running this > on Xen 3.4 the behaviour should be the same as without this patches, so > there shouldn''t be many differences.I don''t use ZFS personally, so I''m not sure exactly what tests to run on it; hopefully someone else can take care of that.> If you could try that on Xen 4.0 at least (if I remember correctly > that''s when the vector callback was introduced), you should see the PV > timer getting attached, and a performance increase.Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with a panic -- console output below. I can get a backtrace and possibly even a dump if those would help. Booting [/boot/kernel/kernel]... -\|/-\|GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=000000000009e000 SMAP type=02 base=000000000009e000 len=0000000000002000 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=00000000eff00000 SMAP type=02 base=00000000fc000000 len=0000000004000000 SMAP type=01 base=0000000100000000 len=0000003c19000000 Table ''FACP'' at 0xfc014980 Table ''APIC'' at 0xfc014a80 APIC: Found table at 0xfc014a80 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: enabled SMP: Added CPU 14 (AP) MADT: Found CPU APIC ID 32 ACPI ID 8: enabled SMP: Added CPU 32 (AP) MADT: Found CPU APIC ID 34 ACPI ID 9: enabled SMP: Added CPU 34 (AP) MADT: Found CPU APIC ID 36 ACPI ID 10: enabled SMP: Added CPU 36 (AP) MADT: Found CPU APIC ID 38 ACPI ID 11: enabled SMP: Added CPU 38 (AP) MADT: Found CPU APIC ID 40 ACPI ID 12: enabled SMP: Added CPU 40 (AP) MADT: Found CPU APIC ID 42 ACPI ID 13: enabled SMP: Added CPU 42 (AP) MADT: Found CPU APIC ID 44 ACPI ID 14: enabled SMP: Added CPU 44 (AP) MADT: Found CPU APIC ID 46 ACPI ID 15: enabled SMP: Added CPU 46 (AP) MADT: Found CPU APIC ID 1 ACPI ID 16: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 3 ACPI ID 17: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 5 ACPI ID 18: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 7 ACPI ID 19: enabled SMP: Added CPU 7 (AP) MADT: Found CPU APIC ID 9 ACPI ID 20: enabled SMP: Added CPU 9 (AP) MADT: Found CPU APIC ID 11 ACPI ID 21: enabled SMP: Added CPU 11 (AP) MADT: Found CPU APIC ID 13 ACPI ID 22: enabled SMP: Added CPU 13 (AP) MADT: Found CPU APIC ID 15 ACPI ID 23: enabled SMP: Added CPU 15 (AP) MADT: Found CPU APIC ID 33 ACPI ID 24: enabled SMP: Added CPU 33 (AP) MADT: Found CPU APIC ID 35 ACPI ID 25: enabled SMP: Added CPU 35 (AP) MADT: Found CPU APIC ID 37 ACPI ID 26: enabled SMP: Added CPU 37 (AP) MADT: Found CPU APIC ID 39 ACPI ID 27: enabled SMP: Added CPU 39 (AP) MADT: Found CPU APIC ID 41 ACPI ID 28: enabled SMP: Added CPU 41 (AP) MADT: Found CPU APIC ID 43 ACPI ID 29: enabled SMP: Added CPU 43 (AP) MADT: Found CPU APIC ID 45 ACPI ID 30: enabled SMP: Added CPU 45 (AP) MADT: Found CPU APIC ID 47 ACPI ID 31: enabled SMP: Added CPU 47 (AP) MADT: Found CPU APIC ID 0 ACPI ID 32: disabled MADT: Found CPU APIC ID 0 ACPI ID 33: disabled MADT: Found CPU APIC ID 0 ACPI ID 34: disabled MADT: Found CPU APIC ID 0 ACPI ID 35: disabled MADT: Found CPU APIC ID 0 ACPI ID 36: disabled MADT: Found CPU APIC ID 0 ACPI ID 37: disabled MADT: Found CPU APIC ID 0 ACPI ID 38: disabled MADT: Found CPU APIC ID 0 ACPI ID 39: disabled MADT: Found CPU APIC ID 0 ACPI ID 40: disabled MADT: Found CPU APIC ID 0 ACPI ID 41: disabled MADT: Found CPU APIC ID 0 ACPI ID 42: disabled MADT: Found CPU APIC ID 0 ACPI ID 43: disabled MADT: Found CPU APIC ID 0 ACPI ID 44: disabled MADT: Found CPU APIC ID 0 ACPI ID 45: disabled MADT: Found CPU APIC ID 0 ACPI ID 46: disabled MADT: Found CPU APIC ID 0 ACPI ID 47: disabled MADT: Found CPU APIC ID 0 ACPI ID 48: disabled MADT: Found CPU APIC ID 0 ACPI ID 49: disabled MADT: Found CPU APIC ID 0 ACPI ID 50: disabled MADT: Found CPU APIC ID 0 ACPI ID 51: disabled MADT: Found CPU APIC ID 0 ACPI ID 52: disabled MADT: Found CPU APIC ID 0 ACPI ID 53: disabled MADT: Found CPU APIC ID 0 ACPI ID 54: disabled MADT: Found CPU APIC ID 0 ACPI ID 55: disabled MADT: Found CPU APIC ID 0 ACPI ID 56: disabled MADT: Found CPU APIC ID 0 ACPI ID 57: disabled MADT: Found CPU APIC ID 0 ACPI ID 58: disabled MADT: Found CPU APIC ID 0 ACPI ID 59: disabled MADT: Found CPU APIC ID 0 ACPI ID 60: disabled MADT: Found CPU APIC ID 0 ACPI ID 61: disabled MADT: Found CPU APIC ID 0 ACPI ID 62: disabled MADT: Found CPU APIC ID 0 ACPI ID 63: disabled MADT: Found CPU APIC ID 0 ACPI ID 64: disabled MADT: Found CPU APIC ID 0 ACPI ID 65: disabled MADT: Found CPU APIC ID 0 ACPI ID 66: disabled MADT: Found CPU APIC ID 0 ACPI ID 67: disabled MADT: Found CPU APIC ID 0 ACPI ID 68: disabled MADT: Found CPU APIC ID 0 ACPI ID 69: disabled MADT: Found CPU APIC ID 0 ACPI ID 70: disabled MADT: Found CPU APIC ID 0 ACPI ID 71: disabled MADT: Found CPU APIC ID 0 ACPI ID 72: disabled MADT: Found CPU APIC ID 0 ACPI ID 73: disabled MADT: Found CPU APIC ID 0 ACPI ID 74: disabled MADT: Found CPU APIC ID 0 ACPI ID 75: disabled MADT: Found CPU APIC ID 0 ACPI ID 76: disabled MADT: Found CPU APIC ID 0 ACPI ID 77: disabled MADT: Found CPU APIC ID 0 ACPI ID 78: disabled MADT: Found CPU APIC ID 0 ACPI ID 79: disabled MADT: Found CPU APIC ID 0 ACPI ID 80: disabled MADT: Found CPU APIC ID 0 ACPI ID 81: disabled MADT: Found CPU APIC ID 0 ACPI ID 82: disabled MADT: Found CPU APIC ID 0 ACPI ID 83: disabled MADT: Found CPU APIC ID 0 ACPI ID 84: disabled MADT: Found CPU APIC ID 0 ACPI ID 85: disabled MADT: Found CPU APIC ID 0 ACPI ID 86: disabled MADT: Found CPU APIC ID 0 ACPI ID 87: disabled MADT: Found CPU APIC ID 0 ACPI ID 88: disabled MADT: Found CPU APIC ID 0 ACPI ID 89: disabled MADT: Found CPU APIC ID 0 ACPI ID 90: disabled MADT: Found CPU APIC ID 0 ACPI ID 91: disabled MADT: Found CPU APIC ID 0 ACPI ID 92: disabled MADT: Found CPU APIC ID 0 ACPI ID 93: disabled MADT: Found CPU APIC ID 0 ACPI ID 94: disabled MADT: Found CPU APIC ID 0 ACPI ID 95: disabled MADT: Found CPU APIC ID 0 ACPI ID 96: disabled MADT: Found CPU APIC ID 0 ACPI ID 97: disabled MADT: Found CPU APIC ID 0 ACPI ID 98: disabled MADT: Found CPU APIC ID 0 ACPI ID 99: disabled MADT: Found CPU APIC ID 0 ACPI ID 100: disabled MADT: Found CPU APIC ID 0 ACPI ID 101: disabled MADT: Found CPU APIC ID 0 ACPI ID 102: disabled MADT: Found CPU APIC ID 0 ACPI ID 103: disabled MADT: Found CPU APIC ID 0 ACPI ID 104: disabled MADT: Found CPU APIC ID 0 ACPI ID 105: disabled MADT: Found CPU APIC ID 0 ACPI ID 106: disabled MADT: Found CPU APIC ID 0 ACPI ID 107: disabled MADT: Found CPU APIC ID 0 ACPI ID 108: disabled MADT: Found CPU APIC ID 0 ACPI ID 109: disabled MADT: Found CPU APIC ID 0 ACPI ID 110: disabled MADT: Found CPU APIC ID 0 ACPI ID 111: disabled MADT: Found CPU APIC ID 0 ACPI ID 112: disabled MADT: Found CPU APIC ID 0 ACPI ID 113: disabled MADT: Found CPU APIC ID 0 ACPI ID 114: disabled MADT: Found CPU APIC ID 0 ACPI ID 115: disabled MADT: Found CPU APIC ID 0 ACPI ID 116: disabled MADT: Found CPU APIC ID 0 ACPI ID 117: disabled MADT: Found CPU APIC ID 0 ACPI ID 118: disabled MADT: Found CPU APIC ID 0 ACPI ID 119: disabled MADT: Found CPU APIC ID 0 ACPI ID 120: disabled MADT: Found CPU APIC ID 0 ACPI ID 121: disabled MADT: Found CPU APIC ID 0 ACPI ID 122: disabled MADT: Found CPU APIC ID 0 ACPI ID 123: disabled MADT: Found CPU APIC ID 0 ACPI ID 124: disabled MADT: Found CPU APIC ID 0 ACPI ID 125: disabled MADT: Found CPU APIC ID 0 ACPI ID 126: disabled MADT: Found CPU APIC ID 0 ACPI ID 127: disabled Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r+9b25356: Sat May 18 14:46:16 UTC 2013 root@ip-10-140-132-115:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. XEN: Disabling emulated block and network devices Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81912000. Hypervisor: Origin = "XenVMMXenVMM" Calibrating TSC clock ... TSC clock: 2600048761 Hz CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.05-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0x9fba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> real memory = 262144000000 (250000 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x0000000001a2a000 - 0x00000000efffffff, 3999096832 bytes (976342 pages) 0x0000000100000000 - 0x0000003b8ae37fff, 251438268416 bytes (61386296 pages) avail memory = 244393709568 (233072 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target INTR: Adding local APIC 8 as a target INTR: Adding local APIC 9 as a target INTR: Adding local APIC 10 as a target INTR: Adding local APIC 11 as a target INTR: Adding local APIC 12 as a target INTR: Adding local APIC 13 as a target INTR: Adding local APIC 14 as a target INTR: Adding local APIC 15 as a target INTR: Adding local APIC 32 as a target INTR: Adding local APIC 33 as a target INTR: Adding local APIC 34 as a target INTR: Adding local APIC 35 as a target INTR: Adding local APIC 36 as a target INTR: Adding local APIC 37 as a target INTR: Adding local APIC 38 as a target INTR: Adding local APIC 39 as a target INTR: Adding local APIC 40 as a target INTR: Adding local APIC 41 as a target INTR: Adding local APIC 42 as a target INTR: Adding local APIC 43 as a target INTR: Adding local APIC 44 as a target INTR: Adding local APIC 45 as a target INTR: Adding local APIC 46 as a target INTR: Adding local APIC 47 as a target FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 12 cpu13 (AP): APIC ID: 13 cpu14 (AP): APIC ID: 14 cpu15 (AP): APIC ID: 15 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 33 cpu18 (AP): APIC ID: 34 cpu19 (AP): APIC ID: 35 cpu20 (AP): APIC ID: 36 cpu21 (AP): APIC ID: 37 cpu22 (AP): APIC ID: 38 cpu23 (AP): APIC ID: 39 cpu24 (AP): APIC ID: 40 cpu25 (AP): APIC ID: 41 cpu26 (AP): APIC ID: 42 cpu27 (AP): APIC ID: 43 cpu28 (AP): APIC ID: 44 cpu29 (AP): APIC ID: 45 cpu30 (AP): APIC ID: 46 cpu31 (AP): APIC ID: 47 x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 x86bios: SSEG 0x001000-0x001fff at 0xffffff80005e3000 x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 16 APIC: CPU 2 has ACPI ID 1 APIC: CPU 3 has ACPI ID 17 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 18 APIC: CPU 6 has ACPI ID 3 APIC: CPU 7 has ACPI ID 19 APIC: CPU 8 has ACPI ID 4 APIC: CPU 9 has ACPI ID 20 APIC: CPU 10 has ACPI ID 5 APIC: CPU 11 has ACPI ID 21 APIC: CPU 12 has ACPI ID 6 APIC: CPU 13 has ACPI ID 22 APIC: CPU 14 has ACPI ID 7 APIC: CPU 15 has ACPI ID 23 APIC: CPU 16 has ACPI ID 8 APIC: CPU 17 has ACPI ID 24 APIC: CPU 18 has ACPI ID 9 APIC: CPU 19 has ACPI ID 25 APIC: CPU 20 has ACPI ID 10 APIC: CPU 21 has ACPI ID 26 APIC: CPU 22 has ACPI ID 11 APIC: CPU 23 has ACPI ID 27 APIC: CPU 24 has ACPI ID 12 APIC: CPU 25 has ACPI ID 28 APIC: CPU 26 has ACPI ID 13 APIC: CPU 27 has ACPI ID 29 APIC: CPU 28 has ACPI ID 14 APIC: CPU 29 has ACPI ID 30 APIC: CPU 30 has ACPI ID 15 APIC: CPU 31 has ACPI ID 31 random device not loaded; using insecure entropy ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ULE: setup cpu 8 ULE: setup cpu 9 ULE: setup cpu 10 ULE: setup cpu 11 ULE: setup cpu 12 ULE: setup cpu 13 ULE: setup cpu 14 ULE: setup cpu 15 ULE: setup cpu 16 ULE: setup cpu 17 ULE: setup cpu 18 ULE: setup cpu 19 ULE: setup cpu 20 ULE: setup cpu 21 ULE: setup cpu 22 ULE: setup cpu 23 ULE: setup cpu 24 ULE: setup cpu 25 ULE: setup cpu 26 ULE: setup cpu 27 ULE: setup cpu 28 ULE: setup cpu 29 ULE: setup cpu 30 ULE: setup cpu 31 ACPI: RSDP 0xea020 00024 (v02 Xen) ACPI: XSDT 0xfc015920 0005C (v01 Xen HVM 00000000 HVML 00000000) ACPI: FACP 0xfc014980 000F4 (v04 Xen HVM 00000000 HVML 00000000) ACPI: DSDT 0xfc0035e0 11315 (v02 Xen HVM 00000000 INTL 20090123) ACPI: FACS 0xfc0035a0 00040 ACPI: APIC 0xfc014a80 00460 (v02 Xen HVM 00000000 HVML 00000000) ACPI: SRAT 0xfc014f60 008A8 (v01 Xen HVM 00000000 HVML 00000000) ACPI: HPET 0xfc015830 00038 (v01 Xen HVM 00000000 HVML 00000000) ACPI: WAET 0xfc015870 00028 (v01 Xen HVM 00000000 HVML 00000000) ACPI: SSDT 0xfc0158a0 00031 (v02 Xen HVM 00000000 INTL 20090123) ACPI: SSDT 0xfc0158e0 00031 (v02 Xen HVM 00000000 INTL 20090123) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A''s -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 5, irq 5 ioapic0: intpin 5 trigger: level ioapic0: intpin 5 polarity: low MADT: Interrupt override: source 10, irq 10 ioapic0: intpin 10 trigger: level ioapic0: intpin 10 polarity: low MADT: Interrupt override: source 11, irq 11 ioapic0: intpin 11 trigger: level ioapic0: intpin 11 polarity: low MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 <Version 1.1> irqs 0-47 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Event-channel device installed. snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 wlan: <802.11 Link Layer> null: <null device, zero device> nfslock: pseudo-device random: <entropy source, Software, Yarrow> VESA: INT 0x10 vector 0xc000:0x836e VESA: information block 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 15 mode(s) found VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80005fd040 (2000040) VESA: VGABIOS Cirrus extension VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0 io: <I/O> kbd: new array size 4 kbd1 at kbdmux0 mem: <memory> hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 hpt27xx: RocketRAID 27xx controller driver v1.0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 xen_et0: registered as a time-of-day clock (resolution 10000000us, adjustment 5.000000000s) acpi0: <Xen> on motherboard ACPI: All ACPI Tables successfully acquired ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: Processor \_SB_.PR00 (ACPI ID 0) -> APIC ID 0 cpu0: <ACPI CPU> on acpi0 cpu0: switching to generic Cx mode cpu1: Processor \_SB_.PR01 (ACPI ID 1) -> APIC ID 2 cpu1: <ACPI CPU> on acpi0 cpu2: Processor \_SB_.PR02 (ACPI ID 2) -> APIC ID 4 cpu2: <ACPI CPU> on acpi0 cpu3: Processor \_SB_.PR03 (ACPI ID 3) -> APIC ID 6 cpu3: <ACPI CPU> on acpi0 cpu4: Processor \_SB_.PR04 (ACPI ID 4) -> APIC ID 8 cpu4: <ACPI CPU> on acpi0 cpu5: Processor \_SB_.PR05 (ACPI ID 5) -> APIC ID 10 cpu5: <ACPI CPU> on acpi0 cpu6: Processor \_SB_.PR06 (ACPI ID 6) -> APIC ID 12 cpu6: <ACPI CPU> on acpi0 cpu7: Processor \_SB_.PR07 (ACPI ID 7) -> APIC ID 14 cpu7: <ACPI CPU> on acpi0 cpu8: Processor \_SB_.PR08 (ACPI ID 8) -> APIC ID 16 cpu8: <ACPI CPU> on acpi0 cpu9: Processor \_SB_.PR09 (ACPI ID 9) -> APIC ID 18 cpu9: <ACPI CPU> on acpi0 cpu10: Processor \_SB_.PR0A (ACPI ID 10) -> APIC ID 20 cpu10: <ACPI CPU> on acpi0 cpu11: Processor \_SB_.PR0B (ACPI ID 11) -> APIC ID 22 cpu11: <ACPI CPU> on acpi0 cpu12: Processor \_SB_.PR0C (ACPI ID 12) -> APIC ID 24 cpu12: <ACPI CPU> on acpi0 cpu13: Processor \_SB_.PR0D (ACPI ID 13) -> APIC ID 26 cpu13: <ACPI CPU> on acpi0 cpu14: Processor \_SB_.PR0E (ACPI ID 14) -> APIC ID 28 cpu14: <ACPI CPU> on acpi0 cpu15: Processor \_SB_.PR0F (ACPI ID 15) -> APIC ID 30 cpu15: <ACPI CPU> on acpi0 cpu16: Processor \_SB_.PR10 (ACPI ID 16) -> APIC ID 1 cpu16: <ACPI CPU> on acpi0 cpu17: Processor \_SB_.PR11 (ACPI ID 17) -> APIC ID 3 cpu17: <ACPI CPU> on acpi0 cpu18: Processor \_SB_.PR12 (ACPI ID 18) -> APIC ID 5 cpu18: <ACPI CPU> on acpi0 cpu19: Processor \_SB_.PR13 (ACPI ID 19) -> APIC ID 7 cpu19: <ACPI CPU> on acpi0 cpu20: Processor \_SB_.PR14 (ACPI ID 20) -> APIC ID 9 cpu20: <ACPI CPU> on acpi0 cpu21: Processor \_SB_.PR15 (ACPI ID 21) -> APIC ID 11 cpu21: <ACPI CPU> on acpi0 cpu22: Processor \_SB_.PR16 (ACPI ID 22) -> APIC ID 13 cpu22: <ACPI CPU> on acpi0 cpu23: Processor \_SB_.PR17 (ACPI ID 23) -> APIC ID 15 cpu23: <ACPI CPU> on acpi0 cpu24: Processor \_SB_.PR18 (ACPI ID 24) -> APIC ID 17 cpu24: <ACPI CPU> on acpi0 cpu25: Processor \_SB_.PR19 (ACPI ID 25) -> APIC ID 19 cpu25: <ACPI CPU> on acpi0 cpu26: Processor \_SB_.PR1A (ACPI ID 26) -> APIC ID 21 cpu26: <ACPI CPU> on acpi0 cpu27: Processor \_SB_.PR1B (ACPI ID 27) -> APIC ID 23 cpu27: <ACPI CPU> on acpi0 cpu28: Processor \_SB_.PR1C (ACPI ID 28) -> APIC ID 25 cpu28: <ACPI CPU> on acpi0 cpu29: Processor \_SB_.PR1D (ACPI ID 29) -> APIC ID 27 cpu29: <ACPI CPU> on acpi0 cpu30: Processor \_SB_.PR1E (ACPI ID 30) -> APIC ID 29 cpu30: <ACPI CPU> on acpi0 cpu31: Processor \_SB_.PR1F (ACPI ID 31) -> APIC ID 31 cpu31: <ACPI CPU> on acpi0 ACPI: Processor \_SB_.PR20 (ACPI ID 32) ignored ACPI: Processor \_SB_.PR21 (ACPI ID 33) ignored ACPI: Processor \_SB_.PR22 (ACPI ID 34) ignored ACPI: Processor \_SB_.PR23 (ACPI ID 35) ignored ACPI: Processor \_SB_.PR24 (ACPI ID 36) ignored ACPI: Processor \_SB_.PR25 (ACPI ID 37) ignored ACPI: Processor \_SB_.PR26 (ACPI ID 38) ignored ACPI: Processor \_SB_.PR27 (ACPI ID 39) ignored ACPI: Processor \_SB_.PR28 (ACPI ID 40) ignored ACPI: Processor \_SB_.PR29 (ACPI ID 41) ignored ACPI: Processor \_SB_.PR2A (ACPI ID 42) ignored ACPI: Processor \_SB_.PR2B (ACPI ID 43) ignored ACPI: Processor \_SB_.PR2C (ACPI ID 44) ignored ACPI: Processor \_SB_.PR2D (ACPI ID 45) ignored ACPI: Processor \_SB_.PR2E (ACPI ID 46) ignored ACPI: Processor \_SB_.PR2F (ACPI ID 47) ignored ACPI: Processor \_SB_.PR30 (ACPI ID 48) ignored ACPI: Processor \_SB_.PR31 (ACPI ID 49) ignored ACPI: Processor \_SB_.PR32 (ACPI ID 50) ignored ACPI: Processor \_SB_.PR33 (ACPI ID 51) ignored ACPI: Processor \_SB_.PR34 (ACPI ID 52) ignored ACPI: Processor \_SB_.PR35 (ACPI ID 53) ignored ACPI: Processor \_SB_.PR36 (ACPI ID 54) ignored ACPI: Processor \_SB_.PR37 (ACPI ID 55) ignored ACPI: Processor \_SB_.PR38 (ACPI ID 56) ignored ACPI: Processor \_SB_.PR39 (ACPI ID 57) ignored ACPI: Processor \_SB_.PR3A (ACPI ID 58) ignored ACPI: Processor \_SB_.PR3B (ACPI ID 59) ignored ACPI: Processor \_SB_.PR3C (ACPI ID 60) ignored ACPI: Processor \_SB_.PR3D (ACPI ID 61) ignored ACPI: Processor \_SB_.PR3E (ACPI ID 62) ignored ACPI: Processor \_SB_.PR3F (ACPI ID 63) ignored ACPI: Processor \_SB_.PR40 (ACPI ID 64) ignored ACPI: Processor \_SB_.PR41 (ACPI ID 65) ignored ACPI: Processor \_SB_.PR42 (ACPI ID 66) ignored ACPI: Processor \_SB_.PR43 (ACPI ID 67) ignored ACPI: Processor \_SB_.PR44 (ACPI ID 68) ignored ACPI: Processor \_SB_.PR45 (ACPI ID 69) ignored ACPI: Processor \_SB_.PR46 (ACPI ID 70) ignored ACPI: Processor \_SB_.PR47 (ACPI ID 71) ignored ACPI: Processor \_SB_.PR48 (ACPI ID 72) ignored ACPI: Processor \_SB_.PR49 (ACPI ID 73) ignored ACPI: Processor \_SB_.PR4A (ACPI ID 74) ignored ACPI: Processor \_SB_.PR4B (ACPI ID 75) ignored ACPI: Processor \_SB_.PR4C (ACPI ID 76) ignored ACPI: Processor \_SB_.PR4D (ACPI ID 77) ignored ACPI: Processor \_SB_.PR4E (ACPI ID 78) ignored ACPI: Processor \_SB_.PR4F (ACPI ID 79) ignored ACPI: Processor \_SB_.PR50 (ACPI ID 80) ignored ACPI: Processor \_SB_.PR51 (ACPI ID 81) ignored ACPI: Processor \_SB_.PR52 (ACPI ID 82) ignored ACPI: Processor \_SB_.PR53 (ACPI ID 83) ignored ACPI: Processor \_SB_.PR54 (ACPI ID 84) ignored ACPI: Processor \_SB_.PR55 (ACPI ID 85) ignored ACPI: Processor \_SB_.PR56 (ACPI ID 86) ignored ACPI: Processor \_SB_.PR57 (ACPI ID 87) ignored ACPI: Processor \_SB_.PR58 (ACPI ID 88) ignored ACPI: Processor \_SB_.PR59 (ACPI ID 89) ignored ACPI: Processor \_SB_.PR5A (ACPI ID 90) ignored ACPI: Processor \_SB_.PR5B (ACPI ID 91) ignored ACPI: Processor \_SB_.PR5C (ACPI ID 92) ignored ACPI: Processor \_SB_.PR5D (ACPI ID 93) ignored ACPI: Processor \_SB_.PR5E (ACPI ID 94) ignored ACPI: Processor \_SB_.PR5F (ACPI ID 95) ignored ACPI: Processor \_SB_.PR60 (ACPI ID 96) ignored ACPI: Processor \_SB_.PR61 (ACPI ID 97) ignored ACPI: Processor \_SB_.PR62 (ACPI ID 98) ignored ACPI: Processor \_SB_.PR63 (ACPI ID 99) ignored ACPI: Processor \_SB_.PR64 (ACPI ID 100) ignored ACPI: Processor \_SB_.PR65 (ACPI ID 101) ignored ACPI: Processor \_SB_.PR66 (ACPI ID 102) ignored ACPI: Processor \_SB_.PR67 (ACPI ID 103) ignored ACPI: Processor \_SB_.PR68 (ACPI ID 104) ignored ACPI: Processor \_SB_.PR69 (ACPI ID 105) ignored ACPI: Processor \_SB_.PR6A (ACPI ID 106) ignored ACPI: Processor \_SB_.PR6B (ACPI ID 107) ignored ACPI: Processor \_SB_.PR6C (ACPI ID 108) ignored ACPI: Processor \_SB_.PR6D (ACPI ID 109) ignored ACPI: Processor \_SB_.PR6E (ACPI ID 110) ignored ACPI: Processor \_SB_.PR6F (ACPI ID 111) ignored ACPI: Processor \_SB_.PR70 (ACPI ID 112) ignored ACPI: Processor \_SB_.PR71 (ACPI ID 113) ignored ACPI: Processor \_SB_.PR72 (ACPI ID 114) ignored ACPI: Processor \_SB_.PR73 (ACPI ID 115) ignored ACPI: Processor \_SB_.PR74 (ACPI ID 116) ignored ACPI: Processor \_SB_.PR75 (ACPI ID 117) ignored ACPI: Processor \_SB_.PR76 (ACPI ID 118) ignored ACPI: Processor \_SB_.PR77 (ACPI ID 119) ignored ACPI: Processor \_SB_.PR78 (ACPI ID 120) ignored ACPI: Processor \_SB_.PR79 (ACPI ID 121) ignored ACPI: Processor \_SB_.PR7A (ACPI ID 122) ignored ACPI: Processor \_SB_.PR7B (ACPI ID 123) ignored ACPI: Processor \_SB_.PR7C (ACPI ID 124) ignored ACPI: Processor \_SB_.PR7D (ACPI ID 125) ignored ACPI: Processor \_SB_.PR7E (ACPI ID 126) ignored ACPI: Processor \_SB_.PR7F (ACPI ID 127) ignored hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 atrtc0: not installed as time-of-day clock: clock xen_et has higher resolution ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50 Event timer "RTC" frequency 32768 Hz quality 0 ACPI timer: 1/18 1/17 1/21 1/18 1/18 1/16 1/20 1/22 1/21 1/22 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 10 11 Validation 0 10 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 10 11 Validation 0 11 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xf0000000-0xfbffffff pci0: <ACPI PCI bus> on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x1237, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7000, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7010, revid=0x00 domain=0, bus=0, slot=1, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1 found-> vendor=0x8086, dev=0x7113, revid=0x01 domain=0, bus=0, slot=1, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 20 found-> vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, enabled pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0 map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0 found-> vendor=0x5853, dev=0x0001, revid=0x01 domain=0, bus=0, slot=3, func=0 class=ff-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, enabled pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0 pcib0: matched entry for 0.3.INTA pcib0: slot 3 INTA hardwired to IRQ 28 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51 ata1: <ATA channel> at channel 1 on atapci0 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53 xenstore0: <XenStore> on xenpci0 Grant table initialized psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0061 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54 atkbd0: [GIANT-LOCKED] psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 00 02 64 psm0: <PS/2 Mouse> irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56 uart0: fast interrupt uart0: console (9600,n,8,1) ACPI: Enabled 2 GPEs in block 00 to 0F acpi0: wakeup code va 0xffffffc2cdff7000 pa 0x4000 ex_isa_identify() pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 ahc_isa_identify 0: ioport 0xc00 alloc failed ahc_isa_identify 1: ioport 0x1c00 alloc failed ahc_isa_identify 2: ioport 0x2c00 alloc failed ahc_isa_identify 3: ioport 0x3c00 alloc failed ahc_isa_identify 4: ioport 0x4c00 alloc failed ahc_isa_identify 5: ioport 0x5c00 alloc failed ahc_isa_identify 6: ioport 0x6c00 alloc failed ahc_isa_identify 7: ioport 0x7c00 alloc failed ahc_isa_identify 8: ioport 0x8c00 alloc failed ahc_isa_identify 9: ioport 0x9c00 alloc failed ahc_isa_identify 10: ioport 0xac00 alloc failed ahc_isa_identify 11: ioport 0xbc00 alloc failed ahc_isa_identify 12: ioport 0xcc00 alloc failed ahc_isa_identify 13: ioport 0xdc00 alloc failed ahc_isa_identify 14: ioport 0xec00 alloc failed isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it uart: uart0 already exists; skipping it isa_probe_children: probing non-PnP devices sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 fdc0: No FDOUT register! fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2097152 lo0: bpf attached hptrr: no controller detected. hpt27xx: no controller detected. xenbusb_front0: <Xen Frontend Devices> on xenstore0 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x0 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x0 xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 22:00:0a:94:b4:ba xenbusb_back0: <Xen Backend Devices> on xenstore0 xctrl0: <Xen Control Device> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: barriers GEOM: new disk ad0 xbd1: 122866MB <Virtual Block Device> at device/vbd/51728 on xenbusb_front0 xbd1: disk supports cache flush using: flush xbd2: 122866MB <Virtual Block Device> at device/vbd/51744 on xenbusb_front0 xbd2: disk supports cache flush using: flush SMP: AP CPU #29 Launched! cpu29 AP: ID: 0x2d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #24 Launched! cpu24 AP: ID: 0x28000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #21 Launched! cpu21 AP: ID: 0x25000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #6 Launched! cpu6 AP: ID: 0x06000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #7 Launched! cpu7 AP: ID: 0x07000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #23 Launched! cpu23 AP: ID: 0x27000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #18 Launched! cpu18 AP: ID: 0x22000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #25 Launched! cpu25 AP: ID: 0x29000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #16 Launched! cpu16 AP: ID: 0x20000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #28 Launched! cpu28 AP: ID: 0x2c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #10 Launched! cpu10 AP: ID: 0x0a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #27 Launched! cpu27 AP: ID: 0x2b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #12 Launched! cpu12 AP: ID: 0x0c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #30 Launched! cpu30 AP: ID: 0x2e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #31 Launched! cpu31 AP: ID: 0x2f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #19 Launched! cpu19 AP: ID: 0x23000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #15 Launched! cpu15 AP: ID: 0x0f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #17 Launched! cpu17 AP: ID: 0x21000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #14 Launched! cpu14 AP: ID: 0x0e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #20 Launched! cpu20 AP: ID: 0x24000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #22 Launched! cpu22 AP: ID: 0x26000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #4 Launched! cpu4 AP: ID: 0x04000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #8 Launched! cpu8 AP: ID: 0x08000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #13 Launched! cpu13 AP: ID: 0x0d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #11 Launched! cpu11 AP: ID: 0x0b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #5 Launched! cpu5 AP: ID: 0x05000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #26 Launched! cpu26 AP: ID: 0x2a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #9 Launched! cpu9 AP: ID: 0x09000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 panic: xen_et0: Error -22 setting singleshot timer to 766317887512893 cpuid = 8 KDB: enter: panic [ thread pid 11 tid 100011 ] Stopped at kdb_enter+0x3e: movq $0,kdb_why db> -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 05/22/13 04:45, Roger Pau Monné wrote:> On 18/05/13 17:44, Colin Percival wrote: >> That seems to work. dmesg is attached. Are there any particular tests >> you''d like me to run? > > I have not tested ZFS, that might be a good one. If you are running this > on Xen 3.4 the behaviour should be the same as without this patches, so > there shouldn''t be many differences.I don''t use ZFS personally, so I''m not sure exactly what tests to run on it; hopefully someone else can take care of that.> If you could try that on Xen 4.0 at least (if I remember correctly > that''s when the vector callback was introduced), you should see the PV > timer getting attached, and a performance increase.Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with a panic -- console output below. I can get a backtrace and possibly even a dump if those would help. Booting [/boot/kernel/kernel]... -\|/-\|GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=000000000009e000 SMAP type=02 base=000000000009e000 len=0000000000002000 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=00000000eff00000 SMAP type=02 base=00000000fc000000 len=0000000004000000 SMAP type=01 base=0000000100000000 len=0000003c19000000 Table ''FACP'' at 0xfc014980 Table ''APIC'' at 0xfc014a80 APIC: Found table at 0xfc014a80 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: enabled SMP: Added CPU 14 (AP) MADT: Found CPU APIC ID 32 ACPI ID 8: enabled SMP: Added CPU 32 (AP) MADT: Found CPU APIC ID 34 ACPI ID 9: enabled SMP: Added CPU 34 (AP) MADT: Found CPU APIC ID 36 ACPI ID 10: enabled SMP: Added CPU 36 (AP) MADT: Found CPU APIC ID 38 ACPI ID 11: enabled SMP: Added CPU 38 (AP) MADT: Found CPU APIC ID 40 ACPI ID 12: enabled SMP: Added CPU 40 (AP) MADT: Found CPU APIC ID 42 ACPI ID 13: enabled SMP: Added CPU 42 (AP) MADT: Found CPU APIC ID 44 ACPI ID 14: enabled SMP: Added CPU 44 (AP) MADT: Found CPU APIC ID 46 ACPI ID 15: enabled SMP: Added CPU 46 (AP) MADT: Found CPU APIC ID 1 ACPI ID 16: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 3 ACPI ID 17: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 5 ACPI ID 18: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 7 ACPI ID 19: enabled SMP: Added CPU 7 (AP) MADT: Found CPU APIC ID 9 ACPI ID 20: enabled SMP: Added CPU 9 (AP) MADT: Found CPU APIC ID 11 ACPI ID 21: enabled SMP: Added CPU 11 (AP) MADT: Found CPU APIC ID 13 ACPI ID 22: enabled SMP: Added CPU 13 (AP) MADT: Found CPU APIC ID 15 ACPI ID 23: enabled SMP: Added CPU 15 (AP) MADT: Found CPU APIC ID 33 ACPI ID 24: enabled SMP: Added CPU 33 (AP) MADT: Found CPU APIC ID 35 ACPI ID 25: enabled SMP: Added CPU 35 (AP) MADT: Found CPU APIC ID 37 ACPI ID 26: enabled SMP: Added CPU 37 (AP) MADT: Found CPU APIC ID 39 ACPI ID 27: enabled SMP: Added CPU 39 (AP) MADT: Found CPU APIC ID 41 ACPI ID 28: enabled SMP: Added CPU 41 (AP) MADT: Found CPU APIC ID 43 ACPI ID 29: enabled SMP: Added CPU 43 (AP) MADT: Found CPU APIC ID 45 ACPI ID 30: enabled SMP: Added CPU 45 (AP) MADT: Found CPU APIC ID 47 ACPI ID 31: enabled SMP: Added CPU 47 (AP) MADT: Found CPU APIC ID 0 ACPI ID 32: disabled MADT: Found CPU APIC ID 0 ACPI ID 33: disabled MADT: Found CPU APIC ID 0 ACPI ID 34: disabled MADT: Found CPU APIC ID 0 ACPI ID 35: disabled MADT: Found CPU APIC ID 0 ACPI ID 36: disabled MADT: Found CPU APIC ID 0 ACPI ID 37: disabled MADT: Found CPU APIC ID 0 ACPI ID 38: disabled MADT: Found CPU APIC ID 0 ACPI ID 39: disabled MADT: Found CPU APIC ID 0 ACPI ID 40: disabled MADT: Found CPU APIC ID 0 ACPI ID 41: disabled MADT: Found CPU APIC ID 0 ACPI ID 42: disabled MADT: Found CPU APIC ID 0 ACPI ID 43: disabled MADT: Found CPU APIC ID 0 ACPI ID 44: disabled MADT: Found CPU APIC ID 0 ACPI ID 45: disabled MADT: Found CPU APIC ID 0 ACPI ID 46: disabled MADT: Found CPU APIC ID 0 ACPI ID 47: disabled MADT: Found CPU APIC ID 0 ACPI ID 48: disabled MADT: Found CPU APIC ID 0 ACPI ID 49: disabled MADT: Found CPU APIC ID 0 ACPI ID 50: disabled MADT: Found CPU APIC ID 0 ACPI ID 51: disabled MADT: Found CPU APIC ID 0 ACPI ID 52: disabled MADT: Found CPU APIC ID 0 ACPI ID 53: disabled MADT: Found CPU APIC ID 0 ACPI ID 54: disabled MADT: Found CPU APIC ID 0 ACPI ID 55: disabled MADT: Found CPU APIC ID 0 ACPI ID 56: disabled MADT: Found CPU APIC ID 0 ACPI ID 57: disabled MADT: Found CPU APIC ID 0 ACPI ID 58: disabled MADT: Found CPU APIC ID 0 ACPI ID 59: disabled MADT: Found CPU APIC ID 0 ACPI ID 60: disabled MADT: Found CPU APIC ID 0 ACPI ID 61: disabled MADT: Found CPU APIC ID 0 ACPI ID 62: disabled MADT: Found CPU APIC ID 0 ACPI ID 63: disabled MADT: Found CPU APIC ID 0 ACPI ID 64: disabled MADT: Found CPU APIC ID 0 ACPI ID 65: disabled MADT: Found CPU APIC ID 0 ACPI ID 66: disabled MADT: Found CPU APIC ID 0 ACPI ID 67: disabled MADT: Found CPU APIC ID 0 ACPI ID 68: disabled MADT: Found CPU APIC ID 0 ACPI ID 69: disabled MADT: Found CPU APIC ID 0 ACPI ID 70: disabled MADT: Found CPU APIC ID 0 ACPI ID 71: disabled MADT: Found CPU APIC ID 0 ACPI ID 72: disabled MADT: Found CPU APIC ID 0 ACPI ID 73: disabled MADT: Found CPU APIC ID 0 ACPI ID 74: disabled MADT: Found CPU APIC ID 0 ACPI ID 75: disabled MADT: Found CPU APIC ID 0 ACPI ID 76: disabled MADT: Found CPU APIC ID 0 ACPI ID 77: disabled MADT: Found CPU APIC ID 0 ACPI ID 78: disabled MADT: Found CPU APIC ID 0 ACPI ID 79: disabled MADT: Found CPU APIC ID 0 ACPI ID 80: disabled MADT: Found CPU APIC ID 0 ACPI ID 81: disabled MADT: Found CPU APIC ID 0 ACPI ID 82: disabled MADT: Found CPU APIC ID 0 ACPI ID 83: disabled MADT: Found CPU APIC ID 0 ACPI ID 84: disabled MADT: Found CPU APIC ID 0 ACPI ID 85: disabled MADT: Found CPU APIC ID 0 ACPI ID 86: disabled MADT: Found CPU APIC ID 0 ACPI ID 87: disabled MADT: Found CPU APIC ID 0 ACPI ID 88: disabled MADT: Found CPU APIC ID 0 ACPI ID 89: disabled MADT: Found CPU APIC ID 0 ACPI ID 90: disabled MADT: Found CPU APIC ID 0 ACPI ID 91: disabled MADT: Found CPU APIC ID 0 ACPI ID 92: disabled MADT: Found CPU APIC ID 0 ACPI ID 93: disabled MADT: Found CPU APIC ID 0 ACPI ID 94: disabled MADT: Found CPU APIC ID 0 ACPI ID 95: disabled MADT: Found CPU APIC ID 0 ACPI ID 96: disabled MADT: Found CPU APIC ID 0 ACPI ID 97: disabled MADT: Found CPU APIC ID 0 ACPI ID 98: disabled MADT: Found CPU APIC ID 0 ACPI ID 99: disabled MADT: Found CPU APIC ID 0 ACPI ID 100: disabled MADT: Found CPU APIC ID 0 ACPI ID 101: disabled MADT: Found CPU APIC ID 0 ACPI ID 102: disabled MADT: Found CPU APIC ID 0 ACPI ID 103: disabled MADT: Found CPU APIC ID 0 ACPI ID 104: disabled MADT: Found CPU APIC ID 0 ACPI ID 105: disabled MADT: Found CPU APIC ID 0 ACPI ID 106: disabled MADT: Found CPU APIC ID 0 ACPI ID 107: disabled MADT: Found CPU APIC ID 0 ACPI ID 108: disabled MADT: Found CPU APIC ID 0 ACPI ID 109: disabled MADT: Found CPU APIC ID 0 ACPI ID 110: disabled MADT: Found CPU APIC ID 0 ACPI ID 111: disabled MADT: Found CPU APIC ID 0 ACPI ID 112: disabled MADT: Found CPU APIC ID 0 ACPI ID 113: disabled MADT: Found CPU APIC ID 0 ACPI ID 114: disabled MADT: Found CPU APIC ID 0 ACPI ID 115: disabled MADT: Found CPU APIC ID 0 ACPI ID 116: disabled MADT: Found CPU APIC ID 0 ACPI ID 117: disabled MADT: Found CPU APIC ID 0 ACPI ID 118: disabled MADT: Found CPU APIC ID 0 ACPI ID 119: disabled MADT: Found CPU APIC ID 0 ACPI ID 120: disabled MADT: Found CPU APIC ID 0 ACPI ID 121: disabled MADT: Found CPU APIC ID 0 ACPI ID 122: disabled MADT: Found CPU APIC ID 0 ACPI ID 123: disabled MADT: Found CPU APIC ID 0 ACPI ID 124: disabled MADT: Found CPU APIC ID 0 ACPI ID 125: disabled MADT: Found CPU APIC ID 0 ACPI ID 126: disabled MADT: Found CPU APIC ID 0 ACPI ID 127: disabled Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r+9b25356: Sat May 18 14:46:16 UTC 2013 root@ip-10-140-132-115:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. XEN: Disabling emulated block and network devices Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81912000. Hypervisor: Origin = "XenVMMXenVMM" Calibrating TSC clock ... TSC clock: 2600048761 Hz CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.05-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0x9fba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> real memory = 262144000000 (250000 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x0000000001a2a000 - 0x00000000efffffff, 3999096832 bytes (976342 pages) 0x0000000100000000 - 0x0000003b8ae37fff, 251438268416 bytes (61386296 pages) avail memory = 244393709568 (233072 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target INTR: Adding local APIC 8 as a target INTR: Adding local APIC 9 as a target INTR: Adding local APIC 10 as a target INTR: Adding local APIC 11 as a target INTR: Adding local APIC 12 as a target INTR: Adding local APIC 13 as a target INTR: Adding local APIC 14 as a target INTR: Adding local APIC 15 as a target INTR: Adding local APIC 32 as a target INTR: Adding local APIC 33 as a target INTR: Adding local APIC 34 as a target INTR: Adding local APIC 35 as a target INTR: Adding local APIC 36 as a target INTR: Adding local APIC 37 as a target INTR: Adding local APIC 38 as a target INTR: Adding local APIC 39 as a target INTR: Adding local APIC 40 as a target INTR: Adding local APIC 41 as a target INTR: Adding local APIC 42 as a target INTR: Adding local APIC 43 as a target INTR: Adding local APIC 44 as a target INTR: Adding local APIC 45 as a target INTR: Adding local APIC 46 as a target INTR: Adding local APIC 47 as a target FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 12 cpu13 (AP): APIC ID: 13 cpu14 (AP): APIC ID: 14 cpu15 (AP): APIC ID: 15 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 33 cpu18 (AP): APIC ID: 34 cpu19 (AP): APIC ID: 35 cpu20 (AP): APIC ID: 36 cpu21 (AP): APIC ID: 37 cpu22 (AP): APIC ID: 38 cpu23 (AP): APIC ID: 39 cpu24 (AP): APIC ID: 40 cpu25 (AP): APIC ID: 41 cpu26 (AP): APIC ID: 42 cpu27 (AP): APIC ID: 43 cpu28 (AP): APIC ID: 44 cpu29 (AP): APIC ID: 45 cpu30 (AP): APIC ID: 46 cpu31 (AP): APIC ID: 47 x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 x86bios: SSEG 0x001000-0x001fff at 0xffffff80005e3000 x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 16 APIC: CPU 2 has ACPI ID 1 APIC: CPU 3 has ACPI ID 17 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 18 APIC: CPU 6 has ACPI ID 3 APIC: CPU 7 has ACPI ID 19 APIC: CPU 8 has ACPI ID 4 APIC: CPU 9 has ACPI ID 20 APIC: CPU 10 has ACPI ID 5 APIC: CPU 11 has ACPI ID 21 APIC: CPU 12 has ACPI ID 6 APIC: CPU 13 has ACPI ID 22 APIC: CPU 14 has ACPI ID 7 APIC: CPU 15 has ACPI ID 23 APIC: CPU 16 has ACPI ID 8 APIC: CPU 17 has ACPI ID 24 APIC: CPU 18 has ACPI ID 9 APIC: CPU 19 has ACPI ID 25 APIC: CPU 20 has ACPI ID 10 APIC: CPU 21 has ACPI ID 26 APIC: CPU 22 has ACPI ID 11 APIC: CPU 23 has ACPI ID 27 APIC: CPU 24 has ACPI ID 12 APIC: CPU 25 has ACPI ID 28 APIC: CPU 26 has ACPI ID 13 APIC: CPU 27 has ACPI ID 29 APIC: CPU 28 has ACPI ID 14 APIC: CPU 29 has ACPI ID 30 APIC: CPU 30 has ACPI ID 15 APIC: CPU 31 has ACPI ID 31 random device not loaded; using insecure entropy ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ULE: setup cpu 8 ULE: setup cpu 9 ULE: setup cpu 10 ULE: setup cpu 11 ULE: setup cpu 12 ULE: setup cpu 13 ULE: setup cpu 14 ULE: setup cpu 15 ULE: setup cpu 16 ULE: setup cpu 17 ULE: setup cpu 18 ULE: setup cpu 19 ULE: setup cpu 20 ULE: setup cpu 21 ULE: setup cpu 22 ULE: setup cpu 23 ULE: setup cpu 24 ULE: setup cpu 25 ULE: setup cpu 26 ULE: setup cpu 27 ULE: setup cpu 28 ULE: setup cpu 29 ULE: setup cpu 30 ULE: setup cpu 31 ACPI: RSDP 0xea020 00024 (v02 Xen) ACPI: XSDT 0xfc015920 0005C (v01 Xen HVM 00000000 HVML 00000000) ACPI: FACP 0xfc014980 000F4 (v04 Xen HVM 00000000 HVML 00000000) ACPI: DSDT 0xfc0035e0 11315 (v02 Xen HVM 00000000 INTL 20090123) ACPI: FACS 0xfc0035a0 00040 ACPI: APIC 0xfc014a80 00460 (v02 Xen HVM 00000000 HVML 00000000) ACPI: SRAT 0xfc014f60 008A8 (v01 Xen HVM 00000000 HVML 00000000) ACPI: HPET 0xfc015830 00038 (v01 Xen HVM 00000000 HVML 00000000) ACPI: WAET 0xfc015870 00028 (v01 Xen HVM 00000000 HVML 00000000) ACPI: SSDT 0xfc0158a0 00031 (v02 Xen HVM 00000000 INTL 20090123) ACPI: SSDT 0xfc0158e0 00031 (v02 Xen HVM 00000000 INTL 20090123) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A''s -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 5, irq 5 ioapic0: intpin 5 trigger: level ioapic0: intpin 5 polarity: low MADT: Interrupt override: source 10, irq 10 ioapic0: intpin 10 trigger: level ioapic0: intpin 10 polarity: low MADT: Interrupt override: source 11, irq 11 ioapic0: intpin 11 trigger: level ioapic0: intpin 11 polarity: low MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 <Version 1.1> irqs 0-47 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Event-channel device installed. snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 wlan: <802.11 Link Layer> null: <null device, zero device> nfslock: pseudo-device random: <entropy source, Software, Yarrow> VESA: INT 0x10 vector 0xc000:0x836e VESA: information block 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 15 mode(s) found VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80005fd040 (2000040) VESA: VGABIOS Cirrus extension VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0 io: <I/O> kbd: new array size 4 kbd1 at kbdmux0 mem: <memory> hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 hpt27xx: RocketRAID 27xx controller driver v1.0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 xen_et0: registered as a time-of-day clock (resolution 10000000us, adjustment 5.000000000s) acpi0: <Xen> on motherboard ACPI: All ACPI Tables successfully acquired ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: Processor \_SB_.PR00 (ACPI ID 0) -> APIC ID 0 cpu0: <ACPI CPU> on acpi0 cpu0: switching to generic Cx mode cpu1: Processor \_SB_.PR01 (ACPI ID 1) -> APIC ID 2 cpu1: <ACPI CPU> on acpi0 cpu2: Processor \_SB_.PR02 (ACPI ID 2) -> APIC ID 4 cpu2: <ACPI CPU> on acpi0 cpu3: Processor \_SB_.PR03 (ACPI ID 3) -> APIC ID 6 cpu3: <ACPI CPU> on acpi0 cpu4: Processor \_SB_.PR04 (ACPI ID 4) -> APIC ID 8 cpu4: <ACPI CPU> on acpi0 cpu5: Processor \_SB_.PR05 (ACPI ID 5) -> APIC ID 10 cpu5: <ACPI CPU> on acpi0 cpu6: Processor \_SB_.PR06 (ACPI ID 6) -> APIC ID 12 cpu6: <ACPI CPU> on acpi0 cpu7: Processor \_SB_.PR07 (ACPI ID 7) -> APIC ID 14 cpu7: <ACPI CPU> on acpi0 cpu8: Processor \_SB_.PR08 (ACPI ID 8) -> APIC ID 16 cpu8: <ACPI CPU> on acpi0 cpu9: Processor \_SB_.PR09 (ACPI ID 9) -> APIC ID 18 cpu9: <ACPI CPU> on acpi0 cpu10: Processor \_SB_.PR0A (ACPI ID 10) -> APIC ID 20 cpu10: <ACPI CPU> on acpi0 cpu11: Processor \_SB_.PR0B (ACPI ID 11) -> APIC ID 22 cpu11: <ACPI CPU> on acpi0 cpu12: Processor \_SB_.PR0C (ACPI ID 12) -> APIC ID 24 cpu12: <ACPI CPU> on acpi0 cpu13: Processor \_SB_.PR0D (ACPI ID 13) -> APIC ID 26 cpu13: <ACPI CPU> on acpi0 cpu14: Processor \_SB_.PR0E (ACPI ID 14) -> APIC ID 28 cpu14: <ACPI CPU> on acpi0 cpu15: Processor \_SB_.PR0F (ACPI ID 15) -> APIC ID 30 cpu15: <ACPI CPU> on acpi0 cpu16: Processor \_SB_.PR10 (ACPI ID 16) -> APIC ID 1 cpu16: <ACPI CPU> on acpi0 cpu17: Processor \_SB_.PR11 (ACPI ID 17) -> APIC ID 3 cpu17: <ACPI CPU> on acpi0 cpu18: Processor \_SB_.PR12 (ACPI ID 18) -> APIC ID 5 cpu18: <ACPI CPU> on acpi0 cpu19: Processor \_SB_.PR13 (ACPI ID 19) -> APIC ID 7 cpu19: <ACPI CPU> on acpi0 cpu20: Processor \_SB_.PR14 (ACPI ID 20) -> APIC ID 9 cpu20: <ACPI CPU> on acpi0 cpu21: Processor \_SB_.PR15 (ACPI ID 21) -> APIC ID 11 cpu21: <ACPI CPU> on acpi0 cpu22: Processor \_SB_.PR16 (ACPI ID 22) -> APIC ID 13 cpu22: <ACPI CPU> on acpi0 cpu23: Processor \_SB_.PR17 (ACPI ID 23) -> APIC ID 15 cpu23: <ACPI CPU> on acpi0 cpu24: Processor \_SB_.PR18 (ACPI ID 24) -> APIC ID 17 cpu24: <ACPI CPU> on acpi0 cpu25: Processor \_SB_.PR19 (ACPI ID 25) -> APIC ID 19 cpu25: <ACPI CPU> on acpi0 cpu26: Processor \_SB_.PR1A (ACPI ID 26) -> APIC ID 21 cpu26: <ACPI CPU> on acpi0 cpu27: Processor \_SB_.PR1B (ACPI ID 27) -> APIC ID 23 cpu27: <ACPI CPU> on acpi0 cpu28: Processor \_SB_.PR1C (ACPI ID 28) -> APIC ID 25 cpu28: <ACPI CPU> on acpi0 cpu29: Processor \_SB_.PR1D (ACPI ID 29) -> APIC ID 27 cpu29: <ACPI CPU> on acpi0 cpu30: Processor \_SB_.PR1E (ACPI ID 30) -> APIC ID 29 cpu30: <ACPI CPU> on acpi0 cpu31: Processor \_SB_.PR1F (ACPI ID 31) -> APIC ID 31 cpu31: <ACPI CPU> on acpi0 ACPI: Processor \_SB_.PR20 (ACPI ID 32) ignored ACPI: Processor \_SB_.PR21 (ACPI ID 33) ignored ACPI: Processor \_SB_.PR22 (ACPI ID 34) ignored ACPI: Processor \_SB_.PR23 (ACPI ID 35) ignored ACPI: Processor \_SB_.PR24 (ACPI ID 36) ignored ACPI: Processor \_SB_.PR25 (ACPI ID 37) ignored ACPI: Processor \_SB_.PR26 (ACPI ID 38) ignored ACPI: Processor \_SB_.PR27 (ACPI ID 39) ignored ACPI: Processor \_SB_.PR28 (ACPI ID 40) ignored ACPI: Processor \_SB_.PR29 (ACPI ID 41) ignored ACPI: Processor \_SB_.PR2A (ACPI ID 42) ignored ACPI: Processor \_SB_.PR2B (ACPI ID 43) ignored ACPI: Processor \_SB_.PR2C (ACPI ID 44) ignored ACPI: Processor \_SB_.PR2D (ACPI ID 45) ignored ACPI: Processor \_SB_.PR2E (ACPI ID 46) ignored ACPI: Processor \_SB_.PR2F (ACPI ID 47) ignored ACPI: Processor \_SB_.PR30 (ACPI ID 48) ignored ACPI: Processor \_SB_.PR31 (ACPI ID 49) ignored ACPI: Processor \_SB_.PR32 (ACPI ID 50) ignored ACPI: Processor \_SB_.PR33 (ACPI ID 51) ignored ACPI: Processor \_SB_.PR34 (ACPI ID 52) ignored ACPI: Processor \_SB_.PR35 (ACPI ID 53) ignored ACPI: Processor \_SB_.PR36 (ACPI ID 54) ignored ACPI: Processor \_SB_.PR37 (ACPI ID 55) ignored ACPI: Processor \_SB_.PR38 (ACPI ID 56) ignored ACPI: Processor \_SB_.PR39 (ACPI ID 57) ignored ACPI: Processor \_SB_.PR3A (ACPI ID 58) ignored ACPI: Processor \_SB_.PR3B (ACPI ID 59) ignored ACPI: Processor \_SB_.PR3C (ACPI ID 60) ignored ACPI: Processor \_SB_.PR3D (ACPI ID 61) ignored ACPI: Processor \_SB_.PR3E (ACPI ID 62) ignored ACPI: Processor \_SB_.PR3F (ACPI ID 63) ignored ACPI: Processor \_SB_.PR40 (ACPI ID 64) ignored ACPI: Processor \_SB_.PR41 (ACPI ID 65) ignored ACPI: Processor \_SB_.PR42 (ACPI ID 66) ignored ACPI: Processor \_SB_.PR43 (ACPI ID 67) ignored ACPI: Processor \_SB_.PR44 (ACPI ID 68) ignored ACPI: Processor \_SB_.PR45 (ACPI ID 69) ignored ACPI: Processor \_SB_.PR46 (ACPI ID 70) ignored ACPI: Processor \_SB_.PR47 (ACPI ID 71) ignored ACPI: Processor \_SB_.PR48 (ACPI ID 72) ignored ACPI: Processor \_SB_.PR49 (ACPI ID 73) ignored ACPI: Processor \_SB_.PR4A (ACPI ID 74) ignored ACPI: Processor \_SB_.PR4B (ACPI ID 75) ignored ACPI: Processor \_SB_.PR4C (ACPI ID 76) ignored ACPI: Processor \_SB_.PR4D (ACPI ID 77) ignored ACPI: Processor \_SB_.PR4E (ACPI ID 78) ignored ACPI: Processor \_SB_.PR4F (ACPI ID 79) ignored ACPI: Processor \_SB_.PR50 (ACPI ID 80) ignored ACPI: Processor \_SB_.PR51 (ACPI ID 81) ignored ACPI: Processor \_SB_.PR52 (ACPI ID 82) ignored ACPI: Processor \_SB_.PR53 (ACPI ID 83) ignored ACPI: Processor \_SB_.PR54 (ACPI ID 84) ignored ACPI: Processor \_SB_.PR55 (ACPI ID 85) ignored ACPI: Processor \_SB_.PR56 (ACPI ID 86) ignored ACPI: Processor \_SB_.PR57 (ACPI ID 87) ignored ACPI: Processor \_SB_.PR58 (ACPI ID 88) ignored ACPI: Processor \_SB_.PR59 (ACPI ID 89) ignored ACPI: Processor \_SB_.PR5A (ACPI ID 90) ignored ACPI: Processor \_SB_.PR5B (ACPI ID 91) ignored ACPI: Processor \_SB_.PR5C (ACPI ID 92) ignored ACPI: Processor \_SB_.PR5D (ACPI ID 93) ignored ACPI: Processor \_SB_.PR5E (ACPI ID 94) ignored ACPI: Processor \_SB_.PR5F (ACPI ID 95) ignored ACPI: Processor \_SB_.PR60 (ACPI ID 96) ignored ACPI: Processor \_SB_.PR61 (ACPI ID 97) ignored ACPI: Processor \_SB_.PR62 (ACPI ID 98) ignored ACPI: Processor \_SB_.PR63 (ACPI ID 99) ignored ACPI: Processor \_SB_.PR64 (ACPI ID 100) ignored ACPI: Processor \_SB_.PR65 (ACPI ID 101) ignored ACPI: Processor \_SB_.PR66 (ACPI ID 102) ignored ACPI: Processor \_SB_.PR67 (ACPI ID 103) ignored ACPI: Processor \_SB_.PR68 (ACPI ID 104) ignored ACPI: Processor \_SB_.PR69 (ACPI ID 105) ignored ACPI: Processor \_SB_.PR6A (ACPI ID 106) ignored ACPI: Processor \_SB_.PR6B (ACPI ID 107) ignored ACPI: Processor \_SB_.PR6C (ACPI ID 108) ignored ACPI: Processor \_SB_.PR6D (ACPI ID 109) ignored ACPI: Processor \_SB_.PR6E (ACPI ID 110) ignored ACPI: Processor \_SB_.PR6F (ACPI ID 111) ignored ACPI: Processor \_SB_.PR70 (ACPI ID 112) ignored ACPI: Processor \_SB_.PR71 (ACPI ID 113) ignored ACPI: Processor \_SB_.PR72 (ACPI ID 114) ignored ACPI: Processor \_SB_.PR73 (ACPI ID 115) ignored ACPI: Processor \_SB_.PR74 (ACPI ID 116) ignored ACPI: Processor \_SB_.PR75 (ACPI ID 117) ignored ACPI: Processor \_SB_.PR76 (ACPI ID 118) ignored ACPI: Processor \_SB_.PR77 (ACPI ID 119) ignored ACPI: Processor \_SB_.PR78 (ACPI ID 120) ignored ACPI: Processor \_SB_.PR79 (ACPI ID 121) ignored ACPI: Processor \_SB_.PR7A (ACPI ID 122) ignored ACPI: Processor \_SB_.PR7B (ACPI ID 123) ignored ACPI: Processor \_SB_.PR7C (ACPI ID 124) ignored ACPI: Processor \_SB_.PR7D (ACPI ID 125) ignored ACPI: Processor \_SB_.PR7E (ACPI ID 126) ignored ACPI: Processor \_SB_.PR7F (ACPI ID 127) ignored hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 atrtc0: not installed as time-of-day clock: clock xen_et has higher resolution ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50 Event timer "RTC" frequency 32768 Hz quality 0 ACPI timer: 1/18 1/17 1/21 1/18 1/18 1/16 1/20 1/22 1/21 1/22 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 10 11 Validation 0 10 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 10 11 Validation 0 11 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xf0000000-0xfbffffff pci0: <ACPI PCI bus> on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x1237, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7000, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7010, revid=0x00 domain=0, bus=0, slot=1, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1 found-> vendor=0x8086, dev=0x7113, revid=0x01 domain=0, bus=0, slot=1, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 20 found-> vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, enabled pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0 map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0 found-> vendor=0x5853, dev=0x0001, revid=0x01 domain=0, bus=0, slot=3, func=0 class=ff-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, enabled pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0 pcib0: matched entry for 0.3.INTA pcib0: slot 3 INTA hardwired to IRQ 28 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51 ata1: <ATA channel> at channel 1 on atapci0 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53 xenstore0: <XenStore> on xenpci0 Grant table initialized psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0061 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54 atkbd0: [GIANT-LOCKED] psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 00 02 64 psm0: <PS/2 Mouse> irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56 uart0: fast interrupt uart0: console (9600,n,8,1) ACPI: Enabled 2 GPEs in block 00 to 0F acpi0: wakeup code va 0xffffffc2cdff7000 pa 0x4000 ex_isa_identify() pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 ahc_isa_identify 0: ioport 0xc00 alloc failed ahc_isa_identify 1: ioport 0x1c00 alloc failed ahc_isa_identify 2: ioport 0x2c00 alloc failed ahc_isa_identify 3: ioport 0x3c00 alloc failed ahc_isa_identify 4: ioport 0x4c00 alloc failed ahc_isa_identify 5: ioport 0x5c00 alloc failed ahc_isa_identify 6: ioport 0x6c00 alloc failed ahc_isa_identify 7: ioport 0x7c00 alloc failed ahc_isa_identify 8: ioport 0x8c00 alloc failed ahc_isa_identify 9: ioport 0x9c00 alloc failed ahc_isa_identify 10: ioport 0xac00 alloc failed ahc_isa_identify 11: ioport 0xbc00 alloc failed ahc_isa_identify 12: ioport 0xcc00 alloc failed ahc_isa_identify 13: ioport 0xdc00 alloc failed ahc_isa_identify 14: ioport 0xec00 alloc failed isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it uart: uart0 already exists; skipping it isa_probe_children: probing non-PnP devices sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 fdc0: No FDOUT register! fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2097152 lo0: bpf attached hptrr: no controller detected. hpt27xx: no controller detected. xenbusb_front0: <Xen Frontend Devices> on xenstore0 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x0 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x0 xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 22:00:0a:94:b4:ba xenbusb_back0: <Xen Backend Devices> on xenstore0 xctrl0: <Xen Control Device> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: barriers GEOM: new disk ad0 xbd1: 122866MB <Virtual Block Device> at device/vbd/51728 on xenbusb_front0 xbd1: disk supports cache flush using: flush xbd2: 122866MB <Virtual Block Device> at device/vbd/51744 on xenbusb_front0 xbd2: disk supports cache flush using: flush SMP: AP CPU #29 Launched! cpu29 AP: ID: 0x2d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #24 Launched! cpu24 AP: ID: 0x28000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #21 Launched! cpu21 AP: ID: 0x25000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #6 Launched! cpu6 AP: ID: 0x06000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #7 Launched! cpu7 AP: ID: 0x07000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #23 Launched! cpu23 AP: ID: 0x27000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #18 Launched! cpu18 AP: ID: 0x22000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #25 Launched! cpu25 AP: ID: 0x29000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #16 Launched! cpu16 AP: ID: 0x20000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #28 Launched! cpu28 AP: ID: 0x2c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #10 Launched! cpu10 AP: ID: 0x0a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #27 Launched! cpu27 AP: ID: 0x2b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #12 Launched! cpu12 AP: ID: 0x0c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #30 Launched! cpu30 AP: ID: 0x2e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #31 Launched! cpu31 AP: ID: 0x2f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #19 Launched! cpu19 AP: ID: 0x23000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #15 Launched! cpu15 AP: ID: 0x0f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #17 Launched! cpu17 AP: ID: 0x21000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #14 Launched! cpu14 AP: ID: 0x0e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #20 Launched! cpu20 AP: ID: 0x24000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #22 Launched! cpu22 AP: ID: 0x26000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #4 Launched! cpu4 AP: ID: 0x04000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #8 Launched! cpu8 AP: ID: 0x08000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #13 Launched! cpu13 AP: ID: 0x0d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #11 Launched! cpu11 AP: ID: 0x0b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #5 Launched! cpu5 AP: ID: 0x05000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #26 Launched! cpu26 AP: ID: 0x2a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #9 Launched! cpu9 AP: ID: 0x09000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 panic: xen_et0: Error -22 setting singleshot timer to 766317887512893 cpuid = 8 KDB: enter: panic [ thread pid 11 tid 100011 ] Stopped at kdb_enter+0x3e: movq $0,kdb_why db> -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On 22/05/13 22:03, Colin Percival wrote:> On 05/22/13 04:45, Roger Pau Monné wrote: >> On 18/05/13 17:44, Colin Percival wrote: >>> That seems to work. dmesg is attached. Are there any particular tests >>> you''d like me to run? >> >> I have not tested ZFS, that might be a good one. If you are running this >> on Xen 3.4 the behaviour should be the same as without this patches, so >> there shouldn''t be many differences. > > I don''t use ZFS personally, so I''m not sure exactly what tests to run on it; > hopefully someone else can take care of that. > >> If you could try that on Xen 4.0 at least (if I remember correctly >> that''s when the vector callback was introduced), you should see the PV >> timer getting attached, and a performance increase. > > Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with > a panic -- console output below. I can get a backtrace and possibly even > a dump if those would help.Hello Colin, Thanks for the test, I''ve been using Xen 4.2 (and 4.3) without problems so far. By looking at the Xen code, the only reason the timer setup could return -22 (EINVAL), is that we try to set the timer for a different vCPU than the one we are running on. I''ve been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 (using both qemu-xen and qemu-xen-traditional device models), so I''m unsure if this could be due to some patch Amazon applies to Xen. Could you try the following patch and post the error message? I would like to see if the cpuid reported by kdb and the vCPU that we are trying to set the timer are the same. Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #68: Wed May 22 19:00:14 CEST 2013 root@:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. CPU: Intel(R) Xeon(R) CPU W3550 @ 3.07GHz (3066.83-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 0x6 Model = 0x1a Stepping = 5 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0x81b82201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> real memory = 4286578688 (4088 MB) avail memory = 3961323520 (3777 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 16 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 cpu4 (AP): APIC ID: 8 cpu5 (AP): APIC ID: 10 cpu6 (AP): APIC ID: 12 cpu7 (AP): APIC ID: 14 cpu8 (AP): APIC ID: 16 cpu9 (AP): APIC ID: 18 cpu10 (AP): APIC ID: 20 cpu11 (AP): APIC ID: 22 cpu12 (AP): APIC ID: 24 cpu13 (AP): APIC ID: 26 cpu14 (AP): APIC ID: 28 cpu15 (AP): APIC ID: 30 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 34 cpu18 (AP): APIC ID: 36 cpu19 (AP): APIC ID: 38 cpu20 (AP): APIC ID: 40 cpu21 (AP): APIC ID: 42 cpu22 (AP): APIC ID: 44 cpu23 (AP): APIC ID: 46 cpu24 (AP): APIC ID: 48 cpu25 (AP): APIC ID: 50 cpu26 (AP): APIC ID: 52 cpu27 (AP): APIC ID: 54 cpu28 (AP): APIC ID: 56 cpu29 (AP): APIC ID: 58 cpu30 (AP): APIC ID: 60 cpu31 (AP): APIC ID: 62 random device not loaded; using insecure entropy ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 <Version 1.1> irqs 0-47 on motherboard kbd1 at kbdmux0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 acpi0: <Xen> on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 cpu2: <ACPI CPU> on acpi0 cpu3: <ACPI CPU> on acpi0 cpu4: <ACPI CPU> on acpi0 cpu5: <ACPI CPU> on acpi0 cpu6: <ACPI CPU> on acpi0 cpu7: <ACPI CPU> on acpi0 cpu8: <ACPI CPU> on acpi0 cpu9: <ACPI CPU> on acpi0 cpu10: <ACPI CPU> on acpi0 cpu11: <ACPI CPU> on acpi0 cpu12: <ACPI CPU> on acpi0 cpu13: <ACPI CPU> on acpi0 cpu14: <ACPI CPU> on acpi0 cpu15: <ACPI CPU> on acpi0 cpu16: <ACPI CPU> on acpi0 cpu17: <ACPI CPU> on acpi0 cpu18: <ACPI CPU> on acpi0 cpu19: <ACPI CPU> on acpi0 cpu20: <ACPI CPU> on acpi0 cpu21: <ACPI CPU> on acpi0 cpu22: <ACPI CPU> on acpi0 cpu23: <ACPI CPU> on acpi0 cpu24: <ACPI CPU> on acpi0 cpu25: <ACPI CPU> on acpi0 cpu26: <ACPI CPU> on acpi0 cpu27: <ACPI CPU> on acpi0 cpu28: <ACPI CPU> on acpi0 cpu29: <ACPI CPU> on acpi0 cpu30: <ACPI CPU> on acpi0 cpu31: <ACPI CPU> on acpi0 hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc300-0xc30f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ata1: <ATA channel> at channel 1 on atapci0 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3030000-0xf3030fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenstore0: <XenStore> on xenpci0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: <Parallel port bus> on ppc0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 qpi0: <QPI system bus> on motherboard sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0: No FDOUT register! Timecounters tick every 10.000 msec xenbusb_front0: <Xen Frontend Devices> on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: <QEMU QEMU DVD-ROM 1.0.> Removable CD-ROM SCSI-0 device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:47:d4:52 xn1: <Virtual Network Interface> at device/vif/1 on xenbusb_front0 xn1: Ethernet address: 00:16:3e:47:d4:53 xenbusb_back0: <Xen Backend Devices> on xenstore0 xctrl0: <Xen Control Device> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xn1: backend features: feature-sg feature-gso-tcp4 xbd0: 20480MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: flush SMP: AP CPU #25 Launched! SMP: AP CPU #23 Launched! SMP: AP CPU #27 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #30 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #22 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #29 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #19 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #17 Launched! SMP: AP CPU #18 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #28 Launched! SMP: AP CPU #12 Launched! SMP: AP CPU #31 Launched! SMP: AP CPU #20 Launched! SMP: AP CPU #24 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #16 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #26 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #21 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0p2 [rw]... Setting hostuuid: c9230f36-1a54-489e-877c-1d15b8f463e9. Setting hostid: 0xd52252c7. Entropy harvesting: interrupts ethernet point_to_point kickstart. Starting file system checks: /dev/ad0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0p2: clean, 1690868 free (11852 frags, 209877 blocks, 0.2% fragmentation) Mounting local file systems:. Writing entropy file:. xn0: link state changed to DOWN xn0: link state changed to UP Starting Network: lo0 xn0 xn1. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> xn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=503<RXCSUM,TXCSUM,TSO4,LRO> ether 00:16:3e:47:d4:52 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet manual status: active xn1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=503<RXCSUM,TXCSUM,TSO4,LRO> ether 00:16:3e:47:d4:53 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet manual status: active Starting devd. Starting Network: xn1. xn1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=503<RXCSUM,TXCSUM,TSO4,LRO> ether 00:16:3e:47:d4:53 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet manual status: active Starting dhclient. DHCPREQUEST on xn0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.107 -- renewal in 43200 seconds. add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 add net fe80::: gateway ::1 add net ff02::: gateway ::1 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files. Starting syslogd. Starting watchdogd. watchdogd: patting the dog: Operation not supported /etc/rc: WARNING: failed to start watchdogd No core dumps found. lock order reversal: 1st 0xffffff80f7627d80 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3070 2nd 0xfffffe0027c18000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffff8121720450 kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffff8121720500 witness_checkorder() at witness_checkorder+0xc3f/frame 0xffffff8121720580 _sx_xlock() at _sx_xlock+0x75/frame 0xffffff81217205c0 ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xffffff8121720600 ufs_direnter() at ufs_direnter+0x688/frame 0xffffff81217206c0 ufs_mkdir() at ufs_mkdir+0x863/frame 0xffffff81217208c0 VOP_MKDIR_APV() at VOP_MKDIR_APV+0xf0/frame 0xffffff81217208f0 kern_mkdirat() at kern_mkdirat+0x21a/frame 0xffffff8121720ae0 amd64_syscall() at amd64_syscall+0x265/frame 0xffffff8121720bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xffffff8121720bf0 --- syscall (136, FreeBSD ELF64, sys_mkdir), rip = 0x80092faaa, rsp = 0x7fffffffd788, rbp = 0x7fffffffdc70 --- Clearing /tmp (X related). Updating motd:. Configuring syscons: keymap blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting cron. Starting background file system checks in 60 seconds. Thu May 23 10:08:04 CEST 2013 FreeBSD/amd64 (Amnesiac) (ttyu0) --------------000309090701090501040108 Content-Type: text/plain; charset="UTF-8"; x-mac-type=0; x-mac-creator=0; name="timer_panic.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="timer_panic.patch" diff --git a/sys/dev/xen/timer/timer.c b/sys/dev/xen/timer/timer.c index 7083e46..4cb49b0 100644 --- a/sys/dev/xen/timer/timer.c +++ b/sys/dev/xen/timer/timer.c @@ -418,8 +418,8 @@ xentimer_et_start(struct eventtimer *et, } while (error == -ETIME); if (error) - panic("%s: Error %d setting singleshot timer to %"PRIu64"\n", - device_get_nameunit(sc->dev), error, next_time); + panic("%s: Error %d setting singleshot timer to %"PRIu64" for vCPU#%d\n", + device_get_nameunit(sc->dev), error, next_time, cpu); pcpu->timer = next_time; return (error); --------------000309090701090501040108 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --------------000309090701090501040108--
On 22/05/13 22:03, Colin Percival wrote:> On 05/22/13 04:45, Roger Pau Monné wrote: >> On 18/05/13 17:44, Colin Percival wrote: >>> That seems to work. dmesg is attached. Are there any particular tests >>> you''d like me to run? >> >> I have not tested ZFS, that might be a good one. If you are running this >> on Xen 3.4 the behaviour should be the same as without this patches, so >> there shouldn''t be many differences. > > I don''t use ZFS personally, so I''m not sure exactly what tests to run on it; > hopefully someone else can take care of that. > >> If you could try that on Xen 4.0 at least (if I remember correctly >> that''s when the vector callback was introduced), you should see the PV >> timer getting attached, and a performance increase. > > Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with > a panic -- console output below. I can get a backtrace and possibly even > a dump if those would help.Hello Colin, Thanks for the test, I''ve been using Xen 4.2 (and 4.3) without problems so far. By looking at the Xen code, the only reason the timer setup could return -22 (EINVAL), is that we try to set the timer for a different vCPU than the one we are running on. I''ve been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 (using both qemu-xen and qemu-xen-traditional device models), so I''m unsure if this could be due to some patch Amazon applies to Xen. Could you try the following patch and post the error message? I would like to see if the cpuid reported by kdb and the vCPU that we are trying to set the timer are the same. Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #68: Wed May 22 19:00:14 CEST 2013 root@:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. CPU: Intel(R) Xeon(R) CPU W3550 @ 3.07GHz (3066.83-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 0x6 Model = 0x1a Stepping = 5 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0x81b82201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> real memory = 4286578688 (4088 MB) avail memory = 3961323520 (3777 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 16 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 cpu4 (AP): APIC ID: 8 cpu5 (AP): APIC ID: 10 cpu6 (AP): APIC ID: 12 cpu7 (AP): APIC ID: 14 cpu8 (AP): APIC ID: 16 cpu9 (AP): APIC ID: 18 cpu10 (AP): APIC ID: 20 cpu11 (AP): APIC ID: 22 cpu12 (AP): APIC ID: 24 cpu13 (AP): APIC ID: 26 cpu14 (AP): APIC ID: 28 cpu15 (AP): APIC ID: 30 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 34 cpu18 (AP): APIC ID: 36 cpu19 (AP): APIC ID: 38 cpu20 (AP): APIC ID: 40 cpu21 (AP): APIC ID: 42 cpu22 (AP): APIC ID: 44 cpu23 (AP): APIC ID: 46 cpu24 (AP): APIC ID: 48 cpu25 (AP): APIC ID: 50 cpu26 (AP): APIC ID: 52 cpu27 (AP): APIC ID: 54 cpu28 (AP): APIC ID: 56 cpu29 (AP): APIC ID: 58 cpu30 (AP): APIC ID: 60 cpu31 (AP): APIC ID: 62 random device not loaded; using insecure entropy ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 <Version 1.1> irqs 0-47 on motherboard kbd1 at kbdmux0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 acpi0: <Xen> on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 cpu2: <ACPI CPU> on acpi0 cpu3: <ACPI CPU> on acpi0 cpu4: <ACPI CPU> on acpi0 cpu5: <ACPI CPU> on acpi0 cpu6: <ACPI CPU> on acpi0 cpu7: <ACPI CPU> on acpi0 cpu8: <ACPI CPU> on acpi0 cpu9: <ACPI CPU> on acpi0 cpu10: <ACPI CPU> on acpi0 cpu11: <ACPI CPU> on acpi0 cpu12: <ACPI CPU> on acpi0 cpu13: <ACPI CPU> on acpi0 cpu14: <ACPI CPU> on acpi0 cpu15: <ACPI CPU> on acpi0 cpu16: <ACPI CPU> on acpi0 cpu17: <ACPI CPU> on acpi0 cpu18: <ACPI CPU> on acpi0 cpu19: <ACPI CPU> on acpi0 cpu20: <ACPI CPU> on acpi0 cpu21: <ACPI CPU> on acpi0 cpu22: <ACPI CPU> on acpi0 cpu23: <ACPI CPU> on acpi0 cpu24: <ACPI CPU> on acpi0 cpu25: <ACPI CPU> on acpi0 cpu26: <ACPI CPU> on acpi0 cpu27: <ACPI CPU> on acpi0 cpu28: <ACPI CPU> on acpi0 cpu29: <ACPI CPU> on acpi0 cpu30: <ACPI CPU> on acpi0 cpu31: <ACPI CPU> on acpi0 hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc300-0xc30f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ata1: <ATA channel> at channel 1 on atapci0 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3030000-0xf3030fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenstore0: <XenStore> on xenpci0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: <Parallel port bus> on ppc0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 qpi0: <QPI system bus> on motherboard sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0: No FDOUT register! Timecounters tick every 10.000 msec xenbusb_front0: <Xen Frontend Devices> on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: <QEMU QEMU DVD-ROM 1.0.> Removable CD-ROM SCSI-0 device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:47:d4:52 xn1: <Virtual Network Interface> at device/vif/1 on xenbusb_front0 xn1: Ethernet address: 00:16:3e:47:d4:53 xenbusb_back0: <Xen Backend Devices> on xenstore0 xctrl0: <Xen Control Device> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xn1: backend features: feature-sg feature-gso-tcp4 xbd0: 20480MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: flush SMP: AP CPU #25 Launched! SMP: AP CPU #23 Launched! SMP: AP CPU #27 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #30 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #22 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #29 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #19 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #17 Launched! SMP: AP CPU #18 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #28 Launched! SMP: AP CPU #12 Launched! SMP: AP CPU #31 Launched! SMP: AP CPU #20 Launched! SMP: AP CPU #24 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #16 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #26 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #21 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0p2 [rw]... Setting hostuuid: c9230f36-1a54-489e-877c-1d15b8f463e9. Setting hostid: 0xd52252c7. Entropy harvesting: interrupts ethernet point_to_point kickstart. Starting file system checks: /dev/ad0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0p2: clean, 1690868 free (11852 frags, 209877 blocks, 0.2% fragmentation) Mounting local file systems:. Writing entropy file:. xn0: link state changed to DOWN xn0: link state changed to UP Starting Network: lo0 xn0 xn1. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> xn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=503<RXCSUM,TXCSUM,TSO4,LRO> ether 00:16:3e:47:d4:52 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet manual status: active xn1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=503<RXCSUM,TXCSUM,TSO4,LRO> ether 00:16:3e:47:d4:53 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet manual status: active Starting devd. Starting Network: xn1. xn1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=503<RXCSUM,TXCSUM,TSO4,LRO> ether 00:16:3e:47:d4:53 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet manual status: active Starting dhclient. DHCPREQUEST on xn0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.107 -- renewal in 43200 seconds. add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 add net fe80::: gateway ::1 add net ff02::: gateway ::1 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files. Starting syslogd. Starting watchdogd. watchdogd: patting the dog: Operation not supported /etc/rc: WARNING: failed to start watchdogd No core dumps found. lock order reversal: 1st 0xffffff80f7627d80 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3070 2nd 0xfffffe0027c18000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffff8121720450 kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffff8121720500 witness_checkorder() at witness_checkorder+0xc3f/frame 0xffffff8121720580 _sx_xlock() at _sx_xlock+0x75/frame 0xffffff81217205c0 ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xffffff8121720600 ufs_direnter() at ufs_direnter+0x688/frame 0xffffff81217206c0 ufs_mkdir() at ufs_mkdir+0x863/frame 0xffffff81217208c0 VOP_MKDIR_APV() at VOP_MKDIR_APV+0xf0/frame 0xffffff81217208f0 kern_mkdirat() at kern_mkdirat+0x21a/frame 0xffffff8121720ae0 amd64_syscall() at amd64_syscall+0x265/frame 0xffffff8121720bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xffffff8121720bf0 --- syscall (136, FreeBSD ELF64, sys_mkdir), rip = 0x80092faaa, rsp = 0x7fffffffd788, rbp = 0x7fffffffdc70 --- Clearing /tmp (X related). Updating motd:. Configuring syscons: keymap blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting cron. Starting background file system checks in 60 seconds. Thu May 23 10:08:04 CEST 2013 FreeBSD/amd64 (Amnesiac) (ttyu0) --------------000309090701090501040108 Content-Type: text/plain; charset="UTF-8"; x-mac-type=0; x-mac-creator=0; name="timer_panic.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="timer_panic.patch" diff --git a/sys/dev/xen/timer/timer.c b/sys/dev/xen/timer/timer.c index 7083e46..4cb49b0 100644 --- a/sys/dev/xen/timer/timer.c +++ b/sys/dev/xen/timer/timer.c @@ -418,8 +418,8 @@ xentimer_et_start(struct eventtimer *et, } while (error == -ETIME); if (error) - panic("%s: Error %d setting singleshot timer to %"PRIu64"\n", - device_get_nameunit(sc->dev), error, next_time); + panic("%s: Error %d setting singleshot timer to %"PRIu64" for vCPU#%d\n", + device_get_nameunit(sc->dev), error, next_time, cpu); pcpu->timer = next_time; return (error); --------------000309090701090501040108 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------000309090701090501040108--
Hi, On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote:> Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback.I''ve just been able to install it on a VPS using the latest pvhvm_v9 branch. This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. I''m going to leave this running for a while and do some more tests on it. Jeroen. [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822
Hi, On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote:> Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback.I''ve just been able to install it on a VPS using the latest pvhvm_v9 branch. This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. I''m going to leave this running for a while and do some more tests on it. Jeroen. [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822
On Thu, May 23, 2013 at 8:57 AM, Jeroen van der Ham <jeroen@dckd.nl> wrote:> Hi, > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > > Right now the code is in a state where it can be tested by users, so we > > would like to encourage FreeBSD and Xen users to test it and provide > > feedback. > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 > branch. > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > I''m going to leave this running for a while and do some more tests on it. > > Jeroen. >Curious if this would work under XEN XCP (Xen Cloud Platform)> > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Thu, May 23, 2013 at 8:57 AM, Jeroen van der Ham <jeroen@dckd.nl> wrote:> Hi, > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > > Right now the code is in a state where it can be tested by users, so we > > would like to encourage FreeBSD and Xen users to test it and provide > > feedback. > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 > branch. > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > I''m going to leave this running for a while and do some more tests on it. > > Jeroen. >Curious if this would work under XEN XCP (Xen Cloud Platform)> > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote:> Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMYou mention on that page that it is easier to install on 10.0-CURRENT snapshots. What are the issues with installing this on 9.1? Is it possible? Jeroen.
On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote:> Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMYou mention on that page that it is easier to install on 10.0-CURRENT snapshots. What are the issues with installing this on 9.1? Is it possible? Jeroen.
On 23/05/13 15:20, Jeroen van der Ham wrote:> > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: >> Also, I''ve created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > You mention on that page that it is easier to install on 10.0-CURRENT snapshots. > What are the issues with installing this on 9.1? Is it possible?I don''t think it is recommended to use a HEAD (10) kernel with a 9.1 userland. You can always install a 9.1 and then do a full update with the source on my repository.
On 23/05/13 15:20, Jeroen van der Ham wrote:> > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: >> Also, I''ve created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > You mention on that page that it is easier to install on 10.0-CURRENT snapshots. > What are the issues with installing this on 9.1? Is it possible?I don''t think it is recommended to use a HEAD (10) kernel with a 9.1 userland. You can always install a 9.1 and then do a full update with the source on my repository.
On 23/05/13 14:57, Jeroen van der Ham wrote:> Hi, > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 branch.The branch pvhvm_v9 contains an initial implementation of PV IPIs for amd64. I''ve now finished it and I''m going to port it to i386 also, and push a new branch to the repository.> This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. > > I''m going to leave this running for a while and do some more tests on it. > > Jeroen. > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 >
On 23/05/13 14:57, Jeroen van der Ham wrote:> Hi, > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 branch.The branch pvhvm_v9 contains an initial implementation of PV IPIs for amd64. I''ve now finished it and I''m going to port it to i386 also, and push a new branch to the repository.> This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. > > I''m going to leave this running for a while and do some more tests on it. > > Jeroen. > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 >
On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 > branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I''ve now finished it and I''m going to port it to i386 also, and > push a new branch to the repository. >curious as the from what rev you guys forked your XENPVM work from HEAD, so i can assure Ive not lost some fixes, new commits from upstream> > > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > > > I''m going to leave this running for a while and do some more tests on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 > branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I''ve now finished it and I''m going to port it to i386 also, and > push a new branch to the repository. >curious as the from what rev you guys forked your XENPVM work from HEAD, so i can assure Ive not lost some fixes, new commits from upstream> > > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > > > I''m going to leave this running for a while and do some more tests on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 > branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I''ve now finished it and I''m going to port it to i386 also, and > push a new branch to the repository. > > > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > > > I''m going to leave this running for a while and do some more tests on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeingon boot after ugen0.2: <QEMU 0.10.2> at usbus0 run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_nop_confighook_cb panic: run_interrupt_driven_confighooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) db> _______________________________________________> freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I''ve just been able to install it on a VPS using the latest pvhvm_v9 > branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I''ve now finished it and I''m going to port it to i386 also, and > push a new branch to the repository. > > > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > > > I''m going to leave this running for a while and do some more tests on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeingon boot after ugen0.2: <QEMU 0.10.2> at usbus0 run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_nop_confighook_cb panic: run_interrupt_driven_confighooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) db> _______________________________________________> freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 23 May 2013 20:30, Outback Dingo <outbackdingo@gmail.com> wrote:> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com>wrote: > >> On 23/05/13 14:57, Jeroen van der Ham wrote: >> > Hi, >> > >> > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: >> >> Right now the code is in a state where it can be tested by users, so we >> >> would like to encourage FreeBSD and Xen users to test it and provide >> >> feedback. >> > >> > I''ve just been able to install it on a VPS using the latest pvhvm_v9 >> branch. >> >> The branch pvhvm_v9 contains an initial implementation of PV IPIs for >> amd64. I''ve now finished it and I''m going to port it to i386 also, and >> push a new branch to the repository. >> >> > This is good news, because the system I had before actually had trouble >> with the HVM kernel from 9.1 [0]. >> > >> > I''m going to leave this running for a while and do some more tests on it. >> > >> > Jeroen. >> > >> > >> > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 >> > >> >> I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_nop_confighook_cb > panic: run_interrupt_driven_confighooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > db>Can you recheck this on stock HEAD? From your description this looks like a rather old bug seen with 8.2 or above and XCP (referenced in PR kern/164630). You can trigger it when e.g. booting with empty cdrom. -- wbr, pluknet
On 23 May 2013 20:30, Outback Dingo <outbackdingo@gmail.com> wrote:> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com>wrote: > >> On 23/05/13 14:57, Jeroen van der Ham wrote: >> > Hi, >> > >> > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: >> >> Right now the code is in a state where it can be tested by users, so we >> >> would like to encourage FreeBSD and Xen users to test it and provide >> >> feedback. >> > >> > I''ve just been able to install it on a VPS using the latest pvhvm_v9 >> branch. >> >> The branch pvhvm_v9 contains an initial implementation of PV IPIs for >> amd64. I''ve now finished it and I''m going to port it to i386 also, and >> push a new branch to the repository. >> >> > This is good news, because the system I had before actually had trouble >> with the HVM kernel from 9.1 [0]. >> > >> > I''m going to leave this running for a while and do some more tests on it. >> > >> > Jeroen. >> > >> > >> > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 >> > >> >> I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_nop_confighook_cb > panic: run_interrupt_driven_confighooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > db>Can you recheck this on stock HEAD? From your description this looks like a rather old bug seen with 8.2 or above and XCP (referenced in PR kern/164630). You can trigger it when e.g. booting with empty cdrom. -- wbr, pluknet
On 23/05/13 18:30, Outback Dingo wrote:> > > > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com > <mailto:roger.pau@citrix.com>> wrote: > > On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com > <mailto:roger.pau@citrix.com>> wrote: > >> Right now the code is in a state where it can be tested by users, > so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I''ve just been able to install it on a VPS using the latest > pvhvm_v9 branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I''ve now finished it and I''m going to port it to i386 also, and > push a new branch to the repository. > > > This is good news, because the system I had before actually had > trouble with the HVM kernel from 9.1 [0]. > > > > I''m going to leave this running for a while and do some more tests > on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_nop_confighook_cb > panic: run_interrupt_driven_confighooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > db>From what I''ve read on the list, it seems like you cannot boot the PVHVM kernel if you have a cdrom attached to the guest, could you try disabling the cdrom and booting again?
On 23/05/13 18:30, Outback Dingo wrote:> > > > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com > <mailto:roger.pau@citrix.com>> wrote: > > On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com > <mailto:roger.pau@citrix.com>> wrote: > >> Right now the code is in a state where it can be tested by users, > so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I''ve just been able to install it on a VPS using the latest > pvhvm_v9 branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I''ve now finished it and I''m going to port it to i386 also, and > push a new branch to the repository. > > > This is good news, because the system I had before actually had > trouble with the HVM kernel from 9.1 [0]. > > > > I''m going to leave this running for a while and do some more tests > on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_nop_confighook_cb > panic: run_interrupt_driven_confighooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > db>From what I''ve read on the list, it seems like you cannot boot the PVHVM kernel if you have a cdrom attached to the guest, could you try disabling the cdrom and booting again?
On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 18:30, Outback Dingo wrote: > > > > > > > > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com > > <mailto:roger.pau@citrix.com>> wrote: > > > > On 23/05/13 14:57, Jeroen van der Ham wrote: > > > Hi, > > > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com > > <mailto:roger.pau@citrix.com>> wrote: > > >> Right now the code is in a state where it can be tested by users, > > so we > > >> would like to encourage FreeBSD and Xen users to test it and > provide > > >> feedback. > > > > > > I''ve just been able to install it on a VPS using the latest > > pvhvm_v9 branch. > > > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > > amd64. I''ve now finished it and I''m going to port it to i386 also, > and > > push a new branch to the repository. > > > > > This is good news, because the system I had before actually had > > trouble with the HVM kernel from 9.1 [0]. > > > > > > I''m going to leave this running for a while and do some more tests > > on it. > > > > > > Jeroen. > > > > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > > > on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > > > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_nop_confighook_cb > > panic: run_interrupt_driven_confighooks: waited too long > > cpuid = 0 > > KDB: enter: panic > > [ thread pid 0 tid 100000 ] > > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > > db> > > From what I''ve read on the list, it seems like you cannot boot the PVHVM > kernel if you have a cdrom attached to the guest, could you try > disabling the cdrom and booting again? > >great how does one go about disabling the cdrom, i get some disk parameters needs to be removed from the vm template before boot _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 18:30, Outback Dingo wrote: > > > > > > > > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com > > <mailto:roger.pau@citrix.com>> wrote: > > > > On 23/05/13 14:57, Jeroen van der Ham wrote: > > > Hi, > > > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com > > <mailto:roger.pau@citrix.com>> wrote: > > >> Right now the code is in a state where it can be tested by users, > > so we > > >> would like to encourage FreeBSD and Xen users to test it and > provide > > >> feedback. > > > > > > I''ve just been able to install it on a VPS using the latest > > pvhvm_v9 branch. > > > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > > amd64. I''ve now finished it and I''m going to port it to i386 also, > and > > push a new branch to the repository. > > > > > This is good news, because the system I had before actually had > > trouble with the HVM kernel from 9.1 [0]. > > > > > > I''m going to leave this running for a while and do some more tests > > on it. > > > > > > Jeroen. > > > > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > > > on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > > > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_nop_confighook_cb > > panic: run_interrupt_driven_confighooks: waited too long > > cpuid = 0 > > KDB: enter: panic > > [ thread pid 0 tid 100000 ] > > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > > db> > > From what I''ve read on the list, it seems like you cannot boot the PVHVM > kernel if you have a cdrom attached to the guest, could you try > disabling the cdrom and booting again? > >great how does one go about disabling the cdrom, i get some disk parameters needs to be removed from the vm template before boot _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Hi, Just remove this line (or pointing to a similar file from the template: (It''s part of the disks definition:> ''file:/root/freebsd-10.iso,hdc:cdrom,r'',Jeroen. On 23 May 2013, at 19:02, Outback Dingo <outbackdingo@gmail.com> wrote:> On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné <roger.pau@citrix.com>wrote: > >> On 23/05/13 18:30, Outback Dingo wrote: >>> >>> >>> >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com >>> <mailto:roger.pau@citrix.com>> wrote: >>> >>> On 23/05/13 14:57, Jeroen van der Ham wrote: >>>> Hi, >>>> >>>> On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com >>> <mailto:roger.pau@citrix.com>> wrote: >>>>> Right now the code is in a state where it can be tested by users, >>> so we >>>>> would like to encourage FreeBSD and Xen users to test it and >> provide >>>>> feedback. >>>> >>>> I''ve just been able to install it on a VPS using the latest >>> pvhvm_v9 branch. >>> >>> The branch pvhvm_v9 contains an initial implementation of PV IPIs for >>> amd64. I''ve now finished it and I''m going to port it to i386 also, >> and >>> push a new branch to the repository. >>> >>>> This is good news, because the system I had before actually had >>> trouble with the HVM kernel from 9.1 [0]. >>>> >>>> I''m going to leave this running for a while and do some more tests >>> on it. >>>> >>>> Jeroen. >>>> >>>> >>>> [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 >>>> >>> >>> I built the rev_9 branch on a XCP host and rebooted, however I am seeing >>> >>> on boot after ugen0.2: <QEMU 0.10.2> at usbus0 >>> >>> run_interrupt_driven_hooks: still waiting after 60 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 120 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 180 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 240 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 300 seconds for >>> xenbus_nop_confighook_cb >>> panic: run_interrupt_driven_confighooks: waited too long >>> cpuid = 0 >>> KDB: enter: panic >>> [ thread pid 0 tid 100000 ] >>> Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) >>> db> >> >> From what I''ve read on the list, it seems like you cannot boot the PVHVM >> kernel if you have a cdrom attached to the guest, could you try >> disabling the cdrom and booting again? >> >> > great how does one go about disabling the cdrom, i get some disk parameters > needs to be removed from the vm template before boot
Hi, Just remove this line (or pointing to a similar file from the template: (It''s part of the disks definition:> ''file:/root/freebsd-10.iso,hdc:cdrom,r'',Jeroen. On 23 May 2013, at 19:02, Outback Dingo <outbackdingo@gmail.com> wrote:> On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné <roger.pau@citrix.com>wrote: > >> On 23/05/13 18:30, Outback Dingo wrote: >>> >>> >>> >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com >>> <mailto:roger.pau@citrix.com>> wrote: >>> >>> On 23/05/13 14:57, Jeroen van der Ham wrote: >>>> Hi, >>>> >>>> On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com >>> <mailto:roger.pau@citrix.com>> wrote: >>>>> Right now the code is in a state where it can be tested by users, >>> so we >>>>> would like to encourage FreeBSD and Xen users to test it and >> provide >>>>> feedback. >>>> >>>> I''ve just been able to install it on a VPS using the latest >>> pvhvm_v9 branch. >>> >>> The branch pvhvm_v9 contains an initial implementation of PV IPIs for >>> amd64. I''ve now finished it and I''m going to port it to i386 also, >> and >>> push a new branch to the repository. >>> >>>> This is good news, because the system I had before actually had >>> trouble with the HVM kernel from 9.1 [0]. >>>> >>>> I''m going to leave this running for a while and do some more tests >>> on it. >>>> >>>> Jeroen. >>>> >>>> >>>> [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 >>>> >>> >>> I built the rev_9 branch on a XCP host and rebooted, however I am seeing >>> >>> on boot after ugen0.2: <QEMU 0.10.2> at usbus0 >>> >>> run_interrupt_driven_hooks: still waiting after 60 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 120 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 180 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 240 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 300 seconds for >>> xenbus_nop_confighook_cb >>> panic: run_interrupt_driven_confighooks: waited too long >>> cpuid = 0 >>> KDB: enter: panic >>> [ thread pid 0 tid 100000 ] >>> Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) >>> db> >> >> From what I''ve read on the list, it seems like you cannot boot the PVHVM >> kernel if you have a cdrom attached to the guest, could you try >> disabling the cdrom and booting again? >> >> > great how does one go about disabling the cdrom, i get some disk parameters > needs to be removed from the vm template before boot
On Thu, May 23, 2013 at 1:22 PM, Jeroen van der Ham <jeroen@dckd.nl> wrote:> Hi, > > Just remove this line (or pointing to a similar file from the template: > (It''s part of the disks definition: > > > ''file:/root/freebsd-10.iso,hdc:cdrom,r'', > >Thanks, but this is XCP not a generic XEN server where there are vm config files under /etc/xen/ in XCP they dont exists> Jeroen. > > On 23 May 2013, at 19:02, Outback Dingo <outbackdingo@gmail.com> wrote: > > > On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné <roger.pau@citrix.com > >wrote: > > > >> On 23/05/13 18:30, Outback Dingo wrote: > >>> > >>> > >>> > >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com > >>> <mailto:roger.pau@citrix.com>> wrote: > >>> > >>> On 23/05/13 14:57, Jeroen van der Ham wrote: > >>>> Hi, > >>>> > >>>> On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com > >>> <mailto:roger.pau@citrix.com>> wrote: > >>>>> Right now the code is in a state where it can be tested by users, > >>> so we > >>>>> would like to encourage FreeBSD and Xen users to test it and > >> provide > >>>>> feedback. > >>>> > >>>> I''ve just been able to install it on a VPS using the latest > >>> pvhvm_v9 branch. > >>> > >>> The branch pvhvm_v9 contains an initial implementation of PV IPIs > for > >>> amd64. I''ve now finished it and I''m going to port it to i386 also, > >> and > >>> push a new branch to the repository. > >>> > >>>> This is good news, because the system I had before actually had > >>> trouble with the HVM kernel from 9.1 [0]. > >>>> > >>>> I''m going to leave this running for a while and do some more tests > >>> on it. > >>>> > >>>> Jeroen. > >>>> > >>>> > >>>> [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > >>>> > >>> > >>> I built the rev_9 branch on a XCP host and rebooted, however I am > seeing > >>> > >>> on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > >>> > >>> run_interrupt_driven_hooks: still waiting after 60 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 120 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 180 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 240 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 300 seconds for > >>> xenbus_nop_confighook_cb > >>> panic: run_interrupt_driven_confighooks: waited too long > >>> cpuid = 0 > >>> KDB: enter: panic > >>> [ thread pid 0 tid 100000 ] > >>> Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > >>> db> > >> > >> From what I''ve read on the list, it seems like you cannot boot the PVHVM > >> kernel if you have a cdrom attached to the guest, could you try > >> disabling the cdrom and booting again? > >> > >> > > great how does one go about disabling the cdrom, i get some disk > parameters > > needs to be removed from the vm template before boot > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, May 23, 2013 at 1:22 PM, Jeroen van der Ham <jeroen@dckd.nl> wrote:> Hi, > > Just remove this line (or pointing to a similar file from the template: > (It''s part of the disks definition: > > > ''file:/root/freebsd-10.iso,hdc:cdrom,r'', > >Thanks, but this is XCP not a generic XEN server where there are vm config files under /etc/xen/ in XCP they dont exists> Jeroen. > > On 23 May 2013, at 19:02, Outback Dingo <outbackdingo@gmail.com> wrote: > > > On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monné <roger.pau@citrix.com > >wrote: > > > >> On 23/05/13 18:30, Outback Dingo wrote: > >>> > >>> > >>> > >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné <roger.pau@citrix.com > >>> <mailto:roger.pau@citrix.com>> wrote: > >>> > >>> On 23/05/13 14:57, Jeroen van der Ham wrote: > >>>> Hi, > >>>> > >>>> On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com > >>> <mailto:roger.pau@citrix.com>> wrote: > >>>>> Right now the code is in a state where it can be tested by users, > >>> so we > >>>>> would like to encourage FreeBSD and Xen users to test it and > >> provide > >>>>> feedback. > >>>> > >>>> I''ve just been able to install it on a VPS using the latest > >>> pvhvm_v9 branch. > >>> > >>> The branch pvhvm_v9 contains an initial implementation of PV IPIs > for > >>> amd64. I''ve now finished it and I''m going to port it to i386 also, > >> and > >>> push a new branch to the repository. > >>> > >>>> This is good news, because the system I had before actually had > >>> trouble with the HVM kernel from 9.1 [0]. > >>>> > >>>> I''m going to leave this running for a while and do some more tests > >>> on it. > >>>> > >>>> Jeroen. > >>>> > >>>> > >>>> [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > >>>> > >>> > >>> I built the rev_9 branch on a XCP host and rebooted, however I am > seeing > >>> > >>> on boot after ugen0.2: <QEMU 0.10.2> at usbus0 > >>> > >>> run_interrupt_driven_hooks: still waiting after 60 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 120 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 180 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 240 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 300 seconds for > >>> xenbus_nop_confighook_cb > >>> panic: run_interrupt_driven_confighooks: waited too long > >>> cpuid = 0 > >>> KDB: enter: panic > >>> [ thread pid 0 tid 100000 ] > >>> Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > >>> db> > >> > >> From what I''ve read on the list, it seems like you cannot boot the PVHVM > >> kernel if you have a cdrom attached to the guest, could you try > >> disabling the cdrom and booting again? > >> > >> > > great how does one go about disabling the cdrom, i get some disk > parameters > > needs to be removed from the vm template before boot > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Hello,
I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI
implementation for both amd64 and i386. I''ve also updated the wiki to
point to the pvhvm_v10 branch:
http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v10
I''ve updated my tree to latest HEAD, so now branch pvhvm_v10 is on top
of this commit:
commit b44da0fb82647f2cfb06f65a6695c7e36c98828c
Author: gber <gber@FreeBSD.org>
Date: Thu May 23 12:24:46 2013 +0000
Rework and organize pmap_enter_locked() function.
pmap_enter_locked() implementation was very ambiguous and confusing.
Rearrange it so that each part of the mapping creation is separated.
Avoid walking through the redundant conditions.
Extract vector_page specific PTE setup from normal PTE setting.
Submitted by: Zbigniew Bodek <zbb@semihalf.com>
Sponsored by: The FreeBSD Foundation, Semihalf
Thanks for the testing, Roger.
Hello,
I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI
implementation for both amd64 and i386. I''ve also updated the wiki to
point to the pvhvm_v10 branch:
http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v10
I''ve updated my tree to latest HEAD, so now branch pvhvm_v10 is on top
of this commit:
commit b44da0fb82647f2cfb06f65a6695c7e36c98828c
Author: gber <gber@FreeBSD.org>
Date: Thu May 23 12:24:46 2013 +0000
Rework and organize pmap_enter_locked() function.
pmap_enter_locked() implementation was very ambiguous and confusing.
Rearrange it so that each part of the mapping creation is separated.
Avoid walking through the redundant conditions.
Extract vector_page specific PTE setup from normal PTE setting.
Submitted by: Zbigniew Bodek <zbb@semihalf.com>
Sponsored by: The FreeBSD Foundation, Semihalf
Thanks for the testing, Roger.
On 05/23/13 02:06, Roger Pau Monné wrote:> On 22/05/13 22:03, Colin Percival wrote: >> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >> a panic -- console output below. I can get a backtrace and possibly even >> a dump if those would help. > > Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems > so far. By looking at the Xen code, the only reason the timer setup > could return -22 (EINVAL), is that we try to set the timer for a > different vCPU than the one we are running on. > > I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 > (using both qemu-xen and qemu-xen-traditional device models), so I'm > unsure if this could be due to some patch Amazon applies to Xen. Could > you try the following patch and post the error message? I would like to > see if the cpuid reported by kdb and the vCPU that we are trying to set > the timer are the same.Looks like there's agreement about the cpuids here. Anything else I should try testing? SMAP type=01 base=0000000000000000 len=000000000009e000 SMAP type=02 base=000000000009e000 len=0000000000002000 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=00000000eff00000 SMAP type=02 base=00000000fc000000 len=0000000004000000 SMAP type=01 base=0000000100000000 len=0000003c19000000 Table 'FACP' at 0xfc014980 Table 'APIC' at 0xfc014a80 APIC: Found table at 0xfc014a80 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: enabled SMP: Added CPU 14 (AP) MADT: Found CPU APIC ID 32 ACPI ID 8: enabled SMP: Added CPU 32 (AP) MADT: Found CPU APIC ID 34 ACPI ID 9: enabled SMP: Added CPU 34 (AP) MADT: Found CPU APIC ID 36 ACPI ID 10: enabled SMP: Added CPU 36 (AP) MADT: Found CPU APIC ID 38 ACPI ID 11: enabled SMP: Added CPU 38 (AP) MADT: Found CPU APIC ID 40 ACPI ID 12: enabled SMP: Added CPU 40 (AP) MADT: Found CPU APIC ID 42 ACPI ID 13: enabled SMP: Added CPU 42 (AP) MADT: Found CPU APIC ID 44 ACPI ID 14: enabled SMP: Added CPU 44 (AP) MADT: Found CPU APIC ID 46 ACPI ID 15: enabled SMP: Added CPU 46 (AP) MADT: Found CPU APIC ID 1 ACPI ID 16: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 3 ACPI ID 17: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 5 ACPI ID 18: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 7 ACPI ID 19: enabled SMP: Added CPU 7 (AP) MADT: Found CPU APIC ID 9 ACPI ID 20: enabled SMP: Added CPU 9 (AP) MADT: Found CPU APIC ID 11 ACPI ID 21: enabled SMP: Added CPU 11 (AP) MADT: Found CPU APIC ID 13 ACPI ID 22: enabled SMP: Added CPU 13 (AP) MADT: Found CPU APIC ID 15 ACPI ID 23: enabled SMP: Added CPU 15 (AP) MADT: Found CPU APIC ID 33 ACPI ID 24: enabled SMP: Added CPU 33 (AP) MADT: Found CPU APIC ID 35 ACPI ID 25: enabled SMP: Added CPU 35 (AP) MADT: Found CPU APIC ID 37 ACPI ID 26: enabled SMP: Added CPU 37 (AP) MADT: Found CPU APIC ID 39 ACPI ID 27: enabled SMP: Added CPU 39 (AP) MADT: Found CPU APIC ID 41 ACPI ID 28: enabled SMP: Added CPU 41 (AP) MADT: Found CPU APIC ID 43 ACPI ID 29: enabled SMP: Added CPU 43 (AP) MADT: Found CPU APIC ID 45 ACPI ID 30: enabled SMP: Added CPU 45 (AP) MADT: Found CPU APIC ID 47 ACPI ID 31: enabled SMP: Added CPU 47 (AP) MADT: Found CPU APIC ID 0 ACPI ID 32: disabled MADT: Found CPU APIC ID 0 ACPI ID 33: disabled MADT: Found CPU APIC ID 0 ACPI ID 34: disabled MADT: Found CPU APIC ID 0 ACPI ID 35: disabled MADT: Found CPU APIC ID 0 ACPI ID 36: disabled MADT: Found CPU APIC ID 0 ACPI ID 37: disabled MADT: Found CPU APIC ID 0 ACPI ID 38: disabled MADT: Found CPU APIC ID 0 ACPI ID 39: disabled MADT: Found CPU APIC ID 0 ACPI ID 40: disabled MADT: Found CPU APIC ID 0 ACPI ID 41: disabled MADT: Found CPU APIC ID 0 ACPI ID 42: disabled MADT: Found CPU APIC ID 0 ACPI ID 43: disabled MADT: Found CPU APIC ID 0 ACPI ID 44: disabled MADT: Found CPU APIC ID 0 ACPI ID 45: disabled MADT: Found CPU APIC ID 0 ACPI ID 46: disabled MADT: Found CPU APIC ID 0 ACPI ID 47: disabled MADT: Found CPU APIC ID 0 ACPI ID 48: disabled MADT: Found CPU APIC ID 0 ACPI ID 49: disabled MADT: Found CPU APIC ID 0 ACPI ID 50: disabled MADT: Found CPU APIC ID 0 ACPI ID 51: disabled MADT: Found CPU APIC ID 0 ACPI ID 52: disabled MADT: Found CPU APIC ID 0 ACPI ID 53: disabled MADT: Found CPU APIC ID 0 ACPI ID 54: disabled MADT: Found CPU APIC ID 0 ACPI ID 55: disabled MADT: Found CPU APIC ID 0 ACPI ID 56: disabled MADT: Found CPU APIC ID 0 ACPI ID 57: disabled MADT: Found CPU APIC ID 0 ACPI ID 58: disabled MADT: Found CPU APIC ID 0 ACPI ID 59: disabled MADT: Found CPU APIC ID 0 ACPI ID 60: disabled MADT: Found CPU APIC ID 0 ACPI ID 61: disabled MADT: Found CPU APIC ID 0 ACPI ID 62: disabled MADT: Found CPU APIC ID 0 ACPI ID 63: disabled MADT: Found CPU APIC ID 0 ACPI ID 64: disabled MADT: Found CPU APIC ID 0 ACPI ID 65: disabled MADT: Found CPU APIC ID 0 ACPI ID 66: disabled MADT: Found CPU APIC ID 0 ACPI ID 67: disabled MADT: Found CPU APIC ID 0 ACPI ID 68: disabled MADT: Found CPU APIC ID 0 ACPI ID 69: disabled MADT: Found CPU APIC ID 0 ACPI ID 70: disabled MADT: Found CPU APIC ID 0 ACPI ID 71: disabled MADT: Found CPU APIC ID 0 ACPI ID 72: disabled MADT: Found CPU APIC ID 0 ACPI ID 73: disabled MADT: Found CPU APIC ID 0 ACPI ID 74: disabled MADT: Found CPU APIC ID 0 ACPI ID 75: disabled MADT: Found CPU APIC ID 0 ACPI ID 76: disabled MADT: Found CPU APIC ID 0 ACPI ID 77: disabled MADT: Found CPU APIC ID 0 ACPI ID 78: disabled MADT: Found CPU APIC ID 0 ACPI ID 79: disabled MADT: Found CPU APIC ID 0 ACPI ID 80: disabled MADT: Found CPU APIC ID 0 ACPI ID 81: disabled MADT: Found CPU APIC ID 0 ACPI ID 82: disabled MADT: Found CPU APIC ID 0 ACPI ID 83: disabled MADT: Found CPU APIC ID 0 ACPI ID 84: disabled MADT: Found CPU APIC ID 0 ACPI ID 85: disabled MADT: Found CPU APIC ID 0 ACPI ID 86: disabled MADT: Found CPU APIC ID 0 ACPI ID 87: disabled MADT: Found CPU APIC ID 0 ACPI ID 88: disabled MADT: Found CPU APIC ID 0 ACPI ID 89: disabled MADT: Found CPU APIC ID 0 ACPI ID 90: disabled MADT: Found CPU APIC ID 0 ACPI ID 91: disabled MADT: Found CPU APIC ID 0 ACPI ID 92: disabled MADT: Found CPU APIC ID 0 ACPI ID 93: disabled MADT: Found CPU APIC ID 0 ACPI ID 94: disabled MADT: Found CPU APIC ID 0 ACPI ID 95: disabled MADT: Found CPU APIC ID 0 ACPI ID 96: disabled MADT: Found CPU APIC ID 0 ACPI ID 97: disabled MADT: Found CPU APIC ID 0 ACPI ID 98: disabled MADT: Found CPU APIC ID 0 ACPI ID 99: disabled MADT: Found CPU APIC ID 0 ACPI ID 100: disabled MADT: Found CPU APIC ID 0 ACPI ID 101: disabled MADT: Found CPU APIC ID 0 ACPI ID 102: disabled MADT: Found CPU APIC ID 0 ACPI ID 103: disabled MADT: Found CPU APIC ID 0 ACPI ID 104: disabled MADT: Found CPU APIC ID 0 ACPI ID 105: disabled MADT: Found CPU APIC ID 0 ACPI ID 106: disabled MADT: Found CPU APIC ID 0 ACPI ID 107: disabled MADT: Found CPU APIC ID 0 ACPI ID 108: disabled MADT: Found CPU APIC ID 0 ACPI ID 109: disabled MADT: Found CPU APIC ID 0 ACPI ID 110: disabled MADT: Found CPU APIC ID 0 ACPI ID 111: disabled MADT: Found CPU APIC ID 0 ACPI ID 112: disabled MADT: Found CPU APIC ID 0 ACPI ID 113: disabled MADT: Found CPU APIC ID 0 ACPI ID 114: disabled MADT: Found CPU APIC ID 0 ACPI ID 115: disabled MADT: Found CPU APIC ID 0 ACPI ID 116: disabled MADT: Found CPU APIC ID 0 ACPI ID 117: disabled MADT: Found CPU APIC ID 0 ACPI ID 118: disabled MADT: Found CPU APIC ID 0 ACPI ID 119: disabled MADT: Found CPU APIC ID 0 ACPI ID 120: disabled MADT: Found CPU APIC ID 0 ACPI ID 121: disabled MADT: Found CPU APIC ID 0 ACPI ID 122: disabled MADT: Found CPU APIC ID 0 ACPI ID 123: disabled MADT: Found CPU APIC ID 0 ACPI ID 124: disabled MADT: Found CPU APIC ID 0 ACPI ID 125: disabled MADT: Found CPU APIC ID 0 ACPI ID 126: disabled MADT: Found CPU APIC ID 0 ACPI ID 127: disabled Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #2 r+9b25356-dirty: Thu May 23 18:49:22 UTC 2013 root@ip-10-148-177-216:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. XEN: Disabling emulated block and network devices Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff818ca000. Hypervisor: Origin = "XenVMMXenVMM" Calibrating TSC clock ... TSC clock: 2600046368 Hz CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.05-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0x9fba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> real memory = 262144000000 (250000 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x00000000019e1000 - 0x00000000efffffff, 3999395840 bytes (976415 pages) 0x0000000100000000 - 0x0000003b8ae37fff, 251438268416 bytes (61386296 pages) avail memory = 244393992192 (233072 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target INTR: Adding local APIC 8 as a target INTR: Adding local APIC 9 as a target INTR: Adding local APIC 10 as a target INTR: Adding local APIC 11 as a target INTR: Adding local APIC 12 as a target INTR: Adding local APIC 13 as a target INTR: Adding local APIC 14 as a target INTR: Adding local APIC 15 as a target INTR: Adding local APIC 32 as a target INTR: Adding local APIC 33 as a target INTR: Adding local APIC 34 as a target INTR: Adding local APIC 35 as a target INTR: Adding local APIC 36 as a target INTR: Adding local APIC 37 as a target INTR: Adding local APIC 38 as a target INTR: Adding local APIC 39 as a target INTR: Adding local APIC 40 as a target INTR: Adding local APIC 41 as a target INTR: Adding local APIC 42 as a target INTR: Adding local APIC 43 as a target INTR: Adding local APIC 44 as a target INTR: Adding local APIC 45 as a target INTR: Adding local APIC 46 as a target INTR: Adding local APIC 47 as a target FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 12 cpu13 (AP): APIC ID: 13 cpu14 (AP): APIC ID: 14 cpu15 (AP): APIC ID: 15 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 33 cpu18 (AP): APIC ID: 34 cpu19 (AP): APIC ID: 35 cpu20 (AP): APIC ID: 36 cpu21 (AP): APIC ID: 37 cpu22 (AP): APIC ID: 38 cpu23 (AP): APIC ID: 39 cpu24 (AP): APIC ID: 40 cpu25 (AP): APIC ID: 41 cpu26 (AP): APIC ID: 42 cpu27 (AP): APIC ID: 43 cpu28 (AP): APIC ID: 44 cpu29 (AP): APIC ID: 45 cpu30 (AP): APIC ID: 46 cpu31 (AP): APIC ID: 47 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 16 APIC: CPU 2 has ACPI ID 1 APIC: CPU 3 has ACPI ID 17 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 18 APIC: CPU 6 has ACPI ID 3 APIC: CPU 7 has ACPI ID 19 APIC: CPU 8 has ACPI ID 4 APIC: CPU 9 has ACPI ID 20 APIC: CPU 10 has ACPI ID 5 APIC: CPU 11 has ACPI ID 21 APIC: CPU 12 has ACPI ID 6 APIC: CPU 13 has ACPI ID 22 APIC: CPU 14 has ACPI ID 7 APIC: CPU 15 has ACPI ID 23 APIC: CPU 16 has ACPI ID 8 APIC: CPU 17 has ACPI ID 24 APIC: CPU 18 has ACPI ID 9 APIC: CPU 19 has ACPI ID 25 APIC: CPU 20 has ACPI ID 10 APIC: CPU 21 has ACPI ID 26 APIC: CPU 22 has ACPI ID 11 APIC: CPU 23 has ACPI ID 27 APIC: CPU 24 has ACPI ID 12 APIC: CPU 25 has ACPI ID 28 APIC: CPU 26 has ACPI ID 13 APIC: CPU 27 has ACPI ID 29 APIC: CPU 28 has ACPI ID 14 APIC: CPU 29 has ACPI ID 30 APIC: CPU 30 has ACPI ID 15 APIC: CPU 31 has ACPI ID 31 x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 x86bios: SSEG 0x001000-0x001fff at 0xffffff80005e3000 x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 random device not loaded; using insecure entropy ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ULE: setup cpu 8 ULE: setup cpu 9 ULE: setup cpu 10 ULE: setup cpu 11 ULE: setup cpu 12 ULE: setup cpu 13 ULE: setup cpu 14 ULE: setup cpu 15 ULE: setup cpu 16 ULE: setup cpu 17 ULE: setup cpu 18 ULE: setup cpu 19 ULE: setup cpu 20 ULE: setup cpu 21 ULE: setup cpu 22 ULE: setup cpu 23 ULE: setup cpu 24 ULE: setup cpu 25 ULE: setup cpu 26 ULE: setup cpu 27 ULE: setup cpu 28 ULE: setup cpu 29 ULE: setup cpu 30 ULE: setup cpu 31 ACPI: RSDP 0xea020 00024 (v02 Xen) ACPI: XSDT 0xfc015920 0005C (v01 Xen HVM 00000000 HVML 00000000) ACPI: FACP 0xfc014980 000F4 (v04 Xen HVM 00000000 HVML 00000000) ACPI: DSDT 0xfc0035e0 11315 (v02 Xen HVM 00000000 INTL 20090123) ACPI: FACS 0xfc0035a0 00040 ACPI: APIC 0xfc014a80 00460 (v02 Xen HVM 00000000 HVML 00000000) ACPI: SRAT 0xfc014f60 008A8 (v01 Xen HVM 00000000 HVML 00000000) ACPI: HPET 0xfc015830 00038 (v01 Xen HVM 00000000 HVML 00000000) ACPI: WAET 0xfc015870 00028 (v01 Xen HVM 00000000 HVML 00000000) ACPI: SSDT 0xfc0158a0 00031 (v02 Xen HVM 00000000 INTL 20090123) ACPI: SSDT 0xfc0158e0 00031 (v02 Xen HVM 00000000 INTL 20090123) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 5, irq 5 ioapic0: intpin 5 trigger: level ioapic0: intpin 5 polarity: low MADT: Interrupt override: source 10, irq 10 ioapic0: intpin 10 trigger: level ioapic0: intpin 10 polarity: low MADT: Interrupt override: source 11, irq 11 ioapic0: intpin 11 trigger: level ioapic0: intpin 11 polarity: low MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 <Version 1.1> irqs 0-47 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 wlan: <802.11 Link Layer> Event-channel device installed. snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 kbd: new array size 4 kbd1 at kbdmux0 mem: <memory> nfslock: pseudo-device null: <null device, zero device> random: <entropy source, Software, Yarrow> VESA: INT 0x10 vector 0xc000:0x836e VESA: information block 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 15 mode(s) found VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80005fd040 (2000040) VESA: VGABIOS Cirrus extension VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0 io: <I/O> hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 hpt27xx: RocketRAID 27xx controller driver v1.0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 xen_et0: registered as a time-of-day clock (resolution 10000000us, adjustment 5.000000000s) acpi0: <Xen> on motherboard ACPI: All ACPI Tables successfully acquired ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: Processor \_SB_.PR00 (ACPI ID 0) -> APIC ID 0 cpu0: <ACPI CPU> on acpi0 cpu0: switching to generic Cx mode cpu1: Processor \_SB_.PR01 (ACPI ID 1) -> APIC ID 2 cpu1: <ACPI CPU> on acpi0 cpu2: Processor \_SB_.PR02 (ACPI ID 2) -> APIC ID 4 cpu2: <ACPI CPU> on acpi0 cpu3: Processor \_SB_.PR03 (ACPI ID 3) -> APIC ID 6 cpu3: <ACPI CPU> on acpi0 cpu4: Processor \_SB_.PR04 (ACPI ID 4) -> APIC ID 8 cpu4: <ACPI CPU> on acpi0 cpu5: Processor \_SB_.PR05 (ACPI ID 5) -> APIC ID 10 cpu5: <ACPI CPU> on acpi0 cpu6: Processor \_SB_.PR06 (ACPI ID 6) -> APIC ID 12 cpu6: <ACPI CPU> on acpi0 cpu7: Processor \_SB_.PR07 (ACPI ID 7) -> APIC ID 14 cpu7: <ACPI CPU> on acpi0 cpu8: Processor \_SB_.PR08 (ACPI ID 8) -> APIC ID 16 cpu8: <ACPI CPU> on acpi0 cpu9: Processor \_SB_.PR09 (ACPI ID 9) -> APIC ID 18 cpu9: <ACPI CPU> on acpi0 cpu10: Processor \_SB_.PR0A (ACPI ID 10) -> APIC ID 20 cpu10: <ACPI CPU> on acpi0 cpu11: Processor \_SB_.PR0B (ACPI ID 11) -> APIC ID 22 cpu11: <ACPI CPU> on acpi0 cpu12: Processor \_SB_.PR0C (ACPI ID 12) -> APIC ID 24 cpu12: <ACPI CPU> on acpi0 cpu13: Processor \_SB_.PR0D (ACPI ID 13) -> APIC ID 26 cpu13: <ACPI CPU> on acpi0 cpu14: Processor \_SB_.PR0E (ACPI ID 14) -> APIC ID 28 cpu14: <ACPI CPU> on acpi0 cpu15: Processor \_SB_.PR0F (ACPI ID 15) -> APIC ID 30 cpu15: <ACPI CPU> on acpi0 cpu16: Processor \_SB_.PR10 (ACPI ID 16) -> APIC ID 1 cpu16: <ACPI CPU> on acpi0 cpu17: Processor \_SB_.PR11 (ACPI ID 17) -> APIC ID 3 cpu17: <ACPI CPU> on acpi0 cpu18: Processor \_SB_.PR12 (ACPI ID 18) -> APIC ID 5 cpu18: <ACPI CPU> on acpi0 cpu19: Processor \_SB_.PR13 (ACPI ID 19) -> APIC ID 7 cpu19: <ACPI CPU> on acpi0 cpu20: Processor \_SB_.PR14 (ACPI ID 20) -> APIC ID 9 cpu20: <ACPI CPU> on acpi0 cpu21: Processor \_SB_.PR15 (ACPI ID 21) -> APIC ID 11 cpu21: <ACPI CPU> on acpi0 cpu22: Processor \_SB_.PR16 (ACPI ID 22) -> APIC ID 13 cpu22: <ACPI CPU> on acpi0 cpu23: Processor \_SB_.PR17 (ACPI ID 23) -> APIC ID 15 cpu23: <ACPI CPU> on acpi0 cpu24: Processor \_SB_.PR18 (ACPI ID 24) -> APIC ID 17 cpu24: <ACPI CPU> on acpi0 cpu25: Processor \_SB_.PR19 (ACPI ID 25) -> APIC ID 19 cpu25: <ACPI CPU> on acpi0 cpu26: Processor \_SB_.PR1A (ACPI ID 26) -> APIC ID 21 cpu26: <ACPI CPU> on acpi0 cpu27: Processor \_SB_.PR1B (ACPI ID 27) -> APIC ID 23 cpu27: <ACPI CPU> on acpi0 cpu28: Processor \_SB_.PR1C (ACPI ID 28) -> APIC ID 25 cpu28: <ACPI CPU> on acpi0 cpu29: Processor \_SB_.PR1D (ACPI ID 29) -> APIC ID 27 cpu29: <ACPI CPU> on acpi0 cpu30: Processor \_SB_.PR1E (ACPI ID 30) -> APIC ID 29 cpu30: <ACPI CPU> on acpi0 cpu31: Processor \_SB_.PR1F (ACPI ID 31) -> APIC ID 31 cpu31: <ACPI CPU> on acpi0 ACPI: Processor \_SB_.PR20 (ACPI ID 32) ignored ACPI: Processor \_SB_.PR21 (ACPI ID 33) ignored ACPI: Processor \_SB_.PR22 (ACPI ID 34) ignored ACPI: Processor \_SB_.PR23 (ACPI ID 35) ignored ACPI: Processor \_SB_.PR24 (ACPI ID 36) ignored ACPI: Processor \_SB_.PR25 (ACPI ID 37) ignored ACPI: Processor \_SB_.PR26 (ACPI ID 38) ignored ACPI: Processor \_SB_.PR27 (ACPI ID 39) ignored ACPI: Processor \_SB_.PR28 (ACPI ID 40) ignored ACPI: Processor \_SB_.PR29 (ACPI ID 41) ignored ACPI: Processor \_SB_.PR2A (ACPI ID 42) ignored ACPI: Processor \_SB_.PR2B (ACPI ID 43) ignored ACPI: Processor \_SB_.PR2C (ACPI ID 44) ignored ACPI: Processor \_SB_.PR2D (ACPI ID 45) ignored ACPI: Processor \_SB_.PR2E (ACPI ID 46) ignored ACPI: Processor \_SB_.PR2F (ACPI ID 47) ignored ACPI: Processor \_SB_.PR30 (ACPI ID 48) ignored ACPI: Processor \_SB_.PR31 (ACPI ID 49) ignored ACPI: Processor \_SB_.PR32 (ACPI ID 50) ignored ACPI: Processor \_SB_.PR33 (ACPI ID 51) ignored ACPI: Processor \_SB_.PR34 (ACPI ID 52) ignored ACPI: Processor \_SB_.PR35 (ACPI ID 53) ignored ACPI: Processor \_SB_.PR36 (ACPI ID 54) ignored ACPI: Processor \_SB_.PR37 (ACPI ID 55) ignored ACPI: Processor \_SB_.PR38 (ACPI ID 56) ignored ACPI: Processor \_SB_.PR39 (ACPI ID 57) ignored ACPI: Processor \_SB_.PR3A (ACPI ID 58) ignored ACPI: Processor \_SB_.PR3B (ACPI ID 59) ignored ACPI: Processor \_SB_.PR3C (ACPI ID 60) ignored ACPI: Processor \_SB_.PR3D (ACPI ID 61) ignored ACPI: Processor \_SB_.PR3E (ACPI ID 62) ignored ACPI: Processor \_SB_.PR3F (ACPI ID 63) ignored ACPI: Processor \_SB_.PR40 (ACPI ID 64) ignored ACPI: Processor \_SB_.PR41 (ACPI ID 65) ignored ACPI: Processor \_SB_.PR42 (ACPI ID 66) ignored ACPI: Processor \_SB_.PR43 (ACPI ID 67) ignored ACPI: Processor \_SB_.PR44 (ACPI ID 68) ignored ACPI: Processor \_SB_.PR45 (ACPI ID 69) ignored ACPI: Processor \_SB_.PR46 (ACPI ID 70) ignored ACPI: Processor \_SB_.PR47 (ACPI ID 71) ignored ACPI: Processor \_SB_.PR48 (ACPI ID 72) ignored ACPI: Processor \_SB_.PR49 (ACPI ID 73) ignored ACPI: Processor \_SB_.PR4A (ACPI ID 74) ignored ACPI: Processor \_SB_.PR4B (ACPI ID 75) ignored ACPI: Processor \_SB_.PR4C (ACPI ID 76) ignored ACPI: Processor \_SB_.PR4D (ACPI ID 77) ignored ACPI: Processor \_SB_.PR4E (ACPI ID 78) ignored ACPI: Processor \_SB_.PR4F (ACPI ID 79) ignored ACPI: Processor \_SB_.PR50 (ACPI ID 80) ignored ACPI: Processor \_SB_.PR51 (ACPI ID 81) ignored ACPI: Processor \_SB_.PR52 (ACPI ID 82) ignored ACPI: Processor \_SB_.PR53 (ACPI ID 83) ignored ACPI: Processor \_SB_.PR54 (ACPI ID 84) ignored ACPI: Processor \_SB_.PR55 (ACPI ID 85) ignored ACPI: Processor \_SB_.PR56 (ACPI ID 86) ignored ACPI: Processor \_SB_.PR57 (ACPI ID 87) ignored ACPI: Processor \_SB_.PR58 (ACPI ID 88) ignored ACPI: Processor \_SB_.PR59 (ACPI ID 89) ignored ACPI: Processor \_SB_.PR5A (ACPI ID 90) ignored ACPI: Processor \_SB_.PR5B (ACPI ID 91) ignored ACPI: Processor \_SB_.PR5C (ACPI ID 92) ignored ACPI: Processor \_SB_.PR5D (ACPI ID 93) ignored ACPI: Processor \_SB_.PR5E (ACPI ID 94) ignored ACPI: Processor \_SB_.PR5F (ACPI ID 95) ignored ACPI: Processor \_SB_.PR60 (ACPI ID 96) ignored ACPI: Processor \_SB_.PR61 (ACPI ID 97) ignored ACPI: Processor \_SB_.PR62 (ACPI ID 98) ignored ACPI: Processor \_SB_.PR63 (ACPI ID 99) ignored ACPI: Processor \_SB_.PR64 (ACPI ID 100) ignored ACPI: Processor \_SB_.PR65 (ACPI ID 101) ignored ACPI: Processor \_SB_.PR66 (ACPI ID 102) ignored ACPI: Processor \_SB_.PR67 (ACPI ID 103) ignored ACPI: Processor \_SB_.PR68 (ACPI ID 104) ignored ACPI: Processor \_SB_.PR69 (ACPI ID 105) ignored ACPI: Processor \_SB_.PR6A (ACPI ID 106) ignored ACPI: Processor \_SB_.PR6B (ACPI ID 107) ignored ACPI: Processor \_SB_.PR6C (ACPI ID 108) ignored ACPI: Processor \_SB_.PR6D (ACPI ID 109) ignored ACPI: Processor \_SB_.PR6E (ACPI ID 110) ignored ACPI: Processor \_SB_.PR6F (ACPI ID 111) ignored ACPI: Processor \_SB_.PR70 (ACPI ID 112) ignored ACPI: Processor \_SB_.PR71 (ACPI ID 113) ignored ACPI: Processor \_SB_.PR72 (ACPI ID 114) ignored ACPI: Processor \_SB_.PR73 (ACPI ID 115) ignored ACPI: Processor \_SB_.PR74 (ACPI ID 116) ignored ACPI: Processor \_SB_.PR75 (ACPI ID 117) ignored ACPI: Processor \_SB_.PR76 (ACPI ID 118) ignored ACPI: Processor \_SB_.PR77 (ACPI ID 119) ignored ACPI: Processor \_SB_.PR78 (ACPI ID 120) ignored ACPI: Processor \_SB_.PR79 (ACPI ID 121) ignored ACPI: Processor \_SB_.PR7A (ACPI ID 122) ignored ACPI: Processor \_SB_.PR7B (ACPI ID 123) ignored ACPI: Processor \_SB_.PR7C (ACPI ID 124) ignored ACPI: Processor \_SB_.PR7D (ACPI ID 125) ignored ACPI: Processor \_SB_.PR7E (ACPI ID 126) ignored ACPI: Processor \_SB_.PR7F (ACPI ID 127) ignored hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 atrtc0: not installed as time-of-day clock: clock xen_et has higher resolution ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50 Event timer "RTC" frequency 32768 Hz quality 0 ACPI timer: 1/20 1/19 1/19 1/20 1/19 1/23 1/20 1/19 1/18 1/17 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 10 11 Validation 0 10 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 10 11 Validation 0 11 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xf0000000-0xfbffffff pci0: <ACPI PCI bus> on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x1237, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7000, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7010, revid=0x00 domain=0, bus=0, slot=1, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1 found-> vendor=0x8086, dev=0x7113, revid=0x01 domain=0, bus=0, slot=1, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 20 found-> vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, enabled pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0 map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0 found-> vendor=0x5853, dev=0x0001, revid=0x01 domain=0, bus=0, slot=3, func=0 class=ff-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, enabled pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0 pcib0: matched entry for 0.3.INTA pcib0: slot 3 INTA hardwired to IRQ 28 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51 ata1: <ATA channel> at channel 1 on atapci0 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53 xenstore0: <XenStore> on xenpci0 Grant table initialized psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0061 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54 atkbd0: [GIANT-LOCKED] psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 00 02 64 psm0: <PS/2 Mouse> irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56 uart0: fast interrupt uart0: console (9600,n,8,1) ACPI: Enabled 2 GPEs in block 00 to 0F acpi0: wakeup code va 0xffffffc2ce049000 pa 0x30000 ahc_isa_identify 0: ioport 0xc00 alloc failed ahc_isa_identify 1: ioport 0x1c00 alloc failed ahc_isa_identify 2: ioport 0x2c00 alloc failed ahc_isa_identify 3: ioport 0x3c00 alloc failed ahc_isa_identify 4: ioport 0x4c00 alloc failed ahc_isa_identify 5: ioport 0x5c00 alloc failed ahc_isa_identify 6: ioport 0x6c00 alloc failed ahc_isa_identify 7: ioport 0x7c00 alloc failed ahc_isa_identify 8: ioport 0x8c00 alloc failed ahc_isa_identify 9: ioport 0x9c00 alloc failed ahc_isa_identify 10: ioport 0xac00 alloc failed ahc_isa_identify 11: ioport 0xbc00 alloc failed ahc_isa_identify 12: ioport 0xcc00 alloc failed ahc_isa_identify 13: ioport 0xdc00 alloc failed ahc_isa_identify 14: ioport 0xec00 alloc failed pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 ex_isa_identify() isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it uart: uart0 already exists; skipping it isa_probe_children: probing non-PnP devices sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 fdc0: No FDOUT register! fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2097152 lo0: bpf attached hptrr: no controller detected. hpt27xx: no controller detected. xctrl0: <Xen Control Device> on xenstore0 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 xenbusb_front0: <Xen Frontend Devices> on xenstore0 ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x0 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x0 xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 22:00:0a:94:b5:05 xenbusb_back0: <Xen Backend Devices> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: barriers GEOM: new disk ad0 xbd1: 122866MB <Virtual Block Device> at device/vbd/51728 on xenbusb_front0 xbd1: disk supports cache flush using: flush xbd2: 122866MB <Virtual Block Device> at device/vbd/51744 on xenbusb_front0 xbd2: disk supports cache flush using: flush SMP: AP CPU #4 Launched! cpu4 AP: ID: 0x04000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #10 Launched! cpu10 AP: ID: 0x0a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #11 Launched! cpu11 AP: ID: 0x0b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #16 Launched! cpu16 AP: ID: 0x20000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #22 Launched! cpu22 AP: ID: 0x26000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #23 Launched! cpu23 AP: ID: 0x27000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #19 Launched! cpu19 AP: ID: 0x23000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #17 Launched! cpu17 AP: ID: 0x21000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #7 Launched! cpu7 AP: ID: 0x07000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #27 Launched! cpu27 AP: ID: 0x2b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #26 Launched! cpu26 AP: ID: 0x2a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #25 Launched! cpu25 AP: ID: 0x29000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #21 Launched! cpu21 AP: ID: 0x25000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #20 Launched! cpu20 AP: ID: 0x24000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #29 Launched! cpu29 AP: ID: 0x2d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #31 Launched! cpu31 AP: ID: 0x2f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #18 Launched! cpu18 AP: ID: 0x22000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #30 Launched! cpu30 AP: ID: 0x2e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #13 Launched! cpu13 AP: ID: 0x0d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #24 Launched! cpu24 AP: ID: 0x28000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #28 Launched! cpu28 AP: ID: 0x2c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #8 Launched! cpu8 AP: ID: 0x08000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #14 Launched! cpu14 AP: ID: 0x0e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #5 Launched! cpu5 AP: ID: 0x05000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #12 Launched! cpu12 AP: ID: 0x0c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #15 Launched! cpu15 AP: ID: 0x0f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #6 Launched! cpu6 AP: ID: 0x06000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #9 Launched! cpu9 AP: ID: 0x09000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 panic: xen_et0: Error -22 setting singleshot timer to 506167555095805 for vCPU#1 cpuid = 1 KDB: stack backtrace: #0 0xffffffff808e6ed0 at kdb_backtrace+0x60 #1 0xffffffff808b22b6 at vpanic+0x126 #2 0xffffffff808b2343 at panic+0x43 #3 0xffffffff807a445a at xentimer_et_start+0xca #4 0xffffffff80cb365d at loadtimer+0xfd #5 0xffffffff80cb38d7 at cpu_new_callout+0xc7 #6 0xffffffff808c5ca1 at callout_process+0x2c1 #7 0xffffffff80cb25d5 at handleevents+0x185 #8 0xffffffff80cb324b at cpu_initclocks_ap+0xcb #9 0xffffffff80c2fc84 at init_secondary+0x474 Uptime: 3s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 05/23/13 02:06, Roger Pau Monné wrote:> On 22/05/13 22:03, Colin Percival wrote: >> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >> a panic -- console output below. I can get a backtrace and possibly even >> a dump if those would help. > > Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems > so far. By looking at the Xen code, the only reason the timer setup > could return -22 (EINVAL), is that we try to set the timer for a > different vCPU than the one we are running on. > > I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 > (using both qemu-xen and qemu-xen-traditional device models), so I'm > unsure if this could be due to some patch Amazon applies to Xen. Could > you try the following patch and post the error message? I would like to > see if the cpuid reported by kdb and the vCPU that we are trying to set > the timer are the same.Looks like there's agreement about the cpuids here. Anything else I should try testing? SMAP type=01 base=0000000000000000 len=000000000009e000 SMAP type=02 base=000000000009e000 len=0000000000002000 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=00000000eff00000 SMAP type=02 base=00000000fc000000 len=0000000004000000 SMAP type=01 base=0000000100000000 len=0000003c19000000 Table 'FACP' at 0xfc014980 Table 'APIC' at 0xfc014a80 APIC: Found table at 0xfc014a80 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: enabled SMP: Added CPU 14 (AP) MADT: Found CPU APIC ID 32 ACPI ID 8: enabled SMP: Added CPU 32 (AP) MADT: Found CPU APIC ID 34 ACPI ID 9: enabled SMP: Added CPU 34 (AP) MADT: Found CPU APIC ID 36 ACPI ID 10: enabled SMP: Added CPU 36 (AP) MADT: Found CPU APIC ID 38 ACPI ID 11: enabled SMP: Added CPU 38 (AP) MADT: Found CPU APIC ID 40 ACPI ID 12: enabled SMP: Added CPU 40 (AP) MADT: Found CPU APIC ID 42 ACPI ID 13: enabled SMP: Added CPU 42 (AP) MADT: Found CPU APIC ID 44 ACPI ID 14: enabled SMP: Added CPU 44 (AP) MADT: Found CPU APIC ID 46 ACPI ID 15: enabled SMP: Added CPU 46 (AP) MADT: Found CPU APIC ID 1 ACPI ID 16: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 3 ACPI ID 17: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 5 ACPI ID 18: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 7 ACPI ID 19: enabled SMP: Added CPU 7 (AP) MADT: Found CPU APIC ID 9 ACPI ID 20: enabled SMP: Added CPU 9 (AP) MADT: Found CPU APIC ID 11 ACPI ID 21: enabled SMP: Added CPU 11 (AP) MADT: Found CPU APIC ID 13 ACPI ID 22: enabled SMP: Added CPU 13 (AP) MADT: Found CPU APIC ID 15 ACPI ID 23: enabled SMP: Added CPU 15 (AP) MADT: Found CPU APIC ID 33 ACPI ID 24: enabled SMP: Added CPU 33 (AP) MADT: Found CPU APIC ID 35 ACPI ID 25: enabled SMP: Added CPU 35 (AP) MADT: Found CPU APIC ID 37 ACPI ID 26: enabled SMP: Added CPU 37 (AP) MADT: Found CPU APIC ID 39 ACPI ID 27: enabled SMP: Added CPU 39 (AP) MADT: Found CPU APIC ID 41 ACPI ID 28: enabled SMP: Added CPU 41 (AP) MADT: Found CPU APIC ID 43 ACPI ID 29: enabled SMP: Added CPU 43 (AP) MADT: Found CPU APIC ID 45 ACPI ID 30: enabled SMP: Added CPU 45 (AP) MADT: Found CPU APIC ID 47 ACPI ID 31: enabled SMP: Added CPU 47 (AP) MADT: Found CPU APIC ID 0 ACPI ID 32: disabled MADT: Found CPU APIC ID 0 ACPI ID 33: disabled MADT: Found CPU APIC ID 0 ACPI ID 34: disabled MADT: Found CPU APIC ID 0 ACPI ID 35: disabled MADT: Found CPU APIC ID 0 ACPI ID 36: disabled MADT: Found CPU APIC ID 0 ACPI ID 37: disabled MADT: Found CPU APIC ID 0 ACPI ID 38: disabled MADT: Found CPU APIC ID 0 ACPI ID 39: disabled MADT: Found CPU APIC ID 0 ACPI ID 40: disabled MADT: Found CPU APIC ID 0 ACPI ID 41: disabled MADT: Found CPU APIC ID 0 ACPI ID 42: disabled MADT: Found CPU APIC ID 0 ACPI ID 43: disabled MADT: Found CPU APIC ID 0 ACPI ID 44: disabled MADT: Found CPU APIC ID 0 ACPI ID 45: disabled MADT: Found CPU APIC ID 0 ACPI ID 46: disabled MADT: Found CPU APIC ID 0 ACPI ID 47: disabled MADT: Found CPU APIC ID 0 ACPI ID 48: disabled MADT: Found CPU APIC ID 0 ACPI ID 49: disabled MADT: Found CPU APIC ID 0 ACPI ID 50: disabled MADT: Found CPU APIC ID 0 ACPI ID 51: disabled MADT: Found CPU APIC ID 0 ACPI ID 52: disabled MADT: Found CPU APIC ID 0 ACPI ID 53: disabled MADT: Found CPU APIC ID 0 ACPI ID 54: disabled MADT: Found CPU APIC ID 0 ACPI ID 55: disabled MADT: Found CPU APIC ID 0 ACPI ID 56: disabled MADT: Found CPU APIC ID 0 ACPI ID 57: disabled MADT: Found CPU APIC ID 0 ACPI ID 58: disabled MADT: Found CPU APIC ID 0 ACPI ID 59: disabled MADT: Found CPU APIC ID 0 ACPI ID 60: disabled MADT: Found CPU APIC ID 0 ACPI ID 61: disabled MADT: Found CPU APIC ID 0 ACPI ID 62: disabled MADT: Found CPU APIC ID 0 ACPI ID 63: disabled MADT: Found CPU APIC ID 0 ACPI ID 64: disabled MADT: Found CPU APIC ID 0 ACPI ID 65: disabled MADT: Found CPU APIC ID 0 ACPI ID 66: disabled MADT: Found CPU APIC ID 0 ACPI ID 67: disabled MADT: Found CPU APIC ID 0 ACPI ID 68: disabled MADT: Found CPU APIC ID 0 ACPI ID 69: disabled MADT: Found CPU APIC ID 0 ACPI ID 70: disabled MADT: Found CPU APIC ID 0 ACPI ID 71: disabled MADT: Found CPU APIC ID 0 ACPI ID 72: disabled MADT: Found CPU APIC ID 0 ACPI ID 73: disabled MADT: Found CPU APIC ID 0 ACPI ID 74: disabled MADT: Found CPU APIC ID 0 ACPI ID 75: disabled MADT: Found CPU APIC ID 0 ACPI ID 76: disabled MADT: Found CPU APIC ID 0 ACPI ID 77: disabled MADT: Found CPU APIC ID 0 ACPI ID 78: disabled MADT: Found CPU APIC ID 0 ACPI ID 79: disabled MADT: Found CPU APIC ID 0 ACPI ID 80: disabled MADT: Found CPU APIC ID 0 ACPI ID 81: disabled MADT: Found CPU APIC ID 0 ACPI ID 82: disabled MADT: Found CPU APIC ID 0 ACPI ID 83: disabled MADT: Found CPU APIC ID 0 ACPI ID 84: disabled MADT: Found CPU APIC ID 0 ACPI ID 85: disabled MADT: Found CPU APIC ID 0 ACPI ID 86: disabled MADT: Found CPU APIC ID 0 ACPI ID 87: disabled MADT: Found CPU APIC ID 0 ACPI ID 88: disabled MADT: Found CPU APIC ID 0 ACPI ID 89: disabled MADT: Found CPU APIC ID 0 ACPI ID 90: disabled MADT: Found CPU APIC ID 0 ACPI ID 91: disabled MADT: Found CPU APIC ID 0 ACPI ID 92: disabled MADT: Found CPU APIC ID 0 ACPI ID 93: disabled MADT: Found CPU APIC ID 0 ACPI ID 94: disabled MADT: Found CPU APIC ID 0 ACPI ID 95: disabled MADT: Found CPU APIC ID 0 ACPI ID 96: disabled MADT: Found CPU APIC ID 0 ACPI ID 97: disabled MADT: Found CPU APIC ID 0 ACPI ID 98: disabled MADT: Found CPU APIC ID 0 ACPI ID 99: disabled MADT: Found CPU APIC ID 0 ACPI ID 100: disabled MADT: Found CPU APIC ID 0 ACPI ID 101: disabled MADT: Found CPU APIC ID 0 ACPI ID 102: disabled MADT: Found CPU APIC ID 0 ACPI ID 103: disabled MADT: Found CPU APIC ID 0 ACPI ID 104: disabled MADT: Found CPU APIC ID 0 ACPI ID 105: disabled MADT: Found CPU APIC ID 0 ACPI ID 106: disabled MADT: Found CPU APIC ID 0 ACPI ID 107: disabled MADT: Found CPU APIC ID 0 ACPI ID 108: disabled MADT: Found CPU APIC ID 0 ACPI ID 109: disabled MADT: Found CPU APIC ID 0 ACPI ID 110: disabled MADT: Found CPU APIC ID 0 ACPI ID 111: disabled MADT: Found CPU APIC ID 0 ACPI ID 112: disabled MADT: Found CPU APIC ID 0 ACPI ID 113: disabled MADT: Found CPU APIC ID 0 ACPI ID 114: disabled MADT: Found CPU APIC ID 0 ACPI ID 115: disabled MADT: Found CPU APIC ID 0 ACPI ID 116: disabled MADT: Found CPU APIC ID 0 ACPI ID 117: disabled MADT: Found CPU APIC ID 0 ACPI ID 118: disabled MADT: Found CPU APIC ID 0 ACPI ID 119: disabled MADT: Found CPU APIC ID 0 ACPI ID 120: disabled MADT: Found CPU APIC ID 0 ACPI ID 121: disabled MADT: Found CPU APIC ID 0 ACPI ID 122: disabled MADT: Found CPU APIC ID 0 ACPI ID 123: disabled MADT: Found CPU APIC ID 0 ACPI ID 124: disabled MADT: Found CPU APIC ID 0 ACPI ID 125: disabled MADT: Found CPU APIC ID 0 ACPI ID 126: disabled MADT: Found CPU APIC ID 0 ACPI ID 127: disabled Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #2 r+9b25356-dirty: Thu May 23 18:49:22 UTC 2013 root@ip-10-148-177-216:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. XEN: Disabling emulated block and network devices Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff818ca000. Hypervisor: Origin = "XenVMMXenVMM" Calibrating TSC clock ... TSC clock: 2600046368 Hz CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.05-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> Features2=0x9fba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,HV> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> real memory = 262144000000 (250000 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x00000000019e1000 - 0x00000000efffffff, 3999395840 bytes (976415 pages) 0x0000000100000000 - 0x0000003b8ae37fff, 251438268416 bytes (61386296 pages) avail memory = 244393992192 (233072 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <Xen HVM> INTR: Adding local APIC 1 as a target INTR: Adding local APIC 2 as a target INTR: Adding local APIC 3 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 5 as a target INTR: Adding local APIC 6 as a target INTR: Adding local APIC 7 as a target INTR: Adding local APIC 8 as a target INTR: Adding local APIC 9 as a target INTR: Adding local APIC 10 as a target INTR: Adding local APIC 11 as a target INTR: Adding local APIC 12 as a target INTR: Adding local APIC 13 as a target INTR: Adding local APIC 14 as a target INTR: Adding local APIC 15 as a target INTR: Adding local APIC 32 as a target INTR: Adding local APIC 33 as a target INTR: Adding local APIC 34 as a target INTR: Adding local APIC 35 as a target INTR: Adding local APIC 36 as a target INTR: Adding local APIC 37 as a target INTR: Adding local APIC 38 as a target INTR: Adding local APIC 39 as a target INTR: Adding local APIC 40 as a target INTR: Adding local APIC 41 as a target INTR: Adding local APIC 42 as a target INTR: Adding local APIC 43 as a target INTR: Adding local APIC 44 as a target INTR: Adding local APIC 45 as a target INTR: Adding local APIC 46 as a target INTR: Adding local APIC 47 as a target FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 12 cpu13 (AP): APIC ID: 13 cpu14 (AP): APIC ID: 14 cpu15 (AP): APIC ID: 15 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 33 cpu18 (AP): APIC ID: 34 cpu19 (AP): APIC ID: 35 cpu20 (AP): APIC ID: 36 cpu21 (AP): APIC ID: 37 cpu22 (AP): APIC ID: 38 cpu23 (AP): APIC ID: 39 cpu24 (AP): APIC ID: 40 cpu25 (AP): APIC ID: 41 cpu26 (AP): APIC ID: 42 cpu27 (AP): APIC ID: 43 cpu28 (AP): APIC ID: 44 cpu29 (AP): APIC ID: 45 cpu30 (AP): APIC ID: 46 cpu31 (AP): APIC ID: 47 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 16 APIC: CPU 2 has ACPI ID 1 APIC: CPU 3 has ACPI ID 17 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 18 APIC: CPU 6 has ACPI ID 3 APIC: CPU 7 has ACPI ID 19 APIC: CPU 8 has ACPI ID 4 APIC: CPU 9 has ACPI ID 20 APIC: CPU 10 has ACPI ID 5 APIC: CPU 11 has ACPI ID 21 APIC: CPU 12 has ACPI ID 6 APIC: CPU 13 has ACPI ID 22 APIC: CPU 14 has ACPI ID 7 APIC: CPU 15 has ACPI ID 23 APIC: CPU 16 has ACPI ID 8 APIC: CPU 17 has ACPI ID 24 APIC: CPU 18 has ACPI ID 9 APIC: CPU 19 has ACPI ID 25 APIC: CPU 20 has ACPI ID 10 APIC: CPU 21 has ACPI ID 26 APIC: CPU 22 has ACPI ID 11 APIC: CPU 23 has ACPI ID 27 APIC: CPU 24 has ACPI ID 12 APIC: CPU 25 has ACPI ID 28 APIC: CPU 26 has ACPI ID 13 APIC: CPU 27 has ACPI ID 29 APIC: CPU 28 has ACPI ID 14 APIC: CPU 29 has ACPI ID 30 APIC: CPU 30 has ACPI ID 15 APIC: CPU 31 has ACPI ID 31 x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 x86bios: SSEG 0x001000-0x001fff at 0xffffff80005e3000 x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 random device not loaded; using insecure entropy ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ULE: setup cpu 4 ULE: setup cpu 5 ULE: setup cpu 6 ULE: setup cpu 7 ULE: setup cpu 8 ULE: setup cpu 9 ULE: setup cpu 10 ULE: setup cpu 11 ULE: setup cpu 12 ULE: setup cpu 13 ULE: setup cpu 14 ULE: setup cpu 15 ULE: setup cpu 16 ULE: setup cpu 17 ULE: setup cpu 18 ULE: setup cpu 19 ULE: setup cpu 20 ULE: setup cpu 21 ULE: setup cpu 22 ULE: setup cpu 23 ULE: setup cpu 24 ULE: setup cpu 25 ULE: setup cpu 26 ULE: setup cpu 27 ULE: setup cpu 28 ULE: setup cpu 29 ULE: setup cpu 30 ULE: setup cpu 31 ACPI: RSDP 0xea020 00024 (v02 Xen) ACPI: XSDT 0xfc015920 0005C (v01 Xen HVM 00000000 HVML 00000000) ACPI: FACP 0xfc014980 000F4 (v04 Xen HVM 00000000 HVML 00000000) ACPI: DSDT 0xfc0035e0 11315 (v02 Xen HVM 00000000 INTL 20090123) ACPI: FACS 0xfc0035a0 00040 ACPI: APIC 0xfc014a80 00460 (v02 Xen HVM 00000000 HVML 00000000) ACPI: SRAT 0xfc014f60 008A8 (v01 Xen HVM 00000000 HVML 00000000) ACPI: HPET 0xfc015830 00038 (v01 Xen HVM 00000000 HVML 00000000) ACPI: WAET 0xfc015870 00028 (v01 Xen HVM 00000000 HVML 00000000) ACPI: SSDT 0xfc0158a0 00031 (v02 Xen HVM 00000000 INTL 20090123) ACPI: SSDT 0xfc0158e0 00031 (v02 Xen HVM 00000000 INTL 20090123) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 5, irq 5 ioapic0: intpin 5 trigger: level ioapic0: intpin 5 polarity: low MADT: Interrupt override: source 10, irq 10 ioapic0: intpin 10 trigger: level ioapic0: intpin 10 polarity: low MADT: Interrupt override: source 11, irq 11 ioapic0: intpin 11 trigger: level ioapic0: intpin 11 polarity: low MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 <Version 1.1> irqs 0-47 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 wlan: <802.11 Link Layer> Event-channel device installed. snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 kbd: new array size 4 kbd1 at kbdmux0 mem: <memory> nfslock: pseudo-device null: <null device, zero device> random: <entropy source, Software, Yarrow> VESA: INT 0x10 vector 0xc000:0x836e VESA: information block 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 15 mode(s) found VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80005fd040 (2000040) VESA: VGABIOS Cirrus extension VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0 io: <I/O> hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 hpt27xx: RocketRAID 27xx controller driver v1.0 xen_et0: <Xen PV Clock> on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 xen_et0: registered as a time-of-day clock (resolution 10000000us, adjustment 5.000000000s) acpi0: <Xen> on motherboard ACPI: All ACPI Tables successfully acquired ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: Processor \_SB_.PR00 (ACPI ID 0) -> APIC ID 0 cpu0: <ACPI CPU> on acpi0 cpu0: switching to generic Cx mode cpu1: Processor \_SB_.PR01 (ACPI ID 1) -> APIC ID 2 cpu1: <ACPI CPU> on acpi0 cpu2: Processor \_SB_.PR02 (ACPI ID 2) -> APIC ID 4 cpu2: <ACPI CPU> on acpi0 cpu3: Processor \_SB_.PR03 (ACPI ID 3) -> APIC ID 6 cpu3: <ACPI CPU> on acpi0 cpu4: Processor \_SB_.PR04 (ACPI ID 4) -> APIC ID 8 cpu4: <ACPI CPU> on acpi0 cpu5: Processor \_SB_.PR05 (ACPI ID 5) -> APIC ID 10 cpu5: <ACPI CPU> on acpi0 cpu6: Processor \_SB_.PR06 (ACPI ID 6) -> APIC ID 12 cpu6: <ACPI CPU> on acpi0 cpu7: Processor \_SB_.PR07 (ACPI ID 7) -> APIC ID 14 cpu7: <ACPI CPU> on acpi0 cpu8: Processor \_SB_.PR08 (ACPI ID 8) -> APIC ID 16 cpu8: <ACPI CPU> on acpi0 cpu9: Processor \_SB_.PR09 (ACPI ID 9) -> APIC ID 18 cpu9: <ACPI CPU> on acpi0 cpu10: Processor \_SB_.PR0A (ACPI ID 10) -> APIC ID 20 cpu10: <ACPI CPU> on acpi0 cpu11: Processor \_SB_.PR0B (ACPI ID 11) -> APIC ID 22 cpu11: <ACPI CPU> on acpi0 cpu12: Processor \_SB_.PR0C (ACPI ID 12) -> APIC ID 24 cpu12: <ACPI CPU> on acpi0 cpu13: Processor \_SB_.PR0D (ACPI ID 13) -> APIC ID 26 cpu13: <ACPI CPU> on acpi0 cpu14: Processor \_SB_.PR0E (ACPI ID 14) -> APIC ID 28 cpu14: <ACPI CPU> on acpi0 cpu15: Processor \_SB_.PR0F (ACPI ID 15) -> APIC ID 30 cpu15: <ACPI CPU> on acpi0 cpu16: Processor \_SB_.PR10 (ACPI ID 16) -> APIC ID 1 cpu16: <ACPI CPU> on acpi0 cpu17: Processor \_SB_.PR11 (ACPI ID 17) -> APIC ID 3 cpu17: <ACPI CPU> on acpi0 cpu18: Processor \_SB_.PR12 (ACPI ID 18) -> APIC ID 5 cpu18: <ACPI CPU> on acpi0 cpu19: Processor \_SB_.PR13 (ACPI ID 19) -> APIC ID 7 cpu19: <ACPI CPU> on acpi0 cpu20: Processor \_SB_.PR14 (ACPI ID 20) -> APIC ID 9 cpu20: <ACPI CPU> on acpi0 cpu21: Processor \_SB_.PR15 (ACPI ID 21) -> APIC ID 11 cpu21: <ACPI CPU> on acpi0 cpu22: Processor \_SB_.PR16 (ACPI ID 22) -> APIC ID 13 cpu22: <ACPI CPU> on acpi0 cpu23: Processor \_SB_.PR17 (ACPI ID 23) -> APIC ID 15 cpu23: <ACPI CPU> on acpi0 cpu24: Processor \_SB_.PR18 (ACPI ID 24) -> APIC ID 17 cpu24: <ACPI CPU> on acpi0 cpu25: Processor \_SB_.PR19 (ACPI ID 25) -> APIC ID 19 cpu25: <ACPI CPU> on acpi0 cpu26: Processor \_SB_.PR1A (ACPI ID 26) -> APIC ID 21 cpu26: <ACPI CPU> on acpi0 cpu27: Processor \_SB_.PR1B (ACPI ID 27) -> APIC ID 23 cpu27: <ACPI CPU> on acpi0 cpu28: Processor \_SB_.PR1C (ACPI ID 28) -> APIC ID 25 cpu28: <ACPI CPU> on acpi0 cpu29: Processor \_SB_.PR1D (ACPI ID 29) -> APIC ID 27 cpu29: <ACPI CPU> on acpi0 cpu30: Processor \_SB_.PR1E (ACPI ID 30) -> APIC ID 29 cpu30: <ACPI CPU> on acpi0 cpu31: Processor \_SB_.PR1F (ACPI ID 31) -> APIC ID 31 cpu31: <ACPI CPU> on acpi0 ACPI: Processor \_SB_.PR20 (ACPI ID 32) ignored ACPI: Processor \_SB_.PR21 (ACPI ID 33) ignored ACPI: Processor \_SB_.PR22 (ACPI ID 34) ignored ACPI: Processor \_SB_.PR23 (ACPI ID 35) ignored ACPI: Processor \_SB_.PR24 (ACPI ID 36) ignored ACPI: Processor \_SB_.PR25 (ACPI ID 37) ignored ACPI: Processor \_SB_.PR26 (ACPI ID 38) ignored ACPI: Processor \_SB_.PR27 (ACPI ID 39) ignored ACPI: Processor \_SB_.PR28 (ACPI ID 40) ignored ACPI: Processor \_SB_.PR29 (ACPI ID 41) ignored ACPI: Processor \_SB_.PR2A (ACPI ID 42) ignored ACPI: Processor \_SB_.PR2B (ACPI ID 43) ignored ACPI: Processor \_SB_.PR2C (ACPI ID 44) ignored ACPI: Processor \_SB_.PR2D (ACPI ID 45) ignored ACPI: Processor \_SB_.PR2E (ACPI ID 46) ignored ACPI: Processor \_SB_.PR2F (ACPI ID 47) ignored ACPI: Processor \_SB_.PR30 (ACPI ID 48) ignored ACPI: Processor \_SB_.PR31 (ACPI ID 49) ignored ACPI: Processor \_SB_.PR32 (ACPI ID 50) ignored ACPI: Processor \_SB_.PR33 (ACPI ID 51) ignored ACPI: Processor \_SB_.PR34 (ACPI ID 52) ignored ACPI: Processor \_SB_.PR35 (ACPI ID 53) ignored ACPI: Processor \_SB_.PR36 (ACPI ID 54) ignored ACPI: Processor \_SB_.PR37 (ACPI ID 55) ignored ACPI: Processor \_SB_.PR38 (ACPI ID 56) ignored ACPI: Processor \_SB_.PR39 (ACPI ID 57) ignored ACPI: Processor \_SB_.PR3A (ACPI ID 58) ignored ACPI: Processor \_SB_.PR3B (ACPI ID 59) ignored ACPI: Processor \_SB_.PR3C (ACPI ID 60) ignored ACPI: Processor \_SB_.PR3D (ACPI ID 61) ignored ACPI: Processor \_SB_.PR3E (ACPI ID 62) ignored ACPI: Processor \_SB_.PR3F (ACPI ID 63) ignored ACPI: Processor \_SB_.PR40 (ACPI ID 64) ignored ACPI: Processor \_SB_.PR41 (ACPI ID 65) ignored ACPI: Processor \_SB_.PR42 (ACPI ID 66) ignored ACPI: Processor \_SB_.PR43 (ACPI ID 67) ignored ACPI: Processor \_SB_.PR44 (ACPI ID 68) ignored ACPI: Processor \_SB_.PR45 (ACPI ID 69) ignored ACPI: Processor \_SB_.PR46 (ACPI ID 70) ignored ACPI: Processor \_SB_.PR47 (ACPI ID 71) ignored ACPI: Processor \_SB_.PR48 (ACPI ID 72) ignored ACPI: Processor \_SB_.PR49 (ACPI ID 73) ignored ACPI: Processor \_SB_.PR4A (ACPI ID 74) ignored ACPI: Processor \_SB_.PR4B (ACPI ID 75) ignored ACPI: Processor \_SB_.PR4C (ACPI ID 76) ignored ACPI: Processor \_SB_.PR4D (ACPI ID 77) ignored ACPI: Processor \_SB_.PR4E (ACPI ID 78) ignored ACPI: Processor \_SB_.PR4F (ACPI ID 79) ignored ACPI: Processor \_SB_.PR50 (ACPI ID 80) ignored ACPI: Processor \_SB_.PR51 (ACPI ID 81) ignored ACPI: Processor \_SB_.PR52 (ACPI ID 82) ignored ACPI: Processor \_SB_.PR53 (ACPI ID 83) ignored ACPI: Processor \_SB_.PR54 (ACPI ID 84) ignored ACPI: Processor \_SB_.PR55 (ACPI ID 85) ignored ACPI: Processor \_SB_.PR56 (ACPI ID 86) ignored ACPI: Processor \_SB_.PR57 (ACPI ID 87) ignored ACPI: Processor \_SB_.PR58 (ACPI ID 88) ignored ACPI: Processor \_SB_.PR59 (ACPI ID 89) ignored ACPI: Processor \_SB_.PR5A (ACPI ID 90) ignored ACPI: Processor \_SB_.PR5B (ACPI ID 91) ignored ACPI: Processor \_SB_.PR5C (ACPI ID 92) ignored ACPI: Processor \_SB_.PR5D (ACPI ID 93) ignored ACPI: Processor \_SB_.PR5E (ACPI ID 94) ignored ACPI: Processor \_SB_.PR5F (ACPI ID 95) ignored ACPI: Processor \_SB_.PR60 (ACPI ID 96) ignored ACPI: Processor \_SB_.PR61 (ACPI ID 97) ignored ACPI: Processor \_SB_.PR62 (ACPI ID 98) ignored ACPI: Processor \_SB_.PR63 (ACPI ID 99) ignored ACPI: Processor \_SB_.PR64 (ACPI ID 100) ignored ACPI: Processor \_SB_.PR65 (ACPI ID 101) ignored ACPI: Processor \_SB_.PR66 (ACPI ID 102) ignored ACPI: Processor \_SB_.PR67 (ACPI ID 103) ignored ACPI: Processor \_SB_.PR68 (ACPI ID 104) ignored ACPI: Processor \_SB_.PR69 (ACPI ID 105) ignored ACPI: Processor \_SB_.PR6A (ACPI ID 106) ignored ACPI: Processor \_SB_.PR6B (ACPI ID 107) ignored ACPI: Processor \_SB_.PR6C (ACPI ID 108) ignored ACPI: Processor \_SB_.PR6D (ACPI ID 109) ignored ACPI: Processor \_SB_.PR6E (ACPI ID 110) ignored ACPI: Processor \_SB_.PR6F (ACPI ID 111) ignored ACPI: Processor \_SB_.PR70 (ACPI ID 112) ignored ACPI: Processor \_SB_.PR71 (ACPI ID 113) ignored ACPI: Processor \_SB_.PR72 (ACPI ID 114) ignored ACPI: Processor \_SB_.PR73 (ACPI ID 115) ignored ACPI: Processor \_SB_.PR74 (ACPI ID 116) ignored ACPI: Processor \_SB_.PR75 (ACPI ID 117) ignored ACPI: Processor \_SB_.PR76 (ACPI ID 118) ignored ACPI: Processor \_SB_.PR77 (ACPI ID 119) ignored ACPI: Processor \_SB_.PR78 (ACPI ID 120) ignored ACPI: Processor \_SB_.PR79 (ACPI ID 121) ignored ACPI: Processor \_SB_.PR7A (ACPI ID 122) ignored ACPI: Processor \_SB_.PR7B (ACPI ID 123) ignored ACPI: Processor \_SB_.PR7C (ACPI ID 124) ignored ACPI: Processor \_SB_.PR7D (ACPI ID 125) ignored ACPI: Processor \_SB_.PR7E (ACPI ID 126) ignored ACPI: Processor \_SB_.PR7F (ACPI ID 127) ignored hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 atrtc0: not installed as time-of-day clock: clock xen_et has higher resolution ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50 Event timer "RTC" frequency 32768 Hz quality 0 ACPI timer: 1/20 1/19 1/19 1/20 1/19 1/23 1/20 1/19 1/18 1/17 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 10 11 Validation 0 10 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 10 11 Validation 0 11 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xf0000000-0xfbffffff pci0: <ACPI PCI bus> on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x1237, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7000, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7010, revid=0x00 domain=0, bus=0, slot=1, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1 found-> vendor=0x8086, dev=0x7113, revid=0x01 domain=0, bus=0, slot=1, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 20 found-> vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, enabled pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0 map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0 found-> vendor=0x5853, dev=0x0001, revid=0x01 domain=0, bus=0, slot=3, func=0 class=ff-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, enabled pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0 pcib0: matched entry for 0.3.INTA pcib0: slot 3 INTA hardwired to IRQ 28 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51 ata1: <ATA channel> at channel 1 on atapci0 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53 xenstore0: <XenStore> on xenpci0 Grant table initialized psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0061 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54 atkbd0: [GIANT-LOCKED] psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 00 02 64 psm0: <PS/2 Mouse> irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56 uart0: fast interrupt uart0: console (9600,n,8,1) ACPI: Enabled 2 GPEs in block 00 to 0F acpi0: wakeup code va 0xffffffc2ce049000 pa 0x30000 ahc_isa_identify 0: ioport 0xc00 alloc failed ahc_isa_identify 1: ioport 0x1c00 alloc failed ahc_isa_identify 2: ioport 0x2c00 alloc failed ahc_isa_identify 3: ioport 0x3c00 alloc failed ahc_isa_identify 4: ioport 0x4c00 alloc failed ahc_isa_identify 5: ioport 0x5c00 alloc failed ahc_isa_identify 6: ioport 0x6c00 alloc failed ahc_isa_identify 7: ioport 0x7c00 alloc failed ahc_isa_identify 8: ioport 0x8c00 alloc failed ahc_isa_identify 9: ioport 0x9c00 alloc failed ahc_isa_identify 10: ioport 0xac00 alloc failed ahc_isa_identify 11: ioport 0xbc00 alloc failed ahc_isa_identify 12: ioport 0xcc00 alloc failed ahc_isa_identify 13: ioport 0xdc00 alloc failed ahc_isa_identify 14: ioport 0xec00 alloc failed pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 ex_isa_identify() isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it uart: uart0 already exists; skipping it isa_probe_children: probing non-PnP devices sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 fdc0: No FDOUT register! fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2097152 lo0: bpf attached hptrr: no controller detected. hpt27xx: no controller detected. xctrl0: <Xen Control Device> on xenstore0 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 xenbusb_front0: <Xen Frontend Devices> on xenstore0 ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x0 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x0 xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 22:00:0a:94:b5:05 xenbusb_back0: <Xen Backend Devices> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 10240MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: barriers GEOM: new disk ad0 xbd1: 122866MB <Virtual Block Device> at device/vbd/51728 on xenbusb_front0 xbd1: disk supports cache flush using: flush xbd2: 122866MB <Virtual Block Device> at device/vbd/51744 on xenbusb_front0 xbd2: disk supports cache flush using: flush SMP: AP CPU #4 Launched! cpu4 AP: ID: 0x04000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #10 Launched! cpu10 AP: ID: 0x0a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #11 Launched! cpu11 AP: ID: 0x0b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #16 Launched! cpu16 AP: ID: 0x20000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #22 Launched! cpu22 AP: ID: 0x26000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #23 Launched! cpu23 AP: ID: 0x27000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #19 Launched! cpu19 AP: ID: 0x23000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #17 Launched! cpu17 AP: ID: 0x21000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #7 Launched! cpu7 AP: ID: 0x07000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #27 Launched! cpu27 AP: ID: 0x2b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #26 Launched! cpu26 AP: ID: 0x2a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #25 Launched! cpu25 AP: ID: 0x29000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #21 Launched! cpu21 AP: ID: 0x25000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #20 Launched! cpu20 AP: ID: 0x24000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #29 Launched! cpu29 AP: ID: 0x2d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #31 Launched! cpu31 AP: ID: 0x2f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #18 Launched! cpu18 AP: ID: 0x22000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #30 Launched! cpu30 AP: ID: 0x2e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #13 Launched! cpu13 AP: ID: 0x0d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #24 Launched! cpu24 AP: ID: 0x28000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #28 Launched! cpu28 AP: ID: 0x2c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #8 Launched! cpu8 AP: ID: 0x08000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #14 Launched! cpu14 AP: ID: 0x0e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #5 Launched! cpu5 AP: ID: 0x05000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #12 Launched! cpu12 AP: ID: 0x0c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #15 Launched! cpu15 AP: ID: 0x0f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #6 Launched! cpu6 AP: ID: 0x06000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #9 Launched! cpu9 AP: ID: 0x09000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 panic: xen_et0: Error -22 setting singleshot timer to 506167555095805 for vCPU#1 cpuid = 1 KDB: stack backtrace: #0 0xffffffff808e6ed0 at kdb_backtrace+0x60 #1 0xffffffff808b22b6 at vpanic+0x126 #2 0xffffffff808b2343 at panic+0x43 #3 0xffffffff807a445a at xentimer_et_start+0xca #4 0xffffffff80cb365d at loadtimer+0xfd #5 0xffffffff80cb38d7 at cpu_new_callout+0xc7 #6 0xffffffff808c5ca1 at callout_process+0x2c1 #7 0xffffffff80cb25d5 at handleevents+0x185 #8 0xffffffff80cb324b at cpu_initclocks_ap+0xcb #9 0xffffffff80c2fc84 at init_secondary+0x474 Uptime: 3s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Mon, May 13, 2013 at 2:32 PM, Roger Pau Monné <roger.pau@citrix.com>wrote:> Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. > The main benefits of this changes are that Xen virtual interrupts (event > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when running > as an HVM guest, which should provide better time keeping and reduce the > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. > > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. > > The code is available in the following git repository, under the branch > pvhvm_v5: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > > Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMHey Guys, Huge KUDOS to some great work, Ive gotten 4 VMs booting from zfsonroot with the rev_9 finally under XCP 1.6 after getting through removal of the cdrom device from VMs, they are booted and running supremely nice now. IO for zfs filesystems is much better inside the VMs now, even with 4mb compared to what it was. This is a huge move forward and personally I just wanted to say thanks for this and all the work you put into it. The VMs appear quite stable for me, and are pleasantly responsive with low mem on zpools. Great job and again..... Thanks. Keep up the great effort.> > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Mon, May 13, 2013 at 2:32 PM, Roger Pau Monné <roger.pau@citrix.com>wrote:> Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. > The main benefits of this changes are that Xen virtual interrupts (event > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when running > as an HVM guest, which should provide better time keeping and reduce the > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. > > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. > > The code is available in the following git repository, under the branch > pvhvm_v5: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > > Also, I''ve created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVMHey Guys, Huge KUDOS to some great work, Ive gotten 4 VMs booting from zfsonroot with the rev_9 finally under XCP 1.6 after getting through removal of the cdrom device from VMs, they are booted and running supremely nice now. IO for zfs filesystems is much better inside the VMs now, even with 4mb compared to what it was. This is a huge move forward and personally I just wanted to say thanks for this and all the work you put into it. The VMs appear quite stable for me, and are pleasantly responsive with low mem on zpools. Great job and again..... Thanks. Keep up the great effort.> > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi,
I''ve just successfully run FreeBSD 9.1 based guest with
''pvhvm_v8'' based kernel under Xen 4.2.2.
So I couldn''t confirm any issue with the kernel both on Xen 3.4.4 and
4.2.2.
Nice Job.
Hypervisor details:
# xm info
host : ********
release : 3.8.7-1.el6xen
version : #1 SMP Tue Apr 16 13:14:14 EEST 2013
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1995
hw_caps :
bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 16374
free_memory : 7194
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .2
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : dom0_mem=409600
cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
cc_compile_by : mockbuild
cc_compile_domain : ********
cc_compile_date : Tue May 7 19:26:49 EST 2013
xend_config_format : 4
DomU details:
# xm list --long f2tbrxodmgk9ng
(domain
(domid 146)
(cpu_weight 400)
(cpu_cap 0)
(pool_name Pool-0)
(bootloader '''')
(vcpus 4)
(cpus (() () () ()))
(on_poweroff destroy)
(description '''')
(on_crash restart)
(uuid 355cfb26-4793-f85a-e330-7b6bfcae49b5)
(bootloader_args '''')
(name f2tbrxodmgk9ng)
(on_reboot restart)
(maxmem 1024)
(memory 1024)
(shadow_memory 12)
(features '''')
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1369384081.34)
(cpu_time 59.956655605)
(online_vcpus 4)
(image
(hvm
(kernel '''')
(superpages 0)
(videoram 4)
(hpet 0)
(stdvga 0)
(loader /usr/lib/xen/boot/hvmloader)
(xen_platform_pci 1)
(nestedhvm 0)
(rtc_timeoffset 10801)
(pci ())
(hap 1)
(localtime 0)
(timer_mode 1)
(pci_msitranslate 1)
(oos 1)
(apic 1)
(usbdevice tablet)
(vpt_align 1)
(vncunused 1)
(boot cd)
(pae 1)
(viridian 0)
(acpi 1)
(vnc 1)
(nographic 0)
(nomigrate 0)
(usb 0)
(tsc_mode 0)
(guest_os_type default)
(device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0)
(xauthority /root/.Xauthority)
(isa 0)
(notes (SUSPEND_CANCEL 1))
)
)
(status 2)
(state -b----)
(store_mfn 1044476)
(device
(vif
(bridge nnl9l2z5l3q3d8)
(uuid daeabd68-05a0-f25b-ba65-394627505b50)
(script /etc/xen/scripts/vif-bridge)
(ip 109.123.91.166)
(mac 00:16:3e:e8:88:49)
(vifname qgdvmt5h6d2l9s)
(backend 0)
)
)
(device
(console
(protocol vt100)
(location 7)
(uuid c670a71d-4c3b-1fcb-974a-587f17740a6c)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 9067929c-9b48-99c6-5526-e771d43f427c)
(bootable 1)
(dev hda:disk)
(uname phy:/dev/fv4zl7t2h5wbeq/o76ciuubu0r986)
(mode w)
(backend 0)
(VDI '''')
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 2ae3630e-0e8e-04e4-8caf-ac4d1e9fd402)
(bootable 0)
(dev hdb:disk)
(uname phy:/dev/fv4zl7t2h5wbeq/xi0nw7u4zo0bu9)
(mode w)
(backend 0)
(VDI '''')
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 33d3e25c-0c1c-ced6-c8b6-5a706ab0d403)
(bootable 0)
(dev hdc:cdrom)
(uname file:/tools/freebsd/boot-freebsd-generic.iso)
(mode r)
(backend 0)
(VDI '''')
)
)
(device
(vfb
(vncunused 1)
(vnc 1)
(uuid 438a2ffd-bec7-1e54-bb0b-4fdd400517cf)
(location 0.0.0.0:5908)
)
)
)
DomU from "inside":
# uname -a
FreeBSD yurak2.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Thu May 23
18:55:33 AST 2013 root@yurak2.vm:/usr/obj/freebsd/sys/XENHVM amd64
---
Yura
On May 22, 2013, at 18:27 PM, Yuriy Kohut <ykohut@onapp.com> wrote:
> Hi,
>
> I''ve just successfully run FreeBSD 9.1 based guest with
''pvhvm_v8'' based kernel under Xen 3.4.4.
>
> Hypervisor details:
> # xm info
> host : *******
> release : 2.6.18-348.2.1.el5xen
> version : #1 SMP Tue Mar 5 17:05:33 EST 2013
> machine : x86_64
> nr_cpus : 4
> nr_nodes : 1
> cores_per_socket : 4
> threads_per_core : 1
> cpu_mhz : 2128
> hw_caps :
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
> virt_caps : hvm
> total_memory : 6135
> free_memory : 262
> node_to_cpu : node0:0-3
> node_to_memory : node0:262
> xen_major : 3
> xen_minor : 4
> xen_extra : .4
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : unavailable
> cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)
> cc_compile_by : root
> cc_compile_domain : ******
> cc_compile_date : Wed Sep 5 18:01:10 EEST 2012
> xend_config_format : 4
>
>
> DomU details:
> # xm list --long h283bpm53f9rnx
> (domain
> (domid 61)
> (on_crash restart)
> (uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051)
> (bootloader_args )
> (vcpus 2)
> (name h283bpm53f9rnx)
> (on_poweroff destroy)
> (on_reboot restart)
> (cpus (() ()))
> (bootloader )
> (maxmem 1024)
> (memory 1024)
> (shadow_memory 10)
> (features )
> (on_xend_start ignore)
> (on_xend_stop ignore)
> (start_time 1369235607.92)
> (cpu_time 31.914003553)
> (online_vcpus 2)
> (image
> (hvm
> (kernel )
> (videoram 4)
> (hpet 0)
> (stdvga 0)
> (loader /usr/lib/xen/boot/hvmloader)
> (vncunused 1)
> (xen_platform_pci 1)
> (boot cd)
> (rtc_timeoffset 7202)
> (pci ())
> (pae 1)
> (vpt_align 1)
> (hap 1)
> (viridian 0)
> (acpi 1)
> (localtime 0)
> (timer_mode 1)
> (vnc 1)
> (nographic 0)
> (guest_os_type default)
> (pci_msitranslate 1)
> (apic 1)
> (monitor 0)
> (usbdevice tablet)
> (device_model /usr/lib64/xen/bin/qemu-dm)
> (pci_power_mgmt 0)
> (usb 0)
> (xauthority /root/.Xauthority)
> (isa 0)
> (notes (SUSPEND_CANCEL 1))
> )
> )
> (status 2)
> (state -b----)
> (store_mfn 1044476)
> (device
> (vif
> (bridge xnh5getjoj54ke)
> (uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe)
> (script /etc/xen/scripts/vif-bridge)
> (ip 83.170.81.183)
> (mac 00:16:3e:a4:02:5a)
> (vifname t2vd5w22msrv5d)
> (backend 0)
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a)
> (bootable 1)
> (dev hda:disk)
> (uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby)
> (mode w)
> (backend 0)
> (bootable 1)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba)
> (bootable 0)
> (dev hdb:disk)
> (uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd)
> (mode w)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 2b97ec8c-0cc5-7197-f510-63c272449680)
> (bootable 0)
> (dev hdc:disk)
> (uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq)
> (mode w)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7)
> (bootable 0)
> (dev hdd:cdrom)
> (uname file:/tools/freebsd/boot-freebsd-generic.iso)
> (mode r)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vfb
> (vncunused 1)
> (vnc 1)
> (uuid b3defeea-4acc-1408-9b22-71547a64e705)
> (location 0.0.0.0:5900)
> )
> )
> (device
> (console
> (protocol vt100)
> (location 4)
> (uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da)
> )
> )
> )
>
>
> DomU from "inside":
> # uname -a
> FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed May
22 17:47:40 EEST 2013 root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64
>
>
> I''ll also set up one (hope will have some time) under Xen 4.2.2
tomorrow.
> ---
> Yura
>
> On May 13, 2013, at 21:32 PM, Roger Pau Monné <roger.pau@citrix.com>
wrote:
>
>> Hello,
>>
>> Recently Justin T Gibbs, Will Andrews and myself have been working on
>> improving the Xen support in FreeBSD. The main goal of this was to
bring
>> full PVHVM support to FreeBSD, right now FreeBSD is only using PV
>> interfaces for disk and network interfaces when running as a HVM guest.
>> The main benefits of this changes are that Xen virtual interrupts
(event
>> channels) are now delivered to the guest using a vector callback
>> injection, that is a per-cpu mechanism that allows each vCPU to have
>> different interrupts assigned, so for example network and disk
>> interrupts are delivered to different vCPUs in order to improve
>> performance. With this changes FreeBSD also uses PV timers when running
>> as an HVM guest, which should provide better time keeping and reduce
the
>> virtualization overhead, since emulated timers are no longer used. PV
>> IPIs can also be used inside a HVM guest, but this will be implemented
>> later.
>>
>> Right now the code is in a state where it can be tested by users, so we
>> would like to encourage FreeBSD and Xen users to test it and provide
>> feedback.
>>
>> The code is available in the following git repository, under the branch
>> pvhvm_v5:
>>
>> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary
>>
>> Also, I''ve created a wiki page that explains how to set up a
FreeBSD
>> PVHVM for testing:
>>
>> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
>> _______________________________________________
>> freebsd-xen@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
>> To unsubscribe, send any mail to
"freebsd-xen-unsubscribe@freebsd.org"
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Hi,
I''ve just successfully run FreeBSD 9.1 based guest with
''pvhvm_v8'' based kernel under Xen 4.2.2.
So I couldn''t confirm any issue with the kernel both on Xen 3.4.4 and
4.2.2.
Nice Job.
Hypervisor details:
# xm info
host : ********
release : 3.8.7-1.el6xen
version : #1 SMP Tue Apr 16 13:14:14 EEST 2013
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1995
hw_caps :
bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 16374
free_memory : 7194
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .2
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : dom0_mem=409600
cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
cc_compile_by : mockbuild
cc_compile_domain : ********
cc_compile_date : Tue May 7 19:26:49 EST 2013
xend_config_format : 4
DomU details:
# xm list --long f2tbrxodmgk9ng
(domain
(domid 146)
(cpu_weight 400)
(cpu_cap 0)
(pool_name Pool-0)
(bootloader '''')
(vcpus 4)
(cpus (() () () ()))
(on_poweroff destroy)
(description '''')
(on_crash restart)
(uuid 355cfb26-4793-f85a-e330-7b6bfcae49b5)
(bootloader_args '''')
(name f2tbrxodmgk9ng)
(on_reboot restart)
(maxmem 1024)
(memory 1024)
(shadow_memory 12)
(features '''')
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1369384081.34)
(cpu_time 59.956655605)
(online_vcpus 4)
(image
(hvm
(kernel '''')
(superpages 0)
(videoram 4)
(hpet 0)
(stdvga 0)
(loader /usr/lib/xen/boot/hvmloader)
(xen_platform_pci 1)
(nestedhvm 0)
(rtc_timeoffset 10801)
(pci ())
(hap 1)
(localtime 0)
(timer_mode 1)
(pci_msitranslate 1)
(oos 1)
(apic 1)
(usbdevice tablet)
(vpt_align 1)
(vncunused 1)
(boot cd)
(pae 1)
(viridian 0)
(acpi 1)
(vnc 1)
(nographic 0)
(nomigrate 0)
(usb 0)
(tsc_mode 0)
(guest_os_type default)
(device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0)
(xauthority /root/.Xauthority)
(isa 0)
(notes (SUSPEND_CANCEL 1))
)
)
(status 2)
(state -b----)
(store_mfn 1044476)
(device
(vif
(bridge nnl9l2z5l3q3d8)
(uuid daeabd68-05a0-f25b-ba65-394627505b50)
(script /etc/xen/scripts/vif-bridge)
(ip 109.123.91.166)
(mac 00:16:3e:e8:88:49)
(vifname qgdvmt5h6d2l9s)
(backend 0)
)
)
(device
(console
(protocol vt100)
(location 7)
(uuid c670a71d-4c3b-1fcb-974a-587f17740a6c)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 9067929c-9b48-99c6-5526-e771d43f427c)
(bootable 1)
(dev hda:disk)
(uname phy:/dev/fv4zl7t2h5wbeq/o76ciuubu0r986)
(mode w)
(backend 0)
(VDI '''')
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 2ae3630e-0e8e-04e4-8caf-ac4d1e9fd402)
(bootable 0)
(dev hdb:disk)
(uname phy:/dev/fv4zl7t2h5wbeq/xi0nw7u4zo0bu9)
(mode w)
(backend 0)
(VDI '''')
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 33d3e25c-0c1c-ced6-c8b6-5a706ab0d403)
(bootable 0)
(dev hdc:cdrom)
(uname file:/tools/freebsd/boot-freebsd-generic.iso)
(mode r)
(backend 0)
(VDI '''')
)
)
(device
(vfb
(vncunused 1)
(vnc 1)
(uuid 438a2ffd-bec7-1e54-bb0b-4fdd400517cf)
(location 0.0.0.0:5908)
)
)
)
DomU from "inside":
# uname -a
FreeBSD yurak2.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Thu May 23
18:55:33 AST 2013 root@yurak2.vm:/usr/obj/freebsd/sys/XENHVM amd64
---
Yura
On May 22, 2013, at 18:27 PM, Yuriy Kohut <ykohut@onapp.com> wrote:
> Hi,
>
> I''ve just successfully run FreeBSD 9.1 based guest with
''pvhvm_v8'' based kernel under Xen 3.4.4.
>
> Hypervisor details:
> # xm info
> host : *******
> release : 2.6.18-348.2.1.el5xen
> version : #1 SMP Tue Mar 5 17:05:33 EST 2013
> machine : x86_64
> nr_cpus : 4
> nr_nodes : 1
> cores_per_socket : 4
> threads_per_core : 1
> cpu_mhz : 2128
> hw_caps :
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
> virt_caps : hvm
> total_memory : 6135
> free_memory : 262
> node_to_cpu : node0:0-3
> node_to_memory : node0:262
> xen_major : 3
> xen_minor : 4
> xen_extra : .4
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : unavailable
> cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)
> cc_compile_by : root
> cc_compile_domain : ******
> cc_compile_date : Wed Sep 5 18:01:10 EEST 2012
> xend_config_format : 4
>
>
> DomU details:
> # xm list --long h283bpm53f9rnx
> (domain
> (domid 61)
> (on_crash restart)
> (uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051)
> (bootloader_args )
> (vcpus 2)
> (name h283bpm53f9rnx)
> (on_poweroff destroy)
> (on_reboot restart)
> (cpus (() ()))
> (bootloader )
> (maxmem 1024)
> (memory 1024)
> (shadow_memory 10)
> (features )
> (on_xend_start ignore)
> (on_xend_stop ignore)
> (start_time 1369235607.92)
> (cpu_time 31.914003553)
> (online_vcpus 2)
> (image
> (hvm
> (kernel )
> (videoram 4)
> (hpet 0)
> (stdvga 0)
> (loader /usr/lib/xen/boot/hvmloader)
> (vncunused 1)
> (xen_platform_pci 1)
> (boot cd)
> (rtc_timeoffset 7202)
> (pci ())
> (pae 1)
> (vpt_align 1)
> (hap 1)
> (viridian 0)
> (acpi 1)
> (localtime 0)
> (timer_mode 1)
> (vnc 1)
> (nographic 0)
> (guest_os_type default)
> (pci_msitranslate 1)
> (apic 1)
> (monitor 0)
> (usbdevice tablet)
> (device_model /usr/lib64/xen/bin/qemu-dm)
> (pci_power_mgmt 0)
> (usb 0)
> (xauthority /root/.Xauthority)
> (isa 0)
> (notes (SUSPEND_CANCEL 1))
> )
> )
> (status 2)
> (state -b----)
> (store_mfn 1044476)
> (device
> (vif
> (bridge xnh5getjoj54ke)
> (uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe)
> (script /etc/xen/scripts/vif-bridge)
> (ip 83.170.81.183)
> (mac 00:16:3e:a4:02:5a)
> (vifname t2vd5w22msrv5d)
> (backend 0)
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a)
> (bootable 1)
> (dev hda:disk)
> (uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby)
> (mode w)
> (backend 0)
> (bootable 1)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba)
> (bootable 0)
> (dev hdb:disk)
> (uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd)
> (mode w)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 2b97ec8c-0cc5-7197-f510-63c272449680)
> (bootable 0)
> (dev hdc:disk)
> (uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq)
> (mode w)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7)
> (bootable 0)
> (dev hdd:cdrom)
> (uname file:/tools/freebsd/boot-freebsd-generic.iso)
> (mode r)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vfb
> (vncunused 1)
> (vnc 1)
> (uuid b3defeea-4acc-1408-9b22-71547a64e705)
> (location 0.0.0.0:5900)
> )
> )
> (device
> (console
> (protocol vt100)
> (location 4)
> (uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da)
> )
> )
> )
>
>
> DomU from "inside":
> # uname -a
> FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed May
22 17:47:40 EEST 2013 root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64
>
>
> I''ll also set up one (hope will have some time) under Xen 4.2.2
tomorrow.
> ---
> Yura
>
> On May 13, 2013, at 21:32 PM, Roger Pau Monné <roger.pau@citrix.com>
wrote:
>
>> Hello,
>>
>> Recently Justin T Gibbs, Will Andrews and myself have been working on
>> improving the Xen support in FreeBSD. The main goal of this was to
bring
>> full PVHVM support to FreeBSD, right now FreeBSD is only using PV
>> interfaces for disk and network interfaces when running as a HVM guest.
>> The main benefits of this changes are that Xen virtual interrupts
(event
>> channels) are now delivered to the guest using a vector callback
>> injection, that is a per-cpu mechanism that allows each vCPU to have
>> different interrupts assigned, so for example network and disk
>> interrupts are delivered to different vCPUs in order to improve
>> performance. With this changes FreeBSD also uses PV timers when running
>> as an HVM guest, which should provide better time keeping and reduce
the
>> virtualization overhead, since emulated timers are no longer used. PV
>> IPIs can also be used inside a HVM guest, but this will be implemented
>> later.
>>
>> Right now the code is in a state where it can be tested by users, so we
>> would like to encourage FreeBSD and Xen users to test it and provide
>> feedback.
>>
>> The code is available in the following git repository, under the branch
>> pvhvm_v5:
>>
>> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary
>>
>> Also, I''ve created a wiki page that explains how to set up a
FreeBSD
>> PVHVM for testing:
>>
>> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
>> _______________________________________________
>> freebsd-xen@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
>> To unsubscribe, send any mail to
"freebsd-xen-unsubscribe@freebsd.org"
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
On 23/05/13 21:09, Colin Percival wrote:> On 05/23/13 02:06, Roger Pau Monné wrote: >> On 22/05/13 22:03, Colin Percival wrote: >>> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >>> a panic -- console output below. I can get a backtrace and possibly even >>> a dump if those would help. >> >> Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems >> so far. By looking at the Xen code, the only reason the timer setup >> could return -22 (EINVAL), is that we try to set the timer for a >> different vCPU than the one we are running on. >> >> I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 >> (using both qemu-xen and qemu-xen-traditional device models), so I'm >> unsure if this could be due to some patch Amazon applies to Xen. Could >> you try the following patch and post the error message? I would like to >> see if the cpuid reported by kdb and the vCPU that we are trying to set >> the timer are the same. > > Looks like there's agreement about the cpuids here. Anything else I should > try testing?Thanks for the test, this is what I expected. I'm a little bit out of ideas since I'm not able to reproduce this on upstream Xen 4.2. Without knowing what's happening inside the hypervisor it's hard to tell what's wrong. It would be interesting to try if the same happens with a Linux PVHVM (not PV) running on the same instance type. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 23/05/13 21:09, Colin Percival wrote:> On 05/23/13 02:06, Roger Pau Monné wrote: >> On 22/05/13 22:03, Colin Percival wrote: >>> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >>> a panic -- console output below. I can get a backtrace and possibly even >>> a dump if those would help. >> >> Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems >> so far. By looking at the Xen code, the only reason the timer setup >> could return -22 (EINVAL), is that we try to set the timer for a >> different vCPU than the one we are running on. >> >> I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 >> (using both qemu-xen and qemu-xen-traditional device models), so I'm >> unsure if this could be due to some patch Amazon applies to Xen. Could >> you try the following patch and post the error message? I would like to >> see if the cpuid reported by kdb and the vCPU that we are trying to set >> the timer are the same. > > Looks like there's agreement about the cpuids here. Anything else I should > try testing?Thanks for the test, this is what I expected. I'm a little bit out of ideas since I'm not able to reproduce this on upstream Xen 4.2. Without knowing what's happening inside the hypervisor it's hard to tell what's wrong. It would be interesting to try if the same happens with a Linux PVHVM (not PV) running on the same instance type. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI > implementation for both amd64 and i386. I''ve also updated the wiki to > point to the pvhvm_v10 branch:I feel a bit stupid to ask this, but how I install ''gmake''? Doing ''pkg_add -r gmake'' tells me there is no package (perhaps I am using a too modern version of FreeBSD (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? The Wiki mentions how to install git but that fails b/c it can''t find gmake.
On Fri, May 24, 2013 at 10:14 AM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: > > Hello, > > > > I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI > > implementation for both amd64 and i386. I''ve also updated the wiki to > > point to the pvhvm_v10 branch: > > I feel a bit stupid to ask this, but how I install ''gmake''? Doing ''pkg_add > -r gmake'' > tells me there is no package (perhaps I am using a too modern version of > FreeBSD > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > The Wiki mentions how to install git but that fails b/c it can''t find > gmake. >on 10-CURRENT you need to use pkg or build from ports/devel/gmake> _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 24/05/13 16:14, Konrad Rzeszutek Wilk wrote:> On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: >> Hello, >> >> I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI >> implementation for both amd64 and i386. I''ve also updated the wiki to >> point to the pvhvm_v10 branch: > > I feel a bit stupid to ask this, but how I install ''gmake''? Doing ''pkg_add -r gmake'' > tells me there is no package (perhaps I am using a too modern version of FreeBSD > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > The Wiki mentions how to install git but that fails b/c it can''t find gmake.Did you install the ports tree during the installation? If so I''ve always successfully installed git using: # whereis git # cd <output of above command> # make install Maybe the ISO you picked as a broken ports snapshot?
On Fri, May 24, 2013 at 7:14 AM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote:> On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: > > Hello, > > > > I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI > > implementation for both amd64 and i386. I''ve also updated the wiki to > > point to the pvhvm_v10 branch: > > I feel a bit stupid to ask this, but how I install ''gmake''? Doing ''pkg_add > -r gmake'' > tells me there is no package (perhaps I am using a too modern version of > FreeBSD > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > The Wiki mentions how to install git but that fails b/c it can''t find > gmake. >For 10.0-CURRENT, not all the packages are available yet from the main FreeBSD.org ftp site. I am going through a similar setup issue with someone who has signed up for Google Summer of Code, and I need him to use close to the latest 10.0-CURRENT and have a usable system. I wrote this blog post for the student: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ You may wish to follow those steps to configure your system to download packages from one of the 3rd party pkg mirrors, and then use the "pkg" command to install gmake and whatever other packages you need. Outback Dingo has mentioned using "pkg" command for installing packages in 10-CURRENT, and that is what I am instructing my GSoC to do. Good luck. -- Craig _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Thu, May 23, 2013 at 6:30 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 15:20, Jeroen van der Ham wrote: > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Also, I''ve created a wiki page that explains how to set up a FreeBSD > >> PVHVM for testing: > >> > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > > > You mention on that page that it is easier to install on 10.0-CURRENT > snapshots. > > What are the issues with installing this on 9.1? Is it possible? > > I don''t think it is recommended to use a HEAD (10) kernel with a 9.1 > userland. You can always install a 9.1 and then do a full update with > the source on my repository. >Actually in FreeBSD, it is possible to run an older userland on a newer kernel, and a lot of effort is spent in preserving this type of backwards compatibility. So a 9.1 userland with a 10 kernel will work. However, running a newer userland on an older kernel is not guaranteed to work. So running a 10 userland with a 9.1 kernel will most likely not work. However, since you guys are doing very cutting edge stuff with 10-CURRENT, it is better that you do not waste time with 9.1. I recommend you start with a 10.0 CURRENT snapshot ISO and go from there. I am going through a similar setup exercise with a Google Summer of Code student where he needs to have a latest CURRENT system running in a VM. I wrote this blog post: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ for the steps how to do it. You can follow those steps to get bootstrapped with a working environment if it helps you out. Good luck. -- Craig _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Thu, May 23, 2013 at 6:30 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> On 23/05/13 15:20, Jeroen van der Ham wrote: > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Also, I''ve created a wiki page that explains how to set up a FreeBSD > >> PVHVM for testing: > >> > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > > > You mention on that page that it is easier to install on 10.0-CURRENT > snapshots. > > What are the issues with installing this on 9.1? Is it possible? > > I don''t think it is recommended to use a HEAD (10) kernel with a 9.1 > userland. You can always install a 9.1 and then do a full update with > the source on my repository. >Actually in FreeBSD, it is possible to run an older userland on a newer kernel, and a lot of effort is spent in preserving this type of backwards compatibility. So a 9.1 userland with a 10 kernel will work. However, running a newer userland on an older kernel is not guaranteed to work. So running a 10 userland with a 9.1 kernel will most likely not work. However, since you guys are doing very cutting edge stuff with 10-CURRENT, it is better that you do not waste time with 9.1. I recommend you start with a 10.0 CURRENT snapshot ISO and go from there. I am going through a similar setup exercise with a Google Summer of Code student where he needs to have a latest CURRENT system running in a VM. I wrote this blog post: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ for the steps how to do it. You can follow those steps to get bootstrapped with a working environment if it helps you out. Good luck. -- Craig _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Fri, May 24, 2013 at 03:21:54PM -0700, Craig Rodrigues wrote:> On Fri, May 24, 2013 at 7:14 AM, Konrad Rzeszutek Wilk < > konrad.wilk@oracle.com> wrote: > > > On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: > > > Hello, > > > > > > I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI > > > implementation for both amd64 and i386. I''ve also updated the wiki to > > > point to the pvhvm_v10 branch: > > > > I feel a bit stupid to ask this, but how I install ''gmake''? Doing ''pkg_add > > -r gmake'' > > tells me there is no package (perhaps I am using a too modern version of > > FreeBSD > > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > > > The Wiki mentions how to install git but that fails b/c it can''t find > > gmake. > > > > For 10.0-CURRENT, not all the packages are available yet from the main > FreeBSD.org ftp site. > I am going through a similar setup issue with someone who has signed up for > Google Summer of Code, > and I need him to use close to the latest 10.0-CURRENT and have a usable > system. > > I wrote this blog post for the student: > http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/Excellent! Thanks for the link.
On Fri, May 24, 2013 at 6:27 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote:> On Thu, May 23, 2013 at 6:30 AM, Roger Pau Monné <roger.pau@citrix.com > >wrote: > > > On 23/05/13 15:20, Jeroen van der Ham wrote: > > > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> > wrote: > > >> Also, I''ve created a wiki page that explains how to set up a FreeBSD > > >> PVHVM for testing: > > >> > > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > > > > > > You mention on that page that it is easier to install on 10.0-CURRENT > > snapshots. > > > What are the issues with installing this on 9.1? Is it possible? > > > > I don''t think it is recommended to use a HEAD (10) kernel with a 9.1 > > userland. You can always install a 9.1 and then do a full update with > > the source on my repository. > > > > > Actually in FreeBSD, it is possible to run an older userland on a newer > kernel, > and a lot of effort is spent in preserving this type of backwards > compatibility. > So a 9.1 userland with a 10 kernel will work. > However, running a newer userland on an older kernel is not guaranteed to > work. > So running a 10 userland with a 9.1 kernel will most likely not work. > > However, since you guys are doing very cutting edge stuff with 10-CURRENT, > it is better that you do not waste time with 9.1. > > I recommend you start with a 10.0 CURRENT snapshot ISO and go from there. > I am going through a similar setup exercise with a Google Summer of Code > student > where he needs to have a latest CURRENT system running in a VM. > > I wrote this blog post: > > > http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ > > for the steps how to do it. You can follow those steps to get bootstrapped > with a working environment if it helps you out. > > Good luck. > >Any chance this will be backported to 9.X or 9-STABLE at least ??> -- > Craig > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Fri, May 24, 2013 at 6:27 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote:> On Thu, May 23, 2013 at 6:30 AM, Roger Pau Monné <roger.pau@citrix.com > >wrote: > > > On 23/05/13 15:20, Jeroen van der Ham wrote: > > > > > > On 13 May 2013, at 20:32, Roger Pau Monné <roger.pau@citrix.com> > wrote: > > >> Also, I''ve created a wiki page that explains how to set up a FreeBSD > > >> PVHVM for testing: > > >> > > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > > > > > > You mention on that page that it is easier to install on 10.0-CURRENT > > snapshots. > > > What are the issues with installing this on 9.1? Is it possible? > > > > I don''t think it is recommended to use a HEAD (10) kernel with a 9.1 > > userland. You can always install a 9.1 and then do a full update with > > the source on my repository. > > > > > Actually in FreeBSD, it is possible to run an older userland on a newer > kernel, > and a lot of effort is spent in preserving this type of backwards > compatibility. > So a 9.1 userland with a 10 kernel will work. > However, running a newer userland on an older kernel is not guaranteed to > work. > So running a 10 userland with a 9.1 kernel will most likely not work. > > However, since you guys are doing very cutting edge stuff with 10-CURRENT, > it is better that you do not waste time with 9.1. > > I recommend you start with a 10.0 CURRENT snapshot ISO and go from there. > I am going through a similar setup exercise with a Google Summer of Code > student > where he needs to have a latest CURRENT system running in a VM. > > I wrote this blog post: > > > http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ > > for the steps how to do it. You can follow those steps to get bootstrapped > with a working environment if it helps you out. > > Good luck. > >Any chance this will be backported to 9.X or 9-STABLE at least ??> -- > Craig > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 24/05/13 12:11, Roger Pau Monné wrote:> On 23/05/13 21:09, Colin Percival wrote: >> On 05/23/13 02:06, Roger Pau Monné wrote: >>> On 22/05/13 22:03, Colin Percival wrote: >>>> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >>>> a panic -- console output below. I can get a backtrace and possibly even >>>> a dump if those would help. >>> >>> Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems >>> so far. By looking at the Xen code, the only reason the timer setup >>> could return -22 (EINVAL), is that we try to set the timer for a >>> different vCPU than the one we are running on. >>> >>> I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 >>> (using both qemu-xen and qemu-xen-traditional device models), so I'm >>> unsure if this could be due to some patch Amazon applies to Xen. Could >>> you try the following patch and post the error message? I would like to >>> see if the cpuid reported by kdb and the vCPU that we are trying to set >>> the timer are the same. >> >> Looks like there's agreement about the cpuids here. Anything else I should >> try testing? > > Thanks for the test, this is what I expected. I'm a little bit out of > ideas since I'm not able to reproduce this on upstream Xen 4.2. Without > knowing what's happening inside the hypervisor it's hard to tell what's > wrong. It would be interesting to try if the same happens with a Linux > PVHVM (not PV) running on the same instance type.Hello Matt, Colin has found an issue on the FreeBSD PVHVM port that I haven't been able to reproduce using open source Xen, even when using the same version as the one reported by EC2. Is there anyway you could provide some help debugging this? Without seeing the Xen code that causes VCPUOP_set_singleshot_timer to return EINVAL it is quite hard to figure out what's happening inside the hypervisor. Thanks, Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 24/05/13 12:11, Roger Pau Monné wrote:> On 23/05/13 21:09, Colin Percival wrote: >> On 05/23/13 02:06, Roger Pau Monné wrote: >>> On 22/05/13 22:03, Colin Percival wrote: >>>> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >>>> a panic -- console output below. I can get a backtrace and possibly even >>>> a dump if those would help. >>> >>> Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems >>> so far. By looking at the Xen code, the only reason the timer setup >>> could return -22 (EINVAL), is that we try to set the timer for a >>> different vCPU than the one we are running on. >>> >>> I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 >>> (using both qemu-xen and qemu-xen-traditional device models), so I'm >>> unsure if this could be due to some patch Amazon applies to Xen. Could >>> you try the following patch and post the error message? I would like to >>> see if the cpuid reported by kdb and the vCPU that we are trying to set >>> the timer are the same. >> >> Looks like there's agreement about the cpuids here. Anything else I should >> try testing? > > Thanks for the test, this is what I expected. I'm a little bit out of > ideas since I'm not able to reproduce this on upstream Xen 4.2. Without > knowing what's happening inside the hypervisor it's hard to tell what's > wrong. It would be interesting to try if the same happens with a Linux > PVHVM (not PV) running on the same instance type.Hello Matt, Colin has found an issue on the FreeBSD PVHVM port that I haven't been able to reproduce using open source Xen, even when using the same version as the one reported by EC2. Is there anyway you could provide some help debugging this? Without seeing the Xen code that causes VCPUOP_set_singleshot_timer to return EINVAL it is quite hard to figure out what's happening inside the hypervisor. Thanks, Roger. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, May 28, 2013 at 06:15:00PM +0200, Roger Pau Monné wrote:> On 24/05/13 12:11, Roger Pau Monné wrote: > > > > Thanks for the test, this is what I expected. I''m a little bit out of > > ideas since I''m not able to reproduce this on upstream Xen 4.2. Without > > knowing what''s happening inside the hypervisor it''s hard to tell what''s > > wrong. It would be interesting to try if the same happens with a Linux > > PVHVM (not PV) running on the same instance type. > > Hello Matt, > > Colin has found an issue on the FreeBSD PVHVM port that I haven''t been > able to reproduce using open source Xen, even when using the same > version as the one reported by EC2. Is there anyway you could provide > some help debugging this? Without seeing the Xen code that causes > VCPUOP_set_singleshot_timer to return EINVAL it is quite hard to figure > out what''s happening inside the hypervisor.Hi Roger, VCPUOP_set_singleshot_timer returns -EINVAL when: 1) the specified vCPU ID is out of range (<0 or >MAX_VIRT_CPUS) 2) the specified vCPU ID doesn''t match the running vCPU. It seems that there is a confusion between the logical vCPU ID and the local APIC physical ID. I added some debugging to case 2): diff --git a/xen/common/domain.c b/xen/common/domain.c index e728819..e3efb8c 100644 --- a/xen/common/domain.c +++ b/xen/common/domain.c @@ -901,7 +901,12 @@ long do_vcpu_op(int cmd, int vcpuid, XEN_GUEST_HANDLE(void) arg) struct vcpu_set_singleshot_timer set; if ( v != current ) + { + printk("Domain %d (vcpu#%d) VCPUOP_set_singleshot_timer specified vcpuid %d\n", + d->domain_id, current->vcpu_id, vcpuid); + return -EINVAL; + } if ( copy_from_guest(&set, arg, 1) ) return -EFAULT; The output from booting ami-e75c358e on a cr1.8xlarge: (XEN) Domain 1 (vcpu#16) VCPUOP_set_singleshot_timer specified vcpuid 1 (XEN) Domain 1 (vcpu#7) VCPUOP_set_singleshot_timer specified vcpuid 14 (XEN) Domain 1 (vcpu#23) VCPUOP_set_singleshot_timer specified vcpuid 15 (XEN) Domain 1 (vcpu#11) VCPUOP_set_singleshot_timer specified vcpuid 22 (XEN) Domain 1 (vcpu#27) VCPUOP_set_singleshot_timer specified vcpuid 23 (XEN) Domain 1 (vcpu#18) VCPUOP_set_singleshot_timer specified vcpuid 5 (XEN) Domain 1 (vcpu#2) VCPUOP_set_singleshot_timer specified vcpuid 4 (XEN) Domain 1 (vcpu#9) VCPUOP_set_singleshot_timer specified vcpuid 18 (XEN) Domain 1 (vcpu#25) VCPUOP_set_singleshot_timer specified vcpuid 19 (XEN) Domain 1 (vcpu#1) VCPUOP_set_singleshot_timer specified vcpuid 2 (XEN) Domain 1 (vcpu#6) VCPUOP_set_singleshot_timer specified vcpuid 12 (XEN) Domain 1 (vcpu#22) VCPUOP_set_singleshot_timer specified vcpuid 13 (XEN) Domain 1 (vcpu#26) VCPUOP_set_singleshot_timer specified vcpuid 21 (XEN) Domain 1 (vcpu#10) VCPUOP_set_singleshot_timer specified vcpuid 20 (XEN) Domain 1 (vcpu#14) VCPUOP_set_singleshot_timer specified vcpuid 28 (XEN) Domain 1 (vcpu#30) VCPUOP_set_singleshot_timer specified vcpuid 29 (XEN) Domain 1 (vcpu#3) VCPUOP_set_singleshot_timer specified vcpuid 6 (XEN) Domain 1 (vcpu#19) VCPUOP_set_singleshot_timer specified vcpuid 7 (XEN) Domain 1 (vcpu#12) VCPUOP_set_singleshot_timer specified vcpuid 24 (XEN) Domain 1 (vcpu#28) VCPUOP_set_singleshot_timer specified vcpuid 25 (XEN) Domain 1 (vcpu#5) VCPUOP_set_singleshot_timer specified vcpuid 10 (XEN) Domain 1 (vcpu#21) VCPUOP_set_singleshot_timer specified vcpuid 11 (XEN) Domain 1 (vcpu#24) VCPUOP_set_singleshot_timer specified vcpuid 17 (XEN) Domain 1 (vcpu#8) VCPUOP_set_singleshot_timer specified vcpuid 16 (XEN) Domain 1 (vcpu#17) VCPUOP_set_singleshot_timer specified vcpuid 3 (XEN) Domain 1 (vcpu#20) VCPUOP_set_singleshot_timer specified vcpuid 9 (XEN) Domain 1 (vcpu#4) VCPUOP_set_singleshot_timer specified vcpuid 8 (XEN) Domain 1 (vcpu#13) VCPUOP_set_singleshot_timer specified vcpuid 26 (XEN) Domain 1 (vcpu#29) VCPUOP_set_singleshot_timer specified vcpuid 27 (XEN) Domain 1 (vcpu#15) VCPUOP_set_singleshot_timer specified vcpuid 30 Note from the FreeBSD boot output: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 16 APIC: CPU 2 has ACPI ID 1 APIC: CPU 3 has ACPI ID 17 APIC: CPU 4 has ACPI ID 2 APIC: CPU 5 has ACPI ID 18 APIC: CPU 6 has ACPI ID 3 APIC: CPU 7 has ACPI ID 19 APIC: CPU 8 has ACPI ID 4 APIC: CPU 9 has ACPI ID 20 APIC: CPU 10 has ACPI ID 5 APIC: CPU 11 has ACPI ID 21 APIC: CPU 12 has ACPI ID 6 APIC: CPU 13 has ACPI ID 22 APIC: CPU 14 has ACPI ID 7 APIC: CPU 15 has ACPI ID 23 APIC: CPU 16 has ACPI ID 8 APIC: CPU 17 has ACPI ID 24 APIC: CPU 18 has ACPI ID 9 APIC: CPU 19 has ACPI ID 25 APIC: CPU 20 has ACPI ID 10 APIC: CPU 21 has ACPI ID 26 APIC: CPU 22 has ACPI ID 11 APIC: CPU 23 has ACPI ID 27 APIC: CPU 24 has ACPI ID 12 APIC: CPU 25 has ACPI ID 28 APIC: CPU 26 has ACPI ID 13 APIC: CPU 27 has ACPI ID 29 APIC: CPU 28 has ACPI ID 14 APIC: CPU 29 has ACPI ID 30 APIC: CPU 30 has ACPI ID 15 APIC: CPU 31 has ACPI ID 31 --msw
On 05/28/13 12:18, Matt Wilson wrote:> VCPUOP_set_singleshot_timer returns -EINVAL when: > > 1) the specified vCPU ID is out of range (<0 or >MAX_VIRT_CPUS) > 2) the specified vCPU ID doesn''t match the running vCPU. > > It seems that there is a confusion between the logical vCPU ID and the > local APIC physical ID. > [...] > (XEN) Domain 1 (vcpu#16) VCPUOP_set_singleshot_timer specified vcpuid 1 > [...] > APIC: CPU 1 has ACPI ID 16Thanks Matt! Looks like we need to pass our acpi_id to the Xen hypercall instead of our cpuid. Roger, changing the line int cpu = PCPU_GET(cpuid); to int cpu = PCPU_GET(acpi_id); in xentimer_et_start and xentimer_et_stop fixes this panic and gets me slightly further; the following lines are now added to the console output prior to the system appearing to hang:> ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 > ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 2 vector 48 > ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 3 vector 48 > ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 4 vector 48 > ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 5 vector 48 > ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 6 vector 48 > ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 7 vector 48 > TSC timecounter discards lower 1 bit(s) > Timecounter "TSC-low" frequency 1300024860 Hz quality -100 > WARNING: WITNESS option enabled, expect reduced performance.On a cc2.8xlarge EC2 instance, the lines which come after this are> GEOM: new disk xbd1 > GEOM: new disk xbd2 > GEOM: new disk xbd3 > GEOM: new disk xbd4 > Trying to mount root from ufs:/dev/ad0a [rw]... > start_init: trying /sbin/initand then the userland boot process; have you made any bug fixes after your pvhvm_v7 which would explain why tasting disks was hanging? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On Tue, May 28, 2013 at 8:21 AM, Outback Dingo <outbackdingo@gmail.com>wrote:> > > > On Fri, May 24, 2013 at 6:27 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote: > >> I wrote this blog post: >> >> >> http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ >> >> for the steps how to do it. You can follow those steps to get >> bootstrapped >> with a working environment if it helps you out. >> >> Good luck. >> >> > Any chance this will be backported to 9.X or 9-STABLE at least ?? > >I wrote a blog post specifically for installing 10-CURRENT from a snapshot ISO and getting bootstrapped from there, to help the Google Summer of Code Student that I am mentoring. What specifically do you want to be backported to 9-STABLE? -- Craig _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Tue, May 28, 2013 at 8:21 AM, Outback Dingo <outbackdingo@gmail.com>wrote:> > > > On Fri, May 24, 2013 at 6:27 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote: > >> I wrote this blog post: >> >> >> http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ >> >> for the steps how to do it. You can follow those steps to get >> bootstrapped >> with a working environment if it helps you out. >> >> Good luck. >> >> > Any chance this will be backported to 9.X or 9-STABLE at least ?? > >I wrote a blog post specifically for installing 10-CURRENT from a snapshot ISO and getting bootstrapped from there, to help the Google Summer of Code Student that I am mentoring. What specifically do you want to be backported to 9-STABLE? -- Craig _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, May 28, 2013 at 6:05 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote:> > > > On Tue, May 28, 2013 at 8:21 AM, Outback Dingo <outbackdingo@gmail.com>wrote: > >> >> >> >> On Fri, May 24, 2013 at 6:27 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote: >> >>> I wrote this blog post: >>> >>> >>> http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ >>> >>> for the steps how to do it. You can follow those steps to get >>> bootstrapped >>> with a working environment if it helps you out. >>> >>> Good luck. >>> >>> >> Any chance this will be backported to 9.X or 9-STABLE at least ?? >> >> > > > I wrote a blog post specifically for installing 10-CURRENT from a snapshot > ISO and getting bootstrapped > from there, to help the Google Summer of Code Student that I am mentoring. > What specifically do you want to be backported to 9-STABLE? >Yes Ive seen the post, however we have a hard requirement for 9-STABLE for some development work we are currently involved in. And I would prefer not to move our current infrastructure for development to CURRENT. A major portion of our development environment is based on XEN for testing and development. Therefor we realize PVHVM is a work in progress, and we have built some VMs from it, they run exceptionally well, However our build environments refuse to build 9-STABLE on CURRENT PVHVM, or 10-CURRENT. Lastly Im sure theres a ton of users who would like to see this in 9.x or 9-STABLE> > > -- > Craig >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Tue, May 28, 2013 at 6:05 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote:> > > > On Tue, May 28, 2013 at 8:21 AM, Outback Dingo <outbackdingo@gmail.com>wrote: > >> >> >> >> On Fri, May 24, 2013 at 6:27 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote: >> >>> I wrote this blog post: >>> >>> >>> http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ >>> >>> for the steps how to do it. You can follow those steps to get >>> bootstrapped >>> with a working environment if it helps you out. >>> >>> Good luck. >>> >>> >> Any chance this will be backported to 9.X or 9-STABLE at least ?? >> >> > > > I wrote a blog post specifically for installing 10-CURRENT from a snapshot > ISO and getting bootstrapped > from there, to help the Google Summer of Code Student that I am mentoring. > What specifically do you want to be backported to 9-STABLE? >Yes Ive seen the post, however we have a hard requirement for 9-STABLE for some development work we are currently involved in. And I would prefer not to move our current infrastructure for development to CURRENT. A major portion of our development environment is based on XEN for testing and development. Therefor we realize PVHVM is a work in progress, and we have built some VMs from it, they run exceptionally well, However our build environments refuse to build 9-STABLE on CURRENT PVHVM, or 10-CURRENT. Lastly Im sure theres a ton of users who would like to see this in 9.x or 9-STABLE> > > -- > Craig >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, May 28, 2013 at 3:43 PM, Outback Dingo <outbackdingo@gmail.com>wrote:> > I wrote a blog post specifically for installing 10-CURRENT from a snapshot >> ISO and getting bootstrapped >> from there, to help the Google Summer of Code Student that I am mentoring. >> What specifically do you want to be backported to 9-STABLE? >> > > Yes Ive seen the post, however we have a hard requirement for 9-STABLE for > some development work we are > currently involved in. And I would prefer not to move our current > infrastructure for development to CURRENT. > A major portion of our development environment is based on XEN for testing > and development. > Therefor we realize PVHM is a work in progress, and we have built some > VMs from it, they run exceptionally > well, However our build environments refuse to build 9-STABLE on CURRENT > PVHVM, or 10-CURRENT. > Lastly Im sure theres a ton of users who would like to see this in 9.x or > 9-STABLE > >OK, I misunderstood you since you responded in the thread and quoted some of my post. My blog post has nothing relevant to Xen and PVHM, and is specific to setting up a Google Summer of Code student on a 10-CURRENT environment. The FreeBSD Xen and PVHM developers will need to provide the details about their plans to merge their changes to the 9-STABLE branch..... that''s something which I am not familiar with. -- Craig _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, May 28, 2013 at 3:43 PM, Outback Dingo <outbackdingo@gmail.com>wrote:> > I wrote a blog post specifically for installing 10-CURRENT from a snapshot >> ISO and getting bootstrapped >> from there, to help the Google Summer of Code Student that I am mentoring. >> What specifically do you want to be backported to 9-STABLE? >> > > Yes Ive seen the post, however we have a hard requirement for 9-STABLE for > some development work we are > currently involved in. And I would prefer not to move our current > infrastructure for development to CURRENT. > A major portion of our development environment is based on XEN for testing > and development. > Therefor we realize PVHM is a work in progress, and we have built some > VMs from it, they run exceptionally > well, However our build environments refuse to build 9-STABLE on CURRENT > PVHVM, or 10-CURRENT. > Lastly Im sure theres a ton of users who would like to see this in 9.x or > 9-STABLE > >OK, I misunderstood you since you responded in the thread and quoted some of my post. My blog post has nothing relevant to Xen and PVHM, and is specific to setting up a Google Summer of Code student on a 10-CURRENT environment. The FreeBSD Xen and PVHM developers will need to provide the details about their plans to merge their changes to the 9-STABLE branch..... that''s something which I am not familiar with. -- Craig _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Tue, May 28, 2013 at 7:09 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote:> > > > On Tue, May 28, 2013 at 3:43 PM, Outback Dingo <outbackdingo@gmail.com>wrote: > >> >> I wrote a blog post specifically for installing 10-CURRENT from a >>> snapshot ISO and getting bootstrapped >>> from there, to help the Google Summer of Code Student that I am >>> mentoring. >>> What specifically do you want to be backported to 9-STABLE? >>> >> >> Yes Ive seen the post, however we have a hard requirement for 9-STABLE >> for some development work we are >> currently involved in. And I would prefer not to move our current >> infrastructure for development to CURRENT. >> A major portion of our development environment is based on XEN for >> testing and development. >> Therefor we realize PVHM is a work in progress, and we have built some >> VMs from it, they run exceptionally >> well, However our build environments refuse to build 9-STABLE on CURRENT >> PVHVM, or 10-CURRENT. >> Lastly Im sure theres a ton of users who would like to see this in 9.x or >> 9-STABLE >> >> > > OK, I misunderstood you since you responded in the thread and quoted some > of my post. > My blog post has nothing relevant to Xen and PVHM, and is specific to > setting up > a Google Summer of Code student on a 10-CURRENT environment. The FreeBSD > Xen > and PVHM developers will need to provide the details about their plans to > merge their changes to the 9-STABLE branch..... > that''s something which I am not familiar with. >If we can get a diff of the work done against the master Id be happy to help backporting and testing> > > -- > Craig >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, May 28, 2013 at 7:09 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote:> > > > On Tue, May 28, 2013 at 3:43 PM, Outback Dingo <outbackdingo@gmail.com>wrote: > >> >> I wrote a blog post specifically for installing 10-CURRENT from a >>> snapshot ISO and getting bootstrapped >>> from there, to help the Google Summer of Code Student that I am >>> mentoring. >>> What specifically do you want to be backported to 9-STABLE? >>> >> >> Yes Ive seen the post, however we have a hard requirement for 9-STABLE >> for some development work we are >> currently involved in. And I would prefer not to move our current >> infrastructure for development to CURRENT. >> A major portion of our development environment is based on XEN for >> testing and development. >> Therefor we realize PVHM is a work in progress, and we have built some >> VMs from it, they run exceptionally >> well, However our build environments refuse to build 9-STABLE on CURRENT >> PVHVM, or 10-CURRENT. >> Lastly Im sure theres a ton of users who would like to see this in 9.x or >> 9-STABLE >> >> > > OK, I misunderstood you since you responded in the thread and quoted some > of my post. > My blog post has nothing relevant to Xen and PVHM, and is specific to > setting up > a Google Summer of Code student on a 10-CURRENT environment. The FreeBSD > Xen > and PVHM developers will need to provide the details about their plans to > merge their changes to the 9-STABLE branch..... > that''s something which I am not familiar with. >If we can get a diff of the work done against the master Id be happy to help backporting and testing> > > -- > Craig >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 28/05/13 23:33, Colin Percival wrote:> On 05/28/13 12:18, Matt Wilson wrote: >> VCPUOP_set_singleshot_timer returns -EINVAL when: >> >> 1) the specified vCPU ID is out of range (<0 or >MAX_VIRT_CPUS) >> 2) the specified vCPU ID doesn''t match the running vCPU. >> >> It seems that there is a confusion between the logical vCPU ID and the >> local APIC physical ID. >> [...] >> (XEN) Domain 1 (vcpu#16) VCPUOP_set_singleshot_timer specified vcpuid 1 >> [...] >> APIC: CPU 1 has ACPI ID 16 > > Thanks Matt! Looks like we need to pass our acpi_id to the Xen hypercall > instead of our cpuid. > > Roger, changing the line > int cpu = PCPU_GET(cpuid); > to > int cpu = PCPU_GET(acpi_id); > in xentimer_et_start and xentimer_et_stop fixes this panic and gets me > slightly further; the following lines are now added to the console output > prior to the system appearing to hang: >> ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 >> ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 2 vector 48 >> ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 3 vector 48 >> ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 4 vector 48 >> ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 5 vector 48 >> ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 6 vector 48 >> ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 7 vector 48 >> TSC timecounter discards lower 1 bit(s) >> Timecounter "TSC-low" frequency 1300024860 Hz quality -100 >> WARNING: WITNESS option enabled, expect reduced performance.Hello, Thanks Matt and Colin for the testing and help! I''ve pushed yet another version, now it''s branch pvhvm_v12, which I *think* should solve the issues with cpuid != acpi_id: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 Since I''m not able to reproduce the cpuid != acpi_id case, could you give it a try and report the results?> On a cc2.8xlarge EC2 instance, the lines which come after this are >> GEOM: new disk xbd1 >> GEOM: new disk xbd2 >> GEOM: new disk xbd3 >> GEOM: new disk xbd4 >> Trying to mount root from ufs:/dev/ad0a [rw]... >> start_init: trying /sbin/init > and then the userland boot process; have you made any bug fixes after > your pvhvm_v7 which would explain why tasting disks was hanging?I''m not sure I follow, did you found a regression from previous branches? i.e. it used to work with branch pvhvm_v6 and not pvhvm_v7?
On May 28, 2013, at 5:20 PM, Outback Dingo <outbackdingo@gmail.com> wrote:> On Tue, May 28, 2013 at 7:09 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote: > >> On Tue, May 28, 2013 at 3:43 PM, Outback Dingo <outbackdingo@gmail.com>wrote: >> >>> >>> I wrote a blog post specifically for installing 10-CURRENT from a >>>> snapshot ISO and getting bootstrapped >>>> from there, to help the Google Summer of Code Student that I am >>>> mentoring. >>>> What specifically do you want to be backported to 9-STABLE? >>>> >>> >>> Yes Ive seen the post, however we have a hard requirement for 9-STABLE >>> for some development work we are >>> currently involved in. And I would prefer not to move our current >>> infrastructure for development to CURRENT. >>> A major portion of our development environment is based on XEN for >>> testing and development. >>> Therefor we realize PVHM is a work in progress, and we have built some >>> VMs from it, they run exceptionally >>> well, However our build environments refuse to build 9-STABLE on CURRENT >>> PVHVM, or 10-CURRENT. >>> Lastly Im sure theres a ton of users who would like to see this in 9.x or >>> 9-STABLE >>> >>> >> >> OK, I misunderstood you since you responded in the thread and quoted some >> of my post. >> My blog post has nothing relevant to Xen and PVHM, and is specific to >> setting up >> a Google Summer of Code student on a 10-CURRENT environment. The FreeBSD >> Xen >> and PVHM developers will need to provide the details about their plans to >> merge their changes to the 9-STABLE branch..... >> that''s something which I am not familiar with. >> > > If we can get a diff of the work done against the master Id be happy to > help backporting and testingI plan to backport the work once we have it all in -current. -- Justin
On May 28, 2013, at 5:20 PM, Outback Dingo <outbackdingo@gmail.com> wrote:> On Tue, May 28, 2013 at 7:09 PM, Craig Rodrigues <rodrigc@crodrigues.org>wrote: > >> On Tue, May 28, 2013 at 3:43 PM, Outback Dingo <outbackdingo@gmail.com>wrote: >> >>> >>> I wrote a blog post specifically for installing 10-CURRENT from a >>>> snapshot ISO and getting bootstrapped >>>> from there, to help the Google Summer of Code Student that I am >>>> mentoring. >>>> What specifically do you want to be backported to 9-STABLE? >>>> >>> >>> Yes Ive seen the post, however we have a hard requirement for 9-STABLE >>> for some development work we are >>> currently involved in. And I would prefer not to move our current >>> infrastructure for development to CURRENT. >>> A major portion of our development environment is based on XEN for >>> testing and development. >>> Therefor we realize PVHM is a work in progress, and we have built some >>> VMs from it, they run exceptionally >>> well, However our build environments refuse to build 9-STABLE on CURRENT >>> PVHVM, or 10-CURRENT. >>> Lastly Im sure theres a ton of users who would like to see this in 9.x or >>> 9-STABLE >>> >>> >> >> OK, I misunderstood you since you responded in the thread and quoted some >> of my post. >> My blog post has nothing relevant to Xen and PVHM, and is specific to >> setting up >> a Google Summer of Code student on a 10-CURRENT environment. The FreeBSD >> Xen >> and PVHM developers will need to provide the details about their plans to >> merge their changes to the 9-STABLE branch..... >> that''s something which I am not familiar with. >> > > If we can get a diff of the work done against the master Id be happy to > help backporting and testingI plan to backport the work once we have it all in -current. -- Justin
On Wed, May 29, 2013 at 07:03:40PM +0200, Roger Pau Monné wrote:> > Hello, > > Thanks Matt and Colin for the testing and help! I''ve pushed yet another > version, now it''s branch pvhvm_v12, which I *think* should solve the > issues with cpuid != acpi_id: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 > > Since I''m not able to reproduce the cpuid != acpi_id case, could you > give it a try and report the results?Colin, can you build an AMI with this new kernel? [...]> On 28/05/13 23:33, Colin Percival wrote: > > On a cc2.8xlarge EC2 instance, the lines which come after this are > >> GEOM: new disk xbd1 > >> GEOM: new disk xbd2 > >> GEOM: new disk xbd3 > >> GEOM: new disk xbd4 > >> Trying to mount root from ufs:/dev/ad0a [rw]... > >> start_init: trying /sbin/init > > and then the userland boot process; have you made any bug fixes after > > your pvhvm_v7 which would explain why tasting disks was hanging? > > I''m not sure I follow, did you found a regression from previous > branches? i.e. it used to work with branch pvhvm_v6 and not pvhvm_v7?Colin was saying that his local change only moved the boot process a bit farther for cr1.8xlarge. Perhaps some of the other changes you made in the latest pvhvm_v12 branch will get the VM all the way up. --msw
On 29/05/13 19:22, Matt Wilson wrote:> On Wed, May 29, 2013 at 07:03:40PM +0200, Roger Pau Monné wrote: >> >> Hello, >> >> Thanks Matt and Colin for the testing and help! I''ve pushed yet another >> version, now it''s branch pvhvm_v12, which I *think* should solve the >> issues with cpuid != acpi_id: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 >> >> Since I''m not able to reproduce the cpuid != acpi_id case, could you >> give it a try and report the results? > > Colin, can you build an AMI with this new kernel? > > [...] > >> On 28/05/13 23:33, Colin Percival wrote: >>> On a cc2.8xlarge EC2 instance, the lines which come after this are >>>> GEOM: new disk xbd1 >>>> GEOM: new disk xbd2 >>>> GEOM: new disk xbd3 >>>> GEOM: new disk xbd4 >>>> Trying to mount root from ufs:/dev/ad0a [rw]... >>>> start_init: trying /sbin/init >>> and then the userland boot process; have you made any bug fixes after >>> your pvhvm_v7 which would explain why tasting disks was hanging? >> >> I''m not sure I follow, did you found a regression from previous >> branches? i.e. it used to work with branch pvhvm_v6 and not pvhvm_v7? > > Colin was saying that his local change only moved the boot process a > bit farther for cr1.8xlarge. Perhaps some of the other changes you > made in the latest pvhvm_v12 branch will get the VM all the way up.Oh, sure, more changes where needed in order to get it to work, like using acpi_id to map the vcpu_info and perform the cpu bindings.
On 05/29/13 10:45, Roger Pau Monné wrote:> Oh, sure, more changes where needed in order to get it to work, like > using acpi_id to map the vcpu_info and perform the cpu bindings.Ah, that explains it. I looked at timer.c for other places where that change was needed but it didn''t occur to me that the same problem would exist in other parts of the tree.> On 29/05/13 19:22, Matt Wilson wrote: >> On Wed, May 29, 2013 at 07:03:40PM +0200, Roger Pau Monné wrote: >>> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 >> >> Colin, can you build an AMI with this new kernel?Done, ami-95177dfc in us-east-1. This is now booting successfully on cr1.8xlarge; are there any other instance types I should test? I don''t know which Xen versions you have deployed across the entire fleet. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
On Wed, May 29, 2013 at 01:58:59PM -0700, Colin Percival wrote:> On 29/05/13 19:22, Matt Wilson wrote: > > Colin, can you build an AMI with this new kernel? > > Done, ami-95177dfc in us-east-1. > > This is now booting successfully on cr1.8xlarge; are there any other instance > types I should test? I don''t know which Xen versions you have deployed across > the entire fleet.Nice! The other interesting instance types for problems like this are cc1.4xlarge, cg1.4xlarge and cc2.8xlarge. --msw
On 05/29/13 15:19, Matt Wilson wrote:> On Wed, May 29, 2013 at 01:58:59PM -0700, Colin Percival wrote: >> On 29/05/13 19:22, Matt Wilson wrote: >>> Colin, can you build an AMI with this new kernel? >> >> Done, ami-95177dfc in us-east-1. >> >> This is now booting successfully on cr1.8xlarge; are there any other instance >> types I should test? I don''t know which Xen versions you have deployed across >> the entire fleet. > > Nice! The other interesting instance types for problems like this are > cc1.4xlarge, cg1.4xlarge and cc2.8xlarge.I''ve tried on all three of those and everything seems good -- but I''m only seeing Xen 3.4 on those instance types, so we''re not really testing anything interesting there. I''ll resist asking whether there will be Xen 4.x anywhere else in EC2 in the near future since I''ve had enough of a taste of Amazon NDAs to know that I almost certainly wouldn''t get an answer... ;-) -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Hi, On 23 May 2013, at 19:41, Roger Pau Monné <roger.pau@citrix.com> wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI > implementation for both amd64 and i386. I''ve also updated the wiki to > point to the pvhvm_v10 branch:I''ve been running a VM with this kernel for about a week now. It ran fine, until about 3:30 in the morning. The only thing I can see is the following cryptic messages in /var/log/messages, followed by a reboot of the system. May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] May 30 03:30:57 image01 kernel: . May 30 03:30:57 image01 ntpd[4436]: ntpd exiting on signal 15 May 30 03:30:57 image01 kernel: . May 30 03:30:58 image01 kernel: . May 30 03:31:00 image01 syslogd: exiting on signal 15 May 30 03:32:52 image01 syslogd: kernel boot file is /boot/kernel/kernel May 30 03:32:52 image01 kernel: Copyright (c) 1992-2013 The FreeBSD Project. May 30 03:32:52 image01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 30 03:32:52 image01 kernel: The Regents of the University of California. All rights reserved. May 30 03:32:52 image01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. I''m happy to help to gather more information, just tell me what you need. Jeroen.
Hi, On 23 May 2013, at 19:41, Roger Pau Monné <roger.pau@citrix.com> wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI > implementation for both amd64 and i386. I''ve also updated the wiki to > point to the pvhvm_v10 branch:I''ve been running a VM with this kernel for about a week now. It ran fine, until about 3:30 in the morning. The only thing I can see is the following cryptic messages in /var/log/messages, followed by a reboot of the system. May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] May 30 03:30:57 image01 kernel: . May 30 03:30:57 image01 ntpd[4436]: ntpd exiting on signal 15 May 30 03:30:57 image01 kernel: . May 30 03:30:58 image01 kernel: . May 30 03:31:00 image01 syslogd: exiting on signal 15 May 30 03:32:52 image01 syslogd: kernel boot file is /boot/kernel/kernel May 30 03:32:52 image01 kernel: Copyright (c) 1992-2013 The FreeBSD Project. May 30 03:32:52 image01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 30 03:32:52 image01 kernel: The Regents of the University of California. All rights reserved. May 30 03:32:52 image01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. I''m happy to help to gather more information, just tell me what you need. Jeroen.
On 30/05/13 10:50, Jeroen van der Ham wrote:> Hi, > > On 23 May 2013, at 19:41, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Hello, >> >> I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI >> implementation for both amd64 and i386. I''ve also updated the wiki to >> point to the pvhvm_v10 branch: > > I''ve been running a VM with this kernel for about a week now. It ran fine, until about 3:30 in the morning. The only thing I can see is the following cryptic messages in /var/log/messages, followed by a reboot of the system. > > May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] > May 30 03:30:57 image01 kernel: . > May 30 03:30:57 image01 ntpd[4436]: ntpd exiting on signal 15 > May 30 03:30:57 image01 kernel: . > May 30 03:30:58 image01 kernel: . > May 30 03:31:00 image01 syslogd: exiting on signal 15 > May 30 03:32:52 image01 syslogd: kernel boot file is /boot/kernel/kernel > May 30 03:32:52 image01 kernel: Copyright (c) 1992-2013 The FreeBSD Project. > May 30 03:32:52 image01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > May 30 03:32:52 image01 kernel: The Regents of the University of California. All rights reserved. > May 30 03:32:52 image01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. > > I''m happy to help to gather more information, just tell me what you need.Hello Jeroen, So it looks like the system rebooted (but it was not a crash or a sporadic reboot? the kernel seems to be aware of the reboot request). It would be interesting if you could provide the output of the serial console when this happens, that might be helpful. Did you enable xenconsoled logging? Also, could you provide more info about your system, Xen version, what workload was the DomU running, Dom0 kernel version?
On 30/05/13 10:50, Jeroen van der Ham wrote:> Hi, > > On 23 May 2013, at 19:41, Roger Pau Monné <roger.pau@citrix.com> wrote: > >> Hello, >> >> I''ve pushed a new branch, pvhvm_v10 that contains a PV IPI >> implementation for both amd64 and i386. I''ve also updated the wiki to >> point to the pvhvm_v10 branch: > > I''ve been running a VM with this kernel for about a week now. It ran fine, until about 3:30 in the morning. The only thing I can see is the following cryptic messages in /var/log/messages, followed by a reboot of the system. > > May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] > May 30 03:30:57 image01 kernel: . > May 30 03:30:57 image01 ntpd[4436]: ntpd exiting on signal 15 > May 30 03:30:57 image01 kernel: . > May 30 03:30:58 image01 kernel: . > May 30 03:31:00 image01 syslogd: exiting on signal 15 > May 30 03:32:52 image01 syslogd: kernel boot file is /boot/kernel/kernel > May 30 03:32:52 image01 kernel: Copyright (c) 1992-2013 The FreeBSD Project. > May 30 03:32:52 image01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > May 30 03:32:52 image01 kernel: The Regents of the University of California. All rights reserved. > May 30 03:32:52 image01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. > > I''m happy to help to gather more information, just tell me what you need.Hello Jeroen, So it looks like the system rebooted (but it was not a crash or a sporadic reboot? the kernel seems to be aware of the reboot request). It would be interesting if you could provide the output of the serial console when this happens, that might be helpful. Did you enable xenconsoled logging? Also, could you provide more info about your system, Xen version, what workload was the DomU running, Dom0 kernel version?
Hi, On 30 May 2013, at 11:04, Roger Pau Monné <roger.pau@citrix.com> wrote:> So it looks like the system rebooted (but it was not a crash or a > sporadic reboot? the kernel seems to be aware of the reboot request). It > would be interesting if you could provide the output of the serial > console when this happens, that might be helpful. Did you enable > xenconsoled logging?Unfortunately I did not.> Also, could you provide more info about your system, Xen version, what > workload was the DomU running, Dom0 kernel version?There was no one logged in at the time of the reboot according to the last log. I did do some sysbench tests during the day, but that was way before it rebooted. The only thing that could be running during that time was daily periodic. $ sudo xm info host : soleus01.soleus.nu release : 2.6.32-5-xen-amd64 version : #1 SMP Mon Oct 3 07:53:54 UTC 2011 machine : x86_64 nr_cpus : 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2200 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 65534 free_memory : 6866 node_to_cpu : node0:0-3 node1:4-7 node_to_memory : node0:3128 node1:3737 node_to_dma32_mem : node0:3128 node1:0 max_node_id : 1 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=1852M cc_compiler : gcc version 4.4.5 (Debian 4.4.5-10) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Wed Jan 12 14:04:06 UTC 2011 xend_config_format : 4 $ uname -a Linux soleus01.soleus.nu 2.6.32-5-xen-amd64 #1 SMP Mon Oct 3 07:53:54 UTC 2011 x86_64 GNU/Linux Jeroen.
Hi, On 30 May 2013, at 11:04, Roger Pau Monné <roger.pau@citrix.com> wrote:> So it looks like the system rebooted (but it was not a crash or a > sporadic reboot? the kernel seems to be aware of the reboot request). It > would be interesting if you could provide the output of the serial > console when this happens, that might be helpful. Did you enable > xenconsoled logging?Unfortunately I did not.> Also, could you provide more info about your system, Xen version, what > workload was the DomU running, Dom0 kernel version?There was no one logged in at the time of the reboot according to the last log. I did do some sysbench tests during the day, but that was way before it rebooted. The only thing that could be running during that time was daily periodic. $ sudo xm info host : soleus01.soleus.nu release : 2.6.32-5-xen-amd64 version : #1 SMP Mon Oct 3 07:53:54 UTC 2011 machine : x86_64 nr_cpus : 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2200 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 65534 free_memory : 6866 node_to_cpu : node0:0-3 node1:4-7 node_to_memory : node0:3128 node1:3737 node_to_dma32_mem : node0:3128 node1:0 max_node_id : 1 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=1852M cc_compiler : gcc version 4.4.5 (Debian 4.4.5-10) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Wed Jan 12 14:04:06 UTC 2011 xend_config_format : 4 $ uname -a Linux soleus01.soleus.nu 2.6.32-5-xen-amd64 #1 SMP Mon Oct 3 07:53:54 UTC 2011 x86_64 GNU/Linux Jeroen.
On Thu, May 30, 2013 at 5:15 AM, Jeroen van der Ham <jeroen@dckd.nl> wrote:> Hi, > > On 30 May 2013, at 11:04, Roger Pau Monné <roger.pau@citrix.com> wrote: > > So it looks like the system rebooted (but it was not a crash or a > > sporadic reboot? the kernel seems to be aware of the reboot request). It > > would be interesting if you could provide the output of the serial > > console when this happens, that might be helpful. Did you enable > > xenconsoled logging? > > Unfortunately I did not. > > > Also, could you provide more info about your system, Xen version, what > > workload was the DomU running, Dom0 kernel version? > > There was no one logged in at the time of the reboot according to the last > log. > I did do some sysbench tests during the day, but that was way before it > rebooted. The only thing that could be running during that time was daily > periodic. > > $ sudo xm info > host : soleus01.soleus.nu > release : 2.6.32-5-xen-amd64 > version : #1 SMP Mon Oct 3 07:53:54 UTC 2011 > machine : x86_64 > nr_cpus : 8 > nr_nodes : 2 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2200 > hw_caps : > 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 > virt_caps : hvm > total_memory : 65534 > free_memory : 6866 > node_to_cpu : node0:0-3 > node1:4-7 > node_to_memory : node0:3128 > node1:3737 > node_to_dma32_mem : node0:3128 > node1:0 > max_node_id : 1 > xen_major : 4 > xen_minor : 0 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=1852M > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-10) > cc_compile_by : waldi > cc_compile_domain : debian.org > cc_compile_date : Wed Jan 12 14:04:06 UTC 2011 > xend_config_format : 4 > > $ uname -a > Linux soleus01.soleus.nu 2.6.32-5-xen-amd64 #1 SMP Mon Oct 3 07:53:54 UTC > 2011 x86_64 GNU/Linux > > Jeroen. > >first is this a public vm ? and if so who is?? May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] because it is after this potential ssh login attempt, so is this you, has there been a breach ? only thing i noticed, but it might be nothing.> _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, May 30, 2013 at 5:15 AM, Jeroen van der Ham <jeroen@dckd.nl> wrote:> Hi, > > On 30 May 2013, at 11:04, Roger Pau Monné <roger.pau@citrix.com> wrote: > > So it looks like the system rebooted (but it was not a crash or a > > sporadic reboot? the kernel seems to be aware of the reboot request). It > > would be interesting if you could provide the output of the serial > > console when this happens, that might be helpful. Did you enable > > xenconsoled logging? > > Unfortunately I did not. > > > Also, could you provide more info about your system, Xen version, what > > workload was the DomU running, Dom0 kernel version? > > There was no one logged in at the time of the reboot according to the last > log. > I did do some sysbench tests during the day, but that was way before it > rebooted. The only thing that could be running during that time was daily > periodic. > > $ sudo xm info > host : soleus01.soleus.nu > release : 2.6.32-5-xen-amd64 > version : #1 SMP Mon Oct 3 07:53:54 UTC 2011 > machine : x86_64 > nr_cpus : 8 > nr_nodes : 2 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2200 > hw_caps : > 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 > virt_caps : hvm > total_memory : 65534 > free_memory : 6866 > node_to_cpu : node0:0-3 > node1:4-7 > node_to_memory : node0:3128 > node1:3737 > node_to_dma32_mem : node0:3128 > node1:0 > max_node_id : 1 > xen_major : 4 > xen_minor : 0 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=1852M > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-10) > cc_compile_by : waldi > cc_compile_domain : debian.org > cc_compile_date : Wed Jan 12 14:04:06 UTC 2011 > xend_config_format : 4 > > $ uname -a > Linux soleus01.soleus.nu 2.6.32-5-xen-amd64 #1 SMP Mon Oct 3 07:53:54 UTC > 2011 x86_64 GNU/Linux > > Jeroen. > >first is this a public vm ? and if so who is?? May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from 150.165.15.175: 11: Bye Bye [preauth] because it is after this potential ssh login attempt, so is this you, has there been a breach ? only thing i noticed, but it might be nothing.> _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Hi, On 30 May 2013, at 16:56, Outback Dingo <outbackdingo@gmail.com> wrote:> first is this a public vm ? and if so who is?? > May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from > 150.165.15.175: 11: Bye Bye [preauth] > > because it is after this potential ssh login attempt, so is this you, has > there been a breach ? only thing i noticed, but it might be nothing.This VM is on a public IP indeed, and SSH connectivity is enabled. As with any publicly accessible host this then becomes the target of ssh scans. I included the message just to show that between it and the reboot nothing had been logged. AFAICT there has not been a breach, and I have not seen any indications at all that there may be one. Jeroen.
Hi, On 30 May 2013, at 16:56, Outback Dingo <outbackdingo@gmail.com> wrote:> first is this a public vm ? and if so who is?? > May 29 23:42:30 image01 sshd[31227]: error: Received disconnect from > 150.165.15.175: 11: Bye Bye [preauth] > > because it is after this potential ssh login attempt, so is this you, has > there been a breach ? only thing i noticed, but it might be nothing.This VM is on a public IP indeed, and SSH connectivity is enabled. As with any publicly accessible host this then becomes the target of ssh scans. I included the message just to show that between it and the reboot nothing had been logged. AFAICT there has not been a breach, and I have not seen any indications at all that there may be one. Jeroen.
Hello, I''ve pushed a new branch, pvhvm_v14 that contains support for live migration. While there I''ve also rebased the changes on top of current HEAD, so now it contains the recent fixes to blkfront and netfront. http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14 Some notes on this branch, I''ve mainly tested it with Xen 4.3 (unstable) because previous Xen versions have problems with the PV clock used in PVHVM when migrating. In order to be able to migrate a PVHVM guest you will need to add tsc_mode="native_paravirt" to your config file or apply the following patch to Xen: http://marc.info/?l=xen-devel&m=137036010517331 I would say that migration across the 4.x series will work without problems (because they all have support for vector callback injection), but migrating from 4.x to 3.x will certainly not work. On the other hand, migrating a guest started on 3.4 to 4.0 should work, although I have not tested it. Also, if the migration process fails for some reason, resuming the original guest on the sender side will leave the VM without working nics and disks, this is a problem with netfront and blkfront not being able to resume after suspension if the guest was not actually migrated. Roger.
Hello, I''ve pushed a new branch, pvhvm_v14 that contains support for live migration. While there I''ve also rebased the changes on top of current HEAD, so now it contains the recent fixes to blkfront and netfront. http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14 Some notes on this branch, I''ve mainly tested it with Xen 4.3 (unstable) because previous Xen versions have problems with the PV clock used in PVHVM when migrating. In order to be able to migrate a PVHVM guest you will need to add tsc_mode="native_paravirt" to your config file or apply the following patch to Xen: http://marc.info/?l=xen-devel&m=137036010517331 I would say that migration across the 4.x series will work without problems (because they all have support for vector callback injection), but migrating from 4.x to 3.x will certainly not work. On the other hand, migrating a guest started on 3.4 to 4.0 should work, although I have not tested it. Also, if the migration process fails for some reason, resuming the original guest on the sender side will leave the VM without working nics and disks, this is a problem with netfront and blkfront not being able to resume after suspension if the guest was not actually migrated. Roger.
On Mon, Jun 10, 2013 at 10:48 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v14 that contains support for live > migration. While there I''ve also rebased the changes on top of current > HEAD, so now it contains the recent fixes to blkfront and netfront. > > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14looking at your master branch your 2 weeks behind current... so where did you rebase your changes to head, or are you referring to your HEAD, and not FreeBSD _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Mon, Jun 10, 2013 at 10:48 AM, Roger Pau Monné <roger.pau@citrix.com>wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v14 that contains support for live > migration. While there I''ve also rebased the changes on top of current > HEAD, so now it contains the recent fixes to blkfront and netfront. > > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14looking at your master branch your 2 weeks behind current... so where did you rebase your changes to head, or are you referring to your HEAD, and not FreeBSD _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On 10/06/13 17:09, Outback Dingo wrote:> > > > On Mon, Jun 10, 2013 at 10:48 AM, Roger Pau Monné <roger.pau@citrix.com > <mailto:roger.pau@citrix.com>> wrote: > > Hello, > > I''ve pushed a new branch, pvhvm_v14 that contains support for live > migration. While there I''ve also rebased the changes on top of current > HEAD, so now it contains the recent fixes to blkfront and netfront. > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14 > > > looking at your master branch your 2 weeks behind current... so where > did you rebase your changes to head, or are you referring to your HEAD, > and not FreeBSDNo, my HEAD commit from FreeBSD master repository is from 3 days ago: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=commit;h=5311e12c931df9b67b64913670eab76a994317b9 This is the commit where I rebased my pvhvm_v14 branch.
On 10/06/13 17:09, Outback Dingo wrote:> > > > On Mon, Jun 10, 2013 at 10:48 AM, Roger Pau Monné <roger.pau@citrix.com > <mailto:roger.pau@citrix.com>> wrote: > > Hello, > > I''ve pushed a new branch, pvhvm_v14 that contains support for live > migration. While there I''ve also rebased the changes on top of current > HEAD, so now it contains the recent fixes to blkfront and netfront. > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14 > > > looking at your master branch your 2 weeks behind current... so where > did you rebase your changes to head, or are you referring to your HEAD, > and not FreeBSDNo, my HEAD commit from FreeBSD master repository is from 3 days ago: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=commit;h=5311e12c931df9b67b64913670eab76a994317b9 This is the commit where I rebased my pvhvm_v14 branch.
On 10/06/13 16:48, Roger Pau Monné wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v14 that contains support for live > migration. While there I''ve also rebased the changes on top of current > HEAD, so now it contains the recent fixes to blkfront and netfront. > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14Hello, There where some issues with the previous branch (pvhvm_v14), I''ve pushed a new one (pvhvm_v16) that fixes the following bugs: * Make sure there are no IPIs in flight while the VM is migrated, having in-flight IPIs is a problem because on resume the event channels are re-initialized, so all pending events are lost, including IPIs. * Reset the clock after migration, this prevent clock drifts when the VM is migrated. * blkfront was not correctly freeing the old event channel port. The following two commits are needed for Xen: f8e8fd56bd7d5675e8331b4ec74bae76c9dbf24e x86/HVM: fix initialization of wallclock time for PVHVM on migration 32c864a35ece2c24a336d183869a546798a4b241 x86/vtsc: update vcpu_time in hvm_set_guest_time With this branch I''ve been able to successfully local migrate a busy VM 400 times consecutively. As usual, the branch can be found here: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v16
On 10/06/13 16:48, Roger Pau Monné wrote:> Hello, > > I''ve pushed a new branch, pvhvm_v14 that contains support for live > migration. While there I''ve also rebased the changes on top of current > HEAD, so now it contains the recent fixes to blkfront and netfront. > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v14Hello, There where some issues with the previous branch (pvhvm_v14), I''ve pushed a new one (pvhvm_v16) that fixes the following bugs: * Make sure there are no IPIs in flight while the VM is migrated, having in-flight IPIs is a problem because on resume the event channels are re-initialized, so all pending events are lost, including IPIs. * Reset the clock after migration, this prevent clock drifts when the VM is migrated. * blkfront was not correctly freeing the old event channel port. The following two commits are needed for Xen: f8e8fd56bd7d5675e8331b4ec74bae76c9dbf24e x86/HVM: fix initialization of wallclock time for PVHVM on migration 32c864a35ece2c24a336d183869a546798a4b241 x86/vtsc: update vcpu_time in hvm_set_guest_time With this branch I''ve been able to successfully local migrate a busy VM 400 times consecutively. As usual, the branch can be found here: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v16