From owner-freebsd-virtualization@FreeBSD.ORG Fri Oct 11 17:53:31 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 618FB12E for ; Fri, 11 Oct 2013 17:53:31 +0000 (UTC) (envelope-from tony@tndh.net) Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2E99A2747 for ; Fri, 11 Oct 2013 17:53:31 +0000 (UTC) Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1VUgtw-000L7N-J1 for freebsd-virtualization@freebsd.org; Fri, 11 Oct 2013 10:53:30 -0700 From: "Tony Hain" To: Subject: fastide on hyper-v (pre r2) Date: Fri, 11 Oct 2013 10:53:24 -0700 Message-ID: <02c701cec6aa$c8500370$58f00a50$@tndh.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: Ac7GpkzA9dKm+xgsT+yhsjBIKwLRkA== X-Spam-Score: 1.4 (+) X-Spam-Report: Spam detection software, running on the system "express.tndh.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: I am not able to get fastide working on sbs2008 with the pre-r2 version of hyper-v. Should this work? Has testing been done on older versions of hyper-v? I see there was a commit by grehan 18 hours, 30 minutes ago dealing with the cdrom, so I have a new build in process. To be honest I hadn't gotten far enough to worry about the cdrom device yet, but it is good to see that is dealt with. [...] Content analysis details: (1.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1 1.4 DOS_OUTLOOK_TO_MX Delivered direct to MX with Outlook headers X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a X-SA-Exim-Mail-From: tony@tndh.net X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false 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, 11 Oct 2013 17:53:31 -0000 I am not able to get fastide working on sbs2008 with the pre-r2 version of hyper-v. Should this work? Has testing been done on older versions of hyper-v? I see there was a commit by grehan 18 hours, 30 minutes ago dealing with the cdrom, so I have a new build in process. To be honest I hadn't gotten far enough to worry about the cdrom device yet, but it is good to see that is dealt with. There is an extensive list of things I have tried in the thread http://forums.freebsd.org/showthread.php?p=236012#post236012 In short, if I leave fastide on, it will panic before it gets to error 19, but if I turn it off I can boot to ada0p2, or any label I give the device. My suspicion is that all of the dev work has been done on hyperv-r2, so there may be an oversight. In any case it is good to see all the progress. I have been running FreeBSD in VM's hobbled by the inability to reboot without manual intervention for 4 years, hoping this would happen. Even without fastide, once 10 goes to RELEASE I can move some of the production work off of dedicated hardware. Tony