Re: HEADS UP: merged PVHv2 support and future plans

[Roger Pau Monné]

On Sat, Aug 25, 2018 at 06:54:54PM +0200, Kai Otto wrote:
> On 13/08/18 19:19, Roger Pau Monné wrote:
> > On Mon, Aug 13, 2018 at 05:24:04PM +0200, Kai Otto wrote:
> >> 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-unsubscr...@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-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"
> > 
> > Hello,
> > 
> > This is a mistake of the port makefile which should be fixed in
> > r477080 that I've just committed. I hope updated packages will be
> > generated soon. Thanks for the testing!
> > 
> 
> Hello again :-)
> 
> Today I gave it another try with FreeBSD 12.0-ALPHA3 r338287 and the
> current packages for xen-tools411 and xen-kernel411. Sadly, I didn't get
> very far, even with the above bug being fixed.
> When attempting to start a HVM config, the console (xl console )
> stays empty and unresponsive.
> Connecting via vnc, the screen only shows this message: "Guest has not
> initialized the display (yet)".

I think this should be fixed by r477953, please make sure you have the
following package installed: xen-tools411-4.11.0_4

> When repeatedly running 'xl list', I can see that the domU almost
> consumes 1 second of CPU per second walltime.
> 
> Trying out PVH, the console also doesn't show any sign of life, and VNC
> says: "This VM has no graphic display device."
> Running 'xl list' shows, that the domU consumed about 1.4s of CPU, and
> then switched to 'blocked' state.

Can you paste the config file you are using to create the PVH guest?

And which OS/version are you trying to boot as PVH?

Roger.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Re: Using xen host on freebsd, is com1 the only way to attach to dom0?

[Roger Pau Monné]

On Fri, Aug 31, 2018 at 11:12:30PM -0400, Steven Friedrich wrote:
> I can boot a xen kernel, but it appears it doesn't acquire a DHCP address
> from my router.

Does this mean that the box doesn't boot correctly, or just that the
network card is not working when running under Xen?

> Someone suggested using vga=current,keep on xen_cmdline,
> but I'm unsure of the valid xen_cmdline arguments.

The best option would be to hook a serial cable and get the output
from the serial console.

The list of valid xen_cmdline can be found here for the 4.11 ports:

http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html

Or here if you are using the 4.7 port:

http://xenbits.xen.org/docs/4.7-testing/misc/xen-command-line.html

> Do I have to configure and build a FreeBSD kernel or just use what the xen
> meta-port builds?

You don't have to build a specific kernel to run FreeBSD as Dom0, just
using the GENERIC one from either 11.X or HEAD should work.

Roger.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"