From owner-freebsd-virtualization@freebsd.org Thu Jan 28 19:13:37 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 89180A712ED for ; Thu, 28 Jan 2016 19:13:37 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 22EC8113C for ; Thu, 28 Jan 2016 19:13:37 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id r129so38994700wmr.0 for ; Thu, 28 Jan 2016 11:13:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hFxpIS+6xk/rem9k5gaLpUcMSluf0zVi2ePNYeTZEgU=; b=HSFP/yj6Hp899M7wLcD4S+bv/x6CSBDlwSNTJahLSbzFvaDdhWKjXHag71oBg76HPx KcTVVuFZRXL1uNKzlG1/0fRTrtlUpcSFciP+8vvVjvGOjreCxztnFPXj/6xjRThR8/24 ei+/MumwTTsIzEwX6J7VnrVPhWu3pFTQicgt3jzY3VtPFToRsRyUuoPdZo70irIl3ek7 9tiwVO2lyn9LVjVulUqLSV8g7LeTA4XopbEzXwMVaCWgruYjzTeEHMvOJa+IWRswGIST nIhAaYBEJ4aSlMqEG/hpWYd3k9Nj0/qwadRm2SmOpS+wUw+QrjlVBx1O5rOJmVujiCv6 ivyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hFxpIS+6xk/rem9k5gaLpUcMSluf0zVi2ePNYeTZEgU=; b=hPeu3+26tT7FOmCro3BSRI+7QUVzZpP66jSH2qu/KP4zEZtdkxz5zHkmgAS6QVFt+a X/oQeTdBeB9CbQvEm7+13e9cuOh5kgQI4DdQJXVCb9tcHQZSv7cN4+UbxQrh5bzd4+Lg jbU/Hf1NCbiytfG0WqeegM/MGdh/fphkdhgyL2luwwO+LDL8T4/K8FgzwoXeLt3NdTyw QupK14zQJvKP/dKlSM/xfeUpok88dhXs5vaaS5RIQGYi04QW94pVtTb1mzAMDb6XuIBm at5Wg4f+G4c7HX5uhupOoAjrS+DwJ/hUEaCaWCXcgK6cN7K9UrvAX6nqchWJEoFatVem RBtA== X-Gm-Message-State: AG10YORKJt8eM78c17vPdyeIGGco8h8034k+GhfO1VY5rZuXb9HrsLZSHCEjJhq0gfXcXasGQM9NJCrBZz1dzg== MIME-Version: 1.0 X-Received: by 10.28.35.6 with SMTP id j6mr5045378wmj.80.1454008415612; Thu, 28 Jan 2016 11:13:35 -0800 (PST) Received: by 10.27.81.84 with HTTP; Thu, 28 Jan 2016 11:13:35 -0800 (PST) In-Reply-To: <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> <20160127021348.GE1799@dendrobates.araler.com> <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> Date: Thu, 28 Jan 2016 11:13:35 -0800 Message-ID: Subject: Re: bhyve with Linux guest, how to safely handle updates? From: Neel Natu To: dweimer@dweimer.net Cc: Sergey Manucharian , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Thu, 28 Jan 2016 19:13:37 -0000 Hi Dean, On Thu, Jan 28, 2016 at 10:55 AM, dweimer wrote: > On 2016-01-26 8:13 pm, Sergey Manucharian wrote: >> >> 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 > > > I am back to testing again, copied my ZFS Boot Environment over to a VMware > virtual machine, renamed it and changed IPs, removed the virtual box stuff, > and enabled bhyve. > > I did some searching and found out that I was using > https://github.com/churchers/vm-bhyve to manage the bhyve virtual machines > starting and stopping. Sticking with zvol for disk backing, I know its less > portable. > > I have been able to install a couple of debian virtual machines and play > around with them. So far I have been unable to duplicate the issue I had > before. My current issue which maybe related to running inside a VMware > virtual machine. Is the Linux hwclock and system clock sync issues. If I > power off the vm and reboot it it believes that the disk was modified in the > future and appears to hang. Its actually doing a fsck I just don't see > status if you wait long enough it finally does come up. > > Has anyone else ran into this issue? I have actually ran the hwclock > -systohc --utc prior to powering down and still had the issue. Tried > changing the hwclock to system time by excluding the --utc from the command > no change. Incidentally whether I use the --utc or not the hwclock --show > always displays the local time. I couldn't seem to find any documentation on > bhyve whether or not I should tell the guests that the hwclock is in utc or > local time. > The "-u" option of bhyve(8) will configure the RTC to present UTC time to the guest (default is localtime). best Neel > -- > Thanks, > Dean E. Weimer > http://www.dweimer.net/ > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org"