Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Aug 2018 17:24:04 +0200
From:      Kai Otto <kai_otto@duckster.net>
To:        =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <royger@FreeBSD.org>
Cc:        freebsd-xen@freebsd.org
Subject:   Re: HEADS UP: merged PVHv2 support and future plans
Message-ID:  <3781a579-f00f-96fd-8f73-f3f344cd0aad@duckster.net>
In-Reply-To: <20180730101924.aatt5ug33kg6dfil@mac.bytemobile.com>
References:  <20180719090444.jojyziar2c6wy735@mac> <20180730101924.aatt5ug33kg6dfil@mac.bytemobile.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------7EC552A55C963B0907186647
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 30/07/18 12:19, Roger Pau Monné wrote:
> Packages for Xen 4.11 are now available in pkg.
> 
> Remember that in order to use those you need a very recent FreeBSD
> kernel (r336475 or newer) and the Xen command line has slightly changed,
> so dom0=pvh must be used instead of dom0pvh in order to boot. I will
> see about changing this in the handbook.
> 
> Roger.
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
> 

Hi Roger,
I tried to get some VMs running on
FreeBSD-12.0-CURRENT-amd64-20180802-r337160.
System is a Supermicro X9DRi-LN4F+ mainboard with dual Intel E5-2680v2
(ivy bridge).

When using xen-tools47/xen-kernel47, during boot of dom0, I only get the
error seen in the attached png ("d0v0 Triple fault").


When using xen-tools411/xen-kernel411, I can boot without problems, but
when running "xl create", neither a PVH nor HVM config work (see configs
and logs attached).
They both throw "libxl: info:
libxl_create.c:109:libxl__domain_build_info_setdefault: qemu-xen is
unavailable, using qemu-xen-traditional instead: No such file or directory"

Which doesn't make much sense to me, as PVH shouldn't use qemu at all?

The config files were put together following the documentation in
http://xenbits.xen.org/docs/4.11-testing/man/xl.cfg.5.html
which marks some of the keywords or syntax used in the FreeBSD handbook
as deprecated (i.e. 'builder' vs. 'type').

If I should do something different, or test a patch or something, let me
know. I'm super excited to see a recent Xen version ported to FreeBSD! :-)

- Kai

--------------7EC552A55C963B0907186647
Content-Type: text/plain; charset=UTF-8;
 name="test_server-hvm.cfg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="test_server-hvm.cfg"

dHlwZT0iaHZtIgoKbmFtZSA9ICJ0ZXN0X3NlcnZlciIKbWVtb3J5ID0gNTEyCnZjcHVzID0g
MQp2aWYgPSBbICdicmlkZ2U9YnJpZGdlMCcgXQpkaXNrID0gWyAnL2Rldi96dm9sL3pidWxr
L3ZtL3VuaXZlcnNhbF9tZWRpYV9zZXJ2ZXIscmF3LGhkYSxydycsCiAgICAgICAgICcvemJ1
bGsvbWVkaWFzaGFyZS9pc29zL2xpbnV4L2FscGluZS12aXJ0LTMuOC4wLXg4Nl82NC5pc28s
cmF3LGhkYyxyLGNkcm9tJwpdCgp2bmMgPSAxCnZuY2xpc3RlbiA9ICIwLjAuMC4wIgp1c2Jk
ZXZpY2UgPSBbJ3RhYmxldCddCgoK
--------------7EC552A55C963B0907186647
Content-Type: text/plain; charset=UTF-8;
 name="test_server-pvh.cfg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="test_server-pvh.cfg"

dHlwZT0ncHZoJwoKbmFtZSA9ICJ0ZXN0X3NlcnZlciIKbWVtb3J5ID0gNTEyCnZjcHVzID0g
MQprZXJuZWwgPSAiL21udC9ib290L3ZtbGludXotdmlydCIKcmFtZGlzayA9ICIvbW50L2Jv
b3QvaW5pdHJhbWZzLXZpcnQiCnZpZiA9IFsgJ2JyaWRnZT1icmlkZ2UwJyBdCnZmYiA9IFsg
J3ZuYz0xLCB2bmNsaXN0ZW49MC4wLjAuMCx2bmN1bnVzZWQ9MSddCmRpc2sgPSBbICcvZGV2
L3p2b2wvemJ1bGsvdm0vdW5pdmVyc2FsX21lZGlhX3NlcnZlcixyYXcseHZkYSxydycsCiAg
ICAgICAgICcvemJ1bGsvbWVkaWFzaGFyZS9pc29zL2xpbnV4L2FscGluZS12aXJ0LTMuOC4w
LXg4Nl82NC5pc28scmF3LHh2ZGIscixjZHJvbScKXQp1c2JkZXZpY2UgPSAidGFibGV0IgoK
Cg==
--------------7EC552A55C963B0907186647--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3781a579-f00f-96fd-8f73-f3f344cd0aad>