From owner-freebsd-virtualization@FreeBSD.ORG Mon Dec 24 11:06:52 2012 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9703686 for ; Mon, 24 Dec 2012 11:06:52 +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 BC9E48FC24 for ; Mon, 24 Dec 2012 11:06:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBOB6qpH066237 for ; Mon, 24 Dec 2012 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBOB6qLv066235 for freebsd-virtualization@FreeBSD.org; Mon, 24 Dec 2012 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Dec 2012 11:06:52 GMT Message-Id: <201212241106.qBOB6qLv066235@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 11:06:52 -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/170096 virtualization[vimage] Dynamically-attached network interface will c o kern/169991 virtualization[run] [vimage] panic after device plugged in o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF/IPFilter + VIMAGE k a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic 10 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 28 01:12:12 2012 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A9B9328 for ; Fri, 28 Dec 2012 01:12:12 +0000 (UTC) (envelope-from noidmvp@gmail.com) Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by mx1.freebsd.org (Postfix) with ESMTP id 3F08B8FC08 for ; Fri, 28 Dec 2012 01:12:12 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id c12so12174249ieb.37 for ; Thu, 27 Dec 2012 17:12:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RBxgZVKda8LBKooaU76SHE6hWZJyjorY0aKldaqUJgE=; b=Xpg+rY8bbTdIAVW0cv8u3QhXAOd88aqAGkgGrGWMgDVkm2FglLl3d+V20DaHymt0nN BVQdaUEB9qlHQCQYbttdp2wX3jgC6YQMWERMew1Jm2WdLMfcjzhjHPyMkm4h9j3OR1Uu Xoetjevg0YrKNTw/rPs2MDcfe+otgWw7dDkBb/YGF5G6XvyY3iDP1sco7wn9GGFcXcf+ 6g0EGTduDjPpHaOE1FVYM+OahdJ0X79f6YThOpuZv792neiIxaiFoDUDCSHvbtLajKjv g5dOpKpFihJLPNVRG8E9OFGBRANADHVKAnH8yndx3/kJ0i+rT1lYA1FFSILfa812POCc x1Aw== MIME-Version: 1.0 Received: by 10.50.190.163 with SMTP id gr3mr23753769igc.106.1356657131520; Thu, 27 Dec 2012 17:12:11 -0800 (PST) Received: by 10.231.234.8 with HTTP; Thu, 27 Dec 2012 17:12:11 -0800 (PST) Date: Fri, 28 Dec 2012 01:12:11 +0000 Message-ID: Subject: bhyveload without zfs support? From: marcos alves To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2012 01:12:12 -0000 Hello everyone Sorry if this is not an urgent problem, I just wanted to know if I'm doing wrong or it cannot be done by now Did some tests with bhyve and had success as I described in http://www.emulsoft.com/bhyve-ufs.txt. But during my tests, I tried to make a zfs root installation, all the procces went well (creation of zpool and bootcode etc) but, got stuck with: Consoles: userboot FreeBSD/amd64 User boot, Revision 1.1 (root@, Sun Dec 23 01:00:34 UTC 2012) \ can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK lsdev host devices: host0: Host filesystem disk devices: disk0: Guest drive image disk0p1: FreeBSD boot disk0p2: FreeBSD swap disk0p3: FreeBSD ZFS OK OK ls open '/' failed: no such file or directory OK For me it just looks like the userboot isnt able to load the pool right at the start or it needs to use zfsloader. Am I right with that? Will it be possible in the future? Another issue that is out of the topic, it was that guests couldn't reach another pc using wlan as the host bridged interface. With a wired ethernet interface it worked perfectly. I hope I'm clear with this information and sorry for bad english. Thank you Marcos Alves Emulsoft Corporation @1noid noidmvp@gmail.com From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 28 02:48:57 2012 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9FF19D9 for ; Fri, 28 Dec 2012 02:48:57 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 92E608FC15 for ; Fri, 28 Dec 2012 02:48:57 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 3F905119E4; Fri, 28 Dec 2012 12:43:31 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro.local (c-71-56-248-150.hsd1.co.comcast.net [71.56.248.150]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BIZ23972 (AUTH peterg@ptree32.com.au); Fri, 28 Dec 2012 12:43:29 +1000 Message-ID: <50DD074E.5050209@freebsd.org> Date: Thu, 27 Dec 2012 19:43:26 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: marcos alves Subject: Re: bhyveload without zfs support? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Info: RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,SPF_SOFTFAIL X-Junkmail-Status: score=29/51, host=dommail.onthenet.com.au Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2012 02:48:57 -0000 Hi Marcos, > For me it just looks like the userboot isnt able to load the pool right at > the start or it needs to use zfsloader. Am I right with that? Yes, that's right. ZFS support isn't currently built into userboot. > Will it be possible in the future? Should be - just a matter of adding the loader zfs files to userboot. > Another issue that is out of the topic, it was that guests couldn't reach > another pc using wlan as the host bridged interface. With a wired ethernet > interface it worked perfectly. I don't know the answer to that one: maybe a limitation of WLAN ? > I hope I'm clear with this information and sorry for bad english. Perfectly clear, thanks ! later, Peter.