[Differential] [Updated] D1944: PF and VIMAGE fixes
gnn added a comment. Any update on this? REVISION DETAIL https://reviews.freebsd.org/D1944 To: nvass-gmx.com, bz, zec, trociny, glebius, rodrigc, kristof, gnn Cc: freebsd-virtualization, freebsd-pf, freebsd-net ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
[Differential] [Accepted] D1309: VIMAGE PF fixes #1
gnn accepted this revision. gnn added a reviewer: gnn. This revision is now accepted and ready to land. REVISION DETAIL https://reviews.freebsd.org/D1309 To: rodrigc, bz, glebius, trociny, zec, np, melifaro, hrs, wollman, bryanv, rpaulo, adrian, gnn, hiren, rwatson Cc: freebsd-virtualization, freebsd-pf, freebsd-net ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE in GENERIC
On 30 Nov 2014, at 5:04, Julian Elischer wrote: On 11/29/14, 5:28 PM, Craig Rodrigues wrote: On Mon, Nov 24, 2014 at 9:03 AM, Julian Elischer jul...@freebsd.org mailto:jul...@freebsd.org wrote: also look at the following: (a little dated) http://p4web.freebsd.org/@md=dcd=//depot/projects/vimage/cdf=//depot/projects/vimage/porting_to_vimage.txtc=tO0@//depot/projects/vimage/porting_to_vimage.txt?ac=22 This is a useful document. I put it on the wiki: https://wiki.freebsd.org/VIMAGE/porting-to-vimage Thanks.. wow, did I actually know ALL that only 5 years ago? Scary. probbaly worth having someone who is currently active and up to date look at it to see if it's all still correct.. especially the module load/unload stuff. -- Craig On a slight tangent. I ran VIMAGE kernels vs. non VIMAGE kernels for both a VANILLA kernel and a PF kernel (PF on but no rules) as a quick smoke test today. The raw forwarding performance was unchanged between kernels with and without VIMAGE on a 10G based system in the Sentex lab (lion1). I will be doing a bit more work in this area and will then put up some results in my netperf github repo. The tests are easy enough to run if you have 3 systems, and Conductor installed. The source, sink and dut config files are all there to be updated and tried. Best, George ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE in GENERIC
On 1 Dec 2014, at 23:12, Julian Elischer wrote: On 12/2/14, 12:07 PM, George Neville-Neil wrote: On 30 Nov 2014, at 5:04, Julian Elischer wrote: On 11/29/14, 5:28 PM, Craig Rodrigues wrote: On Mon, Nov 24, 2014 at 9:03 AM, Julian Elischer jul...@freebsd.org mailto:jul...@freebsd.org wrote: also look at the following: (a little dated) http://p4web.freebsd.org/@md=dcd=//depot/projects/vimage/cdf=//depot/projects/vimage/porting_to_vimage.txtc=tO0@//depot/projects/vimage/porting_to_vimage.txt?ac=22 This is a useful document. I put it on the wiki: https://wiki.freebsd.org/VIMAGE/porting-to-vimage Thanks.. wow, did I actually know ALL that only 5 years ago? Scary. probbaly worth having someone who is currently active and up to date look at it to see if it's all still correct.. especially the module load/unload stuff. -- Craig On a slight tangent. I ran VIMAGE kernels vs. non VIMAGE kernels for both a VANILLA kernel and a PF kernel (PF on but no rules) as a quick smoke test today. The raw forwarding performance was unchanged between kernels with and without VIMAGE on a 10G based system in the Sentex lab (lion1). I will be doing a bit more work in this area and will then put up some results in my netperf github repo. The tests are easy enough to run if you have 3 systems, and Conductor installed. The source, sink and dut config files are all there to be updated and tried. Best, George the interesting benchmarks are if you have multiple sessions and spread them across multiple vimage jails, and compare that with the same number of sessions crowded onto a single machine.. lock contention goes down of course so things can actually get faster. All in good time. Best, George ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Fatal trap 1: priviledged instruction fault while in kernel mode...
On Apr 13, 2013, at 23:54 , Peter Grehan gre...@freebsd.org wrote: Hi George, I just started trying to run bhyve on a Thinkpad X220. This has a core i5 and EPT support, dmesg attached. I'm trying with the March snapshots (02 March and 30 March so far) and have gotten the above panic instantly upon trying the vmrun.sh script. I took a shot of the screen after the panic but at that point I can't use the keyboard with the machine at all. dmesg for the machine is attached to this email, and the photo is at: http://people.freebsd.org/~gnn/bhyvecrash.jpg I'm guessing this recent commit may fix the panic http://svnweb.freebsd.org/base?view=revisionrevision=249396 ... but, is it possible that VT-x is disabled in the BIOS ? (the cause of the crash on VM creation). OK I can confirm that updating to the latest HEAD and turning on VT in the BIOS worked. Thanks! Best, George ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Fatal trap 1: priviledged instruction fault while in kernel mode...
On Apr 13, 2013, at 23:54 , Peter Grehan gre...@freebsd.org wrote: Hi George, I just started trying to run bhyve on a Thinkpad X220. This has a core i5 and EPT support, dmesg attached. I'm trying with the March snapshots (02 March and 30 March so far) and have gotten the above panic instantly upon trying the vmrun.sh script. I took a shot of the screen after the panic but at that point I can't use the keyboard with the machine at all. dmesg for the machine is attached to this email, and the photo is at: http://people.freebsd.org/~gnn/bhyvecrash.jpg I'm guessing this recent commit may fix the panic http://svnweb.freebsd.org/base?view=revisionrevision=249396 ... but, is it possible that VT-x is disabled in the BIOS ? (the cause of the crash on VM creation). I'll check that tonight. Thanks! Best, George ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Fatal trap 1: priviledged instruction fault while in kernel mode...
Howdy, I just started trying to run bhyve on a Thinkpad X220. This has a core i5 and EPT support, dmesg attached. I'm trying with the March snapshots (02 March and 30 March so far) and have gotten the above panic instantly upon trying the vmrun.sh script. I took a shot of the screen after the panic but at that point I can't use the keyboard with the machine at all. dmesg for the machine is attached to this email, and the photo is at: http://people.freebsd.org/~gnn/bhyvecrash.jpg Best, George 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 r247862M: Tue Mar 5 23:30:46 EST 2013 root@punk:/usr/obj/usr/home/gnn/svn/head-punk/src/sys/GENERIC amd64 FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 WARNING: WITNESS option enabled, expect reduced performance. module iwn already present! CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (2491.96-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 0x6 Model = 0x2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x1fbae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX AMD Features=0x28000800SYSCALL,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16395001856 (15635 MB) Event timer LAPIC quality 600 ACPI APIC Table: LENOVO TP-8D FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 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 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: LENOVO TP-8D on motherboard acpi_ec0: Embedded Controller: GPE 0x11, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bf90 (3) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 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 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 550 Event timer HPET1 frequency 14318180 Hz quality 440 Event timer HPET2 frequency 14318180 Hz quality 440 Event timer HPET3 frequency 14318180 Hz quality 440 Event timer HPET4 frequency 14318180 Hz quality 440 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: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x5000-0x503f mem 0xd000-0xd03f,0xc000-0xcfff irq 16 at device 2.0 on pci0 agp0: SandyBridge mobile GT2+ IG on vgapci0 agp0: aperture size is 256M, detected 65532k stolen memory pci0: simple comms at device 22.0 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 7.3.7 port 0x5080-0x509f mem 0xd250-0xd251,0xd252b000-0xd252bfff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: f0:de:f1:55:d8:16 ehci0: EHCI (generic) USB 2.0 controller mem 0xd252a000-0xd252a3ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 hdac0: Intel Cougar Point HDA Controller mem 0xd252-0xd2523fff irq 22 at device 27.0 on pci0 pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 pci3: ACPI PCI bus on pcib2 iwn0: Intel Centrino Advanced-N 6205 mem 0xd240-0xd2401fff irq 17 at device 0.0 on pci3 pcib3: ACPI PCI-PCI bridge irq 19 at device 28.3 on pci0 pci5: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci13: ACPI PCI bus on pcib4 sdhci_pci0: RICOH R5CE823 SD mem 0xd140-0xd14000ff irq 16 at device 0.0 on pci13 sdhci_pci0: 1 slot(s) allocated ehci1: EHCI (generic) USB 2.0 controller mem 0xd2529000-0xd25293ff irq 23 at device 29.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci1 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 ahci0: Intel Cougar Point AHCI SATA controller port 0x50a8-0x50af,0x50b4-0x50b7,0x50a0-0x50a7,0x50b0-0x50b3,0x5060-0x507f mem 0xd2528000-0xd25287ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not
