From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [Xen-users] Fedora 17 Dom-U booting issue Date: Fri, 19 Oct 2012 10:21:00 -0400 Message-ID: <20121019142100.GN26830@phenom.dumpdata.com> References: <1350466992.2460.47.camel@zakaz.uk.xensource.com> <1350568154.2460.151.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: "xen-users@lists.xen.org" , kk s , Ian Campbell , xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Oct 18, 2012 at 05:21:06PM +0100, Stefano Stabellini wrote: > On Thu, 18 Oct 2012, Ian Campbell wrote: > > On Thu, 2012-10-18 at 14:42 +0100, Stefano Stabellini wrote: > > > On Wed, 17 Oct 2012, Ian Campbell wrote: > > > > Adding xen-devel and the relevant maintainers. > > > > > > > > On Tue, 2012-10-16 at 20:24 +0100, kk s wrote: > > > > > Hi Folks, > > > > > > > > > > > > > > > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses > > > > > to boot fine and getting the below error on console, > > > > > > > > > > > > > > > -------- > > > > > Booting 'Fedora (3.6.1-1.fc17.x86_64)' > > > > > > > > > > > > > > > Loading Fedora (3.6.1-1.fc17.x86_64) > > > > > Loading initial ramdisk ... > > > > > [ 0.000000] Cannot get hvm parameter 18: -22! > > > > > > > > HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN. > > > > > > -22 is EINVAL, that Xen would return only if: > > > > > > - the requested parameter is out of range > > > this is not the case, 18 < 30 > > > > The hypervisor here is 3.4.3 where the largest hvm param is: > > $ grep define.HVM_PARAM xen-3.4-testing.hg/xen/include/public/hvm/params.h | sort -k3 -n | tail -n 3 > > #define HVM_PARAM_ACPI_S_STATE 14 > > #define HVM_PARAM_VM86_TSS 15 > > #define HVM_PARAM_VPT_ALIGN 16 > > OK, we know that the console is not working because it is not provided > by the hypervisor. > However that shouldn't prevent the domain from booting, the emulated > serial should work fine. Maybe it does? Mr. KK can you boot your guest with this in guest config: serial='pty' and on your Linux line, do 'loglevel=8 initcall_debug console=ttyS0,115200 debug' please?