From owner-freebsd-xen@FreeBSD.ORG Tue Feb 14 10:34:05 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8A671065776 for ; Tue, 14 Feb 2012 10:34:04 +0000 (UTC) (envelope-from trix@basement.net) Received: from anya.basement.net (vt42.crimsonhexagon.com [66.135.63.193]) by mx1.freebsd.org (Postfix) with ESMTP id D5F168FC16 for ; Tue, 14 Feb 2012 10:34:02 +0000 (UTC) Received: from willow.basement.net (home.basement.net [173.162.16.100]) by anya.basement.net (8.13.8/8.13.8) with ESMTP id q1EAY171017221; Tue, 14 Feb 2012 04:34:01 -0600 Received: from willow.basement.net (localhost [127.0.0.1]) by willow.basement.net (8.14.5/8.14.5) with ESMTP id q1EAY0kF004633; Tue, 14 Feb 2012 04:34:00 -0600 (CST) (envelope-from trix@basement.net) Received: (from trix@localhost) by willow.basement.net (8.14.5/8.14.5/Submit) id q1EAY0r9004632; Tue, 14 Feb 2012 04:34:00 -0600 (CST) (envelope-from trix@basement.net) X-Authentication-Warning: willow.basement.net: trix set sender to trix@basement.net using -f Date: Tue, 14 Feb 2012 04:34:00 -0600 From: Trix Farrar To: FreeBSD Xen , Xen-Users Message-ID: <20120214103400.GA4536@basement.net> References: <20120211165544.GA71096@basement.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120211165544.GA71096@basement.net> User-Agent: Mutt/1.4.2.3i X-Crypto: gpg (GnuPG) 2.0.16 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on anya.basement.net Cc: Subject: [RESOLVED] 9.0-RELEASE PV from scratch on XCP v1.1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2012 10:34:06 -0000 On Sat, Feb 11, 2012 at 10:55:44AM -0600, Trix Farrar wrote: > I'm probably missing something really obvious here, but here are a > couple of issues that keep this from being a complete win. Yes, I missed something obvious. I was overthinking things. > * Kernel ignoring/not-getting arguments from the domain builder. > This means that the kernel can''t find its root device. Boot arguments _are_ passed to the kernel correctly. The part that I missed is that they are passed literally. I had used the following: xe vm-param-set \ uuid=$VM_UUID \ PV-bootloader-args="--kernel=/boot/kernel/kernel --args='vfs.root.mountfrom=ufs:xbd0s1a,kern.hz=100,boot_verbose=1'" This meant that what the kernel saw for vfs.root.mountfrom was "'ufs:xbd0s1a", so it was ignoring it becuase there is no "'ufs" filesystem type. By removing the single quotes around the "--args" portion, the kernel boots just fine. btw: "kern.hz" is 100 by default, so that part isn't needed either. The following PV-bootloader-args command allows the VM to boot normally and unattended: xe vm-param-set \ uuid=$VM_UUID \ PV-bootloader-args='--kernel=/boot/kernel/kernel --args=vfs.root.mountfrom=ufs:xbd0s1a,boot_verbose=1' So, I'm willing to call it a win! -- John D. "Trix" Farrar __\\|//__ Basement.NET trix@basement.net (` o-o ') http://www.basement.net/ -----------------------------------ooO-(_)-Ooo-------------------------- GPG Key Fprint: 525F DBA7 1A62 E4C4 E642 DF95 384B B851 3CEF C10A