From owner-freebsd-virtualization@FreeBSD.ORG Thu Apr 23 08:43:58 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33FFE106564A for ; Thu, 23 Apr 2009 08:43:58 +0000 (UTC) (envelope-from zec@icir.org) Received: from labs4.cc.fer.hr (labs4.cc.fer.hr [161.53.72.24]) by mx1.freebsd.org (Postfix) with ESMTP id BAFEB8FC14 for ; Thu, 23 Apr 2009 08:43:57 +0000 (UTC) (envelope-from zec@icir.org) Received: from sluga.fer.hr (sluga.cc.fer.hr [161.53.72.14]) by labs4.cc.fer.hr (8.14.2/8.14.2) with ESMTP id n3N8iB1C028621 for ; Thu, 23 Apr 2009 10:44:11 +0200 (CEST) Received: from [192.168.200.100] ([161.53.19.79]) by sluga.fer.hr over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Apr 2009 10:43:48 +0200 From: Marko Zec To: freebsd-virtualization@freebsd.org Date: Thu, 23 Apr 2009 10:43:46 +0200 User-Agent: KMail/1.9.10 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904231043.46799.zec@icir.org> X-OriginalArrivalTime: 23 Apr 2009 08:43:49.0083 (UTC) FILETIME=[9F1CBAB0:01C9C3EF] X-Scanned-By: MIMEDefang 2.64 on 161.53.72.24 Cc: Subject: Re: about vimage_7_20090401.tgz X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 23 Apr 2009 08:43:58 -0000 On Thursday 23 April 2009 06:52:45 Clarence Chu wrote: > Hi All, > > Seems to me the vimage_7_20090401.tgz > doesn't work, yet on FreeBSD-7.2-PRERELEASE/amd64 > as of Apr 22, 2009 for: > a) IPFIREWALL > b) device pf > c) ZFS > d) rpc.lockd Basically three separate vimage-related efforts are underway, listed in order of priority: 1) merging vimage -> head 2) maintaining vimage branch (tracking head) 3) maintaining vimage_7 branch (tracking stable/7) So you are mosltly right - in both vimage and vimage_7 branches many kernel susbsystems do not work (yet) with options VIMAGE enabled. The current focus is on merging the base network stack infrastructure to head, and deal with those remaining subsystems later. > about a year ago, vimage refused to work with PCCARD NICs, > not to mention building a static kernel by: > hints "GENERIC.hints" > > How's your mileage? Does IMUNES require "most up-dated" version > as a year ago? IMUNES should work with both latest vimage and vimage_7 kernels from the imunes.net/virtnet page, though in general IMUNES mailing list would be a more appropriate place to discuss any IMUNES specific issues. Cheers, Marko