Re: XENPVHVM

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I tried to run the XEN_PVHVM kernel on a -current guest undet XCP-NG;
when I select it, I get only a black screen with a blinking underscore
in the top left corner.

Do I need to modify the guest settings in order to boot a PVHVM
kernel? Not knowing the process, I also tried booting  otherwise a PV
NetBSD-current guest using this kernel, but XCP-NG refuses even to
try.

On Fri, 7 Jun 2019 at 20:06, Brian Marcotte <marcotte%panix.com@localhost> wrote:
>
> > Do you have a bootup dmesg though ?
>
> [   1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
> [   1.0000000]     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
> [   1.0000000]     2018, 2019 The NetBSD Foundation, Inc.  All rights reserved.
> [   1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
> [   1.0000000]     The Regents of the University of California.  All rights reserved.
>
> [   1.0000000] NetBSD 8.99.42 (XEN3_PVHVM) #1: Fri Jun  7 09:44:07 EDT 2019
> [   1.0000000]  root%juggler.panix.com@localhost:/misc/obj64/misc/devel/NO-BACKUPS/current/src/sys/arch/amd64/compile/XEN3_PVHVM
> [   1.0000000] total memory = 1691 MB
> [   1.0000000] avail memory = 1635 MB
> [   1.0000030] mainbus0 (root)
> [   1.0000030] cpu0 at mainbus0
> [   1.0000030] cpu0: Intel(R) Xeon(R) CPU           L5630  @ 2.13GHz, id 0x206c2
> [   1.0000030] cpu0: package 0, core 0, smt 0
> [   1.0000030] isa0 at mainbus0
> [   1.0000030] com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
> [   1.0000030] com0: console
> [   1.0000030] hypervisor: Identified Guest XEN in HVM mode.
> [   1.0000030] hypervisor: detected functional hypercall page.
> [   1.0000030] hypervisor0 at mainbus0: Xen version 4.11.2-pre
> [   1.0000030] vcpu at hypervisor0 not configured
> [   1.0000030] xenbus0 at hypervisor0: Xen Virtual Bus Interface
> [   1.0000030] xencons0 at hypervisor0: Xen Virtual Console Driver
> [   1.0896507] xenbus: can't get state for device/suspend/event-channel (2)
> [   1.1296605] xbd0 at xenbus0 id 768: Xen Virtual Block Device Interface
> [   1.1996599] xbd1 at xenbus0 id 832: Xen Virtual Block Device Interface
> [   1.2896621] unknown type vkbd at xenbus0 id 0 not configured
> [   1.3896636] xennet0 at xenbus0 id 0: Xen Virtual Network Interface
> [   1.4003862] xennet0: MAC address ee:98:25:44:09:23
> [   1.4396660] balloon at xenbus0 id 0 not configured
> [   1.5096654] WARNING: xbd1: total unit size in disklabel (6291456) != the size of xbd1 (2097152)
> [   1.5396558] WARNING: xbd1: end of partition `a' exceeds the size of xbd1 (2097152)
> [   1.5596578] WARNING: xbd1: end of partition `d' exceeds the size of xbd1 (2097152)
> [   1.5896616] boot device: xbd0
> [   1.5996592] xennet0: using RX copy mode
> [   1.6114110] root on xbd0a dumps on xbd0b
> [   1.6296680] xenbus: can't get state for device/suspend/event-channel (2)
> [   1.6596584] /: replaying log to memory
> [   1.6753702] unknown type vkbd at xenbus0 id 0 not configured
> [   1.6918849] root file system type: ffs
> [   1.7007712] kern.module.path=/stand/amd64-xen/8.99.42/modules
> [   1.7202846] clock: unknown CMOS layout
> [   1.7296813] ignore shutdown request:
> [   1.7412554] xenbus: can't get state for device/suspend/event-channel (2)
> [   1.7696601] unknown type vkbd at xenbus0 id 0 not configured
>


-- 
----