From owner-freebsd-virtualization@freebsd.org Wed Jan 27 02:13:52 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9950AA6E6D5 for ; Wed, 27 Jan 2016 02:13:52 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 687C3B79 for ; Wed, 27 Jan 2016 02:13:52 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: by mail-ob0-x22a.google.com with SMTP id ba1so158755676obb.3 for ; Tue, 26 Jan 2016 18:13:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=tgKvnINpVZwp9KqM2ArSx2biJrnRFxQu9t1NpcRjE+8=; b=mwpAD9Wp33dGVNVM6wciuPQfW7IT0YdQG3AWi9kjOSJSa4iAB8GGW2vCheT14Hz2rj SlLwWG1dvg7V0cN5kqBt/r5OwHlNziFNRvDlXa4hyK5e5Du0GV042ziMnzi2wGB36qu/ VJr2qZcMk0uc6C/o+q805mrCfnDVeopPwwO9J+CJqWc5BDMzgLdG9DFFM/MhDS13c2VD w1NaulEDe3SJi0B4PNDaS3Rgg3ZgAMdgK0ajleLzRpX+rxaRAnDh/W6hlcNbVfFPNNic B8+v2lTOTIrMKdGbg8/qJvlF4wHzh+/nbDiBaImrollLsSv96sQLYcSxO0bBV8OEk/na VOkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=tgKvnINpVZwp9KqM2ArSx2biJrnRFxQu9t1NpcRjE+8=; b=KYkwn0XtmOiU/JlwOx/slrEcPQBrxmljJLlkB/hFAxDva8MRFvDPsmhCDoeUdz5Qvc EZ8CRHNITyZUgRkWH33X/bHtKBw4ZhpL1ykDiYfy6DYBki0Hypc09m61MkHM6T5yN+Ek POcUNumO+1zkyEyRRZQcD4LnnY5d8EWKnljxlyi4rmwhZl4VjIirJJur6TEa0+0qIW+O dlCxmHYdSy8/P7RKBs0VBX0d0UmhNZaqxn5uCc10THST3GSlvFpymueWVpqud4K5PpZH oV9LyxyER9X9J1ODVlNePJvTMf95WMAmy85OBBGyvNnzRRVgN5/ryqQh6VSvY6TSM+hd MG9Q== X-Gm-Message-State: AG10YOS63JOIbrJaPArWYYOhcYk0GEmhoKVTu+AO3OuUN0uw93DLaqv8qZDa2JieuGoDxA== X-Received: by 10.60.58.6 with SMTP id m6mr19170973oeq.47.1453860831351; Tue, 26 Jan 2016 18:13:51 -0800 (PST) Received: from dendrobates.araler.com (75-166-211-166.hlrn.qwest.net. [75.166.211.166]) by smtp.gmail.com with ESMTPSA id px4sm2037895oec.7.2016.01.26.18.13.50 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jan 2016 18:13:50 -0800 (PST) Date: Tue, 26 Jan 2016 19:13:48 -0700 From: Sergey Manucharian To: dweimer Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve with Linux guest, how to safely handle updates? Message-ID: <20160127021348.GE1799@dendrobates.araler.com> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9ee895854c862cccc0bcc84c16eee063@dweimer.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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: Wed, 27 Jan 2016 02:13:52 -0000 Excerpts from dweimer's message from Tue 26-Jan-16 19:07: > > Is there anything that normally needs to be done after a Linux kernel > update to refresh the grub2-bhyve setup? The kernel update should not have any effect since grub-bhyve uses the virtual disk mapping file, which should point to your linux drive. I'm using the following command: $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian where "device.map" contains the following: (hd0) /dev/zvol/zroot/linuxdisk1 (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in my case it's a ZFS volume). How do you use that VM in VBox? If it's a .vdi file, bhyve will not be able to recognize it. You should use a raw HDD image file. To make it compatible with VBox you can create a .vmdk file pointing to that raw image. -- Sergey