NetBSD Problem Report #56662

From www@netbsd.org  Mon Jan 24 00:22:44 2022
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 76FD91A9239
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 24 Jan 2022 00:22:44 +0000 (UTC)
Message-Id: <20220124002243.4F6161A923A@mollari.NetBSD.org>
Date: Mon, 24 Jan 2022 00:22:43 +0000 (UTC)
From: coypu@sdf.org
Reply-To: coypu@sdf.org
To: gnats-bugs@NetBSD.org
Subject: Can't boot on hypervisor that only supports grant table v1
X-Send-Pr-Version: www-1.0

>Number:         56662
>Category:       port-xen
>Synopsis:       Can't boot on hypervisor that only supports grant table v1
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-xen-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 24 00:25:00 +0000 2022
>Closed-Date:    Mon Jan 24 01:24:48 +0000 2022
>Last-Modified:  Mon Jan 24 11:00:03 +0000 2022
>Originator:     coypu
>Release:        NetBSD 9.99.93
>Organization:
>Environment:
NetBSD 9.99.93 (XEN3_DOMU) #37: Sun Jan 23 23:08:35 UTC 2022
>Description:
Ever since bouyer-xenpvh, xen grant table v2 is required.
on prgmr.com servers (I am only a user) I get:

[   1.0000000] hypervisor0 at mainbus0: Xen version 4.14.0.88.g1d1d1f53
[   1.0000000] panic: GNTTABOP_set_version 2 failed -38
>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Mon, 24 Jan 2022 01:24:48 +0000
State-Changed-Why:
This won't be chnaged, v2 is required.
Since the grant system is central to proper memory management, it's
extremely bad idea to maintain compatibility with the legacy v1 interface,
which would only be used in extremely rare cases.
AFAIK v2 can be turned off in Dom0 for DomUs, ask them to allow v2.


From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@netbsd.org
Cc: port-xen-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
        gnats-admin@netbsd.org, jdolecek@NetBSD.org, coypu@sdf.org
Subject: Re: port-xen/56662 (Can't boot on hypervisor that only supports
 grant table v1)
Date: Mon, 24 Jan 2022 11:56:18 +0100

 On Mon, Jan 24, 2022 at 01:24:48AM +0000, jdolecek@NetBSD.org wrote:
 > Synopsis: Can't boot on hypervisor that only supports grant table v1
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: jdolecek@NetBSD.org
 > State-Changed-When: Mon, 24 Jan 2022 01:24:48 +0000
 > State-Changed-Why:
 > This won't be chnaged, v2 is required.
 > Since the grant system is central to proper memory management, it's
 > extremely bad idea to maintain compatibility with the legacy v1 interface,
 > which would only be used in extremely rare cases.
 > AFAIK v2 can be turned off in Dom0 for DomUs, ask them to allow v2.

 unforntunably that's not quite true. Newer Xen version removed PV support
 from the hypervisor for x86-32 and supports it only via pvshim (and it's
 recommended to do so for older versions as well). So I fear that we'll
 have to get back v1 support, in addition to v2.

 Linux supports both.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

>Unformatted:

Home	PR Database Search