From owner-freebsd-xen@FreeBSD.ORG  Mon Aug 12 13:29:08 2013
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@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 9A379532
 for <freebsd-xen@freebsd.org>; Mon, 12 Aug 2013 13:29:08 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6EBB62DBF
 for <freebsd-xen@freebsd.org>; Mon, 12 Aug 2013 13:29:08 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 73406211DB
 for <freebsd-xen@freebsd.org>; Mon, 12 Aug 2013 09:29:01 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute3.internal (MEProxy); Mon, 12 Aug 2013 09:29:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=dxbJiZ5TNwqv2Q/2dTSzTXGRq38=; b=crC
 1hWkXmFQwB7IiS7aSu7UCoX8wYFAVZKIwXTQl2SpkQp3AXG/QW4nWKHyTTlq8FMw
 f5sNK9hrHLHmZr5tTqvPD5QE21kx5WiU6Bfkp+wFzaMTdH8MubyvdK5z9f9HyrwT
 GWLYPgiOWkxEdhII+2LY2poOWFzelO+2sCQcNGy4=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 59082B02386; Mon, 12 Aug 2013 09:29:01 -0400 (EDT)
Message-Id: <1376314141.4739.8833555.69CB6771@webmail.messagingengine.com>
X-Sasl-Enc: 64SoFvmrppD0FbrOgaHj0MG8HIeMw0igbWPEbN8OrIuk 1376314141
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-xen@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-d9f253bf
In-Reply-To: <CANrxokG9BtJR1jAu_+8wX8x2KvtMHtxiq_OOE_gLQ+Y0tH0pzQ@mail.gmail.com>
References: <CANrxokG9BtJR1jAu_+8wX8x2KvtMHtxiq_OOE_gLQ+Y0tH0pzQ@mail.gmail.com>
Subject: Re: XENHVM and XenServer 6.2
Date: Mon, 12 Aug 2013 08:29:01 -0500
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 13:29:08 -0000

Hi Micha=C5=82,

To my knowledge this is strictly a qemu issue and should be solved when
XenServer starts shipping upstream qemu instead of their own fork. There
may be a way for FreeBSD to work around it, but I am not aware of anyone
trying.

The current solution is to remove the entire CDROM/DVDROM drive from the
VM to boot a XENHVM kernel. There is no workaround, unfortunately. I
have filed this bug with a couple Citrix contacts of mine but have not
heard back on an ETA for a solution on the XenServer side.