From owner-freebsd-virtualization@freebsd.org Fri Jan 29 05:24:15 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 96CA8A71489 for ; Fri, 29 Jan 2016 05:24:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C44E11AD for ; Fri, 29 Jan 2016 05:24:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-229-231.lns20.per1.internode.on.net [121.45.229.231]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u0T5MliL008151 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 28 Jan 2016 21:22:50 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: bhyve with Linux guest, how to safely handle updates? To: Neel Natu , dweimer@dweimer.net References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net> <20160127021348.GE1799@dendrobates.araler.com> <94df01924b1843c39aaf29a47a4fa2da@dweimer.net> Cc: "freebsd-virtualization@freebsd.org" From: Julian Elischer Message-ID: <56AAF721.4080009@freebsd.org> Date: Fri, 29 Jan 2016 13:22:41 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 29 Jan 2016 05:24:15 -0000 On 29/01/2016 3:13 AM, Neel Natu wrote: > 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). wouldn't it be best if the -u option had an argument to give the offsett? I had this problem with two windows hosts that were supposed to be in different timezones. I worked around it but... > > 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" > _______________________________________________ > 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" >