From owner-freebsd-xen@FreeBSD.ORG Thu May 16 11:56:49 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 8F484930 for ; Thu, 16 May 2013 11:56:49 +0000 (UTC) (envelope-from feld@feld.me) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 63AD2F7 for ; Thu, 16 May 2013 11:56:49 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 3E6AE20232; Thu, 16 May 2013 07:56:48 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 16 May 2013 07:56:48 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=m2FIYXJIndhHAxrs3dUOb8PrB9o=; b=KBiTRGguiFV4PvmAqhqU4 Qaz6p6RBv5CfIHVMhKHABALfx1MhfRqmx9I7xf8TNyXYWZ6xAcLJcqkGY3OpHdE1 1FcT3MawwDGaVppm/+ndxdlr7kZtR3Gb+1Ci53MTvgTF8FIlr/gEkPkMvSy9+R6Z DDItsCWkQiNRqo5kYUziCY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:cc:subject:references :date:mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=m2FIYXJIndhHAxrs3dUOb8PrB9o=; b=j20c TpqK0sB59PA64uTt4TkImNOaFoaX+h/Qlx/ZtP1JfPUNdG8LhU+pv5JNFcNtagp7 U3WTbwM5d65ZDYTiBzN2DX6jSVKK+adDXhwTg9URt2IOqrm6Yw4IV0NLjbwfwWmE TWn3MgdmA0SM+NTti1vu4eNk+JNjBFNJRQcAQeE= X-Sasl-enc: DzZ1aYrj45B72zMnxCKdBy1YXbXFtGWFPeIDw+RSzdRM 1368705408 Received: from tech304.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id EACE52001A3; Thu, 16 May 2013 07:56:47 -0400 (EDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Sergey Nasonov" , =?utf-8?Q?Roger_Pau_Monn=C3=A9?= Subject: Re: FreeBSD PVHVM call for testing References: <1999857.JXnoEZ2rWX@snasonovnbwxp.bcc> <5194B8CF.9020202@citrix.com> Date: Thu, 16 May 2013 06:56:47 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Mark Felder" Message-ID: In-Reply-To: <5194B8CF.9020202@citrix.com> User-Agent: Opera Mail/12.15 (FreeBSD) Cc: "freebsd-xen@freebsd.org" 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: Thu, 16 May 2013 11:56:49 -0000 On Thu, 16 May 2013 05:45:35 -0500, Roger Pau Monn=C3=A9 = wrote: > > Thanks for testing this, I'm afraid I'm not really familiar with > XenServer or XenCenter. It looks like Linux users are also running int= o > problems when trying to setup Linux PVHVMs on XenServer 6.1: He's hitting a well-known bug that's had a lot of discussion on this lis= t = and a little bit on one of the xen lists. I'm waiting for someone at = Citrix to fix this, but it doesn't seem to be a priority. Considering yo= ur = email is @citrix.com, it's a little bit disheartening that you're not = familiar with XenServer or XCP -- the only Xen platform where a business= = can get support direct from the vendor. :( Please use whatever resources= = you can to prioritize this issue as we'd love to upgrade our = virtualization environment to 1.6 ASAP. From all the information I've gathered it appears there's a regression = in = qemu used in XenServer/XCP that prevents FreeBSD XENHVM from booting on = = XenServer 6.1 / XCP 1.6. Earlier versions it works fine. NetBSD and = Linux-based Xen installs don't tend to have this problem because they us= e = upstream qemu directly. I'm waiting for the next release (XenServer 6.2?= ) = to come out so I can test again as they're supposed to be using upstream= = directly in future releases. Sergey, you can work around this by removing the CDROM/DVDROM device fro= m = the VM. This will allow you to boot the OS and use it. You could also st= ep = back down to XenServer 6.0 or XCP 1.5beta to work around it, but I'm sur= e = you're relying on some of the new features 6.1 has to offer.