From owner-freebsd-xen@FreeBSD.ORG Wed May 29 17:22:30 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F1A5C7C1; Wed, 29 May 2013 17:22:29 +0000 (UTC) (envelope-from prvs=854e4d353=msw@amazon.com) Received: from smtp-fw-2101.amazon.com (smtp-fw-2101.amazon.com [72.21.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7E7A4ABB; Wed, 29 May 2013 17:22:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=msw@amazon.com; q=dns/txt; s=amazon201209; t=1369848149; x=1401384149; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=EtD99msgmr/hICSmuSUv9+Q5jjpgnXxuR0eMMuvNfa8=; b=Ukk9jb0Gu5iJC4WQp6QLBsFY+X71oE/QJ1O5SaLjMcFCArciORC8zfQh ImvG5+mfqrH3td7wEQFc4+DjL+Gds1w+53gxFjxjr6IqH/Pe+3QB9/TEl 9VDZta/hbOf1PJQlkDK2zMciHInGiD8DEa/bSmoE3cfonhndL0UQLRQmv w=; X-IronPort-AV: E=Sophos;i="4.87,765,1363132800"; d="scan'208";a="568401090" Received: from smtp-in-1101.vdc.amazon.com ([10.146.54.37]) by smtp-border-fw-out-2101.iad2.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 May 2013 17:22:27 +0000 Received: from ex10-hub-9003.ant.amazon.com (ex10-hub-9003.ant.amazon.com [10.185.137.132]) by smtp-in-1101.vdc.amazon.com (8.13.8/8.13.8) with ESMTP id r4THMOUl029000 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 29 May 2013 17:22:27 GMT Received: from u109add4315675089e695.ant.amazon.com (10.184.8.86) by ex10-hub-9003.ant.amazon.com (10.185.137.132) with Microsoft SMTP Server id 14.2.247.3; Wed, 29 May 2013 10:22:03 -0700 Received: by u109add4315675089e695.ant.amazon.com (sSMTP sendmail emulation); Wed, 29 May 2013 10:22:03 -0700 Date: Wed, 29 May 2013 10:22:03 -0700 From: Matt Wilson To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing Message-ID: <20130529172201.GA20973@u109add4315675089e695.ant.amazon.com> References: <5197A1EA.2040404@freebsd.org> <519CAFC7.1070908@citrix.com> <519D24A9.3050407@freebsd.org> <519DDC0A.9000201@citrix.com> <519E6958.6020606@freebsd.org> <519F3CD0.5090405@citrix.com> <51A4D804.9050208@citrix.com> <20130528191855.GA13736@u109add4315675089e695.ant.amazon.com> <51A5229F.80205@freebsd.org> <51A634EC.7050805@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <51A634EC.7050805@citrix.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , "freebsd-virtualization@freebsd.org" , xen-devel X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 29 May 2013 17:22:30 -0000 On Wed, May 29, 2013 at 07:03:40PM +0200, Roger Pau Monné wrote: > > Hello, > > Thanks Matt and Colin for the testing and help! I've pushed yet another > version, now it's branch pvhvm_v12, which I *think* should solve the > issues with cpuid != acpi_id: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 > > Since I'm not able to reproduce the cpuid != acpi_id case, could you > give it a try and report the results? Colin, can you build an AMI with this new kernel? [...] > On 28/05/13 23:33, Colin Percival wrote: > > On a cc2.8xlarge EC2 instance, the lines which come after this are > >> GEOM: new disk xbd1 > >> GEOM: new disk xbd2 > >> GEOM: new disk xbd3 > >> GEOM: new disk xbd4 > >> Trying to mount root from ufs:/dev/ad0a [rw]... > >> start_init: trying /sbin/init > > and then the userland boot process; have you made any bug fixes after > > your pvhvm_v7 which would explain why tasting disks was hanging? > > I'm not sure I follow, did you found a regression from previous > branches? i.e. it used to work with branch pvhvm_v6 and not pvhvm_v7? Colin was saying that his local change only moved the boot process a bit farther for cr1.8xlarge. Perhaps some of the other changes you made in the latest pvhvm_v12 branch will get the VM all the way up. --msw