From owner-freebsd-xen@FreeBSD.ORG Mon Apr 18 11:07:16 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FC771065678 for ; Mon, 18 Apr 2011 11:07:16 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 726368FC23 for ; Mon, 18 Apr 2011 11:07:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3IB7GrJ019697 for ; Mon, 18 Apr 2011 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3IB7FNH019695 for freebsd-xen@FreeBSD.org; Mon, 18 Apr 2011 11:07:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Apr 2011 11:07:15 GMT Message-Id: <201104181107.p3IB7FNH019695@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 Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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 Apr 2011 11:07:16 -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/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/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar 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 24 problems total. From owner-freebsd-xen@FreeBSD.ORG Sat Apr 23 21:04:26 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0A2F106566C for ; Sat, 23 Apr 2011 21:04:26 +0000 (UTC) (envelope-from florian.heigl@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 891918FC0A for ; Sat, 23 Apr 2011 21:04:26 +0000 (UTC) Received: by iwn33 with SMTP id 33so1598057iwn.13 for ; Sat, 23 Apr 2011 14:04:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=6sdeGzZ661NWydI3tcUWvqS3nAMF/JH3BHBwsRUiF74=; b=vzT+yPov8kAZ9E7peVAQBXEBnDyK6QySTcgrl7eN5+egmXDNlRknAQKbrMpgnMpfbB hWQVYMgY+h0Uh8PNzui2CjN9OXST1UwNEqei1dPAa80JcSmpr1Sy8ddfOuL64LSk+9BI jm2OgYHDojNOpJvHEWOKVkk9gLM3e68nZXDH4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hgs8GFbsifRCisj2UoqtvhbWu0xxlwtEeypTCCMtZUyaZtBZ1BojiPXtE2LtNcmfLu +TT4VZP/HTAySiEUdyEts4WcZJgaDDJEoPELjnwanq8lbrcIsXV1X9sezs/+CyQBaq5k vBguGoCHQFyC09ZUMU04tH3UTp/usb3HjHB+8= MIME-Version: 1.0 Received: by 10.42.108.73 with SMTP id g9mr2990191icp.250.1303590806021; Sat, 23 Apr 2011 13:33:26 -0700 (PDT) Received: by 10.42.189.6 with HTTP; Sat, 23 Apr 2011 13:33:26 -0700 (PDT) Date: Sat, 23 Apr 2011 22:33:26 +0200 Message-ID: From: Florian Heigl To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: a little lost: Xen HVM acpi shutdown? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 23 Apr 2011 21:04:26 -0000 Hi all, I have a nicely working FreeBSD image now, that seems stable enough for production use. The one thing I couldn't find out was how to make it shut down upon xm shutdown as this would be required to ensure the vm will be gracefully shutdown if some issue occurs in the host... Has one of you solved that and is there any documentation to it? Greetings, Florian (FreeBSD xen10.waxh0002.wartungsfenster.de 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Apr 21 00:09:13 CEST 2011 root@:/usr/src/sys/amd64/compile/XENHVM Using amd64, using Xen PV disk and network drivers It's somewhat telling that the final hints about PV drivers came from someone over at webhostingtalk.com. I see some overhead from HVM instead of PV, but I opt a working & fast system over the last 2% of performance here... -- the purpose of libvirt is to provide an abstraction layer hiding all xen features added since 2006 until they were finally understood and copied by the kvm devs. From owner-freebsd-xen@FreeBSD.ORG Sat Apr 23 21:59:29 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 984011065672 for ; Sat, 23 Apr 2011 21:59:29 +0000 (UTC) (envelope-from florian.heigl@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5A7308FC0A for ; Sat, 23 Apr 2011 21:59:28 +0000 (UTC) Received: by iyj12 with SMTP id 12so1627110iyj.13 for ; Sat, 23 Apr 2011 14:59:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mBLskQID7HLukG+fbaau/1K1SyrvNjWkkrbOdjj3X2s=; b=gD31adC3L0QoSg3TavF2DfI4GoB7546EXYt02lZIlY/58RlvPt5aCd633Ccf5hn3FC bI5R9CxA/ZkDu4uJ3DYOAQkoKo3cbSXn6O6c1kR/t8uLQoB0TI8adebMb8kx0/z0Y6ne FS/ARbUbZ92xgYq5mhh3X4HZ9jk2tZDsynghI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HQVU06K++x5QWPs2vlFHn5vxlNyuAo/TDFIgD/nLIiDVwJHH4oDzInZO7zsOxZqcWu VdqHkAicZPOCllU5zHhzg2GH/HGNLZmhtZ9j4gyaySOzNh34tBh9PqMTdjgHz3tS8AIX SZErcewznm7lRsLkr5GLGIvvsdyXVFYtwuHeg= MIME-Version: 1.0 Received: by 10.43.54.142 with SMTP id vu14mr2729130icb.384.1303595968541; Sat, 23 Apr 2011 14:59:28 -0700 (PDT) Received: by 10.42.189.6 with HTTP; Sat, 23 Apr 2011 14:59:28 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Apr 2011 23:59:28 +0200 Message-ID: From: Florian Heigl To: admin@dmarkey.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-xen@freebsd.org Subject: Re: a little lost: Xen HVM acpi shutdown? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 23 Apr 2011 21:59:29 -0000 Hi David, thanks for your reply. 2011/4/23 David Markey : > ACPI shutdown can be done via the QEMU process. > It should be listening on a control pipe where you can tell it to shutdown. I don't really understand that: If you do a xm shutdown then I'm quite sure that Xen does send the right commands to a PV/HVM domU or is it in fact not something FreeBSD specific and doesn't work for any guest OS on HVM domU? I remember that i.e. the windows GPLPV drivers have a device driver that is used to trigger the VM shutdown. So I'd think this is an issue where I gotta do something on the domU side. But maybe we're talking different things :)) Florian From owner-freebsd-xen@FreeBSD.ORG Sat Apr 23 22:10:00 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AC84106566B for ; Sat, 23 Apr 2011 22:10:00 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 469B68FC0C for ; Sat, 23 Apr 2011 22:10:00 +0000 (UTC) Received: by gxk28 with SMTP id 28so494853gxk.13 for ; Sat, 23 Apr 2011 15:09:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.190.73 with SMTP id d49mr706880yhn.322.1303595296178; Sat, 23 Apr 2011 14:48:16 -0700 (PDT) Received: by 10.236.103.146 with HTTP; Sat, 23 Apr 2011 14:48:16 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Apr 2011 22:48:16 +0100 Message-ID: From: David Markey To: Florian Heigl Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@freebsd.org Subject: Re: a little lost: Xen HVM acpi shutdown? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com 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: Sat, 23 Apr 2011 22:10:00 -0000 ACPI shutdown can be done via the QEMU process. It should be listening on a control pipe where you can tell it to shutdown. On 23 April 2011 21:33, Florian Heigl wrote: > Hi all, > > I have a nicely working FreeBSD image now, that seems stable enough > for production use. > > The one thing I couldn't find out was how to make it shut down upon xm > shutdown as this would be required to ensure the vm will be > gracefully shutdown if some issue occurs in the host... > Has one of you solved that and is there any documentation to it? > > > Greetings, > Florian > > (FreeBSD xen10.waxh0002.wartungsfenster.de 8.2-RELEASE FreeBSD > 8.2-RELEASE #0: Thu Apr 21 00:09:13 CEST 2011 > root@:/usr/src/sys/amd64/compile/XENHVM > Using amd64, using Xen PV disk and network drivers > It's somewhat telling that the final hints about PV drivers came from > someone over at webhostingtalk.com. I see some overhead from HVM > instead of PV, but I opt a working & fast system over the last 2% of > performance here... > > > -- > the purpose of libvirt is to provide an abstraction layer hiding all > xen features added since 2006 until they were finally understood and > copied by the kvm devs. > _______________________________________________ > 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" > From owner-freebsd-xen@FreeBSD.ORG Sat Apr 23 22:15:38 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47E21106566C for ; Sat, 23 Apr 2011 22:15:38 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 05B4C8FC08 for ; Sat, 23 Apr 2011 22:15:37 +0000 (UTC) Received: by gyg13 with SMTP id 13so494583gyg.13 for ; Sat, 23 Apr 2011 15:15:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.197.3 with SMTP id s3mr2725313yhn.54.1303596937182; Sat, 23 Apr 2011 15:15:37 -0700 (PDT) Received: by 10.236.103.146 with HTTP; Sat, 23 Apr 2011 15:15:37 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Apr 2011 23:15:37 +0100 Message-ID: From: David Markey To: Florian Heigl Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@freebsd.org Subject: Re: a little lost: Xen HVM acpi shutdown? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com 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: Sat, 23 Apr 2011 22:15:38 -0000 It normally is done by sending the shutdown signal via the xenstore.. However something has to be listening for the signal in the guest in order for this to work(then it initiates shutdown). I'm not sure FreeBSD has anything listening on the guest side. On 23 April 2011 22:59, Florian Heigl wrote: > Hi David, thanks for your reply. > > 2011/4/23 David Markey : > > ACPI shutdown can be done via the QEMU process. > > It should be listening on a control pipe where you can tell it to > shutdown. > > I don't really understand that: > > If you do a xm shutdown then I'm quite sure that Xen does send > the right commands to a PV/HVM domU or is it in fact not something > FreeBSD specific and doesn't work for any guest OS on HVM domU? > I remember that i.e. the windows GPLPV drivers have a device driver > that is used to trigger the VM shutdown. > > So I'd think this is an issue where I gotta do something on the domU side. > > But maybe we're talking different things :)) > > Florian >