From owner-freebsd-xen@FreeBSD.ORG Sun Feb 17 22:39:50 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DD2218E6; Sun, 17 Feb 2013 22:39:50 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B7CA0C19; Sun, 17 Feb 2013 22:39:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1HMdoxX009005; Sun, 17 Feb 2013 22:39:50 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1HMdoPZ009001; Sun, 17 Feb 2013 22:39:50 GMT (envelope-from linimon) Date: Sun, 17 Feb 2013 22:39:50 GMT Message-Id: <201302172239.r1HMdoPZ009001@freefall.freebsd.org> To: kmacy@FreeBSD.org, linimon@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-xen@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176053: [xen] [patch] i386: Correct wrong usage of vsnprintf() X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Feb 2013 22:39:50 -0000 Old Synopsis: [PATCH] i386: Correct wrong usage of vsnprintf() New Synopsis: [xen] [patch] i386: Correct wrong usage of vsnprintf() Responsible-Changed-From-To: freebsd-i386->freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Sun Feb 17 22:39:23 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176053 From owner-freebsd-xen@FreeBSD.ORG Mon Feb 18 11:06:57 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1AD8F253 for ; Mon, 18 Feb 2013 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id F0D6DE43 for ; Mon, 18 Feb 2013 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1IB6uUV061783 for ; Mon, 18 Feb 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1IB6u03061781 for freebsd-xen@FreeBSD.org; Mon, 18 Feb 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Feb 2013 11:06:56 GMT Message-Id: <201302181106.r1IB6u03061781@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2013 11:06:57 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171138 xen [xen] [panic] Deactivating network interface produces o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 35 problems total. From owner-freebsd-xen@FreeBSD.ORG Fri Feb 22 09:04:56 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BEE9BA98; Fri, 22 Feb 2013 09:04:56 +0000 (UTC) (envelope-from mailinglists.tech@gmail.com) Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by mx1.freebsd.org (Postfix) with ESMTP id 62370FFC; Fri, 22 Feb 2013 09:04:55 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id 1so211210qec.19 for ; Fri, 22 Feb 2013 01:04:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ERXl+jNUvr2+lziSzv2hr85v8VfFNdrXNBS0Hv9Ul5Y=; b=MdkKqQzkrH1d3hRwBLZ3fM8p9lA7/YQSkIs/utnVsCJS4ajEqyYxgPRk1lpELzmCPW j/nwdCPyEruEE2AJ9qZ2sR6kLkoj8lXmojkbeTXDlJnd2Z6CapgrB1+3qIMLdb111H/q UEyNZZyvsixMgdoU4onHSRUIeLmJu4+36bUdNOo15LWCx4OnXhoCixDTWUxyfZ3aofYe yMamqMBdj0cPCYOeFh6SGIbXRtr8OACGSIGdg4ovG0WdyqcwWBh4VTs18Tik5yD9vJy5 lV+ObwpFiypAn0Ly4l9z3wyLeUDbjjR2I3GSZhu/5i9z9c7ywyYMwTwh1qW4BUlHqBLB 8/sw== MIME-Version: 1.0 X-Received: by 10.49.74.198 with SMTP id w6mr476237qev.57.1361523895056; Fri, 22 Feb 2013 01:04:55 -0800 (PST) Received: by 10.49.110.70 with HTTP; Fri, 22 Feb 2013 01:04:54 -0800 (PST) Date: Fri, 22 Feb 2013 10:04:54 +0100 Message-ID: Subject: [Possible Regression] FreeBSD 9.1 i386 in PV mode can not boot on Xen 4.2.1 From: tech mailinglists To: freebsd-stable@freebsd.org, "" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 09:04:56 -0000 Hello all, I tried to setup a FreeBSD i386 guest in PV mode. So I compiled a FreeBSD Xen Kernel with the XEN kernel configuration from 9.1 revision 247145. The detailed information from "svn info" looks like this: Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/release/9.1.0 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 247145 Node Kind: directory Schedule: normal Last Changed Author: kensmith Last Changed Rev: 243808 Last Changed Date: 2012-12-03 06:03:33 +0100 (Mon, 03 Dec 2012) When I try to start the domain the kernel runs into a panic. The output is this: Parsing config from /root/xen/freebsd-test.cfg libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 19 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 4181 WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) Copyright (c) 1992-2012 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 9.1-RELEASE #0 r247145M: Fri Feb 22 09:19:40 CET 2013 root@build:/usr/obj/usr/src/sys/XEN i386 WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 3341.754 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0xbfe3fbff Features2=0x98e3bd AMD Features=0x28100000 AMD Features2=0x1 Data TLB: 4 KB pages, 4-way set associative, 64 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory = 536870912 (512 MB) Physical memory chunk(s): 0x000000000082c000 - 0x000000001f628fff, 517984256 bytes (126461 pages) avail memory = 514850816 (491 MB) INTR: Adding local APIC 0 as a target ULE: setup cpu 0 [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) Event-channel device installed. io: random: mem: Pentium Pro MTRR support enabled null: nfslock: pseudo-device [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock rtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) xenstore0: on motherboard Grant table initialized xc0: on motherboard Device configuration finished. procfs registered Event timer "ixen" quality 600 Timecounters tick every 10.000 msec lo0: bpf attached xenbusb_front0: on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_free_evtchn run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_free_evtchn [XEN] hypervisor wallclock nudged; nudging TOD. run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_free_evtchn panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> The xen configuration file looks like this: kernel = '/home/kernel1' extra = 'boot_verbose=1,kern.hz=100' vcpus = '1' memory = '512' disk = [ 'file:/home/test/disk.img,xvda1,w', ] name = 'freebsd' vif = [ '' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' I can not say where the problem is located. The configuration I used is located in the source tree at /usr/src/sys/i386/conf/XEN I search a while on the web and found that it helped in 8.x to comment out different things. Primary this threads are said such things on the forums: http://forums.freebsd.org/showthread.php?t=10268 http://forums.freebsd.org/showthread.php?t=33435 So it would be great when someone could help me to figure out the boot panic. A second thing is that I use a ZFS formated image. Is it possible to run / on ZFS with a Xen kernel? ZFS is in a module when I am right and I thing I have to boot the guest with PV GRUB to get this working am I right? Best Regards