Re: fpudna: fpcurthread == curthread XXXX times
Hi, I do have the same issue on 8.4-RELEASE, 9.1-RELEASE, 9.2-RELEASE based on XENHVM config (amd64). The 'uname' in the guests looks like this one: root@my:/ # uname -a FreeBSD my.vm 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Mon Aug 19 14:08:42 EEST 2013 r...@my.vm:/usr/obj/usr/src/sys/XENHVM amd64 I could also confirm the issue doesn't affect 8.2 8.3, 9.0 versions. The Hypervisor is "CentOS release 5.9" with Xen 3.4.3, and its details are: # cat /proc/cpuinfo ... processor : 15 vendor_id : AuthenticAMD cpu family : 16 model : 9 model name : AMD Opteron(tm) Processor 6128 stepping: 1 cpu MHz : 2000.140 cache size : 512 KB physical id : 15 siblings: 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc pni cx16 popcnt lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse bogomips: 5002.23 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc [6] [7] [8] # xm info host : hv.build release: 2.6.18-308.20.1.el5.xen version: #1 SMP Wed Dec 5 13:30:38 GMT 2012 machine: x86_64 nr_cpus: 16 nr_nodes : 1 cores_per_socket : 8 threads_per_core : 1 cpu_mhz: 2000 hw_caps: 178bf3ff:efd3fbff::0310:00802001::000837ff: virt_caps : hvm total_memory : 49150 free_memory: 45664 node_to_cpu: node0:0-15 node_to_memory : node0:45664 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=0x8000 xen_changeset : unavailable cc_compiler: gcc version 4.1.2 20080704 (Red Hat 4.1.2-52) cc_compile_by : root cc_compile_domain : hv.build cc_compile_date: Wed Sep 5 18:01:10 EEST 2012 xend_config_format : 4 Could anybody please help/assist me with the issue fixing ? Thanks --- Yura On Jun 2, 2011, at 10:22 PM, Sergi wrote: > On 01/06/11 23:36, Kostik Belousov wrote: >> On Wed, Jun 01, 2011 at 03:00:51PM +0200, Sergi wrote: >> >>> On 01/06/11 11:36, Sergi wrote: >>> On 01/06/11 10:21, Kostik Belousov wrote: > On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote: > >> Hello, >> >> I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian >> squeeze and xen-hypervisor-4.0-amd64. >> >> If I cfg this hvm with cpu> 4 : >> >> vcpus= 5 >> >> these messages block the server : >> >> fpudna: fpcurthread == curthread times >> >> The machine is pingable but I'm unable to ssh to it. >> >> On single user it works fine, fsck an so on ok, but when switching to >> multiuser these fpudna messages start flooding. >> >> I've googled but haven't found anything; something from 2005 about >> fpudna : >> >> >> http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html >> >> and this link, but I don't have the options he mentions enabled on the >> kernel : >> >> http://forums.freebsd.org/showthread.php?t=17979 >> >> Has anyone stepped on this behaviour before?, is there any workaround? >> The machine really seems to detect cpu's available and responds to >> keyboard >> on VNC, but it's impossible to see whats written down because of the >> messages flooding the screen. >> > You did not specified the architecture of the domu. From the message, > I can > guess that your guest is running amd64 kernel. There are slight > differences > in the handling of the FPU in i386 and amd64 that may matter there. > > The message you reported means that the FreeBSD kernel assumes that FPU > is currently loaded with the context of the current thread, but the > CR0.TS bit is set, meaning that FPU context is set for switch. > > AFAIR, HVM means that you run bare-metal kernel, right ? Most likely, > it is some issue with Xen itself. I am curious whether the following > will cause any usermode-visible regression for you: > > diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c > index 08e5e57..a5ee853 100644 > --- a/sys/amd64/amd64/fpu.c > +++ b/sys/amd64/amd64/fpu.c > @@ -394,14 +394,8 @@ fpudna(void) > struct pcb *pcb; > > cr
Re: FreeBSD PVHVM call for testing
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::3b40:009ce3bd::0001: 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=0x8000 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 r...@yurak2.vm:/usr/obj/freebsd/sys/XENHVM amd64 --- Yura On May 22, 2013, at 18:27 PM, Yuriy Kohut wrote: > Hi, > > I've just successfully run FreeBSD 9.1 based guest with &
Re: FreeBSD PVHVM call for testing
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::0340:009ce3bd::0001: 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=0x8000 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 r...@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é wrote:
Re: 8.2-RELEASE (XEN config) panics on /usr/src/sys/i386/xen/pmap.c:1073
Thanks for making things clear. --- Yura On Mar 18, 2011, at 10:11 PM, Colin Percival wrote: > On 03/18/11 02:56, Yuriy Kohut wrote: >> I got kernel panics while was compiling GHC from ports: >> >> ===> Configuring for hs-ghc-paths-0.1.0.5_1 >> [1 of 1] Compiling Main ( Setup.hs, Setup.o ) >> Linking setup ... >> gcc: Internal error: Killed: 9 (program ld) >> Please submit a full bug report. >> See http://gcc.gnu.org/bugs.html> for instructions. >> *** Error code 1 > > That's not a kernel panic... > >> The panic details are (from main console): >> >> lock order reversal: >> 1st 0xc05b08c4 PMAP2 (PMAP2) @ /usr/src/sys/i386/xen/pmap.c:1049 >> 2nd 0xc054de04 vm page queue mutex (vm page queue mutex) @ >> /usr/src/sys/i386/xen/pmap.c:1073 >> KDB: stack backtrace: >> X_db_sym_numargs(c0363f9a,c03e8cbc,282,0,a3481215,...) at >> X_db_sym_numargs+0x146 >> kdb_backtrace(c010e74b,c0366eaf,c16ca5f0,c16ca178,cca6eab8,...) at >> kdb_backtrace+0x2a >> witness_display_spinlock(c0366eaf,c054de04,c03670bc,c16ca178,c038d96c,...) >> at witness_display_spinlock+0x75 >> witness_checkorder(c054de04,9,c038d96c,431,0,...) at witness_checkorder+0x839 >> _mtx_lock_flags(c054de04,0,c038d96c,431,292,...) at _mtx_lock_flags+0xc4 >> pmap_extract(c1ae78fc,28202000,4,c035f3ba,c1ae78fc,...) at pmap_extract+0x1c8 >> vm_fault_unwire(c1ae784c,28202000,28203000,0,0,...) at vm_fault_unwire+0x32 >> vm_map_delete(c1ae784c,1000,bf80,1,c1ae784c,...) at vm_map_delete+0x17f >> vm_map_remove(c1ae784c,1000,bf80,0,c1b2d7f8,...) at vm_map_remove+0x51 >> vmspace_exit(c18f82d0,0,c035bd35,12d,cca6ec60,...) at vmspace_exit+0xbf >> exit1(c18f82d0,0,cca6ec8c,c0117f86,c18f82d0,...) at exit1+0x5db >> sys_exit(c18f82d0,cca6ecfc,cca6ed38,c0365893,0,...) at sys_exit+0x1d >> syscallenter(c18f82d0,cca6ecf4,cca6ecf4,0,c03335ea,...) at syscallenter+0x246 >> syscall(cca6ed38) at syscall+0x34 >> Xint0x80_syscall() at Xint0x80_syscall+0x22 >> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x280ff32f, esp = >> 0xbf7fe72c, ebp = 0xbf7fe738 --- > > This is a known LOR, but shouldn't cause a kernel panic. > > -- > Colin Percival > Security Officer, FreeBSD | freebsd.org | The power to serve > Founder / author, Tarsnap | tarsnap.com | Online backups for the truly > paranoid ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
8.2-RELEASE (XEN config) panics on /usr/src/sys/i386/xen/pmap.c:1073
Hi, FreeBSD DomU details: FreeBSD 8.2-RELEASE (XEN) i386 The kernel was compiled as # make buildkernel KERNCONF=XEN INSTKERNNAME=8.2-XEN The CVS brach used is: RELENG_8_2 I got kernel panics while was compiling GHC from ports: ===> Configuring for hs-ghc-paths-0.1.0.5_1 [1 of 1] Compiling Main ( Setup.hs, Setup.o ) Linking setup ... gcc: Internal error: Killed: 9 (program ld) Please submit a full bug report. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 The panic details are (from main console): lock order reversal: 1st 0xc05b08c4 PMAP2 (PMAP2) @ /usr/src/sys/i386/xen/pmap.c:1049 2nd 0xc054de04 vm page queue mutex (vm page queue mutex) @ /usr/src/sys/i386/xen/pmap.c:1073 KDB: stack backtrace: X_db_sym_numargs(c0363f9a,c03e8cbc,282,0,a3481215,...) at X_db_sym_numargs+0x146 kdb_backtrace(c010e74b,c0366eaf,c16ca5f0,c16ca178,cca6eab8,...) at kdb_backtrace+0x2a witness_display_spinlock(c0366eaf,c054de04,c03670bc,c16ca178,c038d96c,...) at witness_display_spinlock+0x75 witness_checkorder(c054de04,9,c038d96c,431,0,...) at witness_checkorder+0x839 _mtx_lock_flags(c054de04,0,c038d96c,431,292,...) at _mtx_lock_flags+0xc4 pmap_extract(c1ae78fc,28202000,4,c035f3ba,c1ae78fc,...) at pmap_extract+0x1c8 vm_fault_unwire(c1ae784c,28202000,28203000,0,0,...) at vm_fault_unwire+0x32 vm_map_delete(c1ae784c,1000,bf80,1,c1ae784c,...) at vm_map_delete+0x17f vm_map_remove(c1ae784c,1000,bf80,0,c1b2d7f8,...) at vm_map_remove+0x51 vmspace_exit(c18f82d0,0,c035bd35,12d,cca6ec60,...) at vmspace_exit+0xbf exit1(c18f82d0,0,cca6ec8c,c0117f86,c18f82d0,...) at exit1+0x5db sys_exit(c18f82d0,cca6ecfc,cca6ed38,c0365893,0,...) at sys_exit+0x1d syscallenter(c18f82d0,cca6ecf4,cca6ecf4,0,c03335ea,...) at syscallenter+0x246 syscall(cca6ed38) at syscall+0x34 Xint0x80_syscall() at Xint0x80_syscall+0x22 --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x280ff32f, esp = 0xbf7fe72c, ebp = 0xbf7fe738 --- Could somebody assis me with that ? Please let me know if more details required. --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
FreeBSD 8.2-PRERELEASE (XEN) kernel panic at mkdir
Hi, I'm just installed the latest FreeBSD i386 Paravirtualized DomU based on the XEN kernel from RELENG_8. Kernel panics while ports installing (using sysinstall). lock order reversal: 1st 0xc0f37ab0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2636 2nd 0xc13d3e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 KDB: stack backtrace: X_db_sym_numargs(c03635ba,c0514c30,c1232870,c14116f0,636bf9e5,...) at X_db_sym_numargs+0x146 kdb_backtrace(c010e7ab,c03664cf,c10cc6d8,c10cf0b0,c80fc8a0,...) at kdb_backtrace+0x2a witness_display_spinlock(c03664cf,c13d3e00,c03814cd,c10cf0b0,c0381166,...) at witness_display_spinlock+0x75 witness_checkorder(c13d3e00,9,c0381166,11d,0,...) at witness_checkorder+0x839 _sx_xlock(c13d3e00,0,c0381166,11d,c141e32c,...) at _sx_xlock+0x85 ufsdirhash_enduseful(c0f37a50,c4214800,200,c4214810,c80fc970,...) at ufsdirhash_enduseful+0x2f5 ufsdirhash_add(c141e32c,c80fc9fc,810,c80fc95c,c80fc960,...) at ufsdirhash_add+0x13 ufs_direnter(c1411648,c14fe648,c80fc9fc,c80fcbe0,c0f452e0,...) at ufs_direnter+0x729 ufs_readdir(c80fcc08,c80fcc1c,0,c80fcbb4,c80fcb4c,...) at ufs_readdir+0x2267 VOP_MKDIR_APV(c03bd600,c80fcc08,68,0,0,...) at VOP_MKDIR_APV+0xa5 kern_mkdirat(c1232870,ff9c,2843a780,0,1ed,...) at kern_mkdirat+0x211 kern_mkdir(c1232870,2843a780,0,1ed,c80fcc8c,...) at kern_mkdir+0x2e mkdir(c1232870,c80fccfc,c80fcd38,c0364eb3,0,...) at mkdir+0x29 syscallenter(c1232870,c80fccf4,c80fccf4,2,c0332bfa,...) at syscallenter+0x246 syscall(c80fcd38) at syscall+0x34 Xint0x80_syscall() at Xint0x80_syscall+0x22 --- syscall (136, FreeBSD ELF32, mkdir), eip = 0x28331a53, esp = 0xbf7fc47c, ebp = 0xbf7fc4a8 --- panic: ufs_dirbad: /: bad dir ino 95182 at offset 0: mangled entry cpuid = 0 KDB: enter: panic [thread pid 849 tid 100032 ] Stopped at kdb_enter+0x3a: movl$0,kdb_why DomU details: kernel = "/var/lib/xen/images/kernel.freebsd" memory = "128" name = "freebsd" vcpus = "1" vif = [ 'mac=00:16:3e:fb:41:28, bridge=xenbr0, ip=68.169.47.45, vifname=freebsd ] disk = [ 'phy:/dev/iscsi_0_5,sda,w', 'phy:/dev/iscsi_0_125,sdb,w' ] extra = "boot_verbose=1" extra += ",vfs.root.mountfrom=ufs:/dev/da0" extra += ",kern.hz=100" Dom0 details: CentOS release 5.4 (Final) Linux 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-94.el5_4.2 --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, Just let you know: everything starts work for me in 8.2-PRERELEASE (RELENG_8) Thank you for your work. I'm also highly interesting FreeBSD paravirtualized DOMU to be stable. I'll build test XEN i386 today. I'll let you know results if you want. --- Yura On Dec 3, 2010, at 3:23 PM, Justin T. Gibbs wrote: > On Dec 3, 2010, at 4:12 AM, Yuriy Kohut wrote: > >> Hi, >> >> I would not like to disturb you, but, have you a chance to reproduce the >> issue ? > > A FreeBSD stable/8 XENHVM kernel from yesterday functions properly for me in > my Xen environment. > >> The problem is not with CDROM device, but with boot process stops. > > Did you remove the CDROM from the device configuration for your domain? My > host systems do not have CDROM devices to pass through, so I have not tested > the impact of detecting a CDROM device on the FreeBSD XENHVM device probe > process. > > In short, I understand that you are not directly complaining a about CDROM > functionality, but my hunch is that the detection of a CDROM device is > exposing a bug in the block front driver which leads to a hang during boot. > > -- > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, I would not like to disturb you, but, have you a chance to reproduce the issue ? The problem is not with CDROM device, but with boot process stops. --- Yura On Dec 1, 2010, at 10:31 PM, Justin T. Gibbs wrote: > On 12/1/2010 4:52 AM, Yuriy Kohut wrote: >> Hi, >> >> Now your commit in place and I have built XENHVM on RELENG_8. >> >> >> Some things are changed for me, but the issue still exists. > > I will try to replicate your issues again later today. One notable > difference between my configuration and yours is that I am not passing > through any cdrom devices. I have no idea how well block front deals > with cdroms. My testing is on OpenSuSE 11.2 with Xen 4.0.0. > > -- > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, Now your commit in place and I have built XENHVM on RELENG_8. Some things are changed for me, but the issue still exists. For now: 'xn0' virtual network interface is detected during boot --- xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: MAC --- Then CDROM is detected, but connected as ad3 however acd0 was some line before: --- acd0: CDROM < QEMU DVD-ROM/0.10.2 at ata1-slave WDMA2 ... xbd2: 27MB at device/vbd/5696 on xenbusb_front0 xbd2: attaching as ad3 --- Just after that, boot stopped with same message: --- xctrl0: on xenstore0 run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb --- and then panic ... --- Yura On Dec 1, 2010, at 12:28 AM, Justin T. Gibbs wrote: > On 11/30/2010 2:45 PM, Sean Bruno wrote: >> Yeah, I'm not seeing this patch in -stable 8 yet. > > I was in such a rush to get out of the house Monday morning that I missed > the fact that I ran into the freeze on stable/8 and my commit was rejected. > I've resubmitted now with re's blessing. > > -- > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
switching to todays updates on RELENG_8 the following is got: - xctrl: xctrl0 already exists; skipping it xctrl0: on xenstore0 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config xen_usb_nop_confighook_cb xenbusb_nop_confighook_cb t_delta ... to long - And message repeats every 60 sec. --- Yura On Nov 30, 2010, at 5:07 PM, Yuriy Kohut wrote: > Hi, ones more > > Here is some results of my investigation running FreeBSD amd64 HVM Xen DomU > with PV drivers installed (XENHVM config is used). > . > FreeBSD was booted on "Boot FreeBSD with verbose logging" mode. > > Custom kernel was built using > - 8.1-RELEASE sources from src/sys installed with sysinstall > - RELENG_8_1 get with csup/cvsup > - RELENG_8 get with csup/cvsup > > Every time the same error got, and boot stops: > > ata1: New device: 00020001 > ata1-slave: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire > ... > ata1: reinit done .. > unknown: FAILURE - ATA_IDENTIFY timed aut LBA=0 > > The next messages are CDROM detection. And after that boot stops. > > > > Here is config I'm using for DomU: > > kernel = "/usr/lib/xen/boot/hvmloader" > builder='hvm' > memory = 1024 > #shadow_memory = 8 > name = "freebsd-8.1" > vif = [ 'bridge=eth0', ] > disk = [ > 'tap:aio:/opt/images/freebsd-8.1-test.img,hda,w', > "tap:aio:/opt/images/freebsd-8.1-swap.img,hdb,w", > #"phy:/dev/vg0/lvol18,ioemu:hdb,w", > 'file:/opt/iso/boot-freebsd.iso,hdd:cdrom,r' ] > device_model = "/usr/lib64/xen/bin/qemu-dm" > boot="cd" > sdl=0 > vnc=1 > vncpasswd='' > stdvga=0 > serial='pty' > acpi=1 > apic=1 > stdvga=0 > > > > Justin, I'm still not seing your update with csup for > sys/kern/subr_autoconf.c in RELENG_8 > --- > Yura > > On Nov 30, 2010, at 1:26 PM, Yuriy Kohut wrote: > >> Just built XENHVM based on RELENG_8 and got kernel panic. >> >> Please find VNC console snapshot attached. >> >> >> >> Unfortunately I have no way to copy/paste from VNC. >> --- >> Yura >> >> On Nov 30, 2010, at 11:36 AM, Yuriy Kohut wrote: >> >>> Hi, Justin, >>> >>> I'm using cvsup (csup) and still didn't see the merge on the RELENG_8... >>> >>> --- >>> Yura >>> >>> On Nov 29, 2010, at 5:29 PM, Yuriy Kohut wrote: >>> >>>> Ok, I'll check and let you know results >>>> >>>> Thank you >>>> --- >>>> Yura >>>> >>>> On Nov 29, 2010, at 5:06 PM, Justin T. Gibbs wrote: >>>> >>>>> On 11/29/2010 6:50 AM, Yuriy Kohut wrote: >>>>>> Hi, >>>>>> >>>>>> I have just build XENHVM from RELANG_8 cvs tag. >>>>>> >>>>>> VM stuck on booting too. The last message in VNC console was: >>>>>> - >>>>>> xctrl0: on xenstore0 >>>>>> - >>>>>> >>>>>> Could somebody please suggest ? >>>>> >>>>> I neglected to merge SVN revision 211236 into -stable, and this >>>>> should be the cause of your hang. I just submitted the merge, >>>>> but it will take a little while for it to be replicated into >>>>> CVS. Once you've pulled down this revision (it updates >>>>> sys/kern/subr_autoconf.c), can you rebuild, test, and report >>>>> your results? >>>>> >>>>> Thanks, >>>>> Justin >>>> >>>> ___ >>>> freebsd-xen@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >>>> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" >>> >>> ___ >>> freebsd-xen@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >>> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" >> >> ___ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" > > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, ones more Here is some results of my investigation running FreeBSD amd64 HVM Xen DomU with PV drivers installed (XENHVM config is used). . FreeBSD was booted on "Boot FreeBSD with verbose logging" mode. Custom kernel was built using - 8.1-RELEASE sources from src/sys installed with sysinstall - RELENG_8_1 get with csup/cvsup - RELENG_8 get with csup/cvsup Every time the same error got, and boot stops: ata1: New device: 00020001 ata1-slave: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ... ata1: reinit done .. unknown: FAILURE - ATA_IDENTIFY timed aut LBA=0 The next messages are CDROM detection. And after that boot stops. Here is config I'm using for DomU: kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 1024 #shadow_memory = 8 name = "freebsd-8.1" vif = [ 'bridge=eth0', ] disk = [ 'tap:aio:/opt/images/freebsd-8.1-test.img,hda,w', "tap:aio:/opt/images/freebsd-8.1-swap.img,hdb,w", #"phy:/dev/vg0/lvol18,ioemu:hdb,w", 'file:/opt/iso/boot-freebsd.iso,hdd:cdrom,r' ] device_model = "/usr/lib64/xen/bin/qemu-dm" boot="cd" sdl=0 vnc=1 vncpasswd='' stdvga=0 serial='pty' acpi=1 apic=1 stdvga=0 ---- Justin, I'm still not seing your update with csup for sys/kern/subr_autoconf.c in RELENG_8 --- Yura On Nov 30, 2010, at 1:26 PM, Yuriy Kohut wrote: > Just built XENHVM based on RELENG_8 and got kernel panic. > > Please find VNC console snapshot attached. > > > > Unfortunately I have no way to copy/paste from VNC. > --- > Yura > > On Nov 30, 2010, at 11:36 AM, Yuriy Kohut wrote: > >> Hi, Justin, >> >> I'm using cvsup (csup) and still didn't see the merge on the RELENG_8... >> >> --- >> Yura >> >> On Nov 29, 2010, at 5:29 PM, Yuriy Kohut wrote: >> >>> Ok, I'll check and let you know results >>> >>> Thank you >>> --- >>> Yura >>> >>> On Nov 29, 2010, at 5:06 PM, Justin T. Gibbs wrote: >>> >>>> On 11/29/2010 6:50 AM, Yuriy Kohut wrote: >>>>> Hi, >>>>> >>>>> I have just build XENHVM from RELANG_8 cvs tag. >>>>> >>>>> VM stuck on booting too. The last message in VNC console was: >>>>> - >>>>> xctrl0: on xenstore0 >>>>> - >>>>> >>>>> Could somebody please suggest ? >>>> >>>> I neglected to merge SVN revision 211236 into -stable, and this >>>> should be the cause of your hang. I just submitted the merge, >>>> but it will take a little while for it to be replicated into >>>> CVS. Once you've pulled down this revision (it updates >>>> sys/kern/subr_autoconf.c), can you rebuild, test, and report >>>> your results? >>>> >>>> Thanks, >>>> Justin >>> >>> ___ >>> freebsd-xen@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >>> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" >> >> ___ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" > > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Just built XENHVM based on RELENG_8 and got kernel panic. Please find VNC console snapshot attached. Unfortunately I have no way to copy/paste from VNC. --- Yura On Nov 30, 2010, at 11:36 AM, Yuriy Kohut wrote: > Hi, Justin, > > I'm using cvsup (csup) and still didn't see the merge on the RELENG_8... > > --- > Yura > > On Nov 29, 2010, at 5:29 PM, Yuriy Kohut wrote: > >> Ok, I'll check and let you know results >> >> Thank you >> --- >> Yura >> >> On Nov 29, 2010, at 5:06 PM, Justin T. Gibbs wrote: >> >>> On 11/29/2010 6:50 AM, Yuriy Kohut wrote: >>>> Hi, >>>> >>>> I have just build XENHVM from RELANG_8 cvs tag. >>>> >>>> VM stuck on booting too. The last message in VNC console was: >>>> - >>>> xctrl0: on xenstore0 >>>> - >>>> >>>> Could somebody please suggest ? >>> >>> I neglected to merge SVN revision 211236 into -stable, and this >>> should be the cause of your hang. I just submitted the merge, >>> but it will take a little while for it to be replicated into >>> CVS. Once you've pulled down this revision (it updates >>> sys/kern/subr_autoconf.c), can you rebuild, test, and report >>> your results? >>> >>> Thanks, >>> Justin >> >> ___ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" > > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, Justin, I'm using cvsup (csup) and still didn't see the merge on the RELENG_8... --- Yura On Nov 29, 2010, at 5:29 PM, Yuriy Kohut wrote: > Ok, I'll check and let you know results > > Thank you > --- > Yura > > On Nov 29, 2010, at 5:06 PM, Justin T. Gibbs wrote: > >> On 11/29/2010 6:50 AM, Yuriy Kohut wrote: >>> Hi, >>> >>> I have just build XENHVM from RELANG_8 cvs tag. >>> >>> VM stuck on booting too. The last message in VNC console was: >>> - >>> xctrl0: on xenstore0 >>> - >>> >>> Could somebody please suggest ? >> >> I neglected to merge SVN revision 211236 into -stable, and this >> should be the cause of your hang. I just submitted the merge, >> but it will take a little while for it to be replicated into >> CVS. Once you've pulled down this revision (it updates >> sys/kern/subr_autoconf.c), can you rebuild, test, and report >> your results? >> >> Thanks, >> Justin > > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Ok, I'll check and let you know results Thank you --- Yura On Nov 29, 2010, at 5:06 PM, Justin T. Gibbs wrote: > On 11/29/2010 6:50 AM, Yuriy Kohut wrote: >> Hi, >> >> I have just build XENHVM from RELANG_8 cvs tag. >> >> VM stuck on booting too. The last message in VNC console was: >> - >> xctrl0: on xenstore0 >> - >> >> Could somebody please suggest ? > > I neglected to merge SVN revision 211236 into -stable, and this > should be the cause of your hang. I just submitted the merge, > but it will take a little while for it to be replicated into > CVS. Once you've pulled down this revision (it updates > sys/kern/subr_autoconf.c), can you rebuild, test, and report > your results? > > Thanks, > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, I have just build XENHVM from RELANG_8 cvs tag. VM stuck on booting too. The last message in VNC console was: - xctrl0: on xenstore0 - Could somebody please suggest ? --- Yura On Nov 27, 2010, at 2:09 AM, Justin T. Gibbs wrote: > On 11/26/2010 8:56 AM, Yuriy Kohut wrote: >> Hi, >> >> I have just built XENHVM from RELANG_8_1. > > RELENG_8_1 doesn't have the latest Xen PV code in it. stable/8 (RELENG_8 if > checking out of CVS instead of SVN?) does. > > -- > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
I'll check RELANG_8. Thank you. --- Yura On Nov 27, 2010, at 2:09 AM, Justin T. Gibbs wrote: > On 11/26/2010 8:56 AM, Yuriy Kohut wrote: >> Hi, >> >> I have just built XENHVM from RELANG_8_1. > > RELENG_8_1 doesn't have the latest Xen PV code in it. stable/8 (RELENG_8 if > checking out of CVS instead of SVN?) does. > > -- > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, Luke, Could you please share your Xen FreeBSD HVM DomU config file ? --- Yura On Nov 26, 2010, at 4:26 PM, Luke Marsden wrote: > On Wed, 2010-11-24 at 09:24 -0800, Sean Bruno wrote: >> The version in -CURRENT and FreeBSD 8 that Justin is talking about is >> very stable. >> >> I will be updating FreeBSD 7 and 6 today. You will need to update from >> source to get this version as it is not on the release ISOs >> >> We are using it a lot at Yahoo. It is very stable. >> > > Just to add another positive data-point, inspired by this post (thanks > Sean!) I've just got 8.1-RELEASE working well on Flexiant, a UK-based > Xen HVM cloud infrastructure provider. > > Here are the incantations I used to get it running stably: > http://lukemarsden.net/blog/2010/11/running-freebsd-8-1-as-a-xen-hvm-domu-on-flexiant/ > > -- > Best Regards, > Luke Marsden > CTO, Hybrid Logic Ltd. > > Web: http://www.hybrid-cluster.com/ > Hybrid Web Cluster - cloud web hosting > > Mobile: +447791750420 > ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, I have just built XENHVM from RELANG_8_1. DomU boot stop just after CDROM was detected in kernel: acd0: CDROM at ata1-slave WDMA2 Boot doesn't continue for a long time, Xen shows VM is blocked: # xm list freebsd-8.1 NameID Mem VCPUs State Time(s) freebsd-8.1346 1024 1 -b113.3 By the other side, GENERIC worked just fine for me. Could somebody please assist ... --- Yura On Nov 26, 2010, at 4:26 PM, Luke Marsden wrote: > On Wed, 2010-11-24 at 09:24 -0800, Sean Bruno wrote: >> The version in -CURRENT and FreeBSD 8 that Justin is talking about is >> very stable. >> >> I will be updating FreeBSD 7 and 6 today. You will need to update from >> source to get this version as it is not on the release ISOs >> >> We are using it a lot at Yahoo. It is very stable. >> > > Just to add another positive data-point, inspired by this post (thanks > Sean!) I've just got 8.1-RELEASE working well on Flexiant, a UK-based > Xen HVM cloud infrastructure provider. > > Here are the incantations I used to get it running stably: > http://lukemarsden.net/blog/2010/11/running-freebsd-8-1-as-a-xen-hvm-domu-on-flexiant/ > > -- > Best Regards, > Luke Marsden > CTO, Hybrid Logic Ltd. > > Web: http://www.hybrid-cluster.com/ > Hybrid Web Cluster - cloud web hosting > > Mobile: +447791750420 > ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Xen PV drivers for FreeBSD
Hi, It is for amd64 only, correct ? Do you know is it stable enough ? --- Yura On Nov 24, 2010, at 3:48 PM, Justin T. Gibbs wrote: > On 11/23/2010 8:27 AM, Yuriy Kohut wrote: >> Hi, >> >> I'm trying HVM DomU since FreeBSD paravirtualized is not stable enough. >> >> Is there any Xen PV drivers which could be used for HVM FreeBSD DomU to not >> load system by full hardware virtualization ? > > Yes. Use the XENHVM kernel config file. > > -- > Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Xen PV drivers for FreeBSD
Hi, I'm trying HVM DomU since FreeBSD paravirtualized is not stable enough. Is there any Xen PV drivers which could be used for HVM FreeBSD DomU to not load system by full hardware virtualization ? Thanks --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: FreeBSD 8.1-RELEASE-p1 i386 xennet_get_responses messages in console
Hi, Dom0 details: CentOS release 5.4 (Final) x86_64 kernel: 2.6.18-164.6.1.el5xen Xen 3.0.3 (package from RHEL5 build xen-3.0.3-94.el5_4.2) DomU details: FreeBSD 8.1-RELEASE-p1 i386 Build from CVS tag: RELANG_8_1 I saw the messages any ones, and they gone after I reinstalled DomU. I'll try the patch if the issue appears ones more. Thank you. --- Yura On Nov 4, 2010, at 12:11 AM, Kenneth D. Merry wrote: > On Thu, Oct 28, 2010 at 15:02:41 +0300, Yuriy Kohut wrote: >> Hi, >> >> Does somebody know haw to deal with the following massages in the console: >> >> xennet_get_responses: too many frags 6 > max 5 > > What are you using for your Domain 0? > > I haven't run into that before, so it would be nice to have a setup that > would trigger this problem. > > It looks like there is a limit on the number of segments for LRO. I think > the limit is arbitrary, but I need to look at it a bit more. > > Try the attached patch and let me know whether it works for you. It > disables the limit on the number of receive segments. > > Thanks, > > Ken > -- > Kenneth Merry > k...@freebsd.org > ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
FreeBSD 8.1-RELEASE-p1 #11 i386 DomU kernel panic on mkdir()
Hi, Got one new kernel panic: mode = 063537, inum = 235520, fs = / panic: ffs_valloc: dup alloc cpuid = 0 KDB: enter: panic [thread pid 845 tid 100036 ] Stopped at kdb_enter+0x3a: movl$0,kdb_why db> where Tracing pid 845 tid 100036 td 0xc24b1280 kdb_enter(c035e9b8,c035e9b8,c037226c,d5740900,0,...) at kdb_enter+0x3a panic(c037226c,675f,39800,c24118d4,0,...) at panic+0x136 ffs_valloc(c28c5a78,41ed,c2495b00,d5740a2c,0,...) at ffs_valloc+0x602 ufs_readdir(d5740c38,0,d5740be4,d5740b7c,d5740c5c,...) at ufs_readdir+0x3d6 VOP_MKDIR_APV(c03a9ec0,d5740c38,68,0,0,...) at VOP_MKDIR_APV+0x42 kern_mkdirat(c24b1280,ff9c,28530180,0,1ed,...) at kern_mkdirat+0x251 kern_mkdir(c24b1280,28530180,0,1ed,d5740d3c,...) at kern_mkdir+0x2e mkdir(c24b1280,d5740d08,c2478280,206,c00fd1af,...) at mkdir+0x29 syscall(d5740d48) at syscall+0x2d3 Xint0x80_syscall() at Xint0x80_syscall+0x22 --- syscall (136, FreeBSD ELF32, mkdir), eip = 0x2833ba53, esp = 0xbf7fc7cc, ebp = 0xbf7fd0d8 --- --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
FreeBSD 8.1-RELEASE-p1 i386 xennet_get_responses messages in console
Hi, Does somebody know haw to deal with the following massages in the console: xennet_get_responses: too many frags 6 > max 5 --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: FreeBSD 8.1-RELEASE-p1 #11 i386 DomU fault in kernel at _mtx_lock_sleep()
The issue is 100% reproducible. Just got it ones more: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8d78d0c fault code = supervisor read, page not present instruction pointer = 0x21:0xc00cbe2f stack pointer = 0x29:0xe553f9e0 frame pointer = 0x29:0xe553f9f8 code segment= base 0x0, limit 0xf9800, type 0x1b = DPL 1, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 7297 (sendmail) [thread pid 7297 tid 100067 ] Stopped at _mtx_lock_sleep+0x3f: movl0x1a4(%ecx),%eax --- Yura On Oct 25, 2010, at 5:59 PM, Yuriy Kohut wrote: > Hi, > > Just got fault in kernel while running 'make' in the port > /usr/ports/lang/ghc: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x1a4 > fault code= supervisor read, page not present > instruction pointer = 0x21:0xc00cbe2f > stack pointer = 0x29:0xc3db09e0 > frame pointer = 0x29:0xc3db09f8 > code segment = base 0x0, limit 0xf9800, type 0x1b > = DPL 1, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 19207 (sendmail) > [thread pid 19207 tid 100049 ] > Stopped at _mtx_lock_sleep+0x3f: movl0x1a4(%ecx),%eax > > > db> where > Tracing pid 19207 tid 100049 td 0xc41e8c80 > _mtx_lock_sleep(c079d808,c41e8c80,0,0,0,...) at _mtx_lock_sleep+0x3f > netisr_clearqdrops(c3db0a34,0,c4368700,c3db0a50,c018f210,...) at > netisr_clearqdrops+0x34e > netisr_queue_src(1,0,c4368700,c3db0a78,c018a5a6,...) at netisr_queue_src+0x38 > netisr_queue(1,c4368700,c3db0b04,c3db0b0c,c3db0a8c,...) at netisr_queue+0x20 > if_simloop(c3f6b400,c4368700,2,0,c01a77df,...) at if_simloop+0xe6 > looutput(c3f6b400,c4368700,c3db0b0c,c3db0b04,c3db0ac8,...) at looutput+0x121 > ip_output(c4368700,0,0,0,0,...) at ip_output+0x98e > tcp_output(c42a39e0,c3f6ac70,c3db0c30,c00c8853,c42a39e0,...) at > tcp_output+0x14bf > tcp_ctloutput(c41b6338,c3f6ac70,c41e8c80,c41b6338,c3db0c70,...) at > tcp_ctloutput+0x2233 > soconnect(c41b6338,c3f6ac70,c41e8c80,bf7fae70,c3f6ac70,...) at soconnect+0x52 > kern_connect(c41e8c80,6,c3f6ac70,c3f6ac70,0,...) at kern_connect+0xa6 > connect(c41e8c80,c3db0d08,c0324244,c3db0020,16,...) at connect+0x46 > syscall(c3db0d48) at syscall+0x2d3 > Xint0x80_syscall() at Xint0x80_syscall+0x22 > --- syscall (98, FreeBSD ELF32, connect), eip = 0x283bd0cb, esp = 0xbf7fad0c, > ebp = 0xbf7faf38 --- > > > > DomU details > FreeBSD 8.1-RELEASE-p1 #11 > kernel config: /usr/src/sys/XEN i386 > xen config: > > kernel = "/var/lib/xen/images/kernel.FDvzVcWQzfgX" > memory = "1504" > name = "FDvzVcWQzfgX" > vcpus = "1" > vid = "7" > > vif = [ 'mac=00:16:3e:bf:2e:2e, bridge=xenbr0, ip=0.0.0.0, > vifname=FDvzVcWQzfgX, rate=0Mb/s' ] > disk = [ 'phy:/dev/iscsi_0_7,sda,w', 'phy:/dev/iscsi_0_127,sdb,w' ] > > extra = "boot_verbose=1" > extra += ",vfs.root.mountfrom=ufs:/dev/da0" > extra += ",kern.hz=100" > > > Dom0 details > CentOS release 5.4 (Final) > Linux hv9-a-chi.vps.net 2.6.18-164.15.1.el5xen #1 SMP Wed Mar 17 12:04:23 EDT > 2010 x86_64 x86_64 x86_64 GNU/Linux > xen-3.0.3-94.el5_4.3 > > > Appreciate any assistance. > Thanks > --- > Yura > > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
FreeBSD 8.1-RELEASE-p1 #11 i386 DomU fault in kernel at _mtx_lock_sleep()
Hi, Just got fault in kernel while running 'make' in the port /usr/ports/lang/ghc: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x1a4 fault code = supervisor read, page not present instruction pointer = 0x21:0xc00cbe2f stack pointer = 0x29:0xc3db09e0 frame pointer = 0x29:0xc3db09f8 code segment= base 0x0, limit 0xf9800, type 0x1b = DPL 1, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 19207 (sendmail) [thread pid 19207 tid 100049 ] Stopped at _mtx_lock_sleep+0x3f: movl0x1a4(%ecx),%eax db> where Tracing pid 19207 tid 100049 td 0xc41e8c80 _mtx_lock_sleep(c079d808,c41e8c80,0,0,0,...) at _mtx_lock_sleep+0x3f netisr_clearqdrops(c3db0a34,0,c4368700,c3db0a50,c018f210,...) at netisr_clearqdrops+0x34e netisr_queue_src(1,0,c4368700,c3db0a78,c018a5a6,...) at netisr_queue_src+0x38 netisr_queue(1,c4368700,c3db0b04,c3db0b0c,c3db0a8c,...) at netisr_queue+0x20 if_simloop(c3f6b400,c4368700,2,0,c01a77df,...) at if_simloop+0xe6 looutput(c3f6b400,c4368700,c3db0b0c,c3db0b04,c3db0ac8,...) at looutput+0x121 ip_output(c4368700,0,0,0,0,...) at ip_output+0x98e tcp_output(c42a39e0,c3f6ac70,c3db0c30,c00c8853,c42a39e0,...) at tcp_output+0x14bf tcp_ctloutput(c41b6338,c3f6ac70,c41e8c80,c41b6338,c3db0c70,...) at tcp_ctloutput+0x2233 soconnect(c41b6338,c3f6ac70,c41e8c80,bf7fae70,c3f6ac70,...) at soconnect+0x52 kern_connect(c41e8c80,6,c3f6ac70,c3f6ac70,0,...) at kern_connect+0xa6 connect(c41e8c80,c3db0d08,c0324244,c3db0020,16,...) at connect+0x46 syscall(c3db0d48) at syscall+0x2d3 Xint0x80_syscall() at Xint0x80_syscall+0x22 --- syscall (98, FreeBSD ELF32, connect), eip = 0x283bd0cb, esp = 0xbf7fad0c, ebp = 0xbf7faf38 --- DomU details FreeBSD 8.1-RELEASE-p1 #11 kernel config: /usr/src/sys/XEN i386 xen config: kernel = "/var/lib/xen/images/kernel.FDvzVcWQzfgX" memory = "1504" name = "FDvzVcWQzfgX" vcpus = "1" vid = "7" vif = [ 'mac=00:16:3e:bf:2e:2e, bridge=xenbr0, ip=0.0.0.0, vifname=FDvzVcWQzfgX, rate=0Mb/s' ] disk = [ 'phy:/dev/iscsi_0_7,sda,w', 'phy:/dev/iscsi_0_127,sdb,w' ] extra = "boot_verbose=1" extra += ",vfs.root.mountfrom=ufs:/dev/da0" extra += ",kern.hz=100" Dom0 details CentOS release 5.4 (Final) Linux hv9-a-chi.vps.net 2.6.18-164.15.1.el5xen #1 SMP Wed Mar 17 12:04:23 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-94.el5_4.3 Appreciate any assistance. Thanks --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: FreeBSD 8.1-RELEASE-p1 DomU vcpus >= 2 issue
Do you know is there any chance that will be fixed nearest future ? --- Yura On Oct 25, 2010, at 1:36 PM, Adrian Chadd wrote: > Xen DomU with vcpu > 1 has not worked in quite a bit of time. > > It's in sore need of attention. > > > Adrian > > On 25 October 2010 18:34, Yuriy Kohut wrote: >> Hello, >> >> >> I faced with the following issue while configuring my FreeBSD >> 8.1-RELEASE-p1 DomU with vcpus >= 2. Here kernel and init messages while >> DomU is booting: >> >> SMP: Added CPU 0 (BSP) >> SMP: Added CPU 1 (AP) >> gdtpfn=85f45 pdptpfn=13537 >> INTR: Adding local APIC 1 as a target >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> ULE: setup cpu 0 >> ULE: setup cpu 1 >> [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) >> [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) >> [XEN] IPI cpu=1 irq=130 vector=RESCHEDULE_VECTOR (0) >> [XEN] IPI cpu=1 irq=131 vector=CALL_FUNCTION_VECTOR (1) >> >> ... >> >> start_init: trying /sbin/init >> pid 22 (sysctl), uid 0: exited on signal 11 >> Segmentation fault >> pid 24 (ps), uid 0: exited on signal 11 >> Segmentation fault >> pid 26 (rcorder), uid 0: exited on signal 11 >> Segmentation fault >> pid 27 (grep), uid 0: exited on signal 11 >> Segmentation fault >> pid 28 (rcorder), uid 0: exited on signal 11 >> Segmentation fault >> >> pid 29 (date), uid 0: exited on signal 11 >> Segmentation fault >> >> FreeBSD/i386 (Amnesiac) (xc0) >> >> login: root >> pid 30 (login), uid 0: exited on signal 11 >> pid 31 (getty), uid 0: exited on signal 11 >> pid 32 (getty), uid 0: exited on signal 11 >> pid 33 (getty), uid 0: exited on signal 11 >> pid 34 (getty), uid 0: exited on signal 11 >> >> >> >> Everything is ok while vcpus = "1" is set into DomU config file. >> >> >> DomU details >> FreeBSD 8.1-RELEASE-p1 #11 >> kernel config: /usr/src/sys/XEN i386 >> xen config: >> >> kernel = "/var/lib/xen/images/kernel.tWcH4oyDer8p" >> memory = "1024" >> name = "tWcH4oyDer8p" >> vcpus = "2" >> vid = "10" >> >> vif = [ 'mac=00:16:3e:68:dd:33, bridge=xenbr0, ip=0.0.0.0, >> vifname=tWcH4oyDer8p, rate=0Mb/s' ] >> disk = [ 'phy:/dev/iscsi_0_10,sda,w', 'phy:/dev/iscsi_0_130,sdb,w' ] >> >> extra = "boot_verbose=1" >> extra += ",vfs.root.mountfrom=ufs:/dev/da0" >> extra += ",kern.hz=100" >> >> >> >> Dom0 details >> CentOS release 5.4 (Final) >> Linux vl-radar-box1.slc.westdc.net 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 >> 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux >> xen-3.0.3-94.el5_4.2 >> >> >> Please assist >> Thank you >> --- >> Yura >> >> ___ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" >> ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
FreeBSD 8.1-RELEASE-p1 DomU vcpus >= 2 issue
Hello, I faced with the following issue while configuring my FreeBSD 8.1-RELEASE-p1 DomU with vcpus >= 2. Here kernel and init messages while DomU is booting: SMP: Added CPU 0 (BSP) SMP: Added CPU 1 (AP) gdtpfn=85f45 pdptpfn=13537 INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ULE: setup cpu 0 ULE: setup cpu 1 [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) [XEN] IPI cpu=1 irq=130 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=1 irq=131 vector=CALL_FUNCTION_VECTOR (1) ... start_init: trying /sbin/init pid 22 (sysctl), uid 0: exited on signal 11 Segmentation fault pid 24 (ps), uid 0: exited on signal 11 Segmentation fault pid 26 (rcorder), uid 0: exited on signal 11 Segmentation fault pid 27 (grep), uid 0: exited on signal 11 Segmentation fault pid 28 (rcorder), uid 0: exited on signal 11 Segmentation fault pid 29 (date), uid 0: exited on signal 11 Segmentation fault FreeBSD/i386 (Amnesiac) (xc0) login: root pid 30 (login), uid 0: exited on signal 11 pid 31 (getty), uid 0: exited on signal 11 pid 32 (getty), uid 0: exited on signal 11 pid 33 (getty), uid 0: exited on signal 11 pid 34 (getty), uid 0: exited on signal 11 Everything is ok while vcpus = "1" is set into DomU config file. DomU details FreeBSD 8.1-RELEASE-p1 #11 kernel config: /usr/src/sys/XEN i386 xen config: kernel = "/var/lib/xen/images/kernel.tWcH4oyDer8p" memory = "1024" name = "tWcH4oyDer8p" vcpus = "2" vid = "10" vif = [ 'mac=00:16:3e:68:dd:33, bridge=xenbr0, ip=0.0.0.0, vifname=tWcH4oyDer8p, rate=0Mb/s' ] disk = [ 'phy:/dev/iscsi_0_10,sda,w', 'phy:/dev/iscsi_0_130,sdb,w' ] extra = "boot_verbose=1" extra += ",vfs.root.mountfrom=ufs:/dev/da0" extra += ",kern.hz=100" Dom0 details CentOS release 5.4 (Final) Linux vl-radar-box1.slc.westdc.net 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-94.el5_4.2 Please assist Thank you --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: FreebBSD 8.1-STABLE i386 PV DomU kernel panic at HYPERVISOR_update_va_mapping
Hi, That works for me too. Thank you --- Yura On Oct 22, 2010, at 8:52 PM, Linda Messerschmidt wrote: > On Fri, Oct 22, 2010 at 7:48 AM, Yuriy Kohut wrote: >> The kernel get into panic while booting: >> >> panic: HYPERVISOR_update_va_mapping(((unsigned long)(va)), (pa | 0x002 | >> 0x001 | > > For 8.1 you must build your kernel without the keyboard drivers for > the time being. This issue is pretty well documented at this point, > so you should be able to find the instructions pretty readily. > > I've done this and it doesn't seem to hurt anything (the Xen "serial > console" for the machine still works fine). > ___ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
FreebBSD 8.1-STABLE i386 PV DomU kernel panic at HYPERVISOR_update_va_mapping
Hi, I have installed FreeBSD 8.1-STABLE paravirtualized Xen DomU according to the documentation at: http://forums.freebsd.org/showthread.php?t=10268 RELENG_8 CVS tag was used to get world and kernel sources. The kernel get into panic while booting: panic: HYPERVISOR_update_va_mapping(((unsigned long)(va)), (pa | 0x002 | 0x001 | pgeflag | pmap_cache_bits(mode, 0)), UVMF_INVLPG| UVMF_ALL) < 0: /usr/src/sys/i386/xen/pmap.c:1269 cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x3a: movl$0,kdb_why db> db> where Tracing pid 0 tid 0 td 0xc03e0af0 kdb_enter(c036c678,c036c678,c0390af5,c051ecb4,0,...) at kdb_enter+0x3a panic(c0390af5,c0398fbf,c0398cd1,4f5,0,...) at panic+0x134 pmap_mapdev_attr(0,0,500,6,c051ed44,...) at pmap_mapdev_attr+0x13d pmap_mapbios(0,0,500,1,c051ed44,...) at pmap_mapbios+0x27 x86bios_call(c22ca3c0,0,0,76,c051ed64,...) at x86bios_call+0x212 module_register_init(c03db8f0,7020800,7020800,523000,0,...) at module_register_init+0xa7 mi_startup(523000,0,0,0,0,...) at mi_startup+0x96 btext() at btext+0x95 DomU details FreeBSD 8.1-STABLE #8 kernel config: /usr/src/sys/XEN i386 xen config: kernel = "/var/lib/xen/images/kernel.6jZmCCXlzjBa" memory = "512" name = "6jZmCCXlzjBa" vcpus = "1" vid = "17" sanip = "10.200.200.19" vif = [ 'mac=00:16:3e:0a:e2:40, bridge=xenbr0, ip=68.169.47.45, vifname=6jZmCCXlzjBa, rate=0Mb/s' ] disk = [ 'phy:/dev/iscsi_0_17,sda,w', 'phy:/dev/iscsi_0_137,sdb,w' ] extra = "boot_verbose=1" extra += ",vfs.root.mountfrom=ufs:/dev/da0" extra += ",kern.hz=100" Dom0 details CentOS release 5.4 (Final) Linux vl-radar-box1.slc.westdc.net 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-94.el5_4.2 DomU built from RELENG_8_0 booted fine for me. But it is very unstable. Kernel panics every time DomU is more higher loaded with network, CPU or memory. I reported several BRs for them, but with no result for the moment. Could somebody please assist with the panic ? --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: kern/148262: [xen] [panic] HYPERVISOR_update_va_mapping
I have built new FreeBSD XEN kernel based the RELENG_8_1 The problem still exists. The kernel config file /sys/i386/conf/XEN version is: $FreeBSD: src/sys/i386/conf/XEN,v 1.9.2.1.4.1 2010/06/14 02:09:06 kensmith Exp $ The problem is still on RELENG_8 too. --- Yura On Oct 2, 2010, at 4:43 PM, Juergen Lock wrote: > [kern/149853 is a duplicate of this] > > I don't use xen myself here but I helped someone on irc troubleshoot > the same crash (before I saw these PRs), and found out the reason it > didn't happen on 8.0 is the x86bios code is new in 8.1 and xen doesn't > like this call in x86bios_map_mem(): > > x86bios_ivt = pmap_mapbios(X86BIOS_IVT_BASE, X86BIOS_IVT_SIZE); > > see: > > > http://fxr.watson.org/fxr/source/compat/x86bios/x86bios.c?v=FREEBSD8#L498 > > It seems the only consumers of x86bios are atkbd(4), dpms(4), and > vesa(4), and indeed removing atkbd(4) from the xen kernel got his > domU running. > > (And now that I just looked at /sys/i386/conf/XEN in svn I see this > was already fixed in r204157, it only never got MFCd.) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
