From xen-users-bounces@lists.xenproject.org Mon Oct 04 00:09:43 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Oct 2021 00:09:43 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201127.355549 (Exim 4.92) (envelope-from ) id 1mXBWr-0004gN-Vt; Mon, 04 Oct 2021 00:08:25 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201127.355549; Mon, 04 Oct 2021 00:08:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXBWr-0004gC-O5; Mon, 04 Oct 2021 00:08:25 +0000 Received: by outflank-mailman (input) for mailman id 201127; Mon, 04 Oct 2021 00:08:23 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXBWp-0004fn-Cy for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 00:08:23 +0000 Received: from mail-vk1-xa2b.google.com (unknown [2607:f8b0:4864:20::a2b]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 1b32eaa3-b1c8-479a-89b7-8f1dd47066f9; Mon, 04 Oct 2021 00:08:22 +0000 (UTC) Received: by mail-vk1-xa2b.google.com with SMTP id o204so6864512vko.9 for ; Sun, 03 Oct 2021 17:08:22 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 1b32eaa3-b1c8-479a-89b7-8f1dd47066f9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=L93zLclW02B6SwmVz7GH2stQHBzwQ0Ybnf6ew38njf8=; b=XEEx440ECGeVxMXXxjlKSu6m3J1Wjav+yqtUd5bvfWFVtrha6+EYRXvfSfv43tTygI LLlghe5m2Px/qE86Pyx/8NhbkKT3wU4JFKTcBLiKXUt7CEEwaVtBQjAvURLJcGSGxqZD Pyf9sU9NrFimNboAfSutkZHBnjeIZOEKen8w5yxr8ValEdajmDlVg1/ESzf1+pyDPw+b X3WY1yCkL0PpYlh/fXyCAvdr95qln3TzV5U2CB7wZUnfsk4TnqFfnV9JLKT+ZsRdqC2w kbcFNyS20WddHnewAQZAyeIoF/mObEdR3uvbpYFiLBwtx3GWmnMAJ3vAietDhKRbqSui liVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=L93zLclW02B6SwmVz7GH2stQHBzwQ0Ybnf6ew38njf8=; b=Ij/rtWQhLfmpaQfqfj4OgIN1umCSnzO7mKWaJMnhnru8oHFCXYQ9Z8/NihrdLRKh5J +UEMChKQQVDrA1AiTvTbsXOINgeQKn4IiVaeNy1A84JmLVsa+GOOcF2vU+ncSeZ31TPI 0uFBdnwUJVtFU4LE4NV/RA/TolD8sszI71i9erSVpCGu5wuHnhB9fnJIzJ+qgdvCao6W L/zZkPuxR4GM9zmwtLTypjKYhR5MTYMoqsammrk1652C+cCwN/dMyr6WY+0OWTIX2fSz CnRjMfLf9k+m7lQ0400q0iLgijPs7MbDMF+4+x9X7+JowdCUt+jIpYFroYvgnQAxZsgQ OfQg== X-Gm-Message-State: AOAM533URnOJlmjI3OhA9T/QTBN96A6cOdMI3maXR8EaECyFBu/ECFzx Q03Oe6QQBNWhaSRd/shT1MyEzhdQy3A2/oKObnSaoEpa5Ps= X-Google-Smtp-Source: ABdhPJyePmQooO1U7qvBfw84ECrAI52x92fF7+HBzhRDigTsbaWtQspu5fIvDdEXlrMNclFnjPXyQRUQQOUjm7uM6SM= X-Received: by 2002:a1f:1c57:: with SMTP id c84mr13127076vkc.22.1633306101763; Sun, 03 Oct 2021 17:08:21 -0700 (PDT) MIME-Version: 1.0 From: Chris Myers Date: Sun, 3 Oct 2021 19:08:10 -0500 Message-ID: Subject: iptables support for Debian 11 PV domu's To: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="0000000000000152ae05cd7bb61e" --0000000000000152ae05cd7bb61e Content-Type: text/plain; charset="UTF-8" I'm working on upgrading my Xen environments from Debian 10 to 11. Today I tried one of my dom0's and that seemed to go fine, so I tried a couple of domu's. That didn't go quite so well; when they started up the networking wouldn't start. Doing some checks, the error message was that it was in the pre-up scripts, which I've only got one thing - restoring the iptables rulesets. Trying to do a generic iptables -V gives the generic message iptables/1.8.7 Failed to initialize nft: Protocol not supported I ran the same command on the dom0 and it worked correctly. I'm restoring my domu snapshots to revert them back to Debian 10, but was curious - is there a way to get the regular iptables-nft stuff to work in a Debian 11 pv domu, or do I need to start migrating over all of my firewall rules (hundreds of them, with some really complex stuff set up that I'm not ready to have break and try to fix...) before I can upgrade my VMs? Chris --0000000000000152ae05cd7bb61e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm working on upgrading my Xen environments from= Debian 10 to 11. Today I tried one of my dom0's and that seemed to go = fine, so I tried a couple of domu's. That didn't go quite so well; = when they started up the networking wouldn't start.

Doing some checks, the error message was that it was in the pre-up sc= ripts, which I've only got one thing - restoring the iptables rulesets.=

Trying to do a generic iptables -V gives the gene= ric message

iptables/1.8.7 Failed to ini= tialize nft: Protocol not supported

I ran t= he same command on the dom0 and it worked correctly.

I'm restoring my domu snapshots to revert them back to Debian 10, bu= t was curious - is there a way to get the regular iptables-nft stuff to wor= k in a Debian 11 pv domu, or do I need to start migrating over all of my fi= rewall rules (hundreds of them, with some really complex stuff set up that = I'm not ready to have break and try to fix...) before I can upgrade my = VMs?

Chris
--0000000000000152ae05cd7bb61e-- From xen-users-bounces@lists.xenproject.org Mon Oct 04 01:26:05 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Oct 2021 01:26:05 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201146.355566 (Exim 4.92) (envelope-from ) id 1mXCj7-0002HU-Mx; Mon, 04 Oct 2021 01:25:09 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201146.355566; Mon, 04 Oct 2021 01:25:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXCj7-0002HM-Jd; Mon, 04 Oct 2021 01:25:09 +0000 Received: by outflank-mailman (input) for mailman id 201146; Mon, 04 Oct 2021 01:25:08 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXCj6-0002HG-I6 for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 01:25:08 +0000 Received: from mail-vs1-xe35.google.com (unknown [2607:f8b0:4864:20::e35]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 92924733-2199-451b-9c4d-8e0e88738e27; Mon, 04 Oct 2021 01:25:07 +0000 (UTC) Received: by mail-vs1-xe35.google.com with SMTP id y14so3796645vsm.9 for ; Sun, 03 Oct 2021 18:25:07 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 92924733-2199-451b-9c4d-8e0e88738e27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+MOPWKH0p1YbqaRQEQaaGVauRVlMKYRo4WJtVvbun5Y=; b=FpR6vYMysNL4WU8Q3qH/JEfftO4IOw6SlO2OocRmBzFh0e+iFN4jCPd5iULylFMJf3 Lcz71bfxQpjNQe05CXKROySkg7aM7yOVlEdDF3f9+P4GzgjLGaCW8AD00R+vNWq0vPDY ju6/+r8DOdeKXJwaWPY9iVwVuMk6AShnvngi7i3zXHiO2Hpn3FDO4RqPfYAiInTvDcc4 4BvX7SG1hEFZCeLWXBcQKBgByvD5wraWlJNzoTwNYgLRt6Oco3OlQ6Lof0WZxW86v5G7 U4BLDG7aNnp1uDn0Xv7v7RgwQ+WJomeFJDjEMuUAzEL0CT1pORVEZ16uUyZp1GIxsTDc XuoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+MOPWKH0p1YbqaRQEQaaGVauRVlMKYRo4WJtVvbun5Y=; b=YVmfpTM7Bh5D0RMyuaGyUX5w5TXsj+0Ut5O4zG2OcVtW14FkgJ5XQbAOdCD7ox5Fa/ Hq8euO8F1Y5VEamNyA+284NuM4Z9I5HQNnSRjxdmJX04WH5I93B+02MjplA5/HlaWrKO vYzl4eC76hYc+8UimGukvO2QnyROpW3f63e3Ji4yVAerIyTU6brh/1LVPSKGx4h725fU oQhTTgYSyndAhMz6581caS126EhO9KKJTXRM+uKQVnjriUHyedi3CvtWYB5RbVch9KsZ psvUtLwlnrnPi+LbPiKFz/U20+Z89HHBaX97vbTyIex6smgro+1uqwkZ3nPAnrF3XQba bJ3g== X-Gm-Message-State: AOAM530zlQ3/qMA/A4m2exBZ8dDitFeW4PLM5mb++3P07xaN3PoZ1mpP 8duc7DZCaXsgN2yC6R398gIOkGeD/p1Jt/q64A== X-Google-Smtp-Source: ABdhPJxvqJ0FDbPvgiPYr1+tTKxVs8iiH5udecolEhoP0pdX99MBH3bedGDL2Okspj2YqHk6hFCuqilPcUNrkhkX5vY= X-Received: by 2002:a67:ab04:: with SMTP id u4mr11346711vse.12.1633310706869; Sun, 03 Oct 2021 18:25:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: TMC Date: Mon, 4 Oct 2021 12:24:55 +1100 Message-ID: Subject: Re: iptables support for Debian 11 PV domu's To: Chris Myers Cc: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="0000000000007daa3d05cd7cc858" --0000000000007daa3d05cd7cc858 Content-Type: text/plain; charset="UTF-8" did you install iptables in your debian 11 VM? On Mon, 4 Oct 2021 at 11:09, Chris Myers wrote: > I'm working on upgrading my Xen environments from Debian 10 to 11. Today I > tried one of my dom0's and that seemed to go fine, so I tried a couple of > domu's. That didn't go quite so well; when they started up the networking > wouldn't start. > > Doing some checks, the error message was that it was in the pre-up > scripts, which I've only got one thing - restoring the iptables rulesets. > > Trying to do a generic iptables -V gives the generic message > > iptables/1.8.7 Failed to initialize nft: Protocol not supported > > I ran the same command on the dom0 and it worked correctly. > > I'm restoring my domu snapshots to revert them back to Debian 10, but was > curious - is there a way to get the regular iptables-nft stuff to work in a > Debian 11 pv domu, or do I need to start migrating over all of my firewall > rules (hundreds of them, with some really complex stuff set up that I'm not > ready to have break and try to fix...) before I can upgrade my VMs? > > Chris > -- -- GPG key fingerprint: 07DF B95B DB58 57B6 9656 682E 830A D092 288E F017 GPG public key available on pgp(dot)net key server --0000000000007daa3d05cd7cc858 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
did you install iptables in your debian 11 VM?
On Mon, = 4 Oct 2021 at 11:09, Chris Myers <chrismyers81@gmail.com> wrote:
I'm working on upgradin= g my Xen environments from Debian 10 to 11. Today I tried one of my dom0= 9;s and that seemed to go fine, so I tried a couple of domu's. That did= n't go quite so well; when they started up the networking wouldn't = start.

Doing some checks, the error message was th= at it was in the pre-up scripts, which I've only got one thing - restor= ing the iptables rulesets.

Trying to do a generic = iptables -V gives the generic message

ip= tables/1.8.7 Failed to initialize nft: Protocol not supported
<= div>
I ran the same command on the dom0 and it worked correct= ly.

I'm restoring my domu snapshots to revert = them back to Debian 10, but was curious - is there a way to get the regular= iptables-nft stuff to work in a Debian 11 pv domu, or do I need to start m= igrating over all of my firewall rules (hundreds of them, with some really = complex stuff set up that I'm not ready to have break and try to fix...= ) before I can upgrade my VMs?

Chris
=


--
--
GPG key fingerprint: 07DF= B95B DB58 57B6 9656=C2=A0 682E 830A D092 288E F017
GPG public ke= y available on pgp(dot)net key server
--0000000000007daa3d05cd7cc858-- From xen-users-bounces@lists.xenproject.org Mon Oct 04 06:57:51 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Oct 2021 06:57:51 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201204.355629 (Exim 4.92) (envelope-from ) id 1mXHuA-0001eL-F7; Mon, 04 Oct 2021 06:56:54 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201204.355629; Mon, 04 Oct 2021 06:56:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXHuA-0001eD-9w; Mon, 04 Oct 2021 06:56:54 +0000 Received: by outflank-mailman (input) for mailman id 201204; Mon, 04 Oct 2021 06:56:53 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXHu9-0001e7-6E for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 06:56:53 +0000 Received: from mail-qt1-x82c.google.com (unknown [2607:f8b0:4864:20::82c]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id f804f698-bbef-424f-8746-2b8395376009; Mon, 04 Oct 2021 06:56:52 +0000 (UTC) Received: by mail-qt1-x82c.google.com with SMTP id r16so14988076qtw.11 for ; Sun, 03 Oct 2021 23:56:52 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: f804f698-bbef-424f-8746-2b8395376009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IPVIcqIFbW2vf8N4tf+OxnTRH0GIfCD1cRQRm7eWaDs=; b=fXzJPQbx6G+KfbfK6mCSiDMXjzVJILqYngWozJnWfde82zSOpUKUbdC6ebxXvkEL1o LOH8AdAQQfxmOGqu/q2dIpDBG9ozhHWAnNHzXPE4e+NAgPgooEVJ/4tk22jv4SPxgfGn Sk9O36hwL//EfpG+8b3ITQJc2an3CLqoeCY13/YtZGLJcDQVvwmqhNJdX4usdnEcYOYi cSWooD4MVkFYKWpeYQnYxX4kdQ35IifLPseSP9PdeqFNadv6wr1ouQFuo4YJuZzu2nkn GYkHN2wd1rlyqPfPNofs5uOcrYh1WrOvwh7CrTorDtbWoZDA5JG0cvm645Ov1FGgRSc0 4TVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IPVIcqIFbW2vf8N4tf+OxnTRH0GIfCD1cRQRm7eWaDs=; b=Evy7LKlHElodtUgTiKZcPNzillLaXg/96yZB5q0GuBLXYigzDjWBZfCu99qOjMlNdU 3HzGu4o9TdwTuWCGF0gDa2zypzIZgTLvMa+rl1XqRjRkDSdS3SxsehcqaNzEkF6wXQW1 PWd3rABBr4IhxcXHEshVZKVF3w2Vhb8aPtt0r0Avrv65mjLWDiZqgAXuZob1fGgUxQMi K8BSdVDmntqa6L2XrxNDckqbyqk5K4EHPLyk59Bz/q9MiivWytUY4MKrbllxsFueyMLi xWiuo2ecEF+cthAoDjn9s95111dGSKy2ySZpxFBdL+DWEgq3VIVaZktDuH7jVKq5Q6j1 xP+Q== X-Gm-Message-State: AOAM530cefQYDoofBL1xrc2iEnnt2FAoVmVPCXC/53ScDyW3WuyXJInb msiRLGa03+FC7Xbc/hId42lljHdwQ3bx12bcZGg= X-Google-Smtp-Source: ABdhPJyOaJhA6TcCCq8A7lDQ5dW1Li4LLNouWkQDAEeGTlWLdMdVX0VhBGwImstYDGi33/DwrK5hfGdgR/tsn2RIvsU= X-Received: by 2002:a05:622a:202:: with SMTP id b2mr11658595qtx.205.1633330611898; Sun, 03 Oct 2021 23:56:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mathias Dufresne Date: Mon, 4 Oct 2021 08:56:39 +0200 Message-ID: Subject: Re: iptables support for Debian 11 PV domu's To: TMC Cc: Chris Myers , xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000ec4c6805cd816a6f" --000000000000ec4c6805cd816a6f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey, As nft seems to me mainly coming from modules (and because seems to be installed), I would check the kernel of guests: which one is loaded, how, does it comes with nft modules.... Cheers, mathias Le lun. 4 oct. 2021 =C3=A0 03:25, TMC a =C3=A9crit : > did you install iptables in your debian 11 VM? > > On Mon, 4 Oct 2021 at 11:09, Chris Myers wrote: > >> I'm working on upgrading my Xen environments from Debian 10 to 11. Today >> I tried one of my dom0's and that seemed to go fine, so I tried a couple= of >> domu's. That didn't go quite so well; when they started up the networkin= g >> wouldn't start. >> >> Doing some checks, the error message was that it was in the pre-up >> scripts, which I've only got one thing - restoring the iptables rulesets= . >> >> Trying to do a generic iptables -V gives the generic message >> >> iptables/1.8.7 Failed to initialize nft: Protocol not supported >> >> I ran the same command on the dom0 and it worked correctly. >> >> I'm restoring my domu snapshots to revert them back to Debian 10, but wa= s >> curious - is there a way to get the regular iptables-nft stuff to work i= n a >> Debian 11 pv domu, or do I need to start migrating over all of my firewa= ll >> rules (hundreds of them, with some really complex stuff set up that I'm = not >> ready to have break and try to fix...) before I can upgrade my VMs? >> >> Chris >> > > > -- > -- > GPG key fingerprint: 07DF B95B DB58 57B6 9656 682E 830A D092 288E F017 > GPG public key available on pgp(dot)net key server > --000000000000ec4c6805cd816a6f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey,

As nft seems to me main= ly coming from modules (and because seems to be installed), I would check t= he kernel of guests: which one is loaded, how, does it comes with nft modul= es....

Cheers,

mathias

Le=C2=A0lun. 4 oct. 2021 =C3=A0=C2=A003:25, TMC <tmciolek@gmail.com> a =C3=A9crit=C2=A0:
did y= ou install iptables in your debian 11 VM?

On Mon, 4 Oct 2021 at 11:09, C= hris Myers <= chrismyers81@gmail.com> wrote:
I'm working on upgrading my= Xen environments from Debian 10 to 11. Today I tried one of my dom0's = and that seemed to go fine, so I tried a couple of domu's. That didn= 9;t go quite so well; when they started up the networking wouldn't star= t.

Doing some checks, the error message was that i= t was in the pre-up scripts, which I've only got one thing - restoring = the iptables rulesets.

Trying to do a generic ipta= bles -V gives the generic message

iptabl= es/1.8.7 Failed to initialize nft: Protocol not supported
=
I ran the same command on the dom0 and it worked correctly.<= /div>

I'm restoring my domu snapshots to revert them= back to Debian 10, but was curious - is there a way to get the regular ipt= ables-nft stuff to work in a Debian 11 pv domu, or do I need to start migra= ting over all of my firewall rules (hundreds of them, with some really comp= lex stuff set up that I'm not ready to have break and try to fix...) be= fore I can upgrade my VMs?

Chris


--
--
GPG key fingerprint: 07DF B95B DB58 57B6 9656=C2= =A0 682E 830A D092 288E F017
GPG public key available on pgp(dot)= net key server
--000000000000ec4c6805cd816a6f-- From xen-users-bounces@lists.xenproject.org Mon Oct 04 11:27:19 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Oct 2021 11:27:19 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201279.355719 (Exim 4.92) (envelope-from ) id 1mXM6s-00055L-H4; Mon, 04 Oct 2021 11:26:18 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201279.355719; Mon, 04 Oct 2021 11:26:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXM6s-00055C-DU; Mon, 04 Oct 2021 11:26:18 +0000 Received: by outflank-mailman (input) for mailman id 201279; Mon, 04 Oct 2021 11:26:16 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXM6q-000556-KQ for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 11:26:16 +0000 Received: from s1-smtprelay.thinkmo.de (unknown [213.239.209.163]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id e21494de-2505-11ec-beab-12813bfff9fa; Mon, 04 Oct 2021 11:26:14 +0000 (UTC) Received: from shell.thinkmo.de (shell.thinkmo.de [IPv6:2a01:4f8:a1:6e:0:22:0:1]) by s1-smtprelay.thinkmo.de (Postfix) with ESMTPS id 4HNJLs0m0Sz9K for ; Mon, 4 Oct 2021 11:26:13 +0000 (UTC) Received: by shell.thinkmo.de (Postfix, from userid 1000) id 4HNJLr6y8fz59; Mon, 4 Oct 2021 13:26:12 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: e21494de-2505-11ec-beab-12813bfff9fa Date: Mon, 4 Oct 2021 13:26:12 +0200 From: Bastian Blank To: xen-users@lists.xenproject.org Subject: Re: iptables support for Debian 11 PV domu's Message-ID: <20211004112612.GA23282@shell.thinkmo.de> Mail-Followup-To: Bastian Blank , xen-users@lists.xenproject.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) On Sun, Oct 03, 2021 at 07:08:10PM -0500, Chris Myers wrote: > Trying to do a generic iptables -V gives the generic message > iptables/1.8.7 Failed to initialize nft: Protocol not supported You are missing NFT support in the kernel. So you run the kernel not shipped in this version of Debian or in an environment that forbids loading modules. You could use a workaround and revert to the old iptables interface, by using iptables-legacy (see update-alternatives --list iptables). Bastian -- "... freedom ... is a worship word..." "It is our worship word too." -- Cloud William and Kirk, "The Omega Glory", stardate unknown From xen-users-bounces@lists.xenproject.org Mon Oct 04 19:51:06 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Oct 2021 19:51:06 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201703.356316 (Exim 4.92) (envelope-from ) id 1mXTyZ-0007iJ-VR; Mon, 04 Oct 2021 19:50:15 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201703.356316; Mon, 04 Oct 2021 19:50:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXTyZ-0007iA-S3; Mon, 04 Oct 2021 19:50:15 +0000 Received: by outflank-mailman (input) for mailman id 201703; Mon, 04 Oct 2021 19:50:13 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXTyX-0007i4-F8 for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 19:50:13 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 3bdaef08-8a5b-4601-9e1c-90fab595137a; Mon, 04 Oct 2021 19:50:12 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mXTyV-00082m-36 for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 19:50:11 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 3bdaef08-8a5b-4601-9e1c-90fab595137a DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=/qHQMkhKqB6DIZyoFGYBBDsEsSlQ0oywekxM2SMRcFg=; b=Y6gRLUhy44HSRB3HwQbT1nnf2F CdRiz13Cf33fshOxVpQlUJkdi/vtFmroIsTxO+66vfU1sLjBwqZwK61qxFS4OUbEHUTIX1v/PvILM KhDJgsIubOjAQcT5Cu+FzHVzfvaHYJfUZ1vNorQgF+1SEeLLIkDTRbo6ChjEYAhHwlANpBNqZjZkA fO1pF2GALtSrf5UpA3FbN0KqALhU6PPaZ+mTsRV76b4rmhPzFvdGZ0LhNf9Cr7sERq3IhV8hRsAF6 O8uBFF5Ugl2OVwwZxJtGdcNMS7s5FVUfZFSOxqqDRIV3BGd8PIwqdEoAiexHk3apW3Y28QeWISWAU /+eWrbAw==; Date: Mon, 4 Oct 2021 19:50:10 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: iptables support for Debian 11 PV domu's Message-ID: <20211004195010.earbegnpot3xr4ok@bitfolk.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Hi Chris, On Sun, Oct 03, 2021 at 07:08:10PM -0500, Chris Myers wrote: is there a way to get the regular iptables-nft stuff to work in a > Debian 11 pv domu, I've not had any issues using iptables, with nft or legacy, in Debian 11 or Debian 12 PV domU, so I think your problem is strictly related to the kernel you are using. Can you confirm whether your domU kernel and its modules are ones that come from the linux-image-amd64 package that comes with Debian 11? Cheers, Andy From xen-users-bounces@lists.xenproject.org Mon Oct 04 23:32:12 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 04 Oct 2021 23:32:12 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201746.356363 (Exim 4.92) (envelope-from ) id 1mXXQP-0003qX-HI; Mon, 04 Oct 2021 23:31:13 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201746.356363; Mon, 04 Oct 2021 23:31:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXXQP-0003qP-D8; Mon, 04 Oct 2021 23:31:13 +0000 Received: by outflank-mailman (input) for mailman id 201746; Mon, 04 Oct 2021 23:31:12 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXXQO-0003qJ-3u for xen-users@lists.xenproject.org; Mon, 04 Oct 2021 23:31:12 +0000 Received: from mail-ua1-x935.google.com (unknown [2607:f8b0:4864:20::935]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id f33734fb-566c-4305-8486-f8904d6724cf; Mon, 04 Oct 2021 23:31:11 +0000 (UTC) Received: by mail-ua1-x935.google.com with SMTP id y3so8215316uar.5 for ; Mon, 04 Oct 2021 16:31:11 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: f33734fb-566c-4305-8486-f8904d6724cf DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=u904l5V43yQ2UczITjgvd13gSs6/fCs9IrJ4xlOSqmY=; b=obAbIfwA39pwZMdP3xkI5nWqdyZ9+pJJTOuz4ryOkAOjeoSPLId8pKqc+5S17r5C89 DFyc9C7p0JYOTTaDHntrfVUqIIPZ5ZoaQxLP7QznTnLh2+igu9JK0l+wsfDceCRv0Qks QL4hCgG++AqwRtJdGBQee6JcFYv2Ijs3cwchOAT2t8TpqVtk+s/KfwcBinKFC2iMK7AI GNe2RAUs5ry8q/Z/lq6x7tLFbMChtayNonsHi1NI7lHqdFzB5WXFeOT9FN8kP4pPrBO5 YRuJMiyhClNG6qZrwOuuqe0HKmuKvlvDUfE1uFgZl9AV56uY1YEwt4kIBJiAnaqiwy7E IXJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=u904l5V43yQ2UczITjgvd13gSs6/fCs9IrJ4xlOSqmY=; b=oUCqYVfm8ullw0JQOuUO9kfW88S7HvGgjrNG8UWgVBFKwHxsoDLnDQBJa1ZxV9srlm bMfEawcYIZ3L/QTJE9P7MP1jCD7FKoQKsWp2kcr9IwuXtuO40QvhPqRmkKlB99p8yz1R bKWRBcePgf7Vwhp1q7sTgk5u+qc/Bx5Kj9lSWB8skYFIm8GGTc7gKzmlKbyA34lkSo2n /z12MVbr5AHl4ZqyBXIUdtt9YoDa1324FKoHKWMb8InyKBmXJtFQFqSohJkdNABnUVQh jqlLGPe2pg8D8eMKP7bLheS5Cct22uvkCNVndpvBJXvbUp301cmVJGfMMXk5mp34PEFp ifMA== X-Gm-Message-State: AOAM533Yw28QoVYKm0YYxuiua/aRPbiB+Imd5Xx0IiU86Uh97LmGqzNj VSTWyP90+tbJHeEXyExNkxivu3Ba4GbYFp2Hkxz3Pkn4dQ== X-Google-Smtp-Source: ABdhPJzj/H0Xy2s0ULdRSdZUfvk9fu5LZtU47CQ4+5uINyCZ4nyP8/rHtwPS6X80oNMwdXXn01T00JSExjajBUXyick= X-Received: by 2002:ab0:5b59:: with SMTP id v25mr9617361uae.57.1633390270728; Mon, 04 Oct 2021 16:31:10 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> In-Reply-To: <20211004195010.earbegnpot3xr4ok@bitfolk.com> From: TMC Date: Tue, 5 Oct 2021 10:30:59 +1100 Message-ID: Subject: Re: iptables support for Debian 11 PV domu's To: Andy Smith Cc: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000ddd00805cd8f4e7e" --000000000000ddd00805cd8f4e7e Content-Type: text/plain; charset="UTF-8" Debian 12? On Tue, 5 Oct 2021 at 06:51, Andy Smith wrote: > Hi Chris, > > On Sun, Oct 03, 2021 at 07:08:10PM -0500, Chris Myers wrote: > is there a way to get the regular iptables-nft stuff to work in a > > Debian 11 pv domu, > > I've not had any issues using iptables, with nft or legacy, in > Debian 11 or Debian 12 PV domU, so I think your problem is strictly > related to the kernel you are using. > > Can you confirm whether your domU kernel and its modules are ones > that come from the linux-image-amd64 package that comes with Debian > 11? > > Cheers, > Andy > > -- -- GPG key fingerprint: 07DF B95B DB58 57B6 9656 682E 830A D092 288E F017 GPG public key available on pgp(dot)net key server --000000000000ddd00805cd8f4e7e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Debian 12?

On Tue, 5 Oct 2021 at 06:51, And= y Smith <andy@strugglers.net&= gt; wrote:
Hi Ch= ris,

On Sun, Oct 03, 2021 at 07:08:10PM -0500, Chris Myers wrote:
is there a way to get the regular iptables-nft stuff to work in a
> Debian 11 pv domu,

I've not had any issues using iptables, with nft or legacy, in
Debian 11 or Debian 12 PV domU, so I think your problem is strictly
related to the kernel you are using.

Can you confirm whether your domU kernel and its modules are ones
that come from the linux-image-amd64 package that comes with Debian
11?

Cheers,
Andy



--
--
GPG key fingerprint: 07DF= B95B DB58 57B6 9656=C2=A0 682E 830A D092 288E F017
GPG public ke= y available on pgp(dot)net key server
--000000000000ddd00805cd8f4e7e-- From xen-users-bounces@lists.xenproject.org Tue Oct 05 00:18:29 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 00:18:29 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201803.356427 (Exim 4.92) (envelope-from ) id 1mXY9M-0003A7-0j; Tue, 05 Oct 2021 00:17:40 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201803.356427; Tue, 05 Oct 2021 00:17:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXY9L-00039z-TW; Tue, 05 Oct 2021 00:17:39 +0000 Received: by outflank-mailman (input) for mailman id 201803; Tue, 05 Oct 2021 00:17:39 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXY9K-00039t-Uf for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 00:17:39 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 8d6aea67-bc39-412c-a702-571ed0a5c310; Tue, 05 Oct 2021 00:17:37 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mXY9I-0003YW-FR for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 00:17:36 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 8d6aea67-bc39-412c-a702-571ed0a5c310 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=JNnzxlP08nQcHnGkTf28sM+7RP+iQ0/rmxA6Bg4HGLo=; b=LXTWfzWTPAbEO82ye4Bs6OJ+Fq IoOL5dF/Qntul4uUr/3vovcKuXc7Ko2sz6SzTyVyjz71XuLHXMLPyQ6zfqGEXuNZHT+43dOs0WDHu HHBbx9ESgsygbSmv9XJKaq/vLaykJrxu3jslk3BkAz0ECWGxLUqROO0clzBbvzbxMiN0t7zmxRZbn klSPYDabDhOpg1Wtg9xSn4J/Onurx5AogwoHM0mxf6JBVnMtb9ngHcf+mjjqEuNmMa2tqngjV8gzn BV0ZPvGmbCgE77xyZNk1REka1oM9jaop/v5rzZlS5ZLYaS88TDl8m1k9cLpDb7vVPuFrST7pU0nwo gwt7JHOQ==; Date: Tue, 5 Oct 2021 00:17:36 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: iptables support for Debian 11 PV domu's Message-ID: <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Hello, On Tue, Oct 05, 2021 at 10:30:59AM +1100, TMC wrote: > Debian 12? Okay, so what will be Debian 12 when it's released - the current testing distribution, bookworm. It currently has a 5.14.x kernel, as opposed to 11's (bullseye's) 5.10.x. Cheers, Andy From xen-users-bounces@lists.xenproject.org Tue Oct 05 01:12:52 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 01:12:52 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201870.356516 (Exim 4.92) (envelope-from ) id 1mXZ01-0002UN-Ry; Tue, 05 Oct 2021 01:12:05 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201870.356516; Tue, 05 Oct 2021 01:12:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZ01-0002UG-O4; Tue, 05 Oct 2021 01:12:05 +0000 Received: by outflank-mailman (input) for mailman id 201870; Tue, 05 Oct 2021 01:12:04 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZ00-0002U6-OH for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 01:12:04 +0000 Received: from mail-vk1-xa29.google.com (unknown [2607:f8b0:4864:20::a29]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id ee4b7836-f01f-48e6-a6cb-8b0bc9e07c3f; Tue, 05 Oct 2021 01:12:03 +0000 (UTC) Received: by mail-vk1-xa29.google.com with SMTP id t200so8587722vkt.0 for ; Mon, 04 Oct 2021 18:12:03 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: ee4b7836-f01f-48e6-a6cb-8b0bc9e07c3f DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=alLCclhREkFSYyfYU2xmPwY2X66ZmSFMlJu7noB5wOY=; b=PhjPmaVOjwYVz4ezaVvLlPyjsJIvexXzBFievWP4X0WSi7h2Ua7u+rDcwFCW8+WbKw +zghVBUVO38jucBmRXlMINiC6Rm7b0wXupVCMxKvzcY9NnW4rWkH/0Auw0W+u1XkRkDD J+uhlHPwvqC5VtuaMtar9dQ6EuVV/lAAyW4gHZ/CD+aNUMctzG/S4xzjTuaeLeL4ltZb cSPnTksGB8gCkqk932S3FzIDxR7Gc/CHUkYn3eBoe5ee8+uxVkoVxBEd2U7z75U5jV+i O1lHCVMJxJJB3+YWPuFCINriaD1eBs8geXTvaGCivI0mhs563Ckv51oygsK7dbX22zuK hrVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=alLCclhREkFSYyfYU2xmPwY2X66ZmSFMlJu7noB5wOY=; b=8FFYfWdy8qtPTVtEYBwEdKJTZX1LuO4kBv8qk3eclPGMgQBV7p5wioxu/QBNBXQOu+ tXN+5uy4RxLulGLAw3jTg2ID0GnkIJeC0MazgJFbx8qtCVBcfGYNgs11AJzq0YxABjyT eDjy+egbulIRDAcxtBgWZRSVFlVBvuO++7IPWnyYLJ6mMRIAgxfAIUO36EF/aWwyxpWv E+1BJaRz5nFuXQiQEk90E1yFmz00WDbpOZs8EkkInKOBm5sxg/A4iG4J++yK41khwsdQ 1uHD+VlnqdeBnp2HX5EYod2zKChkBkci1vIkS5LouzgP+cRkXGlse9L6UkqfqELAj30p 6dEQ== X-Gm-Message-State: AOAM531I39p+nzzI9ESI8Irp3vVLW28MtjcZfhG9uC94MLWo35q2rIIW R6/G4OPrttB77vuJyaziQFWsCEbNHRIX+tUSdbWaxSx4igc= X-Google-Smtp-Source: ABdhPJxshv6/jyLyC3zDurqoueocgQp+Y5xhqdySZJ8LaDjsFBZfquDnJOKwMkUHzklp4F6DgzokOBwz8lhuI4tzgQ4= X-Received: by 2002:ac5:cbcf:: with SMTP id h15mr18963204vkn.0.1633396323266; Mon, 04 Oct 2021 18:12:03 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> In-Reply-To: <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> From: Chris Myers Date: Mon, 4 Oct 2021 20:11:52 -0500 Message-ID: Subject: Re: iptables support for Debian 11 PV domu's To: Andy Smith Cc: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000a0347d05cd90b7b5" --000000000000a0347d05cd90b7b5 Content-Type: text/plain; charset="UTF-8" Forgot to do reply all ... with some additional details at the bottom. Thanks for all the replies! I re-upgraded one of the VMs that I had to revert last night, and tonight it's working, no errors. Exact same commands -- - Make sure all Deb10 patches installed - apt clean - Flip sources.list - apt update - apt upgrade --without-new-pkgs - apt full-upgrade - reboot I realized what's different though. Last night I also changed what kernel I was using on the guest. I flipped my vmname.cfg from [...] kernel = '/boot/vmlinuz-5.10.0-8-amd64' ramdisk = '/boot/initrd.img-5.10.0-8-amd64' [...] (the kernel version that came with Debian 11) back to the 4.19.0-16-amd64 that was with Debian 10. Is it possible that the 5.10.0-8-amd64 that comes with Debian 11 isn't all the way there? I can confirm that the linux-image-amd64 is the one that came as a part of doing the in-place upgrade. I don't mess with custom kernels etc., just the ones that come straight from apt's wisdom. From the perspective of the dom0 :: # uname -a Linux vhost 5.10.0-8-amd64 #1 SMP Debian 5.10.46-5 (2021-09-23) x86_64 GNU/Linux # apt list --installed | grep linux-image-amd64 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-image-amd64/stable-security,now 5.10.46-5 amd64 [installed] # md5sum ./var/cache/apt/archives/linux-image-amd64_5.10.46-5_amd64.deb 9e4185453765f40a69e248925ed0366f ./var/cache/apt/archives/linux-image-amd64_5.10.46-5_amd64.deb /lib/modules# ls 4.19.0-13-amd64 4.19.0-16-amd64 4.19.0-17-amd64 5.10.0-8-amd64 On Mon, Oct 4, 2021 at 7:18 PM Andy Smith wrote: > Hello, > > On Tue, Oct 05, 2021 at 10:30:59AM +1100, TMC wrote: > > Debian 12? > > Okay, so what will be Debian 12 when it's released - the current > testing distribution, bookworm. It currently has a 5.14.x kernel, as > opposed to 11's (bullseye's) 5.10.x. > > Cheers, > Andy > > -- People use duct tape to fix everything....God used nails. http://www.myerscountry.net --000000000000a0347d05cd90b7b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Forgot to do reply all ... with some= additional details at the bottom.

Thanks= for all the replies!

I re-upgraded one of the VMs= that I had to revert=20 last night, and tonight it's working, no errors. Exact same commands --=
=C2=A0- Make sure all Deb10 patches installed
=C2=A0- = apt clean
=C2=A0- Flip sources.list
=C2=A0- apt update<= /div>
=C2=A0- apt upgrade --without-new-pkgs
=C2=A0- apt full= -upgrade
=C2=A0- reboot

I realized what&#= 39;s different though. Last night I also changed what kernel I was using on= the guest. I flipped my vmname.cfg from
[...]
kerne= l =C2=A0 =C2=A0 =C2=A0=3D '/boot/vmlinuz-5.10.0-8-amd64'
ramdisk= =C2=A0 =C2=A0 =3D '/boot/initrd.img-5.10.0-8-amd64'
[...= ]
(the kernel version that came with Debian 11)
back to= the 4.19.0-16-amd64 that was with Debian 10.

= Is it possible that the 5.10.0-8-amd64 that comes with Debian 11 isn't = all the way there? I can confirm that the linux-image-amd64 is the one that= came as a part of doing the in-place upgrade. I don't mess with custom= kernels etc., just the ones that come straight from apt's wisdom. From= the perspective of the dom0 ::

# uname -a
Linux vhost 5.10.0-8-amd64 #1 SMP Debian 5.10.46= -5 (2021-09-23) x86_64 GNU/Linux
<= br>
# apt list --installed | grep linu= x-image-amd64

WARNING: apt does not have a stable CLI interface. Use= with caution in scripts.

linux-image-amd64/stable-security,now 5.10= .46-5 amd64 [installed]

# md5sum ./var/cache/apt/archives/linux-image-a= md64_5.10.46-5_amd64.deb
9e4185453765f40a69e248925ed0366f =C2=A0./var/ca= che/apt/archives/linux-image-amd64_5.10.46-5_amd64.deb


/lib/modules# ls
4.19.0-13-amd64 =C2=A04.19.0-= 16-amd64 =C2=A04.19.0-17-amd64 =C2=A05.10.0-8-amd64






On Mon, Oct = 4, 2021 at 7:18 PM Andy Smith <andy@strugglers.net> wrote:
Hello,

On Tue, Oct 05, 2021 at 10:30:59AM +1100, TMC wrote:
> Debian 12?

Okay, so what will be Debian 12 when it's released - the current
testing distribution, bookworm. It currently has a 5.14.x kernel, as
opposed to 11's (bullseye's) 5.10.x.

Cheers,
Andy



--
People use= duct tape to fix everything....God used nails.

http://www.myerscountry.net
= --000000000000a0347d05cd90b7b5-- From xen-users-bounces@lists.xenproject.org Tue Oct 05 01:28:36 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 01:28:36 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201909.356555 (Exim 4.92) (envelope-from ) id 1mXZFj-0005nX-0s; Tue, 05 Oct 2021 01:28:19 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201909.356555; Tue, 05 Oct 2021 01:28:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZFi-0005nP-Tt; Tue, 05 Oct 2021 01:28:18 +0000 Received: by outflank-mailman (input) for mailman id 201909; Tue, 05 Oct 2021 01:28:17 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZFh-0005nJ-8o for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 01:28:17 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 79de64e0-6b59-495a-9643-7c72f459701c; Tue, 05 Oct 2021 01:28:15 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mXZFe-0006T7-Ku for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 01:28:14 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 79de64e0-6b59-495a-9643-7c72f459701c DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=nKASGNoeybbM3MECzJ7K6Td/6fN4GXmHueAV1egyt+I=; b=NqMCjDLFPoJ0hi1oUaK5Yv6Fbn zIW3CIU1Lyi86EzzyVb6bW8aR1eFNzUP5PYR1gvj+q7oWEVxWRwQc/Upg1minhgtUTe1iSpzuNbcR +rz/RLtX9Co5lsoma0v4rK+1Tfa66TZ3PHvNuZpU2kIbTWd2ZVcMiiduGPi8z7ETcXQoAdFuDFN+K /pLTFNDXM0wAevjvE9C4idGlS33F3/rKmO6bZbmdDxUaMlcKwbeZbr2HqUh6561xiCrr3zbJvAuh1 yR1Kg8sBtECodWjWkYBXC/MNBpljobDcsn1Amt5DM5KYslsXKxHHjYP0xDByUSEUNiZ7OZ/+ZbadB iNvsInQQ==; Date: Tue, 5 Oct 2021 01:28:14 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: iptables support for Debian 11 PV domu's Message-ID: <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Hello, On Mon, Oct 04, 2021 at 08:11:52PM -0500, Chris Myers wrote: > I re-upgraded one of the VMs that I had to revert last night, and tonight > it's working, no errors. Exact same commands -- > - Make sure all Deb10 patches installed > - apt clean > - Flip sources.list When you do this step do you make sure to get the new format "bullseye-security/updates" line correct? Because without that, you end up with linux-image-5.10.0-8-amd64 version 5.10.46-4, not version 5.10.46-5. > I flipped my vmname.cfg from > [...] > kernel = '/boot/vmlinuz-5.10.0-8-amd64' > ramdisk = '/boot/initrd.img-5.10.0-8-amd64' > [...] > (the kernel version that came with Debian 11) > back to the 4.19.0-16-amd64 that was with Debian 10. > > Is it possible that the 5.10.0-8-amd64 that comes with Debian 11 isn't all > the way there? It works for me on 14 different domUs at present, so I'd say not likely. > I can confirm that the linux-image-amd64 is the one that > came as a part of doing the in-place upgrade. I don't mess with custom > kernels etc., just the ones that come straight from apt's wisdom. The way you are booting these domains though inherently requires synchronisation between the domU's config file in dom0 (that says which kernel+initramfs to use) and the /lib/modules directory in the domU. Easy to make a mistake. So are you sure that you haven't mismatched something there? Once you've got to the bottom of this I recommend switching to pvhgrub booting to do away with that class of problems… > From the perspective of the dom0 :: […] > /lib/modules# ls > 4.19.0-13-amd64 4.19.0-16-amd64 4.19.0-17-amd64 5.10.0-8-amd64 …and the domU in question has that same /lib/modules/5.10.0-8-amd64 directory tree from dom0? Cheers, Andy From xen-users-bounces@lists.xenproject.org Tue Oct 05 01:36:00 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 01:36:00 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201929.356574 (Exim 4.92) (envelope-from ) id 1mXZMz-0007gf-UE; Tue, 05 Oct 2021 01:35:49 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201929.356574; Tue, 05 Oct 2021 01:35:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZMz-0007gY-QL; Tue, 05 Oct 2021 01:35:49 +0000 Received: by outflank-mailman (input) for mailman id 201929; Tue, 05 Oct 2021 01:35:48 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZMx-0007gR-Po for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 01:35:47 +0000 Received: from mail-vk1-xa30.google.com (unknown [2607:f8b0:4864:20::a30]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id cee7f9f5-7f84-4bc8-8cda-4bb3f029ce8b; Tue, 05 Oct 2021 01:35:46 +0000 (UTC) Received: by mail-vk1-xa30.google.com with SMTP id x207so8599384vke.2 for ; Mon, 04 Oct 2021 18:35:46 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: cee7f9f5-7f84-4bc8-8cda-4bb3f029ce8b DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=H5P6p1lp1sAO1sRPB697a+XeL7i/TSTb59jEZUL+pxI=; b=EDNauNvyH8Kjxd/mbHgL9/WgDTuh0p5oBakJ0IZ7cYU6+cESgoJKKOAHmzhrK6CJVf EP6WUzOBbR8BDjKrHbfwq7GjVEJzOrs23jZrmM6Oo0Kej438IIUD/YVE6IMfX4LvH47g RqkPv1917tPjMYAHLrlJOSlReQbnqkSnyitNF8Z8OKBJB/EO9g+NMjuYtZ6eb6R9fAgk GJyS9Nj9u+j3q+NXGDY8/t0tw/SenNBfXOgvoQ3A6rKWHwIYCgqf+bMvgf0C4nMxL85i tM6WGsvmXYCzWc5HBXz2EzuCFPc5iPO9zdkgiukrWNWISsDkM302poxnnxMRHuy9GiYn vCXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=H5P6p1lp1sAO1sRPB697a+XeL7i/TSTb59jEZUL+pxI=; b=wM0lYzE7jBL0PYORqXt1r1wTAf+csLuW0VV5CEHn/Cbxh1LAPi9SQjSsjFlNCksSuP U3PnyCtOF4+zWIngTp0HC3KLLOC+jEFL1cTZLdkEvPDuBlrhXz0K7lwQKTHJRO2uZuHJ aEzvhl9f+mawjWQ6aEzPZqqWZrncQOC/3TV1YU+SD6+laOrLxJecX6kWTMQH2agSO2XJ hgUVqCj5+SbwYbN6ItD6SY7+ppNv+gfQ2qa/hSyPzduHvKmX9d4fKje/D3hlx+ydev+f CyB0w9OWVXapmjHneZgtZLvZPJ7RNJMBF2MBZhNIBhrPQAr73EzQKjeeo6edBQRAfobT 1s5w== X-Gm-Message-State: AOAM533jCuE9JtjIhhh9oxIdUbjldJuXuGOCMD2QcYiaNbXCphgA+RuP t3LeYURog+l42CO0/kR+MF4P2nBa/2w6CyAS8Ho= X-Google-Smtp-Source: ABdhPJyXTzqhe1YEHTnapcTe9HRh4lwmC3RC9mz0anaDX2q8IWiVhXzX6LeE2bPV7XCt2DtIXs7OxdkYWqi0kHYt8Ws= X-Received: by 2002:a1f:1609:: with SMTP id 9mr18560017vkw.10.1633397746292; Mon, 04 Oct 2021 18:35:46 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> In-Reply-To: <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> From: Chris Myers Date: Mon, 4 Oct 2021 20:35:35 -0500 Message-ID: Subject: Re: iptables support for Debian 11 PV domu's To: Andy Smith Cc: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="00000000000071ddc505cd910c11" --00000000000071ddc505cd910c11 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le sigh that would be it...I feel like a doofus now. I'd totally forgotten to do that after the upgrade ... I'm surprised the silly things booted at all. Out of curiosity is there a better/preferred way of handling it so that I don't need to remember to keep them in sync every time I do a kernel upgrade? On Mon, Oct 4, 2021 at 8:28 PM Andy Smith wrote: > Hello, > > On Mon, Oct 04, 2021 at 08:11:52PM -0500, Chris Myers wrote: > > I re-upgraded one of the VMs that I had to revert last night, and tonig= ht > > it's working, no errors. Exact same commands -- > > - Make sure all Deb10 patches installed > > - apt clean > > - Flip sources.list > > When you do this step do you make sure to get the new format > "bullseye-security/updates" line correct? Because without that, you > end up with linux-image-5.10.0-8-amd64 version 5.10.46-4, not version > 5.10.46-5. > > > I flipped my vmname.cfg from > > [...] > > kernel =3D '/boot/vmlinuz-5.10.0-8-amd64' > > ramdisk =3D '/boot/initrd.img-5.10.0-8-amd64' > > [...] > > (the kernel version that came with Debian 11) > > back to the 4.19.0-16-amd64 that was with Debian 10. > > > > Is it possible that the 5.10.0-8-amd64 that comes with Debian 11 isn't > all > > the way there? > > It works for me on 14 different domUs at present, so I'd say not > likely. > > > I can confirm that the linux-image-amd64 is the one that > > came as a part of doing the in-place upgrade. I don't mess with custom > > kernels etc., just the ones that come straight from apt's wisdom. > > The way you are booting these domains though inherently requires > synchronisation between the domU's config file in dom0 (that says > which kernel+initramfs to use) and the /lib/modules directory in the > domU. Easy to make a mistake. > > So are you sure that you haven't mismatched something there? > > Once you've got to the bottom of this I recommend switching to > pvhgrub booting to do away with that class of problems=E2=80=A6 > > > From the perspective of the dom0 :: > > [=E2=80=A6] > > > /lib/modules# ls > > 4.19.0-13-amd64 4.19.0-16-amd64 4.19.0-17-amd64 5.10.0-8-amd64 > > =E2=80=A6and the domU in question has that same /lib/modules/5.10.0-8-amd= 64 > directory tree from dom0? > > Cheers, > Andy > > --=20 People use duct tape to fix everything....God used nails. http://www.myerscountry.net --00000000000071ddc505cd910c11 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Le sigh that would be it...I feel like a doofus now. = I'd totally forgotten to do that after the upgrade ... I'm surprise= d the silly things booted at all.

Out of curiosity= is there a better/preferred way of handling it so that I don't need to= remember to keep them in sync every time I do a kernel upgrade?
<= /div>
O= n Mon, Oct 4, 2021 at 8:28 PM Andy Smith <andy@strugglers.net> wrote:
Hello,

On Mon, Oct 04, 2021 at 08:11:52PM -0500, Chris Myers wrote:
> I re-upgraded one of the VMs that I had to revert last night, and toni= ght
> it's working, no errors. Exact same commands --
>=C2=A0 - Make sure all Deb10 patches installed
>=C2=A0 - apt clean
>=C2=A0 - Flip sources.list

When you do this step do you make sure to get the new format
"bullseye-security/updates" line correct? Because without that, y= ou
end up with linux-image-5.10.0-8-amd64 version 5.10.46-4, not version
5.10.46-5.

> I flipped my vmname.cfg from
> [...]
> kernel=C2=A0 =C2=A0 =C2=A0 =3D '/boot/vmlinuz-5.10.0-8-amd64'<= br> > ramdisk=C2=A0 =C2=A0 =C2=A0=3D '/boot/initrd.img-5.10.0-8-amd64= 9;
> [...]
> (the kernel version that came with Debian 11)
> back to the 4.19.0-16-amd64 that was with Debian 10.
>
> Is it possible that the 5.10.0-8-amd64 that comes with Debian 11 isn&#= 39;t all
> the way there?

It works for me on 14 different domUs at present, so I'd say not
likely.

> I can confirm that the linux-image-amd64 is the one that
> came as a part of doing the in-place upgrade. I don't mess with cu= stom
> kernels etc., just the ones that come straight from apt's wisdom.<= br>
The way you are booting these domains though inherently requires
synchronisation between the domU's config file in dom0 (that says
which kernel+initramfs to use) and the /lib/modules directory in the
domU. Easy to make a mistake.

So are you sure that you haven't mismatched something there?

Once you've got to the bottom of this I recommend switching to
pvhgrub booting to do away with that class of problems=E2=80=A6

> From the perspective of the dom0 ::

[=E2=80=A6]

> /lib/modules# ls
> 4.19.0-13-amd64=C2=A0 4.19.0-16-amd64=C2=A0 4.19.0-17-amd64=C2=A0 5.10= .0-8-amd64

=E2=80=A6and the domU in question has that same /lib/modules/5.10.0-8-amd64=
directory tree from dom0?

Cheers,
Andy



--
People use duct tape to fix everything....God used nails.
http://www.= myerscountry.net
--00000000000071ddc505cd910c11-- From xen-users-bounces@lists.xenproject.org Tue Oct 05 01:38:52 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 01:38:52 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201946.356592 (Exim 4.92) (envelope-from ) id 1mXZPk-0000MN-HZ; Tue, 05 Oct 2021 01:38:40 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201946.356592; Tue, 05 Oct 2021 01:38:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZPk-0000MD-E6; Tue, 05 Oct 2021 01:38:40 +0000 Received: by outflank-mailman (input) for mailman id 201946; Tue, 05 Oct 2021 01:38:39 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZPj-0000M0-1Y for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 01:38:39 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id ae902744-74e5-4551-843b-3cb863fdabf4; Tue, 05 Oct 2021 01:38:38 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mXZPh-0006qK-9a for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 01:38:37 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: ae902744-74e5-4551-843b-3cb863fdabf4 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=e/9K6T2DuIsAusufxfFaQiwfGBj2ReFhaffmQkn+N4Y=; b=ivFp9DxKFbMALGozPs8AC14B6v m45MugAVCsFO2T/1rWH3+jZqZQX/0Ynz7dR3nHgYNK05NMtonb9EHCZb4nYo3WjNkCZ/Qz26Ld+/1 TcKvyi5asIjn8Z9pkaKblDMX4jkGo0pSm8VttFfxLXPnqjN2NCs5Uv36iuFha9kWLKK2KTTCajaVX 7HTFfaDoK0z3JVdyDOE3rbmKwm6uR/UZqQQg61ib8v27/PlfTZnQqSXMhZnNZBdlDzqCcDZzGcAdo jr7Y770CjKkBL0GCjhwicHIUmdSh+2qef93VfYeo7B999qNKlYQa0hehs33JQY8ADF8dIYan3kfFH nizvtg+g==; Date: Tue, 5 Oct 2021 01:38:37 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: iptables support for Debian 11 PV domu's Message-ID: <20211005013837.ka625tea5kd4h2qo@bitfolk.com> References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false On Mon, Oct 04, 2021 at 08:35:35PM -0500, Chris Myers wrote: > Out of curiosity is there a better/preferred way of handling it so that I > don't need to remember to keep them in sync every time I do a kernel > upgrade? > > Once you've got to the bottom of this I recommend switching to > > pvhgrub booting to do away with that class of problems… From xen-users-bounces@lists.xenproject.org Tue Oct 05 02:10:30 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 02:10:30 +0000 Received: from list by lists.xenproject.org with outflank-mailman.201968.356610 (Exim 4.92) (envelope-from ) id 1mXZuE-0005Pz-4h; Tue, 05 Oct 2021 02:10:10 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 201968.356610; Tue, 05 Oct 2021 02:10:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZuE-0005Pr-1K; Tue, 05 Oct 2021 02:10:10 +0000 Received: by outflank-mailman (input) for mailman id 201968; Tue, 05 Oct 2021 02:10:08 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXZuC-0005Pk-Ou for xen-users@lists.xenproject.org; Tue, 05 Oct 2021 02:10:08 +0000 Received: from mail-vk1-xa2d.google.com (unknown [2607:f8b0:4864:20::a2d]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id feaa1a8e-131c-46c6-823c-a8467f2f050b; Tue, 05 Oct 2021 02:10:07 +0000 (UTC) Received: by mail-vk1-xa2d.google.com with SMTP id w68so8606519vkd.7 for ; Mon, 04 Oct 2021 19:10:07 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: feaa1a8e-131c-46c6-823c-a8467f2f050b DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M5kJ0S9LJMC0FET6iAkC8+gbGZhkS7AtjHOSLAEknmQ=; b=ZgYKCS7uROKPdgOaajCFlGQJIPXUIDllAlD5d2y8TgmDFIeOLd7LMNy46PloNzb5AI lqQ8X0Wx3YdtLUXr2Pdk619Wfr1R0daCs/dqUYxA68k9V9S6XfBy+Q/wer6Xe2WmRxxb DlABd64KIyu/QQoVvo9wLZjar9/faBkAVXD1Vhjsa1hDP7MNH+c/f3MpWChuzJSP53lY P+MvLQQjd8c7rB23EaOCuPTUNKi+lBhnpymJsCl2t7oC/yDbD8k22/9YkAe7j5yrE0Tl NhHwBhMo9m081v97Dl96wO3ebmpBbQ/gXQqC0hbtdVFf15BH3REO8teEuUAD8LjzNK0t PZHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M5kJ0S9LJMC0FET6iAkC8+gbGZhkS7AtjHOSLAEknmQ=; b=CB5vydONngYHkW0Ee0FnY+43a0IBv0ib/NaccGI5nWDtFvYdWS8MveYz/OzsqraZTQ OODEl+lz5OZUOQHIA6u6J49xQ2iaSLupZtNgsxhLJYVXl/p7WS6AHAVDNvCSI4nvVJR9 7fkao+//oN9Hnvtv5yulMtI4T0IMm/4kqGJl859DgrcSBY0DBshgFjNqfajB2I2+BH5b SeStCCb6V+apwaLv3lpH/BPML+BVtwyjijNm+UOasnjel//81WbHTTw3pt9zvFUm7LwY KiWWL5LZbAMYCebKnk9TZaB5aDSI5LaH+SyECjeAnZ/NS1gKl55HTLkTJCs+2fpy8185 3S5g== X-Gm-Message-State: AOAM532ir4fzPQoZ+Qt6vlf+AOy8fxR3lF107kHFjHzGQgVzD9G+bPbD WfaxOSUf6GOCubV+MkXBRGbmlRLREuBgK8sxNdI+BJFF X-Google-Smtp-Source: ABdhPJxvu+6PLeCRI66ng9AnD1F+EfgMwCwV/FV/WT9zoOh/zaCWuN8azJyjiq0TtrqW+X9/hO4U3zNTF3dII+9MsF0= X-Received: by 2002:a1f:1bc6:: with SMTP id b189mr18508895vkb.15.1633399807429; Mon, 04 Oct 2021 19:10:07 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> In-Reply-To: <20211005013837.ka625tea5kd4h2qo@bitfolk.com> From: Chris Myers Date: Mon, 4 Oct 2021 21:09:56 -0500 Message-ID: Subject: Re: iptables support for Debian 11 PV domu's To: Andy Smith Cc: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="0000000000004c4e2105cd918799" --0000000000004c4e2105cd918799 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks! I'll check that out. Up to this point I've always just done in-place upgrades of everything (been running Xen PV domu's for about 7 years now) and have just followed with that old way because it generally just worked (with a few nuances.) On Mon, Oct 4, 2021 at 8:38 PM Andy Smith wrote: > On Mon, Oct 04, 2021 at 08:35:35PM -0500, Chris Myers wrote: > > Out of curiosity is there a better/preferred way of handling it so that= I > > don't need to remember to keep them in sync every time I do a kernel > > upgrade? > > > > Once you've got to the bottom of this I recommend switching to > > > pvhgrub booting to do away with that class of problems=E2=80=A6 > > --=20 People use duct tape to fix everything....God used nails. http://www.myerscountry.net --0000000000004c4e2105cd918799 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks! I'll check that out.

=
Up to this point I've always just done in-place upgrades of everyt= hing (been running Xen PV domu's for about 7 years now) and have just f= ollowed with that old way because it generally just worked (with a few nuan= ces.)

On Mon, Oct 4, 2021 at 8:38 PM Andy Smith <andy@strugglers.net> wrote:
On Mon, Oct 04, 2021 at 08:35:= 35PM -0500, Chris Myers wrote:
> Out of curiosity is there a better/preferred way of handling it so tha= t I
> don't need to remember to keep them in sync every time I do a kern= el
> upgrade?

> > Once you've got to the bottom of this I recommend switching t= o
> > pvhgrub booting to do away with that class of problems=E2=80=A6


--
People use duct tape to fix everything....God used nails.
http://www.= myerscountry.net
--0000000000004c4e2105cd918799-- From xen-users-bounces@lists.xenproject.org Tue Oct 05 18:43:59 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 05 Oct 2021 18:43:59 +0000 Received: from list by lists.xenproject.org with outflank-mailman.202308.357028 (Exim 4.92) (envelope-from ) id 1mXpPM-0007t3-3G; Tue, 05 Oct 2021 18:43:20 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 202308.357028; Tue, 05 Oct 2021 18:43:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXpPL-0007sv-VC; Tue, 05 Oct 2021 18:43:19 +0000 Received: by outflank-mailman (input) for mailman id 202308; Tue, 05 Oct 2021 18:43:18 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXpPK-0007sp-7h for xen-users@lists.xen.org; Tue, 05 Oct 2021 18:43:18 +0000 Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id c7faa338-6ff0-4ce1-8566-34655533685a; Tue, 05 Oct 2021 18:43:16 +0000 (UTC) Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mXpPC-0001na-3a; Tue, 05 Oct 2021 18:43:10 +0000 Received: from iwj by xenbits.xenproject.org with local (Exim 4.92) (envelope-from ) id 1mXpPC-0006vg-20; Tue, 05 Oct 2021 18:43:10 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: c7faa338-6ff0-4ce1-8566-34655533685a DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Date:Message-Id:Subject:CC:From:To:MIME-Version: Content-Transfer-Encoding:Content-Type; bh=tfi/3QwQXxxrSN8ZOEpf0N6gSqkc9mlvL65nLRNcV9Y=; b=4Xv/9z2YWtWV1lA5qeAWpVtPNQ 5K6Zq8UEV8nWtHoISUY5o5Ad0avsVPp+/zKMOwnrN7aQ4pK7yN3USz9sHwwLr0yC/NRBt04PfNNMQ oxh5eJlwbfCP2baa4EEHoPfnd9pJzxkofsK1zRuc03Pog9Vc1IdaTRHgjcgCN+40Y4iw=; Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team CC: Xen.org security team Subject: Xen Security Advisory 386 v1 (CVE-2021-28702) - PCI devices with RMRRs not deassigned correctly Message-Id: Date: Tue, 05 Oct 2021 18:43:10 +0000 --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Xen Security Advisory CVE-2021-28702 / XSA-386 PCI devices with RMRRs not deassigned correctly ISSUE DESCRIPTION ================= Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR"). These are typically used for platform tasks such as legacy USB emulation. If such a device is passed through to a guest, then on guest shutdown the device is not properly deassigned. The IOMMU configuration for these devices which are not properly deassigned ends up pointing to a freed data structure, including the IO Pagetables. Subsequent DMA or interrupts from the device will have unpredictable behaviour, ranging from IOMMU faults to memory corruption. IMPACT ====== Administrators of guests which have been assigned RMRR-using PCI devices can cause denial of service and other problems, possibly including escalation of privilege. VULNERABLE SYSTEMS ================== All versions of Xen from at least 4.4 onwards are vulnerable. Only Intel x86 systems are affected. AMD x86 systems, and Arm systems, are all unaffected. Only systems using PCI passthrough are affected. (And then, only if the assigned devices have RMRRs, but whether a device advertises RMRRs is not easy to discern.) MITIGATION ========== There is no mitigation (other than not passing through PCI devices with RMRRs to guests). RESOLUTION ========== Applying the appropriate attached patch resolves this issue. Note that patches for released versions are generally prepared to apply to the stable branches, and may not apply cleanly to the most recent release tarball. Downstreams are encouraged to update to the tip of the stable branch before applying these patches. xsa386.patch xen-unstable - Xen 4.12.x $ sha256sum xsa386* f2f83c825e249bba9454437b48bbd8307fe7a224f56484388a67af124dfd279b xsa386.patch $ NOTE CONCERNING LACK OF EMBARGO =============================== This issue was reported and debugged in public before the security nature became apparent. -----BEGIN PGP SIGNATURE----- iQFABAEBCAAqFiEEI+MiLBRfRHX6gGCng/4UyVfoK9kFAmFcnH8MHHBncEB4ZW4u b3JnAAoJEIP+FMlX6CvZje0H+QE5A0ZvoaJ5VupZYjAt5ynbQjVqxwxqAxZDTvP7 t3gtpsHSYgrHW+3giULxjGU0ZUGF9daO1JEIZCPCbUdIlmGqGEXdDoqtz0GrXCJJ swQFeXQVmn9lV4KMTHO0BvGw5aZOft1VgGNrixd3vckFl7c5G8sWFdl7IU7FPDTQ LiLMg6f1oOntBYjNZUZ2210jqct9GZ4ugURRufwZrwYIpc9H5pFnZAFHKismX/2m x/PCdmOCeivytmUPA4k62oJVpJdysAL+31XkZz8bbAhjFsUmYBJscW2T5mSfaYIp TaSrg9WBV+TVW7aNE2iittE2O0/YyOWfpUVh6lliECeFdd0= =aNEo -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa386.patch" Content-Disposition: attachment; filename="xsa386.patch" Content-Transfer-Encoding: base64 RnJvbTogSmFuIEJldWxpY2ggPGpiZXVsaWNoQHN1c2UuY29tPgpTdWJqZWN0 OiBWVC1kOiBmaXggZGVhc3NpZ24gb2YgZGV2aWNlIHdpdGggUk1SUgpEYXRl OiBGcmksIDEgT2N0IDIwMjEgMTU6MDU6NDIgKzAyMDAKCklnbm9yaW5nIGEg c3BlY2lmaWMgZXJyb3IgY29kZSBoZXJlIHdhcyBub3QgbWVhbnQgdG8gc2hv cnQgY2lyY3VpdApkZWFzc2lnbiB0byBfanVzdF8gdGhlIHVubWFwcGluZyBv ZiBSTVJScy4gVGhpcyBidWcgd2FzIHByZXZpb3VzbHkKaGlkZGVuIGJ5IHRo ZSBib2d1cyAocG90ZW50aWFsbHkgaW5kZWZpbml0ZSkgbG9vcGluZyBpbgpw Y2lfcmVsZWFzZV9kZXZpY2VzKCksIHVudGlsIGY1OTE3NTU4MjNhNyAoIklP TU1VL1BDSTogZG9uJ3QgbGV0IGRvbWFpbgpjbGVhbnVwIGNvbnRpbnVlIHdo ZW4gZGV2aWNlIGRlLWFzc2lnbm1lbnQgZmFpbGVkIikgZml4ZWQgdGhhdCBs b29wLgoKVGhpcyBpcyBDVkUtMjAyMS0yODcwMiAvIFhTQS0zODYuCgpGaXhl czogOGI5OWY0NDAwYjY5ICgiVlQtZDogZml4IFJNUlIgcmVsYXRlZCBlcnJv ciBoYW5kbGluZyIpClJlcG9ydGVkLWJ5OiBJdmFuIEthcmR5a292IDxrYXJk eWtvdkB0YWJpdC5wcm8+ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxq YmV1bGljaEBzdXNlLmNvbT4KVGVzdGVkLWJ5OiBJdmFuIEthcmR5a292IDxr YXJkeWtvdkB0YWJpdC5wcm8+CgotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhy b3VnaC92dGQvaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3Vn aC92dGQvaW9tbXUuYwpAQCAtMjQwOSw3ICsyNDA5LDcgQEAgc3RhdGljIGlu dCByZWFzc2lnbl9kZXZpY2Vfb3duZXJzaGlwKAogICAgICAgICAgICAgICAg IHJldCA9IGlvbW11X2lkZW50aXR5X21hcHBpbmcoc291cmNlLCBwMm1fYWNj ZXNzX3gsCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICBybXJyLT5iYXNlX2FkZHJlc3MsCiAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBybXJyLT5lbmRfYWRkcmVz cywgMCk7Ci0gICAgICAgICAgICAgICAgaWYgKCByZXQgIT0gLUVOT0VOVCAp CisgICAgICAgICAgICAgICAgaWYgKCByZXQgJiYgcmV0ICE9IC1FTk9FTlQg KQogICAgICAgICAgICAgICAgICAgICByZXR1cm4gcmV0OwogICAgICAgICAg ICAgfQogICAgIH0KCg== --=separator-- From xen-users-bounces@lists.xenproject.org Thu Oct 07 12:10:38 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 12:10:38 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203506.358641 (Exim 4.92) (envelope-from ) id 1mYSDg-0001n0-BM; Thu, 07 Oct 2021 12:09:52 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203506.358641; Thu, 07 Oct 2021 12:09:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYSDg-0001ms-7u; Thu, 07 Oct 2021 12:09:52 +0000 Received: by outflank-mailman (input) for mailman id 203506; Thu, 07 Oct 2021 12:09:51 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYSDf-0001mm-CT for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 12:09:51 +0000 Received: from mail-vs1-xe2d.google.com (unknown [2607:f8b0:4864:20::e2d]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 683e10b3-518d-44a8-8c84-5bacb94a9870; Thu, 07 Oct 2021 12:09:50 +0000 (UTC) Received: by mail-vs1-xe2d.google.com with SMTP id x192so4254452vsx.5 for ; Thu, 07 Oct 2021 05:09:50 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 683e10b3-518d-44a8-8c84-5bacb94a9870 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:cc; bh=Xg5F4oVOkpxo9tebq0VVvmH99CH+gY9lSxftWUpN+3k=; b=NIayZaQaGRUFGNMZhDaTjzxX4NRxWcTM8wEr/4MsbhrJek4yGvtqgZpYOyQdhUzAAr PZLOp61gj3bE5DlsoIrBLTD/MfgtNNNSMI5T8UXVZUwLsv04NydKga9vgwJ8ai7zxMG7 C5k40+w4mWftJhk1tOqNuF236uJldlOMe6QDI5O33onkvbjXmjrI0pXWdSdj2/kI6mPH 1hL0sRM9AQ0V2Q3eQCPsK/AAIZfYInKjUAijYthrKBKVpX9x7Yqwi75BEmHKNwjrhmBR 2oDFlg26s70jn0DdcQ9heMsQx76r0sTvZzBeY47Coi1i/SzVnzK0s1oqaZ2pKa1lka8e 3JBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=Xg5F4oVOkpxo9tebq0VVvmH99CH+gY9lSxftWUpN+3k=; b=W72xOvAxFO6PJk2a1SJi9apd4qvZqpDaovNPVw18D0sI8V6ZEn/6+hUg1enoVmGoGS PJ4bxo4VNFwgaZosjgTd9CSjkC/zxgXdAwbk/Rxtazx/j2NnMnBJwzbEcj6zwGiVqAoc +b4XQT5ML7mZJJnKLVnS8hkvJWAFApAMzTbwbrE5lARPtHkStw96Lfdhmm+a9329bAm5 DOqsv1qU1bCgojU3xpddoYEUOlX8DxndJ7v7bUh2L56oNmb30POQZ1mv/DemfPugvCue xeKAUzcnbw8bG1Pqloe7JgrAI/bu+/+mdgudx9JhPDP9+B8emP8G52NYg4LDETCORCXx iytw== X-Gm-Message-State: AOAM531L85zyHcpSYyUNfnnFfRgtHqFFILkizmCYiBwa/67OEdQD+uYc 8tvy+Hg+y6ERRTDU6VnXl75UA84ykVEQF6fdms54k5ch X-Google-Smtp-Source: ABdhPJydbjDh2KnTdHjwbWombSKGpLjqYBvYDJK4qWUjp+AjLX8iY1Khb5pKcOE2Cd6ZhenSYqvRnJfI6Gh5BpOQyu4= X-Received: by 2002:a05:6102:389:: with SMTP id m9mr3323217vsq.34.1633608589480; Thu, 07 Oct 2021 05:09:49 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> In-Reply-To: From: Chris Myers Date: Thu, 7 Oct 2021 07:09:35 -0500 Message-ID: Subject: pvhgrub docs Cc: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000ad957e05cdc223a8" --000000000000ad957e05cdc223a8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Out of curiosity, could someone point me to some documentation for pvhgrub? Searching for "pvhgrub" xen returns very few results. Thanks! On Mon, Oct 4, 2021, 9:09 PM Chris Myers wrote: > Thanks! I'll check that out. > > Up to this point I've always just done in-place upgrades of everything > (been running Xen PV domu's for about 7 years now) and have just followed > with that old way because it generally just worked (with a few nuances.) > > On Mon, Oct 4, 2021 at 8:38 PM Andy Smith wrote: > >> On Mon, Oct 04, 2021 at 08:35:35PM -0500, Chris Myers wrote: >> > Out of curiosity is there a better/preferred way of handling it so tha= t >> I >> > don't need to remember to keep them in sync every time I do a kernel >> > upgrade? >> >> > > Once you've got to the bottom of this I recommend switching to >> > > pvhgrub booting to do away with that class of problems=E2=80=A6 >> >> > > -- > People use duct tape to fix everything....God used nails. > > http://www.myerscountry.net > --000000000000ad957e05cdc223a8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Out of curiosity, could someone point me to some document= ation for pvhgrub? Searching for

"pvhgrub" xen

returns very few results.

Thanks!=C2=A0

On Mon, Oct 4, 2021, 9:09 PM Chris Myers <= chrismyers81@gmail.com> wr= ote:
Thanks! = I'll check that out.

Up to this point I've= always just done in-place upgrades of everything (been running Xen PV domu= 's for about 7 years now) and have just followed with that old way beca= use it generally just worked (with a few nuances.)

On Mon, Oct 4, = 2021 at 8:38 PM Andy Smith <andy@strugglers.net> wrote:
On Mon, Oct 04, 2021 at = 08:35:35PM -0500, Chris Myers wrote:
> Out of curiosity is there a better/preferred way of handling it so tha= t I
> don't need to remember to keep them in sync every time I do a kern= el
> upgrade?

> > Once you've got to the bottom of this I recommend switching t= o
> > pvhgrub booting to do away with that class of problems=E2=80=A6


--
People use= duct tape to fix everything....God used nails.

http://www.myersco= untry.net
--000000000000ad957e05cdc223a8-- From xen-users-bounces@lists.xenproject.org Thu Oct 07 14:42:23 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 14:42:23 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203670.358834 (Exim 4.92) (envelope-from ) id 1mYUaU-0000x3-53; Thu, 07 Oct 2021 14:41:34 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203670.358834; Thu, 07 Oct 2021 14:41:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYUaU-0000wt-0v; Thu, 07 Oct 2021 14:41:34 +0000 Received: by outflank-mailman (input) for mailman id 203670; Thu, 07 Oct 2021 14:41:33 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYUaT-0000cy-3M for xen-users@lists.xen.org; Thu, 07 Oct 2021 14:41:33 +0000 Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 36d9d717-bda9-4a44-b076-c8fef00a78af; Thu, 07 Oct 2021 14:41:22 +0000 (UTC) Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYUaC-0005Iu-Sc; Thu, 07 Oct 2021 14:41:16 +0000 Received: from iwj by xenbits.xenproject.org with local (Exim 4.92) (envelope-from ) id 1mYUaC-0002lK-RC; Thu, 07 Oct 2021 14:41:16 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 36d9d717-bda9-4a44-b076-c8fef00a78af DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Date:Message-Id:Subject:CC:From:To:MIME-Version: Content-Transfer-Encoding:Content-Type; bh=whX0VbxgcafzIANGuqkJSRmkjVp04j5bkRzqO6Z/bEI=; b=TnQ+sCxxRcx1nR69qkFJvT3iSH nnyNIW/s7JSg2DfEuJbun9xRYUR2O9fYNs7YA/I1o1BmaZ9L31bQyjZw8tp2D6ktjCQbRuUGjFh0/ EGCNe8fEObnFUk71flf2iPoOMfwCDO197fqYJxEMS//yLWP4GwLMjykxPB4BH1L2ZGKQ=; Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team CC: Xen.org security team Subject: Xen Security Advisory 386 v2 (CVE-2021-28702) - PCI devices with RMRRs not deassigned correctly Message-Id: Date: Thu, 07 Oct 2021 14:41:16 +0000 --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Xen Security Advisory CVE-2021-28702 / XSA-386 version 2 PCI devices with RMRRs not deassigned correctly UPDATES IN VERSION 2 ==================== Updated/corrected information about vulnerable versions. Upstream Xen 4.12 is not affected. There is no harm from applying the patch to an unaffected version. ISSUE DESCRIPTION ================= Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR"). These are typically used for platform tasks such as legacy USB emulation. If such a device is passed through to a guest, then on guest shutdown the device is not properly deassigned. The IOMMU configuration for these devices which are not properly deassigned ends up pointing to a freed data structure, including the IO Pagetables. Subsequent DMA or interrupts from the device will have unpredictable behaviour, ranging from IOMMU faults to memory corruption. This bug has existed since at least Xen 4.4 But it was previously masked by a tangentially-related misbehaviour; that misbehaviour was corrected in f591755823a7 IOMMU/PCI: don't let domain cleanup continue when device de-assignment failed which was backported to supported stable branches. IMPACT ====== Administrators of guests which have been assigned RMRR-using PCI devices can cause denial of service and other problems, possibly including escalation of privilege. VULNERABLE SYSTEMS ================== For stable Xen releases: 4.13.4, 4.14.3 and 4.15.1 are vulnerable. Other versions of Xen released by the Xen Project are not affected. For Xen git branches: the HEADs of 4.13 and later (including xen-unstable) were vulnerable, up until 2021-10-05 (when the patch in this advisory was committed). 4.12 and earlier are not affected. In detail: code that has the following patch applied, is vulnerable: IOMMU/PCI: don't let domain cleanup continue when device de-assignment failed That patch is currently in upstream stable branches 4.13 onwards and was included in the most recent stable point releases of each Xen version. Other downstream Xen builds may be affected if that patch was backported. Only Intel x86 systems are affected. AMD x86 systems, and Arm systems, are all unaffected. Only systems using PCI passthrough are affected. (And then, only if the assigned devices have RMRRs, but whether a device advertises RMRRs is not easy to discern.) MITIGATION ========== There is no mitigation (other than not passing through PCI devices with RMRRs to guests). RESOLUTION ========== Applying the appropriate attached patch resolves this issue. Note that patches for released versions are generally prepared to apply to the stable branches, and may not apply cleanly to the most recent release tarball. Downstreams are encouraged to update to the tip of the stable branch before applying these patches. xsa386.patch xen-unstable - Xen 4.13.x $ sha256sum xsa386* f2f83c825e249bba9454437b48bbd8307fe7a224f56484388a67af124dfd279b xsa386.patch $ NOTE CONCERNING LACK OF EMBARGO =============================== This issue was reported and debugged in public before the security nature became apparent. -----BEGIN PGP SIGNATURE----- iQFABAEBCAAqFiEEI+MiLBRfRHX6gGCng/4UyVfoK9kFAmFfBvkMHHBncEB4ZW4u b3JnAAoJEIP+FMlX6CvZY20H/jWe2XVSU6R+cOv4GbhWL5sWBv4skLZ07yq77p8i JB9nJXdVkyHJPSkENzggGGiygiHMJFSD5cLvczJp1IbAlQKQlZt/oVG9oTWHHeqO joabwgZ9UyNW8/beCigRo1PYdiWI7tMsLp3D/LAjE8+ZhBRjD0NKLyWK26Uw0R8A Su5tApmlBGx0BJzQm4BUWiyog86fPoNcBkP1hRJfj1BfXRjVYB5MsaPCtMhsqBlG CFjDJ51Wn4Esxkg22e/429MbbExIAJUZoxuOWDk/D7nQShQNBTfqci4pfcaf5E+f Mxi32bIr/XY5LLgf0Opu5Sl2JP3s7Ik3IDlSa+wYoGIZWB4= =Ti35 -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa386.patch" Content-Disposition: attachment; filename="xsa386.patch" Content-Transfer-Encoding: base64 RnJvbTogSmFuIEJldWxpY2ggPGpiZXVsaWNoQHN1c2UuY29tPgpTdWJqZWN0 OiBWVC1kOiBmaXggZGVhc3NpZ24gb2YgZGV2aWNlIHdpdGggUk1SUgpEYXRl OiBGcmksIDEgT2N0IDIwMjEgMTU6MDU6NDIgKzAyMDAKCklnbm9yaW5nIGEg c3BlY2lmaWMgZXJyb3IgY29kZSBoZXJlIHdhcyBub3QgbWVhbnQgdG8gc2hv cnQgY2lyY3VpdApkZWFzc2lnbiB0byBfanVzdF8gdGhlIHVubWFwcGluZyBv ZiBSTVJScy4gVGhpcyBidWcgd2FzIHByZXZpb3VzbHkKaGlkZGVuIGJ5IHRo ZSBib2d1cyAocG90ZW50aWFsbHkgaW5kZWZpbml0ZSkgbG9vcGluZyBpbgpw Y2lfcmVsZWFzZV9kZXZpY2VzKCksIHVudGlsIGY1OTE3NTU4MjNhNyAoIklP TU1VL1BDSTogZG9uJ3QgbGV0IGRvbWFpbgpjbGVhbnVwIGNvbnRpbnVlIHdo ZW4gZGV2aWNlIGRlLWFzc2lnbm1lbnQgZmFpbGVkIikgZml4ZWQgdGhhdCBs b29wLgoKVGhpcyBpcyBDVkUtMjAyMS0yODcwMiAvIFhTQS0zODYuCgpGaXhl czogOGI5OWY0NDAwYjY5ICgiVlQtZDogZml4IFJNUlIgcmVsYXRlZCBlcnJv ciBoYW5kbGluZyIpClJlcG9ydGVkLWJ5OiBJdmFuIEthcmR5a292IDxrYXJk eWtvdkB0YWJpdC5wcm8+ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxq YmV1bGljaEBzdXNlLmNvbT4KVGVzdGVkLWJ5OiBJdmFuIEthcmR5a292IDxr YXJkeWtvdkB0YWJpdC5wcm8+CgotLS0gYS94ZW4vZHJpdmVycy9wYXNzdGhy b3VnaC92dGQvaW9tbXUuYworKysgYi94ZW4vZHJpdmVycy9wYXNzdGhyb3Vn aC92dGQvaW9tbXUuYwpAQCAtMjQwOSw3ICsyNDA5LDcgQEAgc3RhdGljIGlu dCByZWFzc2lnbl9kZXZpY2Vfb3duZXJzaGlwKAogICAgICAgICAgICAgICAg IHJldCA9IGlvbW11X2lkZW50aXR5X21hcHBpbmcoc291cmNlLCBwMm1fYWNj ZXNzX3gsCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICBybXJyLT5iYXNlX2FkZHJlc3MsCiAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBybXJyLT5lbmRfYWRkcmVz cywgMCk7Ci0gICAgICAgICAgICAgICAgaWYgKCByZXQgIT0gLUVOT0VOVCAp CisgICAgICAgICAgICAgICAgaWYgKCByZXQgJiYgcmV0ICE9IC1FTk9FTlQg KQogICAgICAgICAgICAgICAgICAgICByZXR1cm4gcmV0OwogICAgICAgICAg ICAgfQogICAgIH0KCg== --=separator-- From xen-users-bounces@lists.xenproject.org Thu Oct 07 14:49:49 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 14:49:49 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203526.358878 (Exim 4.92) (envelope-from ) id 1mYUhz-00043n-Ps; Thu, 07 Oct 2021 14:49:19 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203526.358878; Thu, 07 Oct 2021 14:49:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYUhz-00043f-LU; Thu, 07 Oct 2021 14:49:19 +0000 Received: by outflank-mailman (input) for mailman id 203526; Thu, 07 Oct 2021 12:30:10 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYSXK-0005L1-IR for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 12:30:10 +0000 Received: from mail.kaminski-berlin.org (unknown [134.255.253.37]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 2be25147-f1dc-41c1-ba9f-1b3c0b33312c; Thu, 07 Oct 2021 12:30:09 +0000 (UTC) Received: from mail.home.chao5.net (mail.home.chao5.net [192.168.50.100]) by mail.chao5.net (Postfix) with ESMTP id 5E71780076A; Thu, 7 Oct 2021 14:30:08 +0200 (CEST) Received: from lucypher (localhost [127.0.0.1]) by mail.home.chao5.net (Postfix) with ESMTPA id E803C1F8206; Thu, 7 Oct 2021 14:30:05 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 2be25147-f1dc-41c1-ba9f-1b3c0b33312c Date: Thu, 7 Oct 2021 14:30:05 +0200 From: perun To: "Chris Myers" Cc: xen-users@lists.xenproject.org Message-ID: <5ad86b63-35c0-427d-940c-034d6b5b3dcf@lucypher> In-Reply-To: References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> Subject: Re: pvhgrub docs MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="615ee84d_627c03d8_104d" X-Synology-MCP-Status: no X-Synology-Spam-Flag: no X-Synology-Spam-Status: score=0.4, required 5, FROM_HAS_DN 0, TO_DN_SOME 0, TO_MATCH_ENVRCPT_ALL 0, FREEMAIL_ENVRCPT 0, MIME_GOOD -0.1, __THREADED 0, URI_COUNT_ODD 0, HTML_MISSING_CTYPE 0, RCPT_COUNT_TWO 0, HTML_MESSAGE 0.001, FREEMAIL_TO 0, RCVD_COUNT_ZERO 0, FROM_EQ_ENVFROM 0, MID_RHS_NOT_FQDN 0.5, MIME_TRACE 0, __NOT_SPOOFED 0, __KHOP_NO_FULL_NAME 0, NO_RECEIVED -0.001 X-Synology-Virus-Status: no --615ee84d_627c03d8_104d Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline is pvhgrub a part of xen or grub2 project=3F (dont see it at xen 4.15.1 i= n centos8 RPM's) Am 2021-10-07 14:09, Chris Myers schrieb: > > Out of curiosity, could someone point me to some documen= tation for pvhgrub=3F Searching for > > > =22pvhgrub=22 xen > > > > retur= ns very few results. > > > > Thanks=21 > > > > > On Mon, Oct 4, 2021, 9:0= 9 PM Chris Myers wrote: > > > > > > > > Thanks=21 I'll check that out. > > > > > > > = > Up to this point I've always just done in-place upgrades of everything = (been running Xen PV domu's for about 7 years now) and have just followed= with that old way because it generally just worked (with a few nuances.)= > > > > > > > > > > On Mon, Oct 4, 2021 at 8:38 PM Andy Smith wrote: > > > > > On Mon, Oct= 04, 2021 at 08:35:35PM -0500, Chris Myers wrote: > > > > Out of curiosit= y is there a better/preferred way of handling it so that I > > > > don't = need to remember to keep them in sync every time I do a kernel > > > > up= grade=3F > > > > > > > > Once you've got to the bottom of this I recommen= d switching to > > > > > pvhgrub booting to do away with that class of pr= oblems=E2=80=A6 > > > > -- > > > > People use duct tape to fix everything= ....God used nails. > > > > http://www.myerscountry.net --615ee84d_627c03d8_104d Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
is pvhgrub a part of xen or grub2 project=3F (dont see it at xen 4.1= 5.1 in centos8 RPM's)
 
 
Am 2021-10-07 14:09, Chris Myers <chrismyers81=40gmail.com> sc= hrieb:
Out of curiosity, could someone point me to some do= cumentation for pvhgrub=3F Searching for
 
=22pvhgrub=22 xen
 
returns very few results.
 
Thanks=21 

On Mon, Oct 4, 2021, 9:09= PM Chris Myers <chrismyers81=40gmail.c= om> wrote:
Thanks=21 I'll check that out.
 
Up to this point I've always just done in-place upgrades of everythi= ng (been running Xen PV domu's for about 7 years now) and have just follo= wed with that old way because it generally just worked (with a few nuance= s.)

On Mon, Oct 4, 2021 at 8:= 38 PM Andy Smith <andy=40strugglers.net&= gt; wrote:
On Mon, Oct = 04, 2021 at 08:35:35PM -0500, Chris Myers wrote:
> Out of curiosity is there a better/preferred way of handling it so t= hat I
> don't need to remember to keep them in sync every time I do a kernel=
> upgrade=3F

> > Once you've got to the bottom of this I recommend switching to<= br /> > > pvhgrub booting to do away with that class of problems=E2=80=A6=


--
People use duct tape to fix everything....God used n= ails.

http://www.myerscountry.net
--615ee84d_627c03d8_104d-- From xen-users-bounces@lists.xenproject.org Thu Oct 07 15:26:34 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 15:26:34 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203776.358917 (Exim 4.92) (envelope-from ) id 1mYVHl-0001Uy-A1; Thu, 07 Oct 2021 15:26:17 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203776.358917; Thu, 07 Oct 2021 15:26:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYVHl-0001Uq-6G; Thu, 07 Oct 2021 15:26:17 +0000 Received: by outflank-mailman (input) for mailman id 203776; Thu, 07 Oct 2021 15:26:15 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYVHj-0001Uj-J0 for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 15:26:15 +0000 Received: from smtp-out2.suse.de (unknown [195.135.220.29]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id e86a4f5c-2782-11ec-bfdf-12813bfff9fa; Thu, 07 Oct 2021 15:26:14 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id A1DCB200DF; Thu, 7 Oct 2021 15:26:13 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 865A413E9D; Thu, 7 Oct 2021 15:26:13 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id G9eTH5URX2EffAAAMHmgww (envelope-from ); Thu, 07 Oct 2021 15:26:13 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: e86a4f5c-2782-11ec-bfdf-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1633620373; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=h5PviNlRLV0xj75Nh2TP00/++gLB4AKj+ss7uFbSXUM=; b=FWT0fYr04u6LxKCIhGra35/Mu+Qxqc8f3s+HeFkbqnbTb3X8KWnBJ6ZbT0EG6CfekuMsRk wLxGcwodenpvlx/HgpstvCz+Ce/FtfqszJCHGCGMV5Yg5RuefDcgEqoaccZJxfhJulOdPk baeI1FPxUuk9rpqAwsEE7Ul3HDetR34= Subject: Re: pvhgrub docs To: perun , Chris Myers Cc: xen-users@lists.xenproject.org References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> <5ad86b63-35c0-427d-940c-034d6b5b3dcf@lucypher> From: Juergen Gross Message-ID: <04df5c30-39ef-1a15-216a-05380dac35bf@suse.com> Date: Thu, 7 Oct 2021 17:26:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: <5ad86b63-35c0-427d-940c-034d6b5b3dcf@lucypher> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XwkLVi67Hd0rLKCPSU2jjBvCznSyuxK5V" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XwkLVi67Hd0rLKCPSU2jjBvCznSyuxK5V Content-Type: multipart/mixed; boundary="5Y9T5R9q91I3DJDqKF7KseQvLzWpYk5e1"; protected-headers="v1" From: Juergen Gross To: perun , Chris Myers Cc: xen-users@lists.xenproject.org Message-ID: <04df5c30-39ef-1a15-216a-05380dac35bf@suse.com> Subject: Re: pvhgrub docs References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> <5ad86b63-35c0-427d-940c-034d6b5b3dcf@lucypher> In-Reply-To: <5ad86b63-35c0-427d-940c-034d6b5b3dcf@lucypher> --5Y9T5R9q91I3DJDqKF7KseQvLzWpYk5e1 Content-Type: multipart/mixed; boundary="------------D4CD38ACCB5E0F1647B6E076" Content-Language: en-US This is a multi-part message in MIME format. --------------D4CD38ACCB5E0F1647B6E076 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable On 07.10.21 14:30, perun wrote: > is pvhgrub a part of xen or grub2 project? (dont see it at xen 4.15.1 i= n=20 > centos8 RPM's) It is part of grub2. Juergen --------------D4CD38ACCB5E0F1647B6E076 Content-Type: application/pgp-keys; name="OpenPGP_0xB0DE9DD628BF132F.asc" Content-Transfer-Encoding: quoted-printable Content-Description: OpenPGP public key Content-Disposition: attachment; filename="OpenPGP_0xB0DE9DD628BF132F.asc" -----BEGIN PGP PUBLIC KEY BLOCK----- xsBNBFOMcBYBCACgGjqjoGvbEouQZw/ToiBg9W98AlM2QHV+iNHsEs7kxWhKMjrioyspZKOBy= cWx w3ie3j9uvg9EOB3aN4xiTv4qbnGiTr3oJhkB1gsb6ToJQZ8uxGq2kaV2KL9650I1SJvedYm8O= f8Z d621lSmoKOwlNClALZNew72NjJLEzTalU1OdT7/i1TXkH09XSSI8mEQ/ouNcMvIJNwQpd369y= 9bf IhWUiVXEK7MlRgUG6MvIj6Y3Am/BBLUVbDa4+gmzDC9ezlZkTZG2t14zWPvxXP3FAp2pkW0xq= G7/ 377qptDmrk42GlSKN4z76ELnLxussxc7I2hx18NUcbP8+uty4bMxABEBAAHNHEp1ZXJnZW4gR= 3Jv c3MgPGpnQHBmdXBmLm5ldD7CwHkEEwECACMFAlOMcBYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDA= QIe AQIXgAAKCRCw3p3WKL8TL0KdB/93FcIZ3GCNwFU0u3EjNbNjmXBKDY4FUGNQH2lvWAUy+dnyT= hpw dtF/jQ6j9RwE8VP0+NXcYpGJDWlNb9/JmYqLiX2Q3TyevpB0CA3dbBQp0OW0fgCetToGIQrg0= MbD 1C/sEOv8Mr4NAfbauXjZlvTj30H2jO0u+6WGM6nHwbh2l5O8ZiHkH32iaSTfN7Eu5RnNVUJbv= oPH Z8SlM4KWm8rG+lIkGurqqu5gu8q8ZMKdsdGC4bBxdQKDKHEFExLJK/nRPFmAuGlId1E3fe10v= 5QL +qHI3EIPtyfE7i9Hz6rVwi7lWKgh7pe0ZvatAudZ+JNIlBKptb64FaiIOAWDCx1SzR9KdWVyZ= 2Vu IEdyb3NzIDxqZ3Jvc3NAc3VzZS5jb20+wsB5BBMBAgAjBQJTjHCvAhsDBwsJCAcDAgEGFQgCC= QoL BBYCAwECHgECF4AACgkQsN6d1ii/Ey/HmQf/RtI7kv5A2PS4RF7HoZhPVPogNVbC4YA6lW7Dr= Wf0 teC0RR3MzXfy6pJ+7KLgkqMlrAbN/8Dvjoz78X+5vhH/rDLa9BuZQlhFmvcGtCF8eR0T1v0nC= /nu AFVGy+67q2DH8As3KPu0344TBDpAvr2uYM4tSqxK4DURx5INz4ZZ0WNFHcqsfvlGJALDeE0Lh= ITT d9jLzdDad1pQSToCnLl6SBJZjDOX9QQcyUigZFtCXFst4dlsvddrxyqT1f17+2cFSdu7+ynLm= XBK 7abQ3rwJY8SbRO2iRulogc5vr/RLMMlscDAiDkaFQWLoqHHOdfO9rURssHNN8WkMnQfvUewRz= 80h SnVlcmdlbiBHcm9zcyA8amdyb3NzQG5vdmVsbC5jb20+wsB5BBMBAgAjBQJTjHDXAhsDBwsJC= AcD AgEGFQgCCQoLBBYCAwECHgECF4AACgkQsN6d1ii/Ey8PUQf/ehmgCI9jB9hlgexLvgOtf7PJn= FOX gMLdBQgBlVPO3/D9R8LtF9DBAFPNhlrsfIG/SqICoRCqUcJ96Pn3P7UUinFG/I0ECGF4EvTE1= jnD kfJZr6jrbjgyoZHiw/4BNwSTL9rWASyLgqlA8u1mf+c2yUwcGhgkRAd1gOwungxcwzwqgljf0= N51 N5JfVRHRtyfwq/ge+YEkDGcTU6Y0sPOuj4Dyfm8fJzdfHNQsWq3PnczLVELStJNdapwPOoE+l= otu fe3AM2vAEYJ9rTz3Cki4JFUsgLkHFqGZarrPGi1eyQcXeluldO3m91NK/1xMI3/+8jbO0tsn1= tqS EUGIJi7ox80eSnVlcmdlbiBHcm9zcyA8amdyb3NzQHN1c2UuZGU+wsB5BBMBAgAjBQJTjHDrA= hsD BwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQsN6d1ii/Ey+LhQf9GL45eU5vOowA2u5N3= g3O ZUEBmDHVVbqMtzwlmNC4k9Kx39r5s2vcFl4tXqW7g9/ViXYuiDXb0RfUpZiIUW89siKrkzmQ5= dM7 wRqzgJpJwK8Bn2MIxAKArekWpiCKvBOB/Cc+3EXE78XdlxLyOi/NrmSGRIov0karw2RzMNOu5= D+j LRZQd1Sv27AR+IP3I8U4aqnhLpwhK7MEy9oCILlgZ1QZe49kpcumcZKORmzBTNh30FVKK1Evm= V2x AKDoaEOgQB4iFQLhJCdP1I5aSgM5IVFdn7v5YgEYuJYx37IoN1EblHI//x/e2AaIHpzK5h88N= Eaw QsaNRpNSrcfbFmAg987ATQRTjHAWAQgAyzH6AOODMBjgfWE9VeCgsrwH3exNAU32gLq2xvjpW= nHI s98ndPUDpnoxWQugJ6MpMncr0xSwFmHEgnSEjK/PAjppgmyc57BwKII3sV4on+gDVFJR6Y8ZR= wgn BC5mVM6JjQ5xDk8WRXljExRfUX9pNhdE5eBOZJrDRoLUmmjDtKzWaDhIg/+1Hzz93X4fCQkNV= bVF LELU9bMaLPBG/x5q4iYZ2k2ex6d47YE1ZFdMm6YBYMOljGkZKwYde5ldM9mo45mmwe0icXKLk= pEd IXKTZeKDO+Hdv1aqFuAcccTg9RXDQjmwhC3yEmrmcfl0+rPghO0Iv3OOImwTEe4co3c1mwARA= QAB wsBfBBgBAgAJBQJTjHAWAhsMAAoJELDendYovxMvQ/gH/1ha96vm4P/L+bQpJwrZ/dneZcmEw= Tbe 8YFsw2V/Buv6Z4Mysln3nQK5ZadD534CF7TDVft7fC4tU4PONxF5D+/tvgkPfDAfF77zy2AH1= vJz Q1fOU8lYFpZXTXIHb+559UqvIB8AdgR3SAJGHHt4RKA0F7f5ipYBBrC6cyXJyyoprT10EMvU8= VGi wXvTyJz3fjoYsdFzpWPlJEBRMedCot60g5dmbdrZ5DWClAr0yau47zpWj3enf1tLWaqcsuylW= svi uGjKGw7KHQd3bxALOknAp4dN3QwBYCKuZ7AddY9yjynVaD5X7nF9nO5BjR/i1DG86lem3iBDX= zXs ZDn8R38=3D =3D2wuH -----END PGP PUBLIC KEY BLOCK----- --------------D4CD38ACCB5E0F1647B6E076-- --5Y9T5R9q91I3DJDqKF7KseQvLzWpYk5e1-- --XwkLVi67Hd0rLKCPSU2jjBvCznSyuxK5V Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEhRJncuj2BJSl0Jf3sN6d1ii/Ey8FAmFfEZUFAwAAAAAACgkQsN6d1ii/Ey83 awgAi101fQAdhyNrOeUzd1wSxEMdDLyGWChDLkxLmhyFsT3GMtX4S5tJTQTEH4/PyTXayWtpERml daq+NZYy3/jpokVDGiwyEdIQzy+ufRAHB0uP45EWMSyu38uzZJ4KcdKK29WNQhOwwJkBnsff58c9 umh3h58AR1+BjgnImzUdvvY9qRIv9jlEuOtjmv1z7Ww+N8y7cKVvh26pl2+9NgEFz98Tw+V8s/qz ACGn67e/L0EW9sIjNpe3l0bo0kAzxT95b82/28pAwvE8X60ks3gm7lTsRtJ6eX2q+LbduHQ8XSN6 kDNDRgHWojtNoG6L2WxnPHfGSSrVIZPlcLBosa2O+w== =r7Qc -----END PGP SIGNATURE----- --XwkLVi67Hd0rLKCPSU2jjBvCznSyuxK5V-- From xen-users-bounces@lists.xenproject.org Thu Oct 07 15:44:08 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 15:44:08 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203814.358957 (Exim 4.92) (envelope-from ) id 1mYVYc-0005gE-HU; Thu, 07 Oct 2021 15:43:42 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203814.358957; Thu, 07 Oct 2021 15:43:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYVYc-0005g6-Dn; Thu, 07 Oct 2021 15:43:42 +0000 Received: by outflank-mailman (input) for mailman id 203814; Thu, 07 Oct 2021 15:43:40 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYVYa-0005g0-Rd for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 15:43:40 +0000 Received: from mail-yb1-xb30.google.com (unknown [2607:f8b0:4864:20::b30]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id cfa0f2e6-28d5-4598-8350-7c6cc66de9f2; Thu, 07 Oct 2021 15:43:40 +0000 (UTC) Received: by mail-yb1-xb30.google.com with SMTP id g6so14395107ybb.3 for ; Thu, 07 Oct 2021 08:43:40 -0700 (PDT) Received: by 2002:a25:238b:0:0:0:0:0 with HTTP; Thu, 7 Oct 2021 08:43:38 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: cfa0f2e6-28d5-4598-8350-7c6cc66de9f2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=6oPzn1Ta6SDZTYAHZojfl/w+L3xrzJ890zj/fqAeyKA=; b=ILhF5wuJ/T8tQX6fFqCO6XRXvsF0orkI+mzOXhOuJ4xW8P4MTSZAFdzUPysTWvbQrW N9Lek7mq5pKqHH9Z9I1ZP/8QXTH3VSS2eYuTtuus19L/31Brtev2PolqHflkDqQ7bHl9 aO+SdfubgYxEVmRdKzcT14rnJljxv7pLhd9i9zwBDpb/FIcS6as9ZpwTYh/0WqZgPYFr GjMDM6N+6qDVdDnTlZLVlarnBPHVaVsDGjEfsZFR23Bq1OEeRb560X1oVnNtHuO/3k+S /HK/uRlZ5HkoBvOwlWLF9a2s0IKJ2VOYvSE9B34bTPdNpimCM5iMRS8qwW7itu6rwv31 JgHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6oPzn1Ta6SDZTYAHZojfl/w+L3xrzJ890zj/fqAeyKA=; b=A0PqELKkpaTomOyfvuViBnA1C/NIRC+wRWx6XV+9UtW421jGEDz49VY+gP0tJnWbGo BJ5ODfxfJkp0YowSdGHJkF0qldoZMNW+HcnYUS3fi8dISIyj8ebWu2vbkjOAYc7EuKhb sLh1XJPj27g+vOikX9vl+3MXEuTdCsWpGmQsMgVnqGBKvw16A9EctzkkzCoSrPpLvT/J GsAXxgiisSFsfNL0OBO4mEZ9p3FGDesylhbhT4+t2olXCbjXh26cUHFYsBQYB3copG7R DNJfZgICG115PvnY27fo6eQEGEhBoM8K05sJNfpYWGLk0aTsY9ezN5+raeTkPCDQbGvm dPsw== X-Gm-Message-State: AOAM530abVXtqKUqpcz2Vrth76TPrA3fwN+PZqZSWK/CubuAYA0jeP/+ 1NV/OWycwltVgSwLADw2J9ylQIApzLMM/zliZahtSOBh X-Google-Smtp-Source: ABdhPJwvrp5UGehsfP4ZyqYesSWPoaMuViNaCM7fzz4CqgVusKVzsk6hvIOgprx4Hl3OWEOzajb0oSEKVY2LKPhMWWU= X-Received: by 2002:a25:d906:: with SMTP id q6mr5781229ybg.129.1633621419421; Thu, 07 Oct 2021 08:43:39 -0700 (PDT) MIME-Version: 1.0 From: Pry Mar Date: Thu, 7 Oct 2021 08:43:38 -0700 Message-ID: Subject: is there a repo for xen-4.15.1 in CentOS 8 ? To: xen-users Content-Type: text/plain; charset="UTF-8" hello xen-users, https://lists.xenproject.org/archives/html/xen-users/2021-10/msg00015.html in the above post was mentioned CentOS 8 xen-4.15.1 RPM's. Here is how to browse the said package set, starting with the repo file: -- virt8-xen.repo --- [centos-virt-xen-415] name=CentOS-$releasever - xen-415 baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-415 gpgcheck=1 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization [centos-virt-xen-415-testing] name=CentOS-$releasever - xen-4.15 - testing baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-415 gpgcheck=0 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization -- unsnip -- sh-4.4# dnf list available --disablerepo=\* --enablerepo=centos-virt-xen-415-testing CentOS-8 - xen-4.15 - testing 345 kB/s | 572 kB 00:01 Available Packages centos-release-xen.x86_64 10:9-1.el8 centos-virt-xen-415-testing centos-release-xen-412.x86_64 10:9-1.el8 centos-virt-xen-415-testing centos-release-xen-common.x86_64 10:9-1.el8 centos-virt-xen-415-testing kernel.x86_64 5.4.43-2.el8 centos-virt-xen-415-testing kernel-devel.x86_64 5.4.43-2.el8 centos-virt-xen-415-testing kernel-doc.noarch 5.4.43-2.el8 centos-virt-xen-415-testing kernel-headers.x86_64 5.4.43-2.el8 centos-virt-xen-415-testing perf.x86_64 5.4.43-2.el8 centos-virt-xen-415-testing qemu-xen.x86_64 4.15.0-1.el8 centos-virt-xen-415-testing xen.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-devel.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-doc.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-hypervisor.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-libs.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-licenses.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-livepatch-build-tools.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-ocaml.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-ocaml-devel.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing xen-ovmf.x86_64 202102-1.gitef91b07388e1.el8 centos-virt-xen-415-testing xen-runtime.x86_64 4.15.1-1.el8 centos-virt-xen-415-testing sh-4.4# dnf provides '/usr/bin/qemu-img' --enablerepo=centos-virt-xen-415-testing Last metadata expiration check: 0:00:46 ago on Wed Sep 22 12:38:52 2021. Error: No Matches found cheers, PryMar56 ##xen-packaging on OFTC From xen-users-bounces@lists.xenproject.org Thu Oct 07 17:20:38 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 17:20:38 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203888.359041 (Exim 4.92) (envelope-from ) id 1mYX3f-00020K-Ab; Thu, 07 Oct 2021 17:19:51 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203888.359041; Thu, 07 Oct 2021 17:19:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYX3f-00020C-6x; Thu, 07 Oct 2021 17:19:51 +0000 Received: by outflank-mailman (input) for mailman id 203888; Thu, 07 Oct 2021 17:19:50 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYX3e-000206-0M for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 17:19:50 +0000 Received: from mail-io1-xd36.google.com (unknown [2607:f8b0:4864:20::d36]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id c749948d-cfd7-407c-8403-09d3109fd0c4; Thu, 07 Oct 2021 17:19:49 +0000 (UTC) Received: by mail-io1-xd36.google.com with SMTP id z184so7623222iof.5 for ; Thu, 07 Oct 2021 10:19:49 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: c749948d-cfd7-407c-8403-09d3109fd0c4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=smErhptwsLMznHPU7iZYPCHr6iqt4cTGJH1j9GXupl4=; b=N6RZqr1b/a5JN2gvaTKKSxerlEDLQDKCJ2+YDUyRbPoM3R5Fz4k8Qp3b18EmUGpzWY G+mXKTtqZSDZtSSI5cfCoiu16gCegxB4M+1w6s6KF7atn4sGbkgqdpn0QCCB0gwrV0W1 DrZ2v2aQjYOTDTNfvb7AttPR0ouKEDDg64jqQDFi0oIsp/pWyLj5WVZTEKFyGuvR+8dn 9EUSS/+p6YHXpOF4zONrZXEstzwuee0II7PXQDkgMU99Yy7vN5pMnRpEil2dDjfmDcgV UI0NxSTrsE8xEiuTUp6kjKwaDz2Bda7vWh07Xjr+L8alMb9ryxcLD/a1/gLEjpY70ske 4rJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=smErhptwsLMznHPU7iZYPCHr6iqt4cTGJH1j9GXupl4=; b=kfAdYUCQQupD+C4jbw94nMGqYqunhZLv/gfZp5WIUV8XJ63p03phBFuSh3tc6f2x3B aWyg4o0o7Qktuzst+yRkSenIHwOFkHousryXy878IeYRwx0xJgHa7EPBRajNXBoYOqGE w9KXjS/geahzyzoTxN7eirpz1AJ5g7YMfe5NiQaI5MLJW+MvI3+Ulewn+FqL7MnO5kmF UwwwRhgOZ9FVIwflz9MFLtP/WEDGlUT1j9toRNUTftx+gqwBQ1dkXiY8UyTQLhlc8EtN 7NfPKEo71PvoL9sqDUBdNC9RFefHhdVV7MD0ldzECy+qeEcQ+8ak5vrXQGtDQNWg4odO ZjKQ== X-Gm-Message-State: AOAM5328Xua/4As8D2FlJ8phGRW1qBogbYJZvTwMDaNMx73AJFijVGPT VNnXQ2GVNqoaEfsGEjCSMCoezYajUDuP0qcxByPBsBNOXAo= X-Google-Smtp-Source: ABdhPJxF+lHo3lIiiI2MyJANC5wkAGmPagOn2idIHrIs50lQ7e+Zbbs+lJTihGWFkngzVoNCNKKP4jJtcDK49hJCvB8= X-Received: by 2002:a02:a90c:: with SMTP id n12mr3914061jam.89.1633627188710; Thu, 07 Oct 2021 10:19:48 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> In-Reply-To: From: C Stainer Date: Thu, 7 Oct 2021 18:19:33 +0100 Message-ID: Subject: Re: pvhgrub docs To: Chris Myers Cc: xen-users@lists.xenproject.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Chris, FWIW I found a combination of the Xen PVH wiki [1] and [2] useful when evaluating PVH mode for a use case. On a Debian host (from at least Buster) pvhgrub's install location is /usr/lib/grub-xen/grub-i386-xen_pvh.bin (grub-xen-host) and /usr/lib/grub/* (grub-xen-bin). [1] https://wiki.xenproject.org/wiki/Linux_PVH [2] https://tools.bitfolk.com/wiki/PVH HTH? C On Thu, 7 Oct 2021 at 13:10, Chris Myers wrote: > > Out of curiosity, could someone point me to some documentation for pvhgru= b? Searching for > > "pvhgrub" xen > > returns very few results. > > Thanks! > > On Mon, Oct 4, 2021, 9:09 PM Chris Myers wrote: >> >> Thanks! I'll check that out. >> >> Up to this point I've always just done in-place upgrades of everything (= been running Xen PV domu's for about 7 years now) and have just followed wi= th that old way because it generally just worked (with a few nuances.) >> >> On Mon, Oct 4, 2021 at 8:38 PM Andy Smith wrote: >>> >>> On Mon, Oct 04, 2021 at 08:35:35PM -0500, Chris Myers wrote: >>> > Out of curiosity is there a better/preferred way of handling it so th= at I >>> > don't need to remember to keep them in sync every time I do a kernel >>> > upgrade? >>> >>> > > Once you've got to the bottom of this I recommend switching to >>> > > pvhgrub booting to do away with that class of problems=E2=80=A6 >>> >> >> >> -- >> People use duct tape to fix everything....God used nails. >> >> http://www.myerscountry.net From xen-users-bounces@lists.xenproject.org Thu Oct 07 21:47:50 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 21:47:50 +0000 Received: from list by lists.xenproject.org with outflank-mailman.204052.359256 (Exim 4.92) (envelope-from ) id 1mYbEP-0003cp-BR; Thu, 07 Oct 2021 21:47:13 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 204052.359256; Thu, 07 Oct 2021 21:47:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYbEP-0003ch-6h; Thu, 07 Oct 2021 21:47:13 +0000 Received: by outflank-mailman (input) for mailman id 204052; Thu, 07 Oct 2021 21:47:11 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYbEN-0003cb-Gb for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 21:47:11 +0000 Received: from mail-pj1-x1030.google.com (unknown [2607:f8b0:4864:20::1030]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id c6f42190-7de3-4e4f-b686-86f76778821f; Thu, 07 Oct 2021 21:47:10 +0000 (UTC) Received: by mail-pj1-x1030.google.com with SMTP id ls14-20020a17090b350e00b001a00e2251c8so6241879pjb.4 for ; Thu, 07 Oct 2021 14:47:10 -0700 (PDT) Received: from [192.168.2.12] (d173-181-74-129.bchsia.telus.net. [173.181.74.129]) by smtp.gmail.com with ESMTPSA id d2sm8882100pjg.35.2021.10.07.14.47.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Oct 2021 14:47:08 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: c6f42190-7de3-4e4f-b686-86f76778821f DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telus.net; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=DHUyFe43q/B2C2Fsyv0Fek51WGNDY6Vn/vQ+UL0CPjQ=; b=K+Q3P/MO9SeRvCthElmVducwsOujWxV9HnJbvPyt0Ly9IZx5rRxqG+/usJ9k5dWzab N8HVe30NZHfDi+Anj4f5g7sVCFuHVzi7R3QfJzbQJF5Ph0fy6czkfCPt6IY3qdYvJbWG tftkZTdAysJnEDypqCjFXgbEJ8/mm+IALF/sfYNb1dcnrhw6CqFW7C0B8yNLZlkKAfd7 iopO3s7AayeubRNp9FCaoy0bcrdkcUGVna1ZN09SILOVhps4uovVRm7EZrt32VGYzFYl JpA8J+JGfEPtfR4ZQODgGxQUjxuGbPuLZmftNQKAP8BxBI2zbW3rsx4CZLih7PlLt4so 4YsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=DHUyFe43q/B2C2Fsyv0Fek51WGNDY6Vn/vQ+UL0CPjQ=; b=oQfh3TrqFDDZwRrex+L6jUyYZK7XeSw2FRpkZL53REPQ2GpRKz8WSAgOeHwLL5Nslq etWBNWCFwZ4GEntDnRYL/chp8k/hPNUUZlVXggcIEhyn5YWLJpbZPSajJbE1WhufxV/e XrI1FAME4oIXn390dCDNrr9XzKwey8IeIcA+sJpX9cHFwkW2M5DTb6dGH+vGrRrK+czF GQhstYWpkFYA5yJum73N9GDshMgx24KBnWgbygysA7NQuvijd1v53UfQTcnCaC5P/Lla 0FLX3+LiWl/2Dj3FSr34tfDz5jUtkuwIfjAONU7E6JBx5xkN2LnuWNrkZ8MmD+ezXiJ0 ho2g== X-Gm-Message-State: AOAM530HXk2+7Ff8rQpuOc7UJzLEZ9Y4MH6WQRFvjQXFZbJhoSFaMUSt L4Zdu9N7qi+8tdpYHG4mVE95+Ifi1tJrnw== X-Google-Smtp-Source: ABdhPJxzZ/m6KTmVSYvR1DRMnHgjkYt0jFN/AZsfUuH7w/+mCDry2y4Ry0HLEzzpbLhtP/9pjUVEmA== X-Received: by 2002:a17:902:76c3:b0:13c:957d:561f with SMTP id j3-20020a17090276c300b0013c957d561fmr5895548plt.27.1633643229201; Thu, 07 Oct 2021 14:47:09 -0700 (PDT) Subject: Re: pvhgrub docs To: xen-users@lists.xenproject.org References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> From: David Hill Message-ID: <051ed5a3-a668-950e-66d1-ca71d679628a@telus.net> Date: Thu, 7 Oct 2021 14:47:08 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------24BA3F114763F9A9369A1D98" Content-Language: en-US This is a multi-part message in MIME format. --------------24BA3F114763F9A9369A1D98 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 2021-10-07 5:09 a.m., Chris Myers wrote: > Out of curiosity, could someone point me to some documentation for > pvhgrub? Searching for > > "pvhgrub" xen > > returns very few results. > > Thanks! > > On Mon, Oct 4, 2021, 9:09 PM Chris Myers > wrote: > > Thanks! I'll check that out. > > Up to this point I've always just done in-place upgrades of > everything (been running Xen PV domu's for about 7 years now) and > have just followed with that old way because it generally just > worked (with a few nuances.) > > On Mon, Oct 4, 2021 at 8:38 PM Andy Smith > wrote: > > On Mon, Oct 04, 2021 at 08:35:35PM -0500, Chris Myers wrote: > > Out of curiosity is there a better/preferred way of handling > it so that I > > don't need to remember to keep them in sync every time I do > a kernel > > upgrade? > > > > Once you've got to the bottom of this I recommend switching to > > > pvhgrub booting to do away with that class of problems… > > > > -- > People use duct tape to fix everything....God used nails. > > http://www.myerscountry.net > Hi Chris, pvhgrub is new to me, but to understand the transition away from pygrub, I found pvgrub2 documentation helpful (although some of it is a bit dated): https://wiki.xenproject.org/wiki/PvGrub2 --------------24BA3F114763F9A9369A1D98 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit


On 2021-10-07 5:09 a.m., Chris Myers wrote:
Out of curiosity, could someone point me to some documentation for pvhgrub? Searching for

"pvhgrub" xen

returns very few results.

Thanks! 

On Mon, Oct 4, 2021, 9:09 PM Chris Myers <chrismyers81@gmail.com> wrote:
Thanks! I'll check that out.

Up to this point I've always just done in-place upgrades of everything (been running Xen PV domu's for about 7 years now) and have just followed with that old way because it generally just worked (with a few nuances.)

On Mon, Oct 4, 2021 at 8:38 PM Andy Smith <andy@strugglers.net> wrote:
On Mon, Oct 04, 2021 at 08:35:35PM -0500, Chris Myers wrote:
> Out of curiosity is there a better/preferred way of handling it so that I
> don't need to remember to keep them in sync every time I do a kernel
> upgrade?

> > Once you've got to the bottom of this I recommend switching to
> > pvhgrub booting to do away with that class of problems…



--
People use duct tape to fix everything....God used nails.

http://www.myerscountry.net

Hi Chris,

pvhgrub is new to me, but to understand the transition away from pygrub, I found pvgrub2 documentation helpful (although some of it is a bit dated):

https://wiki.xenproject.org/wiki/PvGrub2


--------------24BA3F114763F9A9369A1D98-- From xen-users-bounces@lists.xenproject.org Thu Oct 07 22:14:52 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 22:14:52 +0000 Received: from list by lists.xenproject.org with outflank-mailman.204083.359287 (Exim 4.92) (envelope-from ) id 1mYbet-00080D-33; Thu, 07 Oct 2021 22:14:35 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 204083.359287; Thu, 07 Oct 2021 22:14:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYbes-000806-VH; Thu, 07 Oct 2021 22:14:34 +0000 Received: by outflank-mailman (input) for mailman id 204083; Thu, 07 Oct 2021 22:14:33 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYber-000800-DD for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 22:14:33 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 6d0e3246-6c8f-498c-acd0-aa31a1f71d0a; Thu, 07 Oct 2021 22:14:31 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mYbeo-0006Jy-PI for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 22:14:30 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 6d0e3246-6c8f-498c-acd0-aa31a1f71d0a DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=jyB29Q2LzPWFPUvGKPl/gsfLUfGgJ8rUfV1MnY+Io0M=; b=ubRgVc06poyIUyyOFWksgOIFq0 ODRXpl7mkEvy2/aiMD5e10dkMICYY3Ce6C9NTr+FTqPmAglnsjpdbvNrugZULgukeFAHc2PNkq1tw 8L52cQGDGA86xqbe5Xy0VphLvgdk668/aW4CrjPIEzrZb/7hN1yWJxC33piYXCLBNKK1dcbUOMVcg sXpRkto21LyC6ZNF9xQx6Bwb00sThiXtJ5zGdVpQzUmNOZKaWTPblB3KOspjj/6xoySPR54nz1W8r ID1gnU4K45ClJToA/C0kbWfznccFvDZpI31KfVbzhimlyZK+eWaaxxd6qziskShTOa6ZoMWTILWnA UjsYHQYg==; Date: Thu, 7 Oct 2021 22:14:30 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: pvhgrub docs Message-ID: <20211007221430.rt6iq3ygoulreoh5@bitfolk.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Hi Chris, On Thu, Oct 07, 2021 at 07:09:35AM -0500, Chris Myers wrote: > Out of curiosity, could someone point me to some documentation for pvhgrub? I haven't found much, I've had to teach myself from other people's examples and some out of date articles on the Xen wiki. Here is what I learned so far and have had working for a year or so. If you're currently running a PV mode guest and it has a kernel of 4.19 or greater, you can/should change it to a PVH mode guest. You can also boot it using pvhgrub (instead of pvgrub, pygrub or direct kernel booting). Inside the domU all you need is a grub.cfg file generated that grub understands. The easiest way to do this in my experience is to actually install grub inside the guest, even though only its config file is needed. So inside a Debian guest you'd install grub-pc and make sure that the install process leaves you with a correct /boot/grub/grub.cfg. I didn't have to do anything special on Debian/Ubuntu to make it generate a correct config, and keep it up to date. On the dom0 the kernel file you use for PVH guests is a grub2 image built as a PVH binary. On Debian it can be found in the grub-xen-host package and once installed that lives at /usr/lib/grub-xen/grub-i386-xen_pvh.bin. I'll refer to that as "the pvhgrub image/binary". So in your domU config: […] type = pvh kernel = /usr/lib/grub-xen/grub-i386-xen_pvh.bin […] I recommend just comment out your existing "kernel", "ramdisk" and "extra" lines so you can put them back if this doesn't work. The default behaviour of that pvhgrub binary is to run grub and search all available block devices for the following file paths: /boot/grub/grub.cfg /grub/grub.cfg If it finds any such file then it assumes that is a grub config and loads it. The second path is for the case where /boot is its own block device. The path on that device would be /grub/grub.cfg. Thus, the domU admin can install their own kernels, initramfs and kernel command line arguments and boot them without dom0 admin assistance. The domU admin can do anything that grub can do, because it really is grub. The domU config file in dom0 doesn't have to be changed every time there is a kernel upgrade inside the guest. I personally wanted a bit more complex initial grub config because I also wanted it to search for /boot/grub2/grub.cfg (Red Hat / Fedora path) and /boot/grub/menu.lst (legacy grub config file), so I compile my own pvhgrub binary. Instructions for that are here: https://wiki.xenproject.org/wiki/Xen_4.12_RC_test_instructions#PVH_domU_boot_via_grub2 Except I seem to have modified my process a little: $ git clone https://git.savannah.gnu.org/git/grub.git $ cd grub $ ./configure --prefix=/opt/grub \ --target=x86-64 \ --with-platform=xenpvh && \ make && sudo make install $ edit /opt/grub/share/memdisk/grub.cfg # YOUR BOOTSTRAP CONFIG $ echo "normal (memdisk)/grub.cfg" | \ sudo tee /opt/grub/etc/grub-bootstrap.cfg $ sudo tar -C /opt/grub/share/memdisk \ -cvf /opt/grub/share/memdisk.tar grub.cfg && \ sudo /opt/grub/bin/grub-mkimage -O i386-xenpvh \ -c /opt/grub/etc/grub-bootstrap.cfg \ -m /opt/grub/share/memdisk.tar \ -o /opt/grub/lib/pvhgrub.bin \ -p /boot/grub \ -v /opt/grub/lib/grub/i386-xenpvh/*.mod So, that works for me, but you don't need to do any of that if you're happy with the Debian default behaviour of just looking for boot/grub.cfg on the domU's block devices. Even if you do want a different bootstrap behaviour maybe you can even get away without completely compiling your own pvhgrub binary — as I do there — by just coming up with your own config and using grub-mkimage from the package, I am doing this because I started before pvhgrub was packaged and only just committed in upstream grub. If you run into any trouble put back the "kernel", "ramdisk" and "extra" lines to return to a booting configuration for that domU. Perhaps some or all of this should go in an article on the Xen wiki. I do worry about it becoming yet another out of date reference though. Cheers, Andy From xen-users-bounces@lists.xenproject.org Thu Oct 07 22:26:29 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 07 Oct 2021 22:26:29 +0000 Received: from list by lists.xenproject.org with outflank-mailman.204104.359305 (Exim 4.92) (envelope-from ) id 1mYbqB-0001XI-9E; Thu, 07 Oct 2021 22:26:15 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 204104.359305; Thu, 07 Oct 2021 22:26:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYbqB-0001XA-5d; Thu, 07 Oct 2021 22:26:15 +0000 Received: by outflank-mailman (input) for mailman id 204104; Thu, 07 Oct 2021 22:26:14 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYbqA-0001X0-16 for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 22:26:14 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 9778f0b6-477f-47ac-b03d-bb91ab668b84; Thu, 07 Oct 2021 22:26:13 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mYbq7-0006kX-UK for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 22:26:11 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 9778f0b6-477f-47ac-b03d-bb91ab668b84 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=V1snvoPXU13h2fosBOcKPqgqcXXj7ERAJu0vLbZBgWc=; b=Z0WIBaHNUvuznzDT9yV/dFyehU hzO1t3MIo9GZ6HTccddd1uVTTNCKSVIF0yjcvRew4ObUJq0fWG35GWfTE9sQSSN0vWDgcFEu9QvsP ZHNJs7IeQBwS1TZ01fowYNwX9Pqt/pX8bwl3+GoeDV5Q1jweCtEaCiiKhozS8jNquK54uHqMcT23Q Hfk2fms2aWIwcUG6+UdNw1SzHhfogkAaaZnSBwXvYilqFI9R/v3n7/IWf0MaR+/VSXlxkIpxP1W5W NHJXMatFNdf0OEuZ6NGB6lk3gC6Ovp2+0ttSHs7CP0UUwex6Er2lsaiosJvf2VDwZ81I6kS5O2tSw paVJKoMA==; Date: Thu, 7 Oct 2021 22:26:11 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: pvhgrub docs Message-ID: <20211007222611.4gga6nmldr2wi6y6@bitfolk.com> References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> <051ed5a3-a668-950e-66d1-ca71d679628a@telus.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <051ed5a3-a668-950e-66d1-ca71d679628a@telus.net> OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Hello, On Thu, Oct 07, 2021 at 02:47:08PM -0700, David Hill wrote: > pvhgrub is new to me, but to understand the transition away from pygrub, I > found pvgrub2 documentation helpful (although some of it is a bit dated): > > https://wiki.xenproject.org/wiki/PvGrub2 Ah yes, that's another one I used to get the idea of the basic concept, and if you still need to run PV domains that would be the way to do it still. But if the guest kernel is new enough I recommend just go straight to PVH mode now, which for this style of booting does need grub compiled as --with-platform=xenpvh On Debian dom0 if you install grub-xen-host you get pvgrub images at: /usr/lib/grub-xen/grub-x86_64-xen.bin /usr/lib/grub-xen/grub-i386-xen.bin and pvhgrub image at: /usr/lib/grub-xen/grub-i386-xen_pvh.bin The PVH one should work for both 64- and 32-bit. If needing the specific one for 32-bit PV then bear in mind that: - there's no security support from Xen for that - 32-bit PV guest support is removed in 4.15 - support for booting as 32-bit PV guest was already removed in Linux kernel at v5.9. Cheers, Andy From xen-users-bounces@lists.xenproject.org Fri Oct 08 07:30:42 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Oct 2021 07:30:42 +0000 Received: from list by lists.xenproject.org with outflank-mailman.204434.359582 (Exim 4.92) (envelope-from ) id 1mYkKH-0006DI-Ft; Fri, 08 Oct 2021 07:29:53 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 204434.359582; Fri, 08 Oct 2021 07:29:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYkKH-0006DA-B7; Fri, 08 Oct 2021 07:29:53 +0000 Received: by outflank-mailman (input) for mailman id 204434; Fri, 08 Oct 2021 07:29:52 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYkKG-0006D4-Gs for xen-users@lists.xenproject.org; Fri, 08 Oct 2021 07:29:52 +0000 Received: from mail-vk1-xa2a.google.com (unknown [2607:f8b0:4864:20::a2a]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 41dd5d62-0164-4065-ba55-04c4e40b941e; Fri, 08 Oct 2021 07:29:51 +0000 (UTC) Received: by mail-vk1-xa2a.google.com with SMTP id 34so752975vkl.13 for ; Fri, 08 Oct 2021 00:29:51 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 41dd5d62-0164-4065-ba55-04c4e40b941e DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=sFPZPLHJGLzJ47cysOO8WyskWCvzjFXcJANWojAXwD4=; b=KeuEiHRoaiDMOhGqEtTTQ6buAM37n7QZJIeZsSz33iI3DFGJH5WG+Gejmsw2yT/i4V k+V1vl/g/wtyzFnikkaunak8ZMjaDyOC8W1FJNH3AgBFkjALahbKQgOjAXDeWiuFlXfE xMp7qjGO35eDoYgbEFRJob/mvxo+1ft/vSVSPXAUDKLJSolNU6NfI8v8BcsIvdxLQCGW tEz4suLfRSngpreWi74k1jKstxzHQr3Pl8S4Iml4K3cNdqycOvtdSYkxy84wsGirSIlR KBHKhG2XfbaWG8Y4+by1JkobtUWgq64c4vsu01Sti2gEHBjR+kJwh3HLpORIgELlEbe/ 7ivA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=sFPZPLHJGLzJ47cysOO8WyskWCvzjFXcJANWojAXwD4=; b=7zwxPVDq7YBkJmPkzs7bBSQVtsHYZljhMgdcU0JW0TF/+WpFYkkjiruPQcIBou85gP hCn9d5o70Vi/hfTfL9BNqGnX8SJt9v5yYzdzy+yr22xJRAd21RwdKysfNfHgABT5oseZ ClpTOGfWrJMpUzNZJ8Yz89IalYgqmIsJ9ea73kc8CW1WyPHj2bXCRwat+w74/nkiyrx1 E6JTqSY9L4jRMlONS4MPDg7o9gnv2fWiliExDfrHA2J1L/fNLPHL8KAFEdCzTRqQPWC0 Q8/yp1KTqiF0yltn7KndLy50wl11YmxFyiqQ50Ju4Sn9BqNSqURhZ8crBYV6kBVrY70+ leNw== X-Gm-Message-State: AOAM530T9DTkNIHOYJPnirT9xb2QgjGTHw5BYMrBuJliR0KdLpGY3zgM hHKP/Z0jEA+Km/gpCqINFd3Kej408hvwiXxZD88arPoa X-Google-Smtp-Source: ABdhPJwH5fNMuGJ6FbQFDeEPIJ5P1X3hOzTnP94wm+CM6e9q8aoUmy62NFtNLgP4s2kLK9E8YOO6QTHMge92xj6Pvxw= X-Received: by 2002:a1f:9713:: with SMTP id z19mr8167246vkd.13.1633678191494; Fri, 08 Oct 2021 00:29:51 -0700 (PDT) MIME-Version: 1.0 From: John Mok Date: Fri, 8 Oct 2021 15:29:40 +0800 Message-ID: Subject: OVMF SecureBoot guest To: xen-users@lists.xenproject.org Content-Type: text/plain; charset="UTF-8" Hi all, I am trying to install Windows 11 guest on Xen 4.14 (on Debian 11). How to configure xl.cfg for OVMF + SecureBoot ? Thanks a lot. John Mok From xen-users-bounces@lists.xenproject.org Fri Oct 08 11:53:16 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 08 Oct 2021 11:53:16 +0000 Received: from list by lists.xenproject.org with outflank-mailman.204673.359839 (Exim 4.92) (envelope-from ) id 1mYoQN-0002jB-3z; Fri, 08 Oct 2021 11:52:27 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 204673.359839; Fri, 08 Oct 2021 11:52:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYoQN-0002j3-0h; Fri, 08 Oct 2021 11:52:27 +0000 Received: by outflank-mailman (input) for mailman id 204673; Fri, 08 Oct 2021 11:52:25 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYoQL-0002ix-AI for xen-users@lists.xenproject.org; Fri, 08 Oct 2021 11:52:25 +0000 Received: from mail-vs1-xe29.google.com (unknown [2607:f8b0:4864:20::e29]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id d0a86263-9ed6-46b6-a49e-0666725573bb; Fri, 08 Oct 2021 11:52:24 +0000 (UTC) Received: by mail-vs1-xe29.google.com with SMTP id p18so10127582vsu.7 for ; Fri, 08 Oct 2021 04:52:24 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: d0a86263-9ed6-46b6-a49e-0666725573bb DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=DjJdbdknsGKKsUSE8hf4ZMJGm4CytP6/3XU42Kkhrtk=; b=hehtOBNJKcyFx81aattYQBSKvroB2I5LYmcvbWuBWT7kSe5vRkTd3U3aItDNb4cGYR 0KpfIpQnK9qmOKJYb8U0qZPQSq231EfneEIaHUBMraL4799c2I3yQg++mzlylTnjphDK ki8c8XUY50d7ttEXwSvPw9gxfkbga0O7VoU91LiaiCEyUeqiJjOMocCuTwJBRbHjEg2x KvnlSJIVyBnARlSnWln8MJ7TxI/7oOuw9fl68ku0eyfk2w3DcRLYOj5lixvVTRMxvTjO GwCrA9A0UspJjLPQ6Y9d9YFrAXUQUxbgnca0liNc7x5EQVo84ZNJvZ2XNxo0/jd1kPdK l4Fw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=DjJdbdknsGKKsUSE8hf4ZMJGm4CytP6/3XU42Kkhrtk=; b=0/Rs+EMkncVXPM5caGEKXbk6l+Xlipmn3TPQzs+GO9ysqmOgh1IAqfDub4WMmaaKlw LtBcacJj26C05tOldTZ88Up5oLS3opsShZ501BsxJCcUaXFM0WApJYbTscTs0fTwsQ86 qj2nG+dAXTK4VLAYq3N82+tjVoESa2vnL95MpbUMintUhe/uz16DDONp9DmWRuxYzIt2 aJlWc9xohbDt6GKTrsfzsY+Iavl8PZipK4WLSF8+jfBf2/MNhOhvpIRwU1Gef3rL7A9c irF9B+9UUXXi8v+kpHpY89mCVjhe3FInIOQ8axGqsBcv4LSneRUS2Mn6httFxcuCn++o 8VCQ== X-Gm-Message-State: AOAM531Um4x8W2z7AQv0TxkrjiieUOilaYn1LaImt37NDETgFEO/Ti/U S1OI5cSnHrgaDCY6lA4RjC6m9P0g7V56iuLquln2dtDW X-Google-Smtp-Source: ABdhPJxNMzQHEFOIwlZKBC+kG6kIlzzvYlvI5+SCpm8T+T+F7PrXZ75QZ+2/UPCvLJ6eKQ+8frdVUJWM4oiZP5ij1Ac= X-Received: by 2002:a05:6102:389:: with SMTP id m9mr9962161vsq.34.1633693944175; Fri, 08 Oct 2021 04:52:24 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> <051ed5a3-a668-950e-66d1-ca71d679628a@telus.net> <20211007222611.4gga6nmldr2wi6y6@bitfolk.com> In-Reply-To: <20211007222611.4gga6nmldr2wi6y6@bitfolk.com> From: Chris Myers Date: Fri, 8 Oct 2021 06:52:10 -0500 Message-ID: Subject: Re: pvhgrub docs To: Andy Smith , xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="00000000000036de0d05cdd60329" --00000000000036de0d05cdd60329 Content-Type: text/plain; charset="UTF-8" Awesome, thanks very much! I'll start playing around with it this weekend after I finish getting things upgraded. Have a great Friday! On Thu, Oct 7, 2021, 5:26 PM Andy Smith wrote: > Hello, > > On Thu, Oct 07, 2021 at 02:47:08PM -0700, David Hill wrote: > > pvhgrub is new to me, but to understand the transition away from pygrub, > I > > found pvgrub2 documentation helpful (although some of it is a bit dated): > > > > https://wiki.xenproject.org/wiki/PvGrub2 > > Ah yes, that's another one I used to get the idea of the basic > concept, and if you still need to run PV domains that would be the > way to do it still. > > But if the guest kernel is new enough I recommend just go straight > to PVH mode now, which for this style of booting does need grub > compiled as --with-platform=xenpvh > > On Debian dom0 if you install grub-xen-host you get pvgrub images > at: > > /usr/lib/grub-xen/grub-x86_64-xen.bin > /usr/lib/grub-xen/grub-i386-xen.bin > > and pvhgrub image at: > > /usr/lib/grub-xen/grub-i386-xen_pvh.bin > > The PVH one should work for both 64- and 32-bit. > > If needing the specific one for 32-bit PV then bear in mind that: > > - there's no security support from Xen for that > > - 32-bit PV guest support is removed in 4.15 > > - support for booting as 32-bit PV guest was already removed in > Linux kernel at v5.9. > > Cheers, > Andy > > --00000000000036de0d05cdd60329 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Awesome, thanks very much! I'll start playing around = with it this weekend after I finish getting things upgraded.

Have a great Friday!

On Thu, Oct 7, 202= 1, 5:26 PM Andy Smith <andy@strug= glers.net> wrote:
Hello,
On Thu, Oct 07, 2021 at 02:47:08PM -0700, David Hill wrote:
> pvhgrub is new to me, but to understand the transition away from pygru= b, I
> found pvgrub2 documentation helpful (although some of it is a bit date= d):
>
> https://wiki.xenproject.org/wiki/PvGrub2=

Ah yes, that's another one I used to get the idea of the basic
concept, and if you still need to run PV domains that would be the
way to do it still.

But if the guest kernel is new enough I recommend just go straight
to PVH mode now, which for this style of booting does need grub
compiled as --with-platform=3Dxenpvh

On Debian dom0 if you install grub-xen-host you get pvgrub images
at:

=C2=A0 =C2=A0 /usr/lib/grub-xen/grub-x86_64-xen.bin
=C2=A0 =C2=A0 /usr/lib/grub-xen/grub-i386-xen.bin

and pvhgrub image at:

=C2=A0 =C2=A0 /usr/lib/grub-xen/grub-i386-xen_pvh.bin

The PVH one should work for both 64- and 32-bit.

If needing the specific one for 32-bit PV then bear in mind that:

- there's no security support from Xen for that

- 32-bit PV guest support is removed in 4.15

- support for booting as 32-bit PV guest was already removed in
=C2=A0 Linux kernel at v5.9.

Cheers,
Andy

--00000000000036de0d05cdd60329-- From xen-users-bounces@lists.xenproject.org Sat Oct 09 15:26:44 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Oct 2021 15:26:44 +0000 Received: from list by lists.xenproject.org with outflank-mailman.204497.360395 (Exim 4.92) (envelope-from ) id 1mZEEg-0007sk-1K; Sat, 09 Oct 2021 15:26:06 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 204497.360395; Sat, 09 Oct 2021 15:26:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZEEf-0007qq-S6; Sat, 09 Oct 2021 15:26:05 +0000 Received: by outflank-mailman (input) for mailman id 204497; Fri, 08 Oct 2021 08:06:36 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYkto-0005If-Sr for xen-users@lists.xenproject.org; Fri, 08 Oct 2021 08:06:36 +0000 Received: from mail.kaminski-berlin.org (unknown [134.255.253.37]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 54d6fa5a-6eed-4dd0-bb3e-616dc4302c6a; Fri, 08 Oct 2021 08:06:35 +0000 (UTC) Received: from mail.home.chao5.net (mail.home.chao5.net [192.168.50.100]) by mail.chao5.net (Postfix) with ESMTP id A317280076A; Fri, 8 Oct 2021 10:06:34 +0200 (CEST) Received: from lucypher (localhost [127.0.0.1]) by mail.home.chao5.net (Postfix) with ESMTPA id 2D45C1FB066; Fri, 8 Oct 2021 10:06:34 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 54d6fa5a-6eed-4dd0-bb3e-616dc4302c6a Date: Fri, 8 Oct 2021 10:06:34 +0200 From: perun To: "John Mok" Cc: xen-users@lists.xenproject.org Message-ID: In-Reply-To: References: Subject: Re: OVMF SecureBoot guest MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="615ffc0a_28e2b02b_51b3" X-Synology-MCP-Status: no X-Synology-Spam-Flag: no X-Synology-Spam-Status: score=0.4, required 5, NO_RECEIVED -0.001, FROM_HAS_DN 0, TO_DN_SOME 0, __PDS_HTML_LENGTH_1024 0, __PDS_HTML_LENGTH_2048 0, MIME_GOOD -0.1, __THREADED 0, FREEMAIL_ENVRCPT 0, HTML_MISSING_CTYPE 0, RCPT_COUNT_TWO 0, HTML_MESSAGE 0.001, FREEMAIL_TO 0, RCVD_COUNT_ZERO 0, FROM_EQ_ENVFROM 0, MID_RHS_NOT_FQDN 0.5, TO_MATCH_ENVRCPT_ALL 0, __NOT_SPOOFED 0, MIME_TRACE 0, __KHOP_NO_FULL_NAME 0, __PDS_MSG_1024 0 X-Synology-Virus-Status: no --615ffc0a_28e2b02b_51b3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline for ovmf (I use it with Win10 DomU): type = "hvm" bios = 'ovmf' for TPM (I dont use it yet): vtpm=["backend=vtpmmgr,uuid=XXXXXXX"] see: https://mhsamsal.wordpress.com/2013/12/05/configuring-virtual-tpm-vtpm-for-xen-4-3-guest-virtual-machines/ Greetz Am 2021-10-08 09:29, John Mok schrieb: > > Hi all, > > I am trying to install Windows 11 guest on Xen 4.14 (on Debian 11). > How to configure xl.cfg for OVMF + SecureBoot ? > > Thanks a lot. > > John Mok > --615ffc0a_28e2b02b_51b3 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
for ovmf (I use it with Win10 DomU):
 
type =3D =22hvm=22
bios =3D 'ovmf'
 
for TPM (I dont use it yet):
 
vtpm=3D=5B=22backend=3Dvtpmmgr,uuid=3DXXXXXXX=22=5D
 
see: https://mhsamsal.wordpress.com/2013/12/05/configuring-virt= ual-tpm-vtpm-for-xen-4-3-guest-virtual-machines/
 
Greetz
 
 
Am 2021-10-08 09:29, John Mok <a9121431=40gmail.com> schrieb:<= /div> 
Hi all,

I am trying to install Windows 11 guest on Xen 4.=
14 (on Debian 11).
How to configure xl.cfg for OVM=46 + SecureBoot =3F=


Thanks a lot.

John Mok

--615ffc0a_28e2b02b_51b3-- From xen-users-bounces@lists.xenproject.org Sat Oct 09 15:26:44 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 09 Oct 2021 15:26:44 +0000 Received: from list by lists.xenproject.org with outflank-mailman.203833.360388 (Exim 4.92) (envelope-from ) id 1mZEEf-0007nT-KD; Sat, 09 Oct 2021 15:26:05 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 203833.360388; Sat, 09 Oct 2021 15:26:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZEEf-0007nI-Dn; Sat, 09 Oct 2021 15:26:05 +0000 Received: by outflank-mailman (input) for mailman id 203833; Thu, 07 Oct 2021 15:50:11 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mYVet-0007Zb-Ap for xen-users@lists.xenproject.org; Thu, 07 Oct 2021 15:50:11 +0000 Received: from mail.kaminski-berlin.org (unknown [134.255.253.37]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 3fac53d4-2786-11ec-bfe1-12813bfff9fa; Thu, 07 Oct 2021 15:50:09 +0000 (UTC) Received: from mail.home.chao5.net (mail.home.chao5.net [192.168.50.100]) by mail.chao5.net (Postfix) with ESMTP id 8382B80076A; Thu, 7 Oct 2021 17:50:08 +0200 (CEST) Received: from lucypher (localhost [127.0.0.1]) by mail.home.chao5.net (Postfix) with ESMTPA id D0FAE1F8879; Thu, 7 Oct 2021 17:50:06 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 3fac53d4-2786-11ec-bfe1-12813bfff9fa Date: Thu, 7 Oct 2021 17:50:06 +0200 From: perun To: "Pry Mar" Cc: xen-users Message-ID: <58270b57-4654-4692-9e90-17663240f88f@lucypher> In-Reply-To: References: Subject: Re: is there a repo for xen-4.15.1 in CentOS 8 ? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="615f172e_13d2714b_38e5" X-Synology-MCP-Status: no X-Synology-Spam-Flag: no X-Synology-Spam-Status: score=1.4, required 5, FROM_HAS_DN 0, TO_MATCH_ENVRCPT_ALL 0, FREEMAIL_ENVRCPT 0, MIME_GOOD -0.1, __THREADED 0, HTML_MISSING_CTYPE 0, TO_DN_ALL 0, RCPT_COUNT_TWO 0, HTML_MESSAGE 0.001, FREEMAIL_TO 0, RCVD_COUNT_ZERO 0, FROM_EQ_ENVFROM 0, SUBJECT_ENDS_QUESTION 1, MID_RHS_NOT_FQDN 0.5, __NOT_SPOOFED 0, MIME_TRACE 0, __KHOP_NO_FULL_NAME 0, NO_RECEIVED -0.001 X-Synology-Virus-Status: no --615f172e_13d2714b_38e5 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline not an official one.... https://cbs.centos.org/kojifiles/repos/virt8-xen-415-el8-build/latest/x86_64/ it works here very good as long I use UEFI boot for Win10 :)... the pvh linux domU's working great. If I use SeaBIOS with Win10 it doesnt start... Am 2021-10-07 17:43, Pry Mar schrieb: > > hello xen-users, > > https://lists.xenproject.org/archives/html/xen-users/2021-10/msg00015.html > > in the above post was mentioned CentOS 8 xen-4.15.1 RPM's. > Here is how to browse the said package set, starting with the repo file: > > -- virt8-xen.repo --- > [centos-virt-xen-415] > name=CentOS-$releasever - xen-415 > baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-415 > gpgcheck=1 > enabled=0 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization > > [centos-virt-xen-415-testing] > name=CentOS-$releasever - xen-4.15 - testing > baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-415 > gpgcheck=0 > enabled=0 > gpgke y=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization > > -- unsnip -- > > sh-4.4# dnf list available --disablerepo=\* > --enablerepo=centos-virt-xen-415-testing > CentOS-8 - xen-4.15 - testing > 345 kB/s | 572 kB 00:01 > Available Packages > centos-release-xen.x86_64 10:9-1.el8 > centos-virt-xen-415-testing > centos-release-xen-412.x86_64 10:9-1.el8 > centos-virt-xen-415-testing > centos-release-xen-common.x86_64 10:9-1.el8 > centos-virt-xen-415-testing > kernel.x86_64 5.4.43-2.el8 > centos-virt-xen-415-testing > kernel-devel.x86_64 5.4.43-2.el8 > centos-virt-xen-415-testing > kernel-doc.noarch 5.4.43-2.el8 > centos-virt-xen-415-testing > kernel-headers.x86_64 5.4.43-2.el8 > centos-virt-xen-415-testing > perf.x86_64 5.4.43-2.el8 > centos-virt-xen-415-testing > qemu-xen.x86_64 4.15.0-1.el8 > centos-virt-xen-415-testing > xen.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-devel.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-doc.x86_64 4.15.1-1 .el8 > centos-virt-xen-415-testing > xen-hypervisor.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-libs.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-licenses.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-livepatch-build-tools.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-ocaml.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-ocaml-devel.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > xen-ovmf.x86_64 > 202102-1.gitef91b07388e1.el8 > centos-virt-xen-415-testing > xen-runtime.x86_64 4.15.1-1.el8 > centos-virt-xen-415-testing > sh-4.4# dnf provides '/usr/bin/qemu-img' > --enablerepo=centos-virt-xen-415-testing > Last metadata expiration check: 0:00:46 ago on Wed Sep 22 12:38:52 2021. > Error: No Matches found > > cheers, > PryMar56 > ##xen-packaging on OFTC > --615f172e_13d2714b_38e5 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
not an official one....
 
https://cbs.cento= s.org/kojifiles/repos/virt8-xen-415-el8-build/latest/x86=5F64/
it works here very good as long I use UE=46I boot for Win10 :)... th= e pvh linux domU's working great.
If I use SeaBIOS with Win10 it doesnt start...
Am 2021-10-07 17:43, Pry Mar <pryorm09=40gmail.com> schrieb: 
hello xen-users,

https://lists.xenproject.org/archives/ht=
ml/xen-users/2021-10/msg00015.html

in the above post was menti=
oned CentOS 8 xen-4.15.1 RPM's.
Here is how to browse the said packa=
ge set, starting with the repo file:

 -- virt8-xen.repo ---=5Bcentos-virt-xen-415=5D
name=3DCentOS-=24releasever - xen-415baseurl=3Dhttp://mirror.centos.org/centos/=24releasever/virt/=24basea=
rch/xen-415
gpgcheck=3D1
enabled=3D0
gpgkey=3Dfile:///etc/=
pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization

=5Bcentos-vi=
rt-xen-415-testing=5D
name=3DCentOS-=24releasever - xen-4.15 - testi=
ng
baseurl=3Dhttp://buildlogs.centos.org/centos/=24releasever/virt/=24=
basearch/xen-415
gpgcheck=3D0
enabled=3D0
gpgkey=3Dfile://=
/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization

 -- uns=
nip --

<mock-chroot> sh-4.4=23 dnf list available --disa=
blerepo=3D=5C*
--enablerepo=3Dcentos-virt-xen-415-testing
CentO=
S-8 - xen-4.15 - testing
                   345 kB/s =7C 572 kB     =
00:01
Available Packages
centos-release-xen.x86=5F64           =
             10:9-1.el8
                        centos-virt-xen-415-=
testing
centos-release-xen-412.x86=5F64                    10:9-1.el=
8
                        centos-virt-xen-415-testing
centos-re=
lease-xen-common.x86=5F64                 10:9-1.el8
               =
         centos-virt-xen-415-testing
kernel.x86=5F64                =
                    5.4.43-2.el8
                        centos-virt=
-xen-415-testing
kernel-devel.x86=5F64                              =
5.4.43-2.el8
                        centos-virt-xen-415-testing
kernel-doc.noarch                                5.4.43-2.el8
    =
                    centos-virt-xen-415-testing
kernel-headers.x86=5F=
64                            5.4.43-2.el8
                        c=
entos-virt-xen-415-testing
perf.x86=5F64                            =
          5.4.43-2.el8
                        centos-virt-xen-415-t=
esting
qemu-xen.x86=5F64                                  4.15.0-1.e=
l8
                        centos-virt-xen-415-testing
xen.x86=5F=
64                                       4.15.1-1.el8
              =
          centos-virt-xen-415-testing
xen-devel.x86=5F64            =
                     4.15.1-1.el8
                        centos-vir=
t-xen-415-testing
xen-doc.x86=5F64                                  =
 4.15.1-1.el8
                        centos-virt-xen-415-testingxen-hypervisor.x86=5F64                            4.15.1-1.el8
 =
                       centos-virt-xen-415-testing
xen-libs.x86=5F64=
                                  4.15.1-1.el8
                     =
   centos-virt-xen-415-testing
xen-licenses.x86=5F64                =
              4.15.1-1.el8
                        centos-virt-xen-4=
15-testing
xen-livepatch-build-tools.x86=5F64                 4.15.1=
-1.el8
                        centos-virt-xen-415-testing
xen-=
ocaml.x86=5F64                                 4.15.1-1.el8
        =
                centos-virt-xen-415-testing
xen-ocaml-devel.x86=5F64=
                           4.15.1-1.el8
                        cent=
os-virt-xen-415-testing
xen-ovmf.x86=5F64
202102-1.gitef91b0738=
8e1.el8
centos-virt-xen-415-testing
xen-runtime.x86=5F64       =
                        4.15.1-1.el8
                        centos-=
virt-xen-415-testing
<mock-chroot> sh-4.4=23  dnf provides '/u=
sr/bin/qemu-img'
--enablerepo=3Dcentos-virt-xen-415-testing
Las=
t metadata expiration check: 0:00:46 ago on Wed Sep 22 12:38:52 2021.
Error: No Matches found

cheers,
PryMar56
 =23=23xe=
n-packaging on O=46TC

--615f172e_13d2714b_38e5-- From xen-users-bounces@lists.xenproject.org Sun Oct 10 09:03:14 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 10 Oct 2021 09:03:14 +0000 Received: from list by lists.xenproject.org with outflank-mailman.205267.360537 (Exim 4.92) (envelope-from ) id 1mZUin-0008KT-UY; Sun, 10 Oct 2021 09:02:17 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 205267.360537; Sun, 10 Oct 2021 09:02:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZUin-0008KK-Qo; Sun, 10 Oct 2021 09:02:17 +0000 Received: by outflank-mailman (input) for mailman id 205267; Sun, 10 Oct 2021 09:02:16 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZUim-0008KE-CB for xen-users@lists.xenproject.org; Sun, 10 Oct 2021 09:02:16 +0000 Received: from mail-vs1-xe35.google.com (unknown [2607:f8b0:4864:20::e35]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id bc5ba95b-e671-40fb-b75a-0e2045b1f747; Sun, 10 Oct 2021 09:02:15 +0000 (UTC) Received: by mail-vs1-xe35.google.com with SMTP id w13so15503497vsa.2 for ; Sun, 10 Oct 2021 02:02:15 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: bc5ba95b-e671-40fb-b75a-0e2045b1f747 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZwuQYr9SQZv0L0bHIn+d4FP1NMKx7wkw7N4xBFOoW5c=; b=TZgSLY3KowoQ1UI1EiOZuUqPxYhHROdlMX70F3xZUAnJeyWAbfmnAMnLx8Rgp1seaF DkMhodvyEcHGUbJWCG+gwTs/40k2OXdyPK3gel9qdVk0zSTVdB7cQDTJ1qeBB7FK4jf0 vcLQIJ4E9UzC9eUHuQfKtl4edUNi387ktZXrrpfDijA8O40feojN3EKC8Gjn1sGrN6b6 82P4DRC82gTuk0eqLNL9PiOPN5vrHc1KZ675fg6iG3E+3DUVEE642rJmSC0Mcj6mAe4k DIaAcVjKf0Lf31k4Y2TakjCeHUatci00D/626TwfHB+P0oLkJ8A27wocW0Zm4esvNg1a 2U0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZwuQYr9SQZv0L0bHIn+d4FP1NMKx7wkw7N4xBFOoW5c=; b=6XItIb+reHCkz8QzEijpuq83ZU+hY5iLt2E3QyNiTVkDPn8dZvH//77XdViuwsRPN4 4/RSH/YZIwIOjSsYj/ATyY8+DZVrKsXrZdPcK+P/M4Ay7aQraNlbcsArUcJ0Mc7fosf8 iUuz5QTlh+sqTQNDw9Sfjm1cxkTmW4UnenRoDcZ9PCogIiJjAaTXvVJEjrjbYpeCTjIs 1DoRwWueI2IGUdE9pb/g5/n5DX+jY+k0Zy24JnJCG1qHN+Q/HyLxsYcPSHRyUoudkicX AIJLQ1PgfgKgCW3zDQxg89iDMfzM3tMEmZjbQCK1KOjJ2vXL+6qsno4zwQIxwo0SYJP1 kjfw== X-Gm-Message-State: AOAM533Ulki20GAwvb4C9XvYqyycZFzKveeXOjGwrfsPGYlt+XndrL/e PAy76TVR629bWHwClC6xt3YdPVm3VC4+Ctb2ysoSiw1J8A== X-Google-Smtp-Source: ABdhPJzEbVm9sShlHjQme2vRNt2yO2C572cQMtb2q9Gw5FAIX4UWZQTVhEOE10UjJjZ+A79ZqMy6kUsWi0F0jPvuDfo= X-Received: by 2002:a67:ab04:: with SMTP id u4mr18573552vse.12.1633856534991; Sun, 10 Oct 2021 02:02:14 -0700 (PDT) MIME-Version: 1.0 References: <20211004195010.earbegnpot3xr4ok@bitfolk.com> <20211005001736.tkswi2a4ii6jg3ic@bitfolk.com> <20211005012814.27dtuvhvo3jjjkfw@bitfolk.com> <20211005013837.ka625tea5kd4h2qo@bitfolk.com> <051ed5a3-a668-950e-66d1-ca71d679628a@telus.net> <20211007222611.4gga6nmldr2wi6y6@bitfolk.com> In-Reply-To: From: TMC Date: Sun, 10 Oct 2021 20:02:03 +1100 Message-ID: Subject: Re: pvhgrub docs To: Chris Myers , xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="00000000000061d6d705cdfbdedf" --00000000000061d6d705cdfbdedf Content-Type: text/plain; charset="UTF-8" On Fri, 8 Oct 2021 at 22:53, Chris Myers wrote: > Awesome, thanks very much! I'll start playing around with it this weekend > after I finish getting things upgraded. > > Have a great Friday! > > On Thu, Oct 7, 2021, 5:26 PM Andy Smith wrote: > >> Hello, >> and pvhgrub image at: >> >> /usr/lib/grub-xen/grub-i386-xen_pvh.bin >> >> The PVH one should work for both 64- and 32-bit. >> >> it does work very well indeed Cheers, Tomasz --00000000000061d6d705cdfbdedf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, 8 Oct 2021 at 22:53, Chris My= ers <chrismyers81@gmail.com> wrote:
Awesome, thanks very much! I'll start playing around wit= h it this weekend after I finish getting things upgraded.
=
Have a great Friday!

On Thu, Oct 7, 2021,= 5:26 PM Andy Smith <andy@strugglers.net> wrote:
Hello,
and pvhgrub image at:

=C2=A0 =C2=A0 /usr/lib/grub-xen/grub-i386-xen_pvh.bin

The PVH one should work for both 64- and 32-bit.


it does work very w= ell indeed

Cheers,
Tomasz
--00000000000061d6d705cdfbdedf-- From xen-users-bounces@lists.xenproject.org Thu Oct 14 18:37:42 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 14 Oct 2021 18:37:42 +0000 Received: from list by lists.xenproject.org with outflank-mailman.209567.366066 (Exim 4.92) (envelope-from ) id 1mb5b4-0000S3-Ar; Thu, 14 Oct 2021 18:36:54 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 209567.366066; Thu, 14 Oct 2021 18:36:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mb5b4-0000Rv-78; Thu, 14 Oct 2021 18:36:54 +0000 Received: by outflank-mailman (input) for mailman id 209567; Thu, 14 Oct 2021 18:36:52 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mb5b1-0000Rp-RV for xen-users@lists.xenproject.org; Thu, 14 Oct 2021 18:36:52 +0000 Received: from wilkes.com (unknown [46.226.110.80]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTP id b111aa01-2d1d-11ec-81d4-12813bfff9fa; Thu, 14 Oct 2021 18:36:50 +0000 (UTC) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: b111aa01-2d1d-11ec-81d4-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wilkes.com; s=default; t=1634236610; bh=QJmeDYQAM3OYOyKG8Qh2Y2/O8Zj/fNOwzu+cabd5FRc=; h=To:From:Subject:Date; b=Z4w82AWrvVeBq/d2gjeBIw5bgTXYgpG8hzUl/hC+VNs1+qQsYP7KDkMI171bIL/DL gcKHJUXGrpwMAqYGdDoxKzDj65w/0FJmH0rNrNOXnC4HPW8OL5o++nem/E1NF6oDrz lT3rjd7Uy5Q4Sv9yIWs5vnYC9xWjJeC4XgEsP61P8SrRVa3tAlfHYVFfxeyFw+0vpQ LxwhoTQJUqH6pLr8FhZpW+md+eMXaGOLD9PS6XP8y6oh0OTZWxxBdXk0i7f6M2ngob vp/PigneTi+h2I7beW1M0fVuBPUbKdL14S/mPTfmtEEIvVpcHLjcoFpGqw6Cen4PRc j+rHjGau07C7Q== X-Default-Received-SPF: pass (skip=forwardok (res=PASS)); To: xen-users@lists.xenproject.org From: John Wilkes Autocrypt: addr=john@wilkes.com; keydata= xsFNBFQ/5IsBEADCIeAJbDETgmrrQOEdRRngd1lcchWtqGKI+qAuEDFH2vcDWbCJeQyasRAx CWbwd/R96ZyugbK8P8vqVFX2/j9wItHNtni0xfikqvBWhbNqTL7VE3jh4NBSJhPJZPUm5/ZI +JUXIafOw3AtHzkzi1g02t63L8ZlJbXuZP19S8ntPiDFOLWyD6jnE5mcrPkLyVmmwHf0OnHO eLDTgVqZhCvd6E2nlwW3DhNWchvdjpt6FfZj0a3RizwZqbZjOjGPCLNca2IXKFl8yhvJzRBR dkFqMtxKVqGUGEX21hzbkiYaHMVtcKSRCWq0t54BZI0vY87LVV6xtgC+2UfcWvH8jN3igVzI Yh4UH8w7EuCMpD2g2pHU4AM7QUS5XFpPXwHk/97DQOuaGKXQpvYalE52n0XGHCWuwfNf/iJ9 pJ28fAsmVbr78P3fyjvW0J5PjCZtloaUH4BDXCFKFtRnNc+XG1kP3Ub5GXx/Uks/WYjlSJtU YQi7Qzhe7h66mPeCwsUvrilfOtTX7f7dap7tqtOUrHr1TDZNHaz/Pye6ZM65sSnqrXQk81sm 1pxbDDn1kbK3B/JLNthqQiVUmeuNXtgKhuQTRx9jVg7MVrvrNS6iVVcfuFNFdqvLhYdXKWZ1 W49e5Z7JQMmFyMIZqEV+TLFYh4UxVpy4AIhV0ZBFp3Y58GmbNwARAQABzR1Kb2huIFdpbGtl cyA8am9obkB3aWxrZXMuY29tPsLBdwQTAQoAIQIbAwULCQgHAwUVCgkICwUWAgMBAAIeAQIX gAUCX3db9AAKCRBmMvbqwgnCFvLYD/92yfxd4dIeXhAQnc7rSnl8lZwNA6huZFqvO3r+NNYW cjreVl6SR0J2Xi8tNbx2VeChoPCmKu123DgbXxq+jyS3cF+8U2g+lur6Dnlby5TAvQSbgkoJ WOLDFPRQXPlIAJQtUubL2nQSk+hGoeC5rC/rRloTvmVmZ5GazA2YO7we6quoZ+BXUCtfp53u TZvgUHzizs1spXlnuplAVygAvVzFe0ZBT2+MgcP5/WaF4SnevZvpkxzjzQ3qoaw5Hwukx16W Hab+U+rEFRXc9EmAXSmUph8JWeoOiE2D5etiv848UBnywyP4xpxyZVU1M+3PRngPVYcSyWsZ IJDMZf9wv5z6crM/sdqHnj4f1rJxyKo/mRoP2rlSWs0taZIQ/TxoRl+LVNMpxnRpBs+wDNel HQ0wURTkPlhy4qtoiNFFuhGQ7rC50YTTEMHeAns8TsqC6gjYK6yK9lJ5fWawGlVBd735wHvI lLeb1e76k2dOwgmEuau8rpXEBLOjzyI8CMf56Ug50WABmz322OqM8MsPgArZxkxW/TKdw0Pq Dkw2nH4xc2d22Rqz7bF6UZyiDInOXviX8nUw/P+VAhEJTXXzjNzRHzYWG4oYhaJogMBk7YgN 4Xwz19E9QOTPAcJt5uElk4rbbNAhr+fJqczvHxlYVazjjdc79GKanqMTFcxs6n0GjM7BTQRU P+SLARAAws26GPShh1t/UgljUO9VZjrgMvXu0cb4N8Yhrn2gwrFVz81bgy2NCRpXp9wPXKuB Lwkzbj2lNIb4iI98Q6X3aAzGEFaT9p/XwVpUc3TAKrtjEcXzUMqdkR9t7tHzxNxp2l0luKmx 1vEMVl6M/6mMsFEIgpTAc+nPjt3k4vivPiPzNhC+9UAh34dwh3XzdzUxFc2Kgbwi2TbWpFR1 nZmnXG3m1fpanT/qpQ8zRATHsJXWQ+8YQs4IzSDbSG8lIJuaRcTkXI0EEUvgFtj7myqWY04N MRHurZ3J+CyFsBHfVX1IysBOtz9mtKNK5JyJPpHyAb5COC0mWgQ8MYdXkuq4ypO12KSjw3In JsHzfg7Wc2hyPLavfiVDnbBAUtAJLqtJgZlz55cWLcussY/DrxVqRWVZo+dQQ/AsukOB56If SeuaGfCRZ2YwAMD9u3pznXUjqK0Z88xG4XL6TAqo6GfeEK0UTUeNXKzMCTUbU09EwvTFmUUj GkG58wN2bGqZYvu29wPz/w5SnjpmqRihgiv3asCNLxUZhcpnX7aSGEfKrO/ZnFlm4zFWxjc0 dInKC6jc+fDmfvifLhKqh0OV5q4VYcnDHHgn3RPHrQxKG2QD2ZHyuDuSDYBNC0tnPCUiO1Za 74jTNyRKYwMVLRbnjZpLbzH+nm9YbifJabL4EfqjafcAEQEAAcLBXwQYAQoACQIbDAUCX3db 9gAKCRBmMvbqwgnCFuRPD/9W9e9BGt0XSb5mbWaNQRiBq/Kr/ISvNSPvRIrsf/RPYUFm/R3J 8df+h5Q54lnRx6RzrK+9n2j78jURtKPnmPEtu8fiXm7NblheAyaE6PTryfaJSqwx0XZGth3g BgLzvTt9UDghsmpUeFCgBtT6oKEbJ7eOwSCKPu9S0dpkhR00BuxlXRiZjxSCw5FAh04hwLS0 q+W4aRoL67SNfrXXK5/JSTZW++IhdTvNGYz8nPtOZIeyBO0v7Z7JtMSxIVMA+Qt57Udt9Or6 a4XhDux9gEMKbor8NMxQIXOsFvlFobBd9VHxX+gRYfu7ErjjVmz2zOCNqWFamL+Q9T8PXqKh LOkinUwQGn7r8gEethv7H7RzOCaK357pXOALDhJrMaQFruUWHY4yW5Ok95zhqmfMSYcbxfCe 9pKlYsfUazrJ5g7MQnCMj1j4eNJjOPkEhmRUQNTO/y1An5oBAvTmC+ubCudJImFouRanqj5a VTqChSj8f38d/rO3/emrembyb9ntX4pgdDhS4dOXN2CN/FHD8ARd7pIEjVE2/9lVs2aOQeeJ UM0VeFijgTylTvaJQvq/gjphdc9ioJivfO04n3JNtTSi9fcw2kJirFgSNtS4ryXQ8D6h3R9O +/tU76sTgTOySZuA/mHx2p7RW9ihwNhFcimfHl8o+Z7Cy6l71fdPUBU5xA== Subject: option for memory backed by hugepages? Message-ID: <65a95add-12a0-9920-f1c1-bdaf1f826109@wilkes.com> Date: Thu, 14 Oct 2021 10:20:21 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------A448790BE2BE8E050A7C28BF" Content-Language: en-US X-Authenticated-User: john@wilkes.com This is a multi-part message in MIME format. --------------A448790BE2BE8E050A7C28BF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable I need to guarantee that allocating 2MB using mmap() with the=20 MAP_HUGETLB flag on a HVM will get a contiguous 2MB huge page in system=20 memory.=C2=A0 HAP is enabled.=C2=A0 This is for some specialized hardware= that=20 requires 2MB of contiguous DRAM, and it will not function properly if=20 the allocated memory uses 4KB pages that appear contiguous in virtual=20 space but are not physically contiguous in system DRAM. It functions correctly running in a non-virtualized host environment if=20 a sufficient number of huge pages is reserved in /proc/sys/vm/nr_hugepage= s. There is a qemu configuration option for guest memory to be backed by=20 huge pages: =C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0 I have confirmed that contiguous 2MB pages are allocated in system=20 physical memory with mmap() and MAP_HUGETLB on a guest VM if the qemu=20 guest's memory is configured to be backed by hugepages. Is there a similar mechanism in Xen that will guarantee that a HVM will=20 get a contiguous 2MB huge page in system DRAM? John --=20 john@wilkes.com --------------A448790BE2BE8E050A7C28BF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

I need to guarantee that allocating 2MB using mmap() with the MAP_HUGETLB flag on a HVM will get a contiguous 2MB huge page in system memory.  HAP is enabled.  This is for some specialized hardware that requires 2MB of contiguous DRAM, and it will not function properly if the allocated memory uses 4KB pages that appear contiguous in virtual space but are not physically contiguous in system DRAM.

It functions correctly running in a non-virtualized host environment if a sufficient number of huge pages is reserved in /proc/sys/vm/nr_hugepages.

There is a qemu configuration option for guest memory to be backed by huge pages:

  <memoryBacking>
    <hugepages/>
  </memoryBacking>

I have confirmed that contiguous 2MB pages are allocated in system physical memory with mmap() and MAP_HUGETLB on a guest VM if the qemu guest's memory is configured to be backed by hugepages.

Is there a similar mechanism in Xen that will guarantee that a HVM will get a contiguous 2MB huge page in system DRAM?

John


--
john@wilkes.com
--------------A448790BE2BE8E050A7C28BF-- From xen-users-bounces@lists.xenproject.org Sun Oct 17 17:28:01 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 17 Oct 2021 17:28:01 +0000 Received: from list by lists.xenproject.org with outflank-mailman.211617.369237 (Exim 4.92) (envelope-from ) id 1mc9wA-0001Jb-QA; Sun, 17 Oct 2021 17:27:06 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 211617.369237; Sun, 17 Oct 2021 17:27:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mc9wA-0001JQ-Kr; Sun, 17 Oct 2021 17:27:06 +0000 Received: by outflank-mailman (input) for mailman id 211617; Sun, 17 Oct 2021 17:27:04 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mc9w8-0001JK-Qh for xen-users@lists.xenproject.org; Sun, 17 Oct 2021 17:27:04 +0000 Received: from relay1-d.mail.gandi.net (unknown [217.70.183.193]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 707428ac-2f6f-11ec-82b4-12813bfff9fa; Sun, 17 Oct 2021 17:27:02 +0000 (UTC) Received: (Authenticated sender: 05jvjfy5ih8ta49jg57xnuh3@helkyn.org) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 0F64D240004 for ; Sun, 17 Oct 2021 17:27:00 +0000 (UTC) Received: by smtp.helkyn.org (Postfix) with ESMTPSA id 523D5C3CF6 for ; Sun, 17 Oct 2021 19:27:00 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 707428ac-2f6f-11ec-82b4-12813bfff9fa Message-ID: <8e9b9e53-5312-f0ab-7b1c-48ae8ae88124@NetBSD.org> Date: Sun, 17 Oct 2021 19:26:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Content-Language: fr To: xen-users@lists.xenproject.org From: Jean-Yves Migeon Subject: Can't create domain with AWS metal instances (latest Xen/Linux revs) Organization: NetBSD Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dear list, While attempting to run Xen on AWS metal instances, I am facing an issue that ressembles the one Tamas (K Lengyel) faced months ago [1]. I have tested this on various variations of CPU revisions and kernels (Linux 5.4 to 11, Xen 4.15), even latest Linux revisions are susceptible to this behavior; as it is a bit cumbersome to trace down xl stack, I have not found yet what happens. Creating new domains seem to fail due to timeouts waiting for block/vbd to switch to later "running" states within xenstore. In my setup it seems specific to block/vbd (I cannot reproduce a similar issue with vif devices). I have not tested with other revisions of Xen, although I doubt the hypervisor has anything to deal with here. It properly allocated the pages and wait to unpause domain when VMM is ready. Does that ring a bell to someone? FWIW the patches mentioned in the original mail thread are applied (or have been backported). Verbose output of a (failed) xl create is attached below, with the xl.cfg file and xenstore-ls /libxl/5 (the domid of the failed domain). Nothing specific logged on dmesg, xl dmesg, or xenstored. The xenstore-ls dump looks like typical entry nodes for a vbd device that stays in init state. Any advice/pointers appreciated; keep me CC please. Thanks [1] https://lore.kernel.org/xen-devel/CABfawh=fNCxQs+QBsYw5StA+vNwqzyQUHyiib3_rujDS1W8S9A@mail.gmail.com/ -- jym@NetBSD.org ====== xl create verbose output ====== # xl -v create debian.cfg Parsing config from debian.cfg libxl: detail: libxl_dom.c:182:numa_place_domain: NUMA placement candidate with 1 nodes, 36 cpus and 256763 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="(null)", features="(null)" domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen-4.15/boot/hvmloader" domainbuilder: detail: xc_dom_malloc_filemap : 174 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.15, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 domainbuilder: detail: xc_dom_parse_image: called domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying HVM-generic loader ... domainbuilder: detail: loader probe OK xc: detail: ELF: phdr: paddr=0x100000 memsz=0x350a4 xc: detail: ELF: memory: 0x100000 -> 0x1350a4 domainbuilder: detail: xc_dom_mem_init: mem 2040 MB, pages 0x7f800 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x7f800 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: xc_dom_malloc : 4080 kB xc: detail: PHYSICAL MEMORY ALLOCATION: xc: detail: 4KB PAGES: 0x0000000000000200 xc: detail: 2MB PAGES: 0x00000000000003fb xc: detail: 1GB PAGES: 0x0000000000000000 domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x100+0x36 at 0x7f74a9265000 domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x100000 -> 0x136000 (pfn 0x100 + 0x36 pages) xc: detail: ELF: phdr 0 at 0x7f74a922f000 -> 0x7f74a925a620 domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x136+0x40 at 0x7f74a9225000 domainbuilder: detail: xc_dom_alloc_segment: System Firmware module : 0x136000 -> 0x176000 (pfn 0x136 + 0x40 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x176+0x1 at 0x7f74a9318000 domainbuilder: detail: xc_dom_alloc_segment: HVM start info : 0x176000 -> 0x177000 (pfn 0x176 + 0x1 pages) domainbuilder: detail: alloc_pgtables_hvm: doing nothing domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x177000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 domainbuilder: detail: clear_page: pfn 0xfefff, mfn 0xfefff domainbuilder: detail: clear_page: pfn 0xfeffc, mfn 0xfeffc domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 4085 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 174 kB domainbuilder: detail: domU mmap : 476 kB domainbuilder: detail: vcpu_hvm: called domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff001 domainbuilder: detail: xc_dom_release: called libxl: error: libxl_device.c:1075:device_backend_callback: Domain 5:unable to add device with path /local/domain/0/backend/vbd/5/51712 libxl: error: libxl_create.c:1249:domcreate_launch_dm: Domain 5:unable to add disk devices libxl: error: libxl_device.c:1075:device_backend_callback: Domain 5:unable to remove device with path /local/domain/0/backend/vbd/5/51712 libxl: error: libxl_domain.c:1075:devices_destroy_cb: Domain 5:libxl__devices_destroy failed libxl: error: libxl_domain.c:1003:libxl__destroy_domid: Domain 5:Non-existant domain libxl: error: libxl_domain.c:962:domain_destroy_callback: Domain 5:Unable to destroy guest libxl: error: libxl_domain.c:889:domain_destroy_cb: Domain 5:Destruction of domain failed # ====== debian.cfg ====== name = "debian" builder = "hvm" vcpus = 1 maxvcpus = 1 memory = 2048 maxmem = 2048 hap = 1 boot = "cd" serial='pty' vif = ['bridge=bridge0'] #vfb = ['vnc=1,vncdisplay=0,vncpasswd=foobar,vnclisten=127.0.0.1'] usb = 1 #usbdevice = ['tablet'] nomigrate = 1 #disk = ['file:/home/ubuntu/VMs/debian/debian11.vmdisk,xvda,w'] disk = ['file:/home/ubuntu/VMs/debian/debian.vmdisk,xvda','file:/home/ubuntu/VMs/debian/debian.iso,xvdc,cdrom'] ====== xenstore-ls /libxl/5 ====== # xenstore-ls /libxl/5 device = "" vbd = "" 51712 = "" frontend = "/local/domain/5/device/vbd/51712" backend = "/local/domain/0/backend/vbd/5/51712" params = "/home/ubuntu/VMs/debian/debian.vmdisk" script = "/etc/xen/scripts/block" frontend-id = "5" online = "1" removable = "0" bootable = "1" state = "1" dev = "xvda" type = "phy" mode = "w" device-type = "disk" discard-enable = "1" 51744 = "" frontend = "/local/domain/5/device/vbd/51744" backend = "/local/domain/0/backend/qdisk/5/51744" params = "aio:/home/ubuntu/VMs/debian/debian.iso" frontend-id = "5" online = "1" removable = "1" bootable = "1" state = "1" dev = "xvdc" type = "qdisk" mode = "r" device-type = "cdrom" discard-enable = "0" dm-version = "qemu_xen" From xen-users-bounces@lists.xenproject.org Tue Oct 19 09:55:30 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Oct 2021 09:55:30 +0000 Received: from list by lists.xenproject.org with outflank-mailman.212910.370964 (Exim 4.92) (envelope-from ) id 1mclpN-0001iH-Ki; Tue, 19 Oct 2021 09:54:37 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 212910.370964; Tue, 19 Oct 2021 09:54:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mclpN-0001i7-Ge; Tue, 19 Oct 2021 09:54:37 +0000 Received: by outflank-mailman (input) for mailman id 212910; Tue, 19 Oct 2021 09:54:36 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mclpM-0001i1-1f for xen-users@lists.xenproject.org; Tue, 19 Oct 2021 09:54:36 +0000 Received: from mout.gmx.net (unknown [212.227.15.18]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id a5065dbc-6a67-41d9-9bbc-e1b8533d3187; Tue, 19 Oct 2021 09:54:34 +0000 (UTC) Received: from lucypher ([91.65.29.128]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M3lY1-1mcUqR3dAJ-000vB1 for ; Tue, 19 Oct 2021 11:54:32 +0200 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: a5065dbc-6a67-41d9-9bbc-e1b8533d3187 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1634637273; bh=naf74+LORAV5CXpBXL3Lr1poPOk5ZMxcDubf2HlfHG4=; h=X-UI-Sender-Class:Date:From:To:Subject; b=Mc7M9E9IAuJFlkbGDwFSu5CBP4D0k73ziAvCKFZMnYZEqKEEp+nlAHUthISDIlcH+ RHK4gN+KEg7dYGyjyxxlSAbjhto8z2QYvb6MTJJkrvhh8nkHjKGTATekkjawmOvN5F C5cENnDvNUK6aEf7xWjrEDHrD0bdx3Otvbd4ADWc= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Date: Tue, 19 Oct 2021 11:54:31 +0200 From: Chris To: xen-users Message-ID: <907a7c3d-a728-4dc6-882a-481a5adacf99@lucypher> Subject: Monitoring Xen MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="616e95d7_7ac3b210_2471" X-Provags-ID: V03:K1:r48qsVMPPRlhzXDArXwxUGoMfftsAVVNnF4xEsTxZsXddhKfPVc rHjPouQGI4PW9/rw440ezvqtvJWNuP0Lm3JdEe78Jf5MsPDY6m2UO5nsUDYAQeM7NtixW/b 748relMTmgHc7MKYt5/p6hSPF9YEJr3cVm5z+DdSRrCagQc/lafEbOk2mpy73A3gVSSUfER QMOXTSNrbAZk2ibG63J1w== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:y+88nLy+wdw=:Ork2CFgg0ghlYdZ6nA+OKg u6hxSdMYxjmavuiEkwYL4nKi0vToVAcdvTrbvSG0K6RhfqWOJ6bEvTqaqpn3XpEYaL6iciGYW XtZs8+U8/LziTA7Vi98lP2hbU4vMHe0oOFEAFnZ7EJGEd3bzyj88glKdJw4/FCXIS2cOXmGG8 noin3bcVRM8ZcXh+/agqntB9k4LL4mV9Vl92M3vlHJYrLg+NoLNwNFo9Z+5kdAlqP18zg361m 5jgeg8ZXwOWt/hOPJqwNcQ4imsDbiXUVZCVY9n1TtSsl1gctlBJvHs1gOcqnLlGMSA5GC7YjE qYU/YPKmCGfgz2pDzEt7IUV83w5ZRyhiq4LBbTC4ThgDpaa/fAL4bLggxzrVKsHj/+EvQRNSv XtdqofsDLgbrYRR5MsPQOEXoazLjNXoEaeIGUUJl8iRSCXwUUwiibQ5SD5BQJoDs8Onp6ilm6 42WvuareOgHRb7h/oUUilEKpEdjWUZGGUR1IIlaElh3R6gbLJv+E6wGJ6AI51GjadNxiUsMD1 wj/oWu2D6EvtstWK5BWMQV6wYOfVfenmqMWGuU0KHksEUTX6ltJOlbkEIPQhQmn+PqZSjCsLv zp/Op9ufgYzql+MTGTOfRzJ1NaScdNebEHMPXm70GPkSJ/hfmFN2UFIQ5sROH68d4HCJvgD4/ tkEzhXGX0WhGFnrCdj9TmvH1gpAYniMnobvFQ5DiIjPCoh5sRtpABXE+/G4CQA3GMJctLsuME lGuQcG8cd0LGGT9PZ3nY1uBT2ZKsOVaMQQhcNCrv5IaTFEdB64z8Wk1y9/nlfwdnSpLividv2 kjnwZ2ePwDHQAldW747BwOKhQvwnojoG+evxTZMq4kNHykwoUZABmdH8MNq5AH0PRocMJ2fqN uOBu7c9W1IRsg8FniBxhMGTk5qBaZ2ljg39DL0dx1Z2PmIhzvAYEdEd0DkJ3bXnFXALeR7ZhM BaosDg3zcAzric3rVXGBIwz3FyT8n7GtJec0FHhRvFXOi/MVv/fohgZn50GJPeT08VcrjxMLo kjS00pLyopBnSqe1LHhrhJWZcHIrTx7/oNgzX8cSa9EKavWMOYHTyg6fnU+lW9GWOW8T8J+FX YrMQ4gJBB/6EZw= --616e95d7_7ac3b210_2471 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, does someone know any good nagios/icinga check for xen? All what I've found are old und use still xm... --------- Greetz --616e95d7_7ac3b210_2471 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi,
 
does someone know any good nagios/icinga check for xen=3F
All what I've found are old und use still xm...
 
---------
Greetz
--616e95d7_7ac3b210_2471-- From xen-users-bounces@lists.xenproject.org Tue Oct 19 13:42:57 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 19 Oct 2021 13:42:57 +0000 Received: from list by lists.xenproject.org with outflank-mailman.213243.371411 (Exim 4.92) (envelope-from ) id 1mcpNY-0003bt-22; Tue, 19 Oct 2021 13:42:08 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 213243.371411; Tue, 19 Oct 2021 13:42:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mcpNX-0003bl-V9; Tue, 19 Oct 2021 13:42:07 +0000 Received: by outflank-mailman (input) for mailman id 213243; Tue, 19 Oct 2021 13:42:07 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mcpNW-0003bf-OR for xen-users@lists.xenproject.org; Tue, 19 Oct 2021 13:42:07 +0000 Received: from mail.syndicat.com (unknown [62.146.89.62]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 58434d7a-30e2-11ec-8313-12813bfff9fa; Tue, 19 Oct 2021 13:42:04 +0000 (UTC) Received: from localhost.syndicat.com ([127.0.0.1]:61142 helo=localhost) by mail.syndicat.com with esmtp (Syndicat PostHamster 11.1 4.94) (envelope-from ) id 1mcpNT-00060M-Q1 for xen-users@lists.xenproject.org; Tue, 19 Oct 2021 15:42:03 +0200 Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2U_GP6eY87h for ; Tue, 19 Oct 2021 15:42:03 +0200 (CEST) Received: from 89-172-48-138.adsl.net.t-com.hr ([89.172.48.138]:34288 helo=gongo.localnet) by mail.syndicat.com with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Syndicat PostHamster 11.1 4.94) (envelope-from ) id 1mcpNT-0002pD-BV for xen-users@lists.xenproject.org; Tue, 19 Oct 2021 15:42:03 +0200 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 58434d7a-30e2-11ec-8313-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=syndicat.com; s=x; h=Content-Type:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=v90zjYTGLlt5AKz6cauZ8CXoiGthrgu4Pq1VrneEXhI=; b=KX3Dx86zhJLqareNVSdBxMjI1m 06H5CLYIcO+u0nycWS5p4L7w6/iPhSpn7t9LGj4+SFY2AFi9DH+twMBZhPAB9bK2cp/a8AWGH0rTL Vj7IGvYefxqSl9Shy35HY/gi4G4+SzldR5VNerVnhanNUKKouko4vJJO3gxOnc3h2GBY=; X-Virus-Scanned: amavisd-new at syndicat.com From: Niels Dettenbach To: xen-users@lists.xenproject.org Subject: Re: Monitoring Xen Date: Tue, 19 Oct 2021 15:42:11 +0200 Message-ID: <2559977.BddDVKsqQX@gongo> Organization: Syndicat IT&Internet Disposition-Notification-To: Niels Dettenbach In-Reply-To: <907a7c3d-a728-4dc6-882a-481a5adacf99@lucypher> References: <907a7c3d-a728-4dc6-882a-481a5adacf99@lucypher> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1732318.TLkxdtWsSY"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Report-Abuse-To: abuse@syndicat.com (see https://www.syndicat.com/kontakt/kontakte/) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mail.syndicat.com X-AntiAbuse: Original Domain - lists.xenproject.org X-AntiAbuse: Sender Address Domain - syndicat.com --nextPart1732318.TLkxdtWsSY Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii"; protected-headers="v1" From: Niels Dettenbach To: xen-users@lists.xenproject.org Subject: Re: Monitoring Xen Date: Tue, 19 Oct 2021 15:42:11 +0200 Message-ID: <2559977.BddDVKsqQX@gongo> Organization: Syndicat IT&Internet Disposition-Notification-To: Niels Dettenbach In-Reply-To: <907a7c3d-a728-4dc6-882a-481a5adacf99@lucypher> References: <907a7c3d-a728-4dc6-882a-481a5adacf99@lucypher> Am Dienstag, 19. Oktober 2021, 11:54:31 CEST schrieb Chris: > does someone know any good nagios/icinga check for xen? What do you want to minitor in detail? Which nagios scripts / plugins you tried? With some luck, you can substitute all occurences of xm to xl in the script to get it working with xl. I use nagios and xen, but don't monitor any xen variables - just Dom0 and Domu. Only a very few special parameters could be read from xl which are practically not really helpful in many xen scenarios (but, that's just my experience). best regards, niels. -- --- Niels Dettenbach Syndicat IT & Internet https://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- --nextPart1732318.TLkxdtWsSY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEen+3H2N8RDyGzUZnDbtaiEWSKkQFAmFuyzMACgkQDbtaiEWS KkSxxA//WQiOPLkkS851VMHuDfuEp8uK6YH+vtQ/DOD98RmZVnvrNPNwpotrefak Hq/zh3IQNhy0DYVc6AtbSAbKasE/jDAJOyx+Z+BXEMZX6JXuQQ5ZWXE+BuJjBEQ8 jSNyYGhTBRNpLhLJEvaA6QJOUc5egRFJL3xbGD2F1P2PEPv9Xl2unxUCVNRXCJoC QAO//yTH8YUQz2wv2uhEKdEhHaCM7A5kwB7GW7F66hE327XcxkSMR7/fQuzHBJNm Kz3x5v4+NHxOOeHbyOkjFmZecy/XiD+9muaYWy27BozsBofoprrWWXnWfbS66h72 ZDIYPBebvjCC4D3iNAklxGjVXcy2uG4a+CHsdDgpWOHymUIw/hz7qh3xL0nZzoJO 4ILNffOmvL01DFhWxynpOx9hj+ApgZmGO2U62Prbg0YRwI91UPPcQ7fKn5H2pAUb yJhupTAMmCuhQ9OgB+jF74fTTMdKgTqJRGaMyTqRX3w267Wmzuuw+m4mnbrtyMdL 4NkfFbuZbeq8g9jS94kBDvzYf1zUrNWQ8e2ps+I3KNYXDfrk3NplwDHPuRi9RYbn KhuGnmGvOBrjGWQDg94z/5NOgInMx2idlhwB0zrpSNv89VPFhDAvPqL3PNogxkK+ v6uHc9AmC52OkEEsUe6OlSgBOE/ay2EQ+CFjWloBumIvMO1wwbs= =IZLU -----END PGP SIGNATURE----- --nextPart1732318.TLkxdtWsSY-- From xen-users-bounces@lists.xenproject.org Sat Oct 23 15:01:37 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 23 Oct 2021 15:01:37 +0000 Received: from list by lists.xenproject.org with outflank-mailman.215380.374537 (Exim 4.92) (envelope-from ) id 1meIVj-0000Oo-7M; Sat, 23 Oct 2021 15:00:39 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 215380.374537; Sat, 23 Oct 2021 15:00:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1meIVj-0000Od-3k; Sat, 23 Oct 2021 15:00:39 +0000 Received: by outflank-mailman (input) for mailman id 215380; Sat, 23 Oct 2021 15:00:37 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1meIVh-0000OX-3R for xen-users@lists.xenproject.org; Sat, 23 Oct 2021 15:00:37 +0000 Received: from syrinx.knorrie.org (unknown [82.94.188.77]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id f95b7ae9-3411-11ec-83e9-12813bfff9fa; Sat, 23 Oct 2021 15:00:35 +0000 (UTC) Received: from [IPv6:2a02:a213:2bc0:9e00::12] (unknown [IPv6:2a02:a213:2bc0:9e00::12]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by syrinx.knorrie.org (Postfix) with ESMTPSA id 7C90060F89C7F; Sat, 23 Oct 2021 17:00:34 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: f95b7ae9-3411-11ec-83e9-12813bfff9fa Subject: Re: pvhgrub docs To: xen-users@lists.xenproject.org, TMC , Andy Smith References: <20211007221430.rt6iq3ygoulreoh5@bitfolk.com> From: Hans van Kranenburg Message-ID: <8611bedf-f2c1-237f-5386-c578a21b23bd@knorrie.org> Date: Sat, 23 Oct 2021 17:00:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <20211007221430.rt6iq3ygoulreoh5@bitfolk.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Hi, On 10/8/21 12:14 AM, Andy Smith wrote: > > On Thu, Oct 07, 2021 at 07:09:35AM -0500, Chris Myers wrote: >> Out of curiosity, could someone point me to some documentation for pvhgrub? > > I haven't found much, I've had to teach myself from other people's > examples and some out of date articles on the Xen wiki. Here is what I > learned so far and have had working for a year or so. > > If you're currently running a PV mode guest and it has a kernel of > 4.19 or greater, you can/should change it to a PVH mode guest. > [...] Actually, it's since Linux 4.20, officially, but the few remaining bits to make it possible were also added [0] to the Debian 4.19 kernel so that we had everything working for Buster. Hans [0] https://salsa.debian.org/kernel-team/linux/commit/4d63e6ccbbd6081068633b1147e0f77a59379795 From xen-users-bounces@lists.xenproject.org Sun Oct 24 19:38:20 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 24 Oct 2021 19:38:20 +0000 Received: from list by lists.xenproject.org with outflank-mailman.215568.374852 (Exim 4.92) (envelope-from ) id 1mejJF-0000sj-Se; Sun, 24 Oct 2021 19:37:33 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 215568.374852; Sun, 24 Oct 2021 19:37:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mejJF-0000sC-Mc; Sun, 24 Oct 2021 19:37:33 +0000 Received: by outflank-mailman (input) for mailman id 215568; Sun, 24 Oct 2021 19:37:31 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mejJD-0000s6-1c for xen-users@lists.xenproject.org; Sun, 24 Oct 2021 19:37:31 +0000 Received: from mout01.posteo.de (unknown [185.67.36.65]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id d2145f41-3501-11ec-8406-12813bfff9fa; Sun, 24 Oct 2021 19:37:29 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 9B03D240028 for ; Sun, 24 Oct 2021 21:37:27 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4HcpJR0QMtz9rxV for ; Sun, 24 Oct 2021 21:37:27 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: d2145f41-3501-11ec-8406-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1635104247; bh=jQbwxyinU8kuLc6ARZezz6Gge6FI1MV/hYxiThTnWaE=; h=Date:To:From:Subject:From; b=Heir3/S+/oA9NtYCCovRq1kETchH1go6jH+945KKjd7KIS6sTc3yv/DUXplFgIPhI +3ENqDzRG9OAMvlRzvq4ahxdsK6uCi4PxiS7XgJT7IaPexCEJBpzED3zjrX/qTtGRI fgCGo14wJwbcb5vghTl4DJTXKeMuVlmeUhG9ZL3UpxCsB0SBJ+hABS+ReSLyTIlirp WV4MdituQ+YYLhZaflOO+ZU0q//ihaXOKY68LUVFdNs/C3H7DpNCKXAWiEFzR4j8aQ VoY4OB9ML/0RYGvv7KccZVhFgkfJzPdSvZZFG2R7xshfeyxOZsFCt896iupUna7yo0 0D6HYcCGKW6JA== Message-ID: Date: Sun, 24 Oct 2021 19:37:36 +0000 MIME-Version: 1.0 Content-Language: de-DE To: "xen-users@lists.xenproject.org" From: Frank Schiebel Subject: xen-3.0-x86_32p capability missing Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello, I'm having an issue running 32bit DomUs on my freshly installed debian bullseye xen 4.14 installation. I am unable to create any 32bit PV DomUs, I always get the following error: > xc: error: panic: xc_dom_boot.c:120: xc_dom_boot_mem_init: can't allocate low memory for domain: Out of memory > libxl: error: libxl_dom.c:593:libxl__build_dom: xc_dom_boot_mem_init failed: Operation not supported After examining the situation it turns out, that the capability for running 32bit PAE VMs apparently is not present: > host : toothless > release : 5.10.0-9-amd64 > version : #1 SMP Debian 5.10.70-1 (2021-09-30) > machine : x86_64 > nr_cpus : 4 > max_cpu_id : 3 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 2893.316 > hw_caps : bfebfbff:76daf3bf:2c100800:00000021:00000001:000027ab:00000000:00000100 > virt_caps : pv hvm hap shadow > total_memory : 16299 > free_memory : 12010 > sharing_freed_memory : 0 > sharing_used_memory : 0 > outstanding_claims : 0 > free_cpus : 0 > xen_major : 4 > xen_minor : 14 > xen_extra : .3 > xen_version : 4.14.3 > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit2 > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : xen_commandline : placeholder dom0_mem=1024M,max:1024M smt=true > cc_compiler : x86_64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110 > cc_compile_by : pkg-xen-devel > cc_compile_domain : lists.alioth.debian.org > cc_compile_date : Mon Sep 13 14:28:21 UTC 2021 > build_id : 1a67c53a8813b422d2033de494f8b444915791f2 > xend_config_format : 4 The capability "xen-3.0-x86_32p" is not listed under xen_caps. I think I am missing something rather emelentary, but am unable to figure out what - so any help would be greatly appreciated. TIA Frank This is the Output of "xl dmesg": > root@toothless:~# xl dmesg > (XEN) Xen version 4.14.3 (Debian 4.14.3-1~deb11u1) (pkg-xen-devel@lists.alioth.debian.org) (x86_64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110) debug=n Mon Sep 13 14:28:21 UTC 2021 > (XEN) Bootloader: GRUB 2.04-20 > (XEN) Command line: placeholder dom0_mem=1024M,max:1024M smt=true > (XEN) Xen image load base address: 0xdac00000 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) [0000000000000000, 000000000009d7ff] (usable) > (XEN) [000000000009d800, 000000000009ffff] (reserved) > (XEN) [00000000000e0000, 00000000000fffff] (reserved) > (XEN) [0000000000100000, 00000000c889ffff] (usable) > (XEN) [00000000c88a0000, 00000000c88a6fff] (ACPI NVS) > (XEN) [00000000c88a7000, 00000000c970efff] (usable) > (XEN) [00000000c970f000, 00000000c9cd5fff] (reserved) > (XEN) [00000000c9cd6000, 00000000db334fff] (usable) > (XEN) [00000000db335000, 00000000db3befff] (reserved) > (XEN) [00000000db3bf000, 00000000db3d4fff] (ACPI data) > (XEN) [00000000db3d5000, 00000000db542fff] (ACPI NVS) > (XEN) [00000000db543000, 00000000dbffefff] (reserved) > (XEN) [00000000dbfff000, 00000000dbffffff] (usable) > (XEN) [00000000dd000000, 00000000df1fffff] (reserved) > (XEN) [00000000f8000000, 00000000fbffffff] (reserved) > (XEN) [00000000fec00000, 00000000fec00fff] (reserved) > (XEN) [00000000fed00000, 00000000fed03fff] (reserved) > (XEN) [00000000fed1c000, 00000000fed1ffff] (reserved) > (XEN) [00000000fee00000, 00000000fee00fff] (reserved) > (XEN) [00000000ff000000, 00000000ffffffff] (reserved) > (XEN) [0000000100000000, 000000041fdfffff] (usable) > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > (XEN) ACPI: XSDT DB3C3080, 007C (r1 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: FACP DB3CFCA8, 010C (r5 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: DSDT DB3C3188, CB1F (r2 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: FACS DB541080, 0040 > (XEN) ACPI: APIC DB3CFDB8, 0072 (r3 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: FPDT DB3CFE30, 0044 (r1 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: LPIT DB3CFE78, 005C (r1 INTEL DH87RL 144 AMI. 5) > (XEN) ACPI: SSDT DB3CFED8, 0539 (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: SSDT DB3D0418, 0AD8 (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: SSDT DB3D0EF0, 01C7 (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: MCFG DB3D10B8, 003C (r1 INTEL DH87RL 144 MSFT 97) > (XEN) ACPI: HPET DB3D10F8, 0038 (r1 INTEL DH87RL 144 AMI. 5) > (XEN) ACPI: SSDT DB3D1130, 036D (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: SSDT DB3D14A0, 3004 (r1 INTEL DH87RL 144 INTL 20091112) > (XEN) System RAM: 16299MB (16690196kB) > (XEN) Domain heap initialised > (XEN) ACPI: 32/64X FACS address mismatch in FADT - db541080/0000000000000000, using 32 > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) CPU0: 800 ... 2900 MHz > (XEN) xstate: size: 0x340 and states: 0x7 > (XEN) Speculative mitigation facilities: > (XEN) Hardware features: > (XEN) Compiled-in support: INDIRECT_THUNK SHADOW_PAGING > (XEN) Xen settings: BTI-Thunk RETPOLINE, SPEC_CTRL: No, Other: BRANCH_HARDEN > (XEN) L1TF: believed vulnerable, maxphysaddr L1D 46, CPUID 39, Safe address 8000000000 > (XEN) Support for HVM VMs: RSB EAGER_FPU > (XEN) Support for PV VMs: RSB EAGER_FPU > (XEN) XPTI (64-bit PV only): Dom0 enabled, DomU enabled (with PCID) > (XEN) PV L1TF shadowing: Dom0 disabled, DomU enabled > (XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2) > (XEN) Initializing Credit2 scheduler > (XEN) Platform timer is 14.318MHz HPET > (XEN) Detected 2893.316 MHz processor. > (XEN) I/O virtualisation disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) TSC_DEADLINE disabled due to Errata; please update microcode to version 0x22 (or later) > (XEN) Allocated console ring of 16 KiB. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) - VM Functions > (XEN) HVM: ASIDs enabled. > (XEN) VMX: Disabling executable EPT superpages due to CVE-2018-12207 > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB > (XEN) Brought up 4 CPUs > (XEN) Scheduling granularity: cpu, 1 CPU per sched-resource > (XEN) Dom0 has maximum 648 PIRQs > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x322c000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000408000000->000000040c000000 (237439 pages to be allocated) > (XEN) Init. ramdisk: 000000041dd7f000->000000041fdffd0b > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff8322c000 > (XEN) Init. ramdisk: 0000000000000000->0000000000000000 > (XEN) Phys-Mach map: 0000008000000000->0000008000200000 > (XEN) Start info: ffffffff8322c000->ffffffff8322c4b8 > (XEN) Xenstore ring: 0000000000000000->0000000000000000 > (XEN) Console ring: 0000000000000000->0000000000000000 > (XEN) Page tables: ffffffff8322d000->ffffffff8324a000 > (XEN) Boot stack: ffffffff8324a000->ffffffff8324b000 > (XEN) TOTAL: ffffffff80000000->ffffffff83400000 > (XEN) ENTRY ADDRESS: ffffffff82c31160 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Scrubbing Free RAM in background > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input) > (XEN) Freed 552kB init memory From xen-users-bounces@lists.xenproject.org Mon Oct 25 16:41:16 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Oct 2021 16:41:16 +0000 Received: from list by lists.xenproject.org with outflank-mailman.215566.375390 (Exim 4.92) (envelope-from ) id 1mf31O-0006ZX-DE; Mon, 25 Oct 2021 16:40:26 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 215566.375390; Mon, 25 Oct 2021 16:40:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf31O-0006ZM-9V; Mon, 25 Oct 2021 16:40:26 +0000 Received: by outflank-mailman (input) for mailman id 215566; Sun, 24 Oct 2021 19:30:43 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mejCd-0000nO-SP for xen-users@lists.xenproject.org; Sun, 24 Oct 2021 19:30:43 +0000 Received: from mail-out02.belwue.de (unknown [129.143.76.12]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 365563d1-a5a1-46ca-88b9-e6364f0a9fde; Sun, 24 Oct 2021 19:30:38 +0000 (UTC) Received: from mail-hub01.belwue.de (mail-hub01.belwue.de [129.143.76.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-out02.belwue.de (Postfix) with ESMTPS id 4Hcp8Y3fBxz9xBMx for ; Sun, 24 Oct 2021 21:30:37 +0200 (CEST) Received: from mbox1.belwue.de (frontend02.mbox1.belwue.de [129.143.76.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-hub01.belwue.de (Postfix) with ESMTPS id 4Hcp8Y1SrNz512P2 for ; Sun, 24 Oct 2021 21:30:37 +0200 (CEST) Received: from [2003:f6:c72c:3800:bf8e:d38c:7ef4:32c6] (account frank.schiebel@quenstedt-gymnasium.de HELO [IPV6:2003:f6:c72c:3800:bf8e:d38c:7ef4:32c6]) by mbox1.belwue.de (CommuniGate Pro SMTP 6.3.7f) with ESMTPSA id 35809007 for xen-users@lists.xenproject.org; Sun, 24 Oct 2021 21:30:37 +0200 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 365563d1-a5a1-46ca-88b9-e6364f0a9fde Message-ID: <44a78aec-2c61-a881-9833-ac41f879f0a7@quenstedt-gymnasium.de> Date: Sun, 24 Oct 2021 21:30:46 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 To: xen-users@lists.xenproject.org Content-Language: de-DE From: Frank Schiebel Subject: xen-3.0-x86_32p capability missing Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-UID: 52cc2f X-Rspamd-Queue-Id: 4Hcp8Y1SrNz512P2 Hello, I'm having an issue running 32bit DomUs on my freshly installed debian bullseye xen 4.14 installation. I am unable to create any 32bit PV DomUs, I always get the following error: > xc: error: panic: xc_dom_boot.c:120: xc_dom_boot_mem_init: can't allocate low memory for domain: Out of memory > libxl: error: libxl_dom.c:593:libxl__build_dom: xc_dom_boot_mem_init failed: Operation not supported After reconsidering the situation it turns out, that the capability for running 32bit PAE VMs is not present: > host : toothless > release : 5.10.0-9-amd64 > version : #1 SMP Debian 5.10.70-1 (2021-09-30) > machine : x86_64 > nr_cpus : 4 > max_cpu_id : 3 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 2893.316 > hw_caps : bfebfbff:76daf3bf:2c100800:00000021:00000001:000027ab:00000000:00000100 > virt_caps : pv hvm hap shadow > total_memory : 16299 > free_memory : 12010 > sharing_freed_memory : 0 > sharing_used_memory : 0 > outstanding_claims : 0 > free_cpus : 0 > xen_major : 4 > xen_minor : 14 > xen_extra : .3 > xen_version : 4.14.3 > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit2 > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : > xen_commandline : placeholder dom0_mem=1024M,max:1024M smt=true > cc_compiler : x86_64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110 > cc_compile_by : pkg-xen-devel > cc_compile_domain : lists.alioth.debian.org > cc_compile_date : Mon Sep 13 14:28:21 UTC 2021 > build_id : 1a67c53a8813b422d2033de494f8b444915791f2 > xend_config_format : 4 The capability "xen-3.0-x86_32p" is not listed? I think I am missing something rather emelentary, but am unable to figure out what - so any help would be greatly appreciated. TIA Frank This is the Output of "xl dmesg": > root@toothless:~# xl dmesg > (XEN) Xen version 4.14.3 (Debian 4.14.3-1~deb11u1) (pkg-xen-devel@lists.alioth.debian.org) (x86_64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110) debug=n Mon Sep 13 14:28:21 UTC 2021 > (XEN) Bootloader: GRUB 2.04-20 > (XEN) Command line: placeholder dom0_mem=1024M,max:1024M smt=true > (XEN) Xen image load base address: 0xdac00000 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) [0000000000000000, 000000000009d7ff] (usable) > (XEN) [000000000009d800, 000000000009ffff] (reserved) > (XEN) [00000000000e0000, 00000000000fffff] (reserved) > (XEN) [0000000000100000, 00000000c889ffff] (usable) > (XEN) [00000000c88a0000, 00000000c88a6fff] (ACPI NVS) > (XEN) [00000000c88a7000, 00000000c970efff] (usable) > (XEN) [00000000c970f000, 00000000c9cd5fff] (reserved) > (XEN) [00000000c9cd6000, 00000000db334fff] (usable) > (XEN) [00000000db335000, 00000000db3befff] (reserved) > (XEN) [00000000db3bf000, 00000000db3d4fff] (ACPI data) > (XEN) [00000000db3d5000, 00000000db542fff] (ACPI NVS) > (XEN) [00000000db543000, 00000000dbffefff] (reserved) > (XEN) [00000000dbfff000, 00000000dbffffff] (usable) > (XEN) [00000000dd000000, 00000000df1fffff] (reserved) > (XEN) [00000000f8000000, 00000000fbffffff] (reserved) > (XEN) [00000000fec00000, 00000000fec00fff] (reserved) > (XEN) [00000000fed00000, 00000000fed03fff] (reserved) > (XEN) [00000000fed1c000, 00000000fed1ffff] (reserved) > (XEN) [00000000fee00000, 00000000fee00fff] (reserved) > (XEN) [00000000ff000000, 00000000ffffffff] (reserved) > (XEN) [0000000100000000, 000000041fdfffff] (usable) > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > (XEN) ACPI: XSDT DB3C3080, 007C (r1 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: FACP DB3CFCA8, 010C (r5 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: DSDT DB3C3188, CB1F (r2 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: FACS DB541080, 0040 > (XEN) ACPI: APIC DB3CFDB8, 0072 (r3 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: FPDT DB3CFE30, 0044 (r1 INTEL DH87RL 144 AMI 10013) > (XEN) ACPI: LPIT DB3CFE78, 005C (r1 INTEL DH87RL 144 AMI. 5) > (XEN) ACPI: SSDT DB3CFED8, 0539 (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: SSDT DB3D0418, 0AD8 (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: SSDT DB3D0EF0, 01C7 (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: MCFG DB3D10B8, 003C (r1 INTEL DH87RL 144 MSFT 97) > (XEN) ACPI: HPET DB3D10F8, 0038 (r1 INTEL DH87RL 144 AMI. 5) > (XEN) ACPI: SSDT DB3D1130, 036D (r1 INTEL DH87RL 144 INTL 20120711) > (XEN) ACPI: SSDT DB3D14A0, 3004 (r1 INTEL DH87RL 144 INTL 20091112) > (XEN) System RAM: 16299MB (16690196kB) > (XEN) Domain heap initialised > (XEN) ACPI: 32/64X FACS address mismatch in FADT - db541080/0000000000000000, using 32 > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) CPU0: 800 ... 2900 MHz > (XEN) xstate: size: 0x340 and states: 0x7 > (XEN) Speculative mitigation facilities: > (XEN) Hardware features: > (XEN) Compiled-in support: INDIRECT_THUNK SHADOW_PAGING > (XEN) Xen settings: BTI-Thunk RETPOLINE, SPEC_CTRL: No, Other: BRANCH_HARDEN > (XEN) L1TF: believed vulnerable, maxphysaddr L1D 46, CPUID 39, Safe address 8000000000 > (XEN) Support for HVM VMs: RSB EAGER_FPU > (XEN) Support for PV VMs: RSB EAGER_FPU > (XEN) XPTI (64-bit PV only): Dom0 enabled, DomU enabled (with PCID) > (XEN) PV L1TF shadowing: Dom0 disabled, DomU enabled > (XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2) > (XEN) Initializing Credit2 scheduler > (XEN) Platform timer is 14.318MHz HPET > (XEN) Detected 2893.316 MHz processor. > (XEN) I/O virtualisation disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) TSC_DEADLINE disabled due to Errata; please update microcode to version 0x22 (or later) > (XEN) Allocated console ring of 16 KiB. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) - VM Functions > (XEN) HVM: ASIDs enabled. > (XEN) VMX: Disabling executable EPT superpages due to CVE-2018-12207 > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB > (XEN) Brought up 4 CPUs > (XEN) Scheduling granularity: cpu, 1 CPU per sched-resource > (XEN) Dom0 has maximum 648 PIRQs > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x322c000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000408000000->000000040c000000 (237439 pages to be allocated) > (XEN) Init. ramdisk: 000000041dd7f000->000000041fdffd0b > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff8322c000 > (XEN) Init. ramdisk: 0000000000000000->0000000000000000 > (XEN) Phys-Mach map: 0000008000000000->0000008000200000 > (XEN) Start info: ffffffff8322c000->ffffffff8322c4b8 > (XEN) Xenstore ring: 0000000000000000->0000000000000000 > (XEN) Console ring: 0000000000000000->0000000000000000 > (XEN) Page tables: ffffffff8322d000->ffffffff8324a000 > (XEN) Boot stack: ffffffff8324a000->ffffffff8324b000 > (XEN) TOTAL: ffffffff80000000->ffffffff83400000 > (XEN) ENTRY ADDRESS: ffffffff82c31160 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Scrubbing Free RAM in background > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input) > (XEN) Freed 552kB init memory From xen-users-bounces@lists.xenproject.org Mon Oct 25 18:13:18 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Oct 2021 18:13:18 +0000 Received: from list by lists.xenproject.org with outflank-mailman.215994.375443 (Exim 4.92) (envelope-from ) id 1mf4SQ-0000W5-33; Mon, 25 Oct 2021 18:12:26 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 215994.375443; Mon, 25 Oct 2021 18:12:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf4SP-0000Vx-Vb; Mon, 25 Oct 2021 18:12:25 +0000 Received: by outflank-mailman (input) for mailman id 215994; Mon, 25 Oct 2021 18:12:25 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf4SO-0000Vr-Uy for xen-users@lists.xenproject.org; Mon, 25 Oct 2021 18:12:25 +0000 Received: from mail-yb1-xb2c.google.com (unknown [2607:f8b0:4864:20::b2c]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 8cdb00c1-87d4-4e22-bbc8-a5c2370b116d; Mon, 25 Oct 2021 18:12:22 +0000 (UTC) Received: by mail-yb1-xb2c.google.com with SMTP id 67so28194455yba.6 for ; Mon, 25 Oct 2021 11:12:22 -0700 (PDT) Received: by 2002:a05:6902:120a:0:0:0:0 with HTTP; Mon, 25 Oct 2021 11:12:20 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 8cdb00c1-87d4-4e22-bbc8-a5c2370b116d DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=cOhaVnv8Wk65hmoSgzvhrwUSizujwT7JVTvTTFkd5q4=; b=Ts2lP+YL3bk2QrzrydI8+or10PDYp9ZNkr+2gOgXO3dNLBKlVHtIQABeK7WVNBrM6L Ie/gCq/XXxwC6zLcHRoMMefF/tUqOx5mnOYSn1Slrg6cFK8i8h2COS/kjHn4DVWGjLl2 sPqTjWR6CkOfGCWhaTGGT4XWAgtfARMJMA8zhWlcjmt34+97R/WfyZL/wk/Bto0JIYkX VyyJZnptL2s5t45sfqU3FiF6GWALA8Aywds2sNhaHrOQmkouHN7qw1SuNi8iYEmNMoRg vc4sno0i9GY1u/dgqTgWiajrQS5v04VNSFztw72UHVJhqJzVFnLczBpizy7ASgZqhtZv UVUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=cOhaVnv8Wk65hmoSgzvhrwUSizujwT7JVTvTTFkd5q4=; b=v0MhCdIbGkT5GqlUpuPIYbpyN6I7aik6dFVbyur/+m9FmKXhAmGYHV/zthNnsPJeHN caLb0eva1dH4QGYrouiPFts4OVdEec98XrxJ6zh/U0pnC/Gahw1dX2mDku3nZzVZAFml kGfSQbcz48us8l+XbOfS1PseNHPWynSfpGfx0vWdWiVITTGt+MemhkA0863wU8p24dgx Aovv/jUTv8+7uQ5wJhr1H6GZtIuCvieICiPPVzgb62seC6sw7g9w1bPHQKeEwi8qo0T7 xgaBkLYFL0fVEYSXeGaSEg7dE4kvLv1Hu8fCYuEO5eJlypm30MtfD3AFTYlTxtLWhlDY OZoQ== X-Gm-Message-State: AOAM532KuGklcIMVwCNDnp1Wy9cBIGtS0LnRxFMKkcOgRCwOuXmm88+c GwYD+tjsz03BzaYvFy4EWcNHaLh/3jzj144oe3mtx2iJ X-Google-Smtp-Source: ABdhPJyVfU/r6+UkMEadOC5b0SCD+clv6Jrokp44zqVJDipVdXcCupViDN53ZVmhsTVRKYOuOWBJrRd35x/7X89r4fE= X-Received: by 2002:a25:4054:: with SMTP id n81mr19429870yba.85.1635185540882; Mon, 25 Oct 2021 11:12:20 -0700 (PDT) MIME-Version: 1.0 From: Pry Mar Date: Mon, 25 Oct 2021 11:12:20 -0700 Message-ID: Subject: re: xen-3.0-x86_32p capability missing To: xen-users Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, >I'm having an issue running 32bit DomUs on my freshly installed debian bul= lseye xen 4.14 >installation. > >I am unable to create any 32bit PV DomUs, I always get the following error= : Here is the trace of a bionic (ub18.04) i386 domU running on AlmaLinux 8 xen-4.15.1 install. The dom0 kernel is older than yours, kernel-5.3.x: [ 4.145553] systemd[1]: Detected architecture x86. The best practice is to use type=3D"pvh" pvshim=3D1 --- trace --- tlviewer@c8xen:~$ sudo xl create -c /etc/xen/vm/bnc32.cfg Parsing config from /etc/xen/vm/bnc32.cfg (XEN) Initialised PV console at 0xffff82cfffffb000 with pfn 0xfefff and evtchn 0x2 __ __ _ _ _ ____ _ \ \/ /___ _ __ | || | / | ___| / | \ // _ \ '_ \ | || |_ | |___ \ | | / \ __/ | | | |__ _|| |___) || | /_/\_\___|_| |_| |_|(_)_|____(_)_| (XEN) Xen version 4.15.1 (mockbuild@prymar56.org) (gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)) debug=3Dn Fri Sep 10 15:55:52 PDT 2021 (XEN) Latest ChangeSet: (XEN) PVH start info: (pa 0000ffc0) (XEN) version: 1 (XEN) flags: 0 (XEN) nr_modules: 1 (XEN) modlist_pa: 000000000000ff80 (XEN) cmdline_pa: 000000000000ffa0 (XEN) cmdline: 'pv-shim console=3Dxen,pv' (XEN) rsdp_pa: 00000000fc008000 (XEN) mod[0].pa: 0000000000a00000 (XEN) mod[0].size: 0000000000692224 (XEN) mod[0].cmdline_pa: 000000000000ff60 (XEN) mod[0].cmdline: '(hd0,0)/boot/grub/menu.lst' (XEN) Bootloader: PVH Directboot (XEN) Command line: pv-shim console=3Dxen,pv (XEN) Xen image load base address: 0 (XEN) Running on Xen (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 0 EDD information structures (XEN) PVH-e820 RAM map: (XEN) [0000000000000000, 00000000168003ff] (usable) (XEN) [00000000fc000000, 00000000fc00803f] (ACPI data) (XEN) [00000000feff8000, 00000000feffbfff] (reserved) (XEN) [00000000feffc000, 00000000feffcfff] (usable) (XEN) [00000000feffd000, 00000000feffffff] (reserved) (XEN) New Xen image base address: 0x15e00000 (XEN) System RAM: 360MB (368644kB) (XEN) ACPI: RSDP FC008000, 0024 (r2 Xen) (XEN) ACPI: XSDT FC007F70, 0034 (r1 Xen HVM 0 HVML 0) (XEN) ACPI: FACP FC007D70, 010C (r5 Xen HVM 0 HVML 0) (XEN) ACPI: DSDT FC001050, 6C9B (r5 Xen HVM 0 INTL 20180629) (XEN) ACPI: FACS FC001010, 0040 (XEN) ACPI: APIC FC007E80, 003C (r2 Xen HVM 0 HVML 0) (XEN) Domain heap initialised (XEN) ACPI: PM-Timer is too short (XEN) ACPI: FACS is not 64-byte aligned: 0xfc001010<2>ACPI: wakeup_vec[fc00101c], vec_size[20] (XEN) ACPI: No IOAPIC entries present (XEN) Found and enabled local APIC! (XEN) Switched to APIC driver x2apic_phys (XEN) xstate: size: 0x240 and states: 0x3 (XEN) Unrecognised CPU model 0x17 - assuming vulnerable to LazyFPU (XEN) Unrecognised CPU model 0x17 - assuming vulnerable to MDS (XEN) Speculative mitigation facilities: (XEN) Hardware features: (XEN) Compiled-in support: INDIRECT_THUNK (XEN) Xen settings: BTI-Thunk RETPOLINE, SPEC_CTRL: No, Other: BRANCH_HAR= DEN (XEN) L1TF: believed vulnerable, maxphysaddr L1D 36, CPUID 36, Safe address c00000000 (XEN) Support for PV VMs: RSB EAGER_FPU (XEN) XPTI (64-bit PV only): Dom0 enabled, DomU enabled (without PCID) (XEN) PV L1TF shadowing: Dom0 disabled, DomU disabled (XEN) Using scheduler: null Scheduler (null) (XEN) Initializing null scheduler (XEN) WARNING: This is experimental software in development. (XEN) Use at your own risk. (XEN) Platform timer is 1000.000MHz XEN PV CLOCK (XEN) Detected 3062.672 MHz processor. (XEN) I/O virtualisation disabled (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 1 CPUs (XEN) Scheduling granularity: cpu, 1 CPU per sched-resource (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0 -> 0x99214c (XEN) shim used pages 0x173a reserving 0x100 free pages (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000014000000->0000000015000000 (81863 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 0000000000000000->000000000099214c (XEN) Init. ramdisk: 0000000000993000->0000000000993000 (XEN) Phys-Mach map: 0000000000993000->00000000009e6f1c (XEN) Start info: 00000000009e7000->00000000009e7490 (XEN) Xenstore ring: 00000000009e8000->00000000009e9000 (XEN) Console ring: 00000000009e9000->00000000009ea000 (XEN) Page tables: 00000000009ea000->00000000009f5000 (XEN) Boot stack: 00000000009f5000->00000000009f6000 (XEN) TOTAL: 0000000000000000->0000000000c00000 (XEN) ENTRY ADDRESS: 0000000000000000 (XEN) Dom10 has maximum 2 VCPUs (XEN) Initial low memory virq threshold set at 0x40 pages. (XEN) Scrubbing Free RAM in background (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input) (XEN) Freed 2048kB init memory Xen Minimal OS (pv)! start_info: 0x9e7000(VA) nr_pages: 0x14fc7 shared_inf: 0x1592f000(MA) pt_base: 0x9ea000(VA) nr_pt_frames: 0xb mfn_list: 0x993000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x200 cmd_line: (hd0,0)/boot/grub/menu.lst stack: 0x971780-0x991780 MM: Init _text: 0x0(VA) _etext: 0x8afc6(VA) _erodata: 0xa3000(VA) _edata: 0xa7048(VA) stack start: 0x971780(VA) _end: 0x99214c(VA) start_pfn: 9f5 max_pfn: 14fc7 Mapping memory range 0x9f5000 - 0x14fc7000 setting 0x0-0xa3000 readonly skipped 1000 MM: Initialise page allocator for a97000(a97000)-14fc7000(14fc7000) Adding memory range a9a000-14fc7000 MM: done Demand map pfns at 40000000-affff000. Heap resides at b0000000-f57ff000. Initialising console ... done. Booting 'Ubuntu Bionic (4.15.0-122-generic)' kernel (hd0,0)/boot/vmlinuz-4.15.0-122-generic root=3D/dev/xvda1 nodmraid n= et.ifn ames=3D0 -noraid vga=3D0x317 noresume DMRAID=3Dno apparmor=3D0 ipv6.disable= =3D1 nopti initrd (hd0,0)/boot/initrd.img-4.15.0-122-generic =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Init TPM Front =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error =3D ENOENT Tpmfront:Info Shutting down tpmfront close blk: backend=3D/local/domain/0/backend/vbd/10/51712 node=3Ddevice/vbd= /51712 close blk: backend=3D/local/domain/0/backend/vbd/10/51728 node=3Ddevice/vbd= /51728 [ 0.000000] Reserving virtual address space above 0xf5800000 (rounded to 0xf5800000) [ 0.000000] Linux version 4.15.0-122-generic (buildd@lgw01-amd64-003) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #124-Ubuntu SMP Thu Oct 15 13:02:56 UTC 2020 (Ubuntu 4.15.0-122.124-generic 4.15.18) [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] NSC Geode by NSC [ 0.000000] Cyrix CyrixInstead [ 0.000000] Centaur CentaurHauls [ 0.000000] Transmeta GenuineTMx86 [ 0.000000] Transmeta TransmetaCPU [ 0.000000] UMC UMC UMC UMC [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format. [ 0.000000] ACPI in unprivileged domain disabled [ 0.000000] Released 0 page(s) [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] Xen: [mem 0x0000000000000000-0x000000000009ffff] usable [ 0.000000] Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved [ 0.000000] Xen: [mem 0x0000000000100000-0x00000000157c6fff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI not present or invalid. [ 0.000000] Hypervisor detected: Xen PV [ 0.000000] e820: last_pfn =3D 0x157c7 max_arch_pfn =3D 0x1000000 [ 0.000000] MTRR: Disabled [ 0.000000] x86/PAT: MTRRs disabled, skipping PAT initialization too. [ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC [ 0.000000] Scanning 1 areas for low memory corruption [ 0.000000] Kernel/User page tables isolation: disabled on XEN PV. [ 0.000000] RAMDISK: [mem 0x02400000-0x033e9fff] [ 0.000000] 0MB HIGHMEM available. [ 0.000000] 343MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 157c7000 [ 0.000000] low ram: 0 - 157c7000 [ 0.000000] tsc: Fast TSC calibration failed [ 0.000000] tsc: Unable to calibrate against PIT [ 0.000000] tsc: No reference (HPET/PMTIMER) available [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.000000] Normal [mem 0x0000000001000000-0x00000000157c6fff] [ 0.000000] HighMem empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009ffff] [ 0.000000] node 0: [mem 0x0000000000100000-0x00000000157c6fff] [ 0.000000] Reserved but unavailable: 1 pages [ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x00000000157c6= fff] [ 0.000000] p2m virtual area at (ptrval), size is 400000 [ 0.000000] Remapped 0 page(s) [ 0.000000] Using APIC driver Xen PV [ 0.000000] SFI: Simple Firmware Interface v0.81 http://simplefirmware.o= rg [ 0.000000] Found and enabled local APIC! [ 0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000fffff] [ 0.000000] e820: [mem 0x157c7000-0xffffffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.15.1 (preserve-AD) [ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns [ 0.000000] random: get_random_bytes called from start_kernel+0x81/0x439 with crng_init=3D0 [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1 [ 0.000000] percpu: Embedded 29 pages/cpu s89036 r0 d29748 u118784 [ 0.000000] PV qspinlock hash table entries: 512 (order: 0, 4096 bytes) [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 87050 [ 0.000000] Kernel command line: root=3D/dev/xvda1 nodmraid net.ifnames=3D0 -noraid vga=3D0x317 noresume DMRAID=3Dno apparmor=3D0 ipv6.disable=3D1 nopti [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 byt= es) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 byte= s) [ 0.000000] Initializing CPU#0 [ 0.000000] Initializing HighMem for node 0 (00000000:00000000) [ 0.000000] Memory: 304784K/351640K available (8970K kernel code, 895K rwdata, 3456K rodata, 1112K init, 860K bss, 46856K reserved, 0K cma-reserved, 0K highmem) [ 0.000000] virtual kernel memory layout: [ 0.000000] fixmap : 0xf5714000 - 0xf57ff000 ( 940 kB) [ 0.000000] cpu_entry : 0xf5200000 - 0xf5339000 (1252 kB) [ 0.000000] pkmap : 0xf4e00000 - 0xf5000000 (2048 kB) [ 0.000000] vmalloc : 0xd5fc7000 - 0xf4dfe000 ( 494 MB) [ 0.000000] lowmem : 0xc0000000 - 0xd57c7000 ( 343 MB) [ 0.000000] .init : 0xc1d1d000 - 0xc1e33000 (1112 kB) [ 0.000000] .data : 0xc18c2ae0 - 0xc1d09c40 (4380 kB) [ 0.000000] .text : 0xc1000000 - 0xc18c2ae0 (8970 kB) [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [ 0.000000] SLUB: HWalign=3D64, Order=3D0-3, MinObjects=3D0, CPUs=3D2, N= odes=3D1 [ 0.000000] ftrace: allocating 38103 entries in 75 pages [ 0.004000] Hierarchical RCU implementation. [ 0.004000] RCU restricting CPUs from NR_CPUS=3D8 to nr_cpu_ids=3D2. [ 0.004000] Tasks RCU enabled. [ 0.004000] RCU: Adjusting geometry for rcu_fanout_leaf=3D16, nr_cpu_ids= =3D2 [ 0.004000] Using NULL legacy PIC [ 0.004000] NR_IRQS: 2304, nr_irqs: 48, preallocated irqs: 0 [ 0.004000] xen:events: Using 2-level ABI [ 0.004000] Console: colour dummy device 80x25 [ 0.004000] console [tty0] enabled [ 0.004000] console [hvc0] enabled [ 0.004000] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.004000] installing Xen timer for CPU 0 [ 0.004000] tsc: Unable to calibrate against PIT [ 0.004000] tsc: No reference (HPET/PMTIMER) available [ 0.004000] tsc: Detected 3062.672 MHz processor [ 0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 6125.34 BogoMIPS (lpj=3D12250688) [ 0.004000] pid_max: default: 32768 minimum: 301 [ 0.004000] Security Framework initialized [ 0.004000] Yama: becoming mindful. [ 0.004000] AppArmor: AppArmor disabled by boot time parameter [ 0.004000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.004000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 by= tes) [ 0.004000] Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4 [ 0.004000] Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32, 1GB 0 [ 0.004000] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 0.004000] Spectre V2 : Mitigation: Full generic retpoline [ 0.004000] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.004000] Speculative Store Bypass: Vulnerable [ 0.004000] MDS: Vulnerable: Clear CPU buffers attempted, no microcode [ 0.350989] cpu 0 spinlock event irq 1 [ 0.351103] VPMU disabled by hypervisor. [ 0.351411] Performance Events: unsupported p6 CPU model 23 no PMU driver, software events only. [ 0.351577] Hierarchical SRCU implementation. [ 0.352858] NMI watchdog: Perf event create on CPU 0 failed with -2 [ 0.352858] NMI watchdog: Perf NMI watchdog permanently disabled [ 0.353057] smp: Bringing up secondary CPUs ... [ 0.353396] installing Xen timer for CPU 1 [ 0.353481] SMP alternatives: switching to SMP code [ 0.004000] Initializing CPU#1 [ 0.701343] cpu 1 spinlock event irq 13 [ 0.701343] smp: Brought up 1 node, 2 CPUs [ 0.701343] smpboot: Max logical packages: 1 [ 0.701343] allocated 524288 bytes of page_ext [ 0.701343] devtmpfs: initialized [ 0.701343] evm: security.selinux [ 0.701343] evm: security.SMACK64 [ 0.701343] evm: security.SMACK64EXEC [ 0.701343] evm: security.SMACK64TRANSMUTE [ 0.701343] evm: security.SMACK64MMAP [ 0.701343] evm: security.apparmor [ 0.701343] evm: security.ima [ 0.701343] evm: security.capability [ 0.701343] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.701343] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.701343] pinctrl core: initialized pinctrl subsystem [ 0.722217] RTC time: 165:165:165, date: 165/165/65 [ 0.722551] NET: Registered protocol family 16 [ 0.722584] xen:grant_table: Grant tables using version 1 layout [ 0.722692] Grant table initialized [ 0.722886] audit: initializing netlink subsys (disabled) [ 0.724074] audit: type=3D2000 audit(1633280578.256:1): state=3Dinitialized audit_enabled=3D0 res=3D1 [ 0.724119] EISA bus registered [ 0.724676] PCI: setting up Xen PCI frontend stub [ 0.728102] ACPI: Interpreter disabled. [ 0.728102] xen:balloon: Initialising balloon driver (XEN) d10v1 failed to allocate 1020 extents of order 0 for onlining [ 0.728306] random: fast init done [ 0.732194] SCSI subsystem initialized [ 0.732311] vgaarb: loaded [ 0.732311] usbcore: registered new interface driver usbfs [ 0.732311] usbcore: registered new interface driver hub [ 0.732311] usbcore: registered new device driver usb [ 0.732311] EDAC MC: Ver: 3.0.0 [ 0.732311] dmi: Firmware registration failed. [ 0.732311] PCI: System does not support PCI [ 0.732311] NetLabel: Initializing [ 0.732311] NetLabel: domain hash size =3D 128 [ 0.732311] NetLabel: protocols =3D UNLABELED CIPSOv4 CALIPSO [ 0.732311] NetLabel: unlabeled traffic allowed by default [ 0.732330] clocksource: Switched to clocksource xen [ 0.747895] VFS: Disk quotas dquot_6.6.0 [ 0.747939] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 byt= es) [ 0.747987] hugetlbfs: disabling because there are no supported hugepage sizes [ 0.748107] pnp: PnP ACPI: disabled [ 0.748124] PnPBIOS: Disabled [ 0.755775] NET: Registered protocol family 2 [ 0.755948] TCP established hash table entries: 4096 (order: 2, 16384 by= tes) [ 0.755981] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 0.756058] TCP: Hash tables configured (established 4096 bind 4096) [ 0.756116] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.756146] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.756200] NET: Registered protocol family 1 [ 0.756264] Unpacking initramfs... [ 0.783015] Freeing initrd memory: 16296K [ 0.783411] Scanning for low memory corruption every 60 seconds [ 0.784291] Initialise system trusted keyrings [ 0.784321] Key type blacklist registered [ 0.784613] workingset: timestamp_bits=3D14 max_order=3D17 bucket_order= =3D3 [ 0.786175] zbud: loaded [ 0.786675] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.786962] fuse init (API version 7.26) [ 0.796827] Key type asymmetric registered [ 0.796844] Asymmetric key parser 'x509' registered [ 0.898843] bounce: pool size: 64 pages [ 0.898880] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 0.899103] io scheduler noop registered [ 0.899119] io scheduler deadline registered [ 0.899232] io scheduler cfq registered (default) [ 0.900077] isapnp: Scanning for PnP cards... [ 0.912441] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ 0.915064] Linux agpgart interface v0.103 [ 0.951558] loop: module loaded [ 0.951853] Invalid max_queues (4), will use default max: 2. [ 0.954976] libphy: Fixed MDIO Bus: probed [ 0.954997] tun: Universal TUN/TAP device driver, 1.6 [ 0.955072] PPP generic driver version 2.4.2 [ 0.955134] xen_netfront: Initialising Xen virtual ethernet driver [ 0.957403] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.957432] ehci-pci: EHCI PCI platform driver [ 0.957461] ehci-platform: EHCI generic platform driver [ 0.957486] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.957509] ohci-pci: OHCI PCI platform driver [ 0.957534] ohci-platform: OHCI generic platform driver [ 0.957559] uhci_hcd: USB Universal Host Controller Interface driver [ 0.957623] i8042: PNP: No PS/2 controller found. [ 0.957641] i8042: Probing ports directly. [ 1.259498] isapnp: No Plug & Play device found [ 2.034966] i8042: No controller found [ 2.035006] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2c258943636, max_idle_ns: 440795262401 ns [ 2.035199] mousedev: PS/2 mouse device common for all mice [ 2.035326] i2c /dev entries driver [ 2.035435] device-mapper: uevent: version 1.0.3 [ 2.035542] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com [ 2.035605] platform eisa.0: Probing EISA bus 0 [ 2.035750] platform eisa.0: EISA: Detected 0 cards [ 2.035771] cpufreq_nforce2: No nForce2 chipset [ 2.036200] ledtrig-cpu: registered to indicate activity on CPUs [ 2.036391] IPv6: Loaded, but administratively disabled, reboot required to enable [ 2.036483] NET: Registered protocol family 17 [ 2.036795] Key type dns_resolver registered [ 2.037313] mce: Using 2 MCE banks [ 2.037342] Using IPI No-Shortcut mode [ 2.037369] sched_clock: Marking stable (2037112200, 0)->(7734906771, -5697794571) [ 2.041889] registered taskstats version 1 [ 2.041991] Loading compiled-in X.509 certificates [ 2.060161] Loaded X.509 cert 'Build time autogenerated kernel key: ebe3a7782c3e3aa41a8e939bf3a202cdfee04a23' [ 2.060173] zswap: loaded using pool lzo/zbud [ 2.078708] blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; [ 2.086517] Key type big_key registered [ 2.092856] xvda: xvda1 [ 2.093351] Key type trusted registered [ 2.099178] blkfront: xvdb: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; [ 2.102503] Key type encrypted registered [ 2.102507] ima: No TPM chip found, activating TPM-bypass! (rc=3D-19) [ 2.102507] ima: Allocated hash algorithm: sha1 [ 2.102538] evm: HMAC attrs: 0x1 [ 2.204275] Magic number: 1:252:3141 [ 2.204350] hctosys: unable to open rtc device (rtc0) [ 2.204663] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 2.204685] EDD information not available. [ 2.206664] Freeing unused kernel image memory: 1112K [ 2.222443] Write protecting the kernel text: 8972k [ 2.223449] Write protecting the kernel read-only data: 3480k [ 2.223477] NX-protecting the kernel data: 7412k [ 2.225474] x86/mm: Checked W+X mappings: passed, no W+X pages found. Loading, please wait... starting version 237 [ 2.307862] random: systemd-udevd: uninitialized urandom read (16 bytes = read) [ 2.308176] random: systemd-udevd: uninitialized urandom read (16 bytes = read) [ 2.308215] random: systemd-udevd: uninitialized urandom read (16 bytes = read) (XEN) d10v1 failed to allocate 1020 extents of order 0 for onlining Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... = done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.31.1 [/sbin/fsck.ext4 (1) -- /dev/xvda1] fsck.ext4 -a -C0 /dev/xvda1 /dev/xvda1: clean, 62198/524288 files, 308417/2096640 blocks done. [ 3.265510] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. [ 4.200658] ip_tables: (C) 2000-2006 Netfilter Core Team [ 4.224471] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=3Dhybrid) [ 4.224586] systemd[1]: Detected virtualization xen. [ 4.224661] systemd[1]: Detected architecture x86. Welcome to Ubuntu 18.04.5 LTS! [ 4.247413] systemd[1]: Set hostname to . [ 5.064645] systemd[1]: Reached target Remote File Systems. [ OK ] Reached target Remote File Systems. [ 5.065270] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ 5.065645] systemd[1]: Created slice System Slice. [ OK ] Created slice System Slice. [ 5.066114] systemd[1]: Listening on Syslog Socket. [ OK ] Listening on Syslog Socket. [ 5.066425] systemd[1]: Listening on /dev/initctl Compatibility Named Pi= pe. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ 5.066755] systemd[1]: Listening on Journal Audit Socket. [ OK ] Listening on Journal Audit Socket. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Listening on udev Control Socket. [ OK ] Created slice User and Session Slice. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. Mounting POSIX Message Queue File System... Starting Load Kernel Modules... Starting Journal Service... Mounting Kernel Debug File System... Starting Set the console keyboard layout... [ OK ] Set up automount Arbitrary Executab=E2=80=A6rmats File System Auto= mount Point. [ OK ] Reached target Slices. [ OK ] Listening on fsck to fsckd communication Socket. Starting Remount Root and Kernel File Systems... [ OK ] Listening on udev Kernel Socket. Starting Create list of required st=E2=80=A6ce nodes for the curre= nt kernel... Starting udev Coldplug all Devices... [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Load Kernel Modules. [ OK ] Mounted Kernel Debug File System. Mounting FUSE Control File System... Starting Apply Kernel Variables... Mounting Kernel Configuration File System... [ OK ] Started Journal Service. [ OK ] Started Create list of required sta=E2=80=A6vice nodes for the cur= rent kernel. Starting Create Static Device Nodes in /dev... [ 5.244379] EXT4-fs (xvda1): re-mounted. Opts: errors=3Dremount-ro [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Mounted FUSE Control File System. [ OK ] Mounted Kernel Configuration File System. Starting Load/Save Random Seed... Starting Flush Journal to Persistent Storage... [ OK ] Started udev Coldplug all Devices. [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started Apply Kernel Variables. [ OK ] Started Load/Save Random Seed. [ OK ] Started Set the console keyboard layout. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting Set console font and keymap... Starting Raise network interfaces... Starting Create Volatile Files and Directories... Starting Tell Plymouth To Write Out Runtime Data... Starting udev Kernel Device Manager... [ OK ] Started Set console font and keymap. [ OK ] Started Tell Plymouth To Write Out Runtime Data. [ OK ] Started udev Kernel Device Manager. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Reached target Paths. [ OK ] Started Create Volatile Files and Directories. Starting Network Name Resolution... Starting Update UTMP about System Boot/Shutdown... Starting Network Time Synchronization... [ OK ] Started Entropy daemon using the HAVEGE algorithm. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Network Time Synchronization. [ OK ] Started Network Name Resolution. [ OK ] Reached target Host and Network Name Lookups. [ OK ] Reached target System Time Synchronized. [ OK ] Found device /dev/hvc0. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ OK ] Found device /sys/subsystem/net/devices/eth0. [ OK ] Started ifup for eth0. [ OK ] Found device /dev/xvdb. Activating swap /dev/xvdb... [ OK ] Activated swap /dev/xvdb. [ OK ] Reached target Swap. [ OK ] Reached target System Initialization. [ OK ] Started Message of the Day. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Started Discard unused blocks once a week. [ OK ] Reached target Timers. [ OK ] Listening on UUID daemon activation socket. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. [ OK ] Started D-Bus System Message Bus. Starting Dispatcher daemon for systemd-networkd... Starting LSB: Record successful boot for GRUB... [ OK ] Started irqbalance daemon. Starting System Logging Service... [ OK ] Started Regular background program processing daemon. Starting Login Service... [ OK ] Started Login Service. [ OK ] Started System Logging Service. (XEN) d10v1 failed to allocate 1020 extents of order 0 for onlining [ OK ] Started LSB: Record successful boot for GRUB. [ OK ] Started Dispatcher daemon for systemd-networkd. [ OK ] Started Raise network interfaces. [ OK ] Reached target Network. Starting Permit User Sessions... Starting OpenBSD Secure Shell server... [ OK ] Started Permit User Sessions. Starting Terminate Plymouth Boot Screen... Starting Hold until boot process finishes up... [ OK ] Started Hold until boot process finishes up. [ OK ] Started Serial Getty on hvc0. Starting Set console scheme... [ OK ] Started Terminate Plymouth Boot Screen. [ OK ] Started Set console scheme. [ OK ] Created slice system-getty.slice. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. [ OK ] Started OpenBSD Secure Shell server. [ OK ] Reached target Multi-User System. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Ubuntu 18.04.5 LTS bnc32 hvc0 bnc32 login: -- snip trace --- cheers PryMar56 ##xen-packaging on OFTC From xen-users-bounces@lists.xenproject.org Mon Oct 25 18:24:28 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Oct 2021 18:24:28 +0000 Received: from list by lists.xenproject.org with outflank-mailman.216015.375463 (Exim 4.92) (envelope-from ) id 1mf4dp-0002Pn-83; Mon, 25 Oct 2021 18:24:13 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216015.375463; Mon, 25 Oct 2021 18:24:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf4dp-0002Pf-4K; Mon, 25 Oct 2021 18:24:13 +0000 Received: by outflank-mailman (input) for mailman id 216015; Mon, 25 Oct 2021 18:24:11 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf4dn-0002PZ-Rs for xen-users@lists.xenproject.org; Mon, 25 Oct 2021 18:24:11 +0000 Received: from mail-yb1-xb33.google.com (unknown [2607:f8b0:4864:20::b33]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 9df8f504-5d5e-4bad-a951-14b1d616395f; Mon, 25 Oct 2021 18:24:10 +0000 (UTC) Received: by mail-yb1-xb33.google.com with SMTP id o12so24250523ybk.1 for ; Mon, 25 Oct 2021 11:24:10 -0700 (PDT) Received: by 2002:a05:6902:120a:0:0:0:0 with HTTP; Mon, 25 Oct 2021 11:24:09 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 9df8f504-5d5e-4bad-a951-14b1d616395f DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=qWuidP1Go2nk3qbO8xOImezHLZPtlK0WaZH48jiPYFA=; b=bldC8O9lsed3qrlmozyatYAVMAPpuyyhvjBFHKZBghHCueE6H2K5W1CAMK54H+UBVY 1xG8U6iiLWjZvK+HxSMS3QxlAoczLqYY5FFpLnXYcMuHqWa0fBAcpFMgMMj65rpLEHnZ j4ZOUplyw82U5wwGVU+6DcF+kZ6BjbYO+IO4H4SQErIlxJgZFZ3XeCEFnQ/IndvztSy6 hj1lVOqwCd1jH3SYA9R+diu7XQ9ovjNw/7MN55dOqENmdcJb6FgK8okCvTraksfopWsQ ZEBNUA6R2xWryxHuxSvtz26AaobmgAPAHlAfOrDIHRo1kuKb1rd1isMtTHcNEbQyUYqe uQXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qWuidP1Go2nk3qbO8xOImezHLZPtlK0WaZH48jiPYFA=; b=dcOCbj5pN6UIfAdQL9P+4g6YyO0kw/pPNJvciGOEcO/SqBZwact3LYxBc6ebikYi2M tFuE40xVHsVgugnamupxP7+QZRVPcPLWmqYzER8UXYmXOUHxZbDUQT7+DiGO7PF092kb cn9Orw/bKGZ0OfLhWqIXy2s+JFiR9n428giW8QsQ3KWkW2MdC62nllKe55CsybzrjJOp axvCmLl+Uc+eXzInIF84EZT1BzgDeQ3QH047QgWMRmoDgiZwLXvh7AyFyV8+kizDQA83 tN4qxUZmBbHxQj0KbPGBd/rE7UpwQvJxYeyZ/1ovsEdviTl3d+GNGqUOPCBLbWnFdlQq CSvw== X-Gm-Message-State: AOAM531vQsT/08jXxWwxZLhB2VpdkIQn/1JsrETW01TJRMvrLoo8bsdF +1fdLTUtNFaQ4x5arRQLFNi3ZZmKCKbDrBVC42Iukct5 X-Google-Smtp-Source: ABdhPJz1vAxkZ4LU876i5jYaqYVC/WEyKMMJkyGXI41vjrG6xR6lkKt1FjxJF1FNxCESC/jdXD5115n10FqgZNH28lY= X-Received: by 2002:a25:3258:: with SMTP id y85mr19441255yby.141.1635186250273; Mon, 25 Oct 2021 11:24:10 -0700 (PDT) MIME-Version: 1.0 From: Pry Mar Date: Mon, 25 Oct 2021 11:24:09 -0700 Message-ID: Subject: re: xen-3.0-x86_32p capability missing To: xen-users Content-Type: text/plain; charset="UTF-8" Hello, Here is host dom0 metainfo for the bnc32 domU. Bionic is still a good choice for 32bit domU since you can debootstrap it, even if there is no ISO. You can't run these 32bit domU with kernel-5.10+ as you see, although that does not explain the missing capability (from subject). $ sudo xl info host : al8xen release : 5.3.6-1.el8.elrepo.x86_64 version : #1 SMP Fri Oct 11 17:31:23 EDT 2019 machine : x86_64 nr_cpus : 2 max_cpu_id : 3 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 3062.673 hw_caps : bfebfbff:0408e3bd:20100800:00000001:00000000:00000000:00000000:00000000 virt_caps : pv hvm shadow total_memory : 4094 free_memory : 352 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 15 xen_extra : .1 xen_version : 4.15.1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit2 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : 3b98d9f35a9edd-VT-d: fix deassign of device with RMRR-Tue 5 Oct xen_commandline : placeholder dom0_mem=700M,max:748M console=vga vga=gfx-1280x1024x16 cpufreq=xen:performance guest_loglvl=all loglvl=all conring_size=48k xpti=false cc_compiler : gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1) cc_compile_by : mockbuild cc_compile_domain : prymar56.org cc_compile_date : Sat Oct 9 09:31:47 PDT 2021 build_id : bdbf6c7552173cae471e78a63fc82c7f2bef33bd xend_config_format : 4 cheers, PryMar56 ##xen-packaging on OFTC From xen-users-bounces@lists.xenproject.org Mon Oct 25 18:52:25 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 25 Oct 2021 18:52:25 +0000 Received: from list by lists.xenproject.org with outflank-mailman.216037.375480 (Exim 4.92) (envelope-from ) id 1mf54p-00060u-Jy; Mon, 25 Oct 2021 18:52:07 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216037.375480; Mon, 25 Oct 2021 18:52:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf54p-00060m-GF; Mon, 25 Oct 2021 18:52:07 +0000 Received: by outflank-mailman (input) for mailman id 216037; Mon, 25 Oct 2021 18:52:06 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mf54o-00060g-1m for xen-users@lists.xenproject.org; Mon, 25 Oct 2021 18:52:06 +0000 Received: from mout.gmx.net (unknown [212.227.17.20]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id b8944286-7334-4b7e-8f5b-617b0774fa77; Mon, 25 Oct 2021 18:52:04 +0000 (UTC) Received: from lucypher ([91.65.29.128]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MUXpQ-1mEZyk44MS-00QWVE for ; Mon, 25 Oct 2021 20:52:03 +0200 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: b8944286-7334-4b7e-8f5b-617b0774fa77 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1635187923; bh=JjhcoF9t4+AwbbbxDWPLJB+xDPStXth0ejA8PRs07TY=; h=X-UI-Sender-Class:Date:From:To:Subject; b=f7atg4EFw551cB94qeqYoWWhdX2lq0u6XCXt9De3HPyjJXed5tCZ0lrFzCPW1LLpZ YbIyidZ0y59uaZkyXqqzRvft3zVShaeAlb0fcZySf7LZ4LFZ1gWs7OCtX5iuFutLhR QIyINWyPG0i/5kAuRHNQgJDimDcQYJVrxTrv1X8w= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Date: Mon, 25 Oct 2021 20:52:02 +0200 From: Chris To: xen-users@lists.xenproject.org Message-ID: <5eea9621-8be1-4a16-bc15-c63476b566cc@lucypher> Subject: other arch MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="6176fcd2_10596eec_24a4" X-Provags-ID: V03:K1:P4juKPWYqR4Y/NuARF64KXUrufxC+ZpvYvKEjlin3ZzaBKAS4yQ iYLqUdCg/4C2hzVoEBSe2YpvWlN+m2WkVwcnF3bRTYWZjK8nX97gs0Mjws1lUM9K2LdUoN0 rT+pEt5KNZMaESXPwNh76wLMPo8YTlhT7eYyyXPQUCmfNsrkYulOufe3oerKykNB96x/cdM 3LnZHHiYdv14wWLaK5ang== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:K03JGhzvS2Y=:prM9vIrOVKzvVoVUALjYVl XkUnpFZH+X6WT3nCEEJhOjWx1zmVsRIZ4oKA6TXwbFPa2sO2jQWdziNzLSzLyoEH2WKJU3Oj0 YpJIZZGwdqBCAXsvnb9d4sbuFdYZ0LDAeCsdI9qp6WGUGfjcu4ZHgdZ3Snfr8E7Lu2rZpyuUF 7qnlkBivCzd7O88k4PbhjwVRwIr4A5izi3rFGNNbgA3djOqUhmk3Ck+HMt8ZIuUR2QYOI8ovQ BGgVs25q3/rM9P2pPCV0zKvNPZJzt2LoMjRlKmiOuA6o1DGTt9g6tYZ3Wrb+9fxC+QsBW73o9 G51766bqOkF6FNLfCzeV8YQ2kNH2LrcaHfmVAONyIQj6jQ/d03DD7sT/bhkC8DHvLcrP8WWMm mrdNHc/Iw8d+LymofZAjrecYAOvJ30bOjU2/NMvMB7r6H0OUN4letSO55JuJmnyDkE010yNQR 45b9a2GMBQp8wLCI67oXkCqYP8jdecGnlbguX7DSzaMRYcAsvVURv5hih34maWKD2xHiVmZMJ BOKu7otjrYIfVEuJXLjOmYVDCLLc4k481Ddx4uEImtbFmjwkMiq+XUzmHDogDKllAQ6zU60dO jtEWqY3zHiTIlp1P5YJvbn/BnVZ4Y7yqRPQ0+mDMKxeXQBCweiemedbrperYRlwR0HPSKiKzT ZAnAlCFLFOwE1sihqLt7Rwc253uHwuYix3WpPH28iaO6w2uD7dWozJs6lAc2fg76yPMeyKZmN MhnSfEPMSclJ1ue8Efp2TkYgU77X36x3MjeHUpIi7Zn/Hr/qMCY/aUpzO8nTy+e3TDykzyJTO e43vkc2QfjzA+kqJtE0qjfr4yJozCytlu3IdPYfvWjqJF4G3lJBdTJ7mgOXmG6BmmCxEixz2S WWnu2QN/p+/vr+qCttDS5f0veX6NohBD3P8Lj63EqDUlMYRrqlU4e/2qjr08fZMoMN+OAOWH6 L9TGrGd0v/1hq0Y/jFyK0MMiBWEN9dfe89280S/1+76xV9loRX8HQ1ZeyMr7AQypL72ncDSqG YlBGfPLaLGgO+GU4Gw9N+QG/ivv9djxS1DDtxXfVHv+jLrxqzRfj23i0IIqs0Yi4ZHYFh1u3u hSrnFBisxd7Vyc= --6176fcd2_10596eec_24a4 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi hmm it is possible to start other arch like aarch64 domU on x86_64 xen? --------- Greetz --6176fcd2_10596eec_24a4 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi
 
hmm it is possible to start other arch like aarch64 domU on x86=5F64= xen=3F
 
---------
Greetz
--6176fcd2_10596eec_24a4-- From xen-users-bounces@lists.xenproject.org Tue Oct 26 15:21:34 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Oct 2021 15:21:34 +0000 Received: from list by lists.xenproject.org with outflank-mailman.216492.376122 (Exim 4.92) (envelope-from ) id 1mfOFf-00054L-6p; Tue, 26 Oct 2021 15:20:35 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216492.376122; Tue, 26 Oct 2021 15:20:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfOFf-00054D-2s; Tue, 26 Oct 2021 15:20:35 +0000 Received: by outflank-mailman (input) for mailman id 216492; Tue, 26 Oct 2021 15:20:33 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfOFc-000546-SG for xen-users@lists.xenproject.org; Tue, 26 Oct 2021 15:20:33 +0000 Received: from mout02.posteo.de (unknown [185.67.36.66]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id cd89f195-7b8a-4dd2-8480-f7dab86d226f; Tue, 26 Oct 2021 15:20:31 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 24E3B240108 for ; Tue, 26 Oct 2021 17:20:30 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4HdwW15h7lz9rxM for ; Tue, 26 Oct 2021 17:20:29 +0200 (CEST) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: cd89f195-7b8a-4dd2-8480-f7dab86d226f DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1635261630; bh=OL8UjPW2sUAgESAFxVTvpQwb9dxdTUU7Bw4LamJEMgI=; h=Date:Subject:To:From:From; b=EUbeyhrc4S+B8dD9VnKy1c2IQvPQ4A83ixAwOIMXPJgBVdaOexWoVXAm6wOCm3vIM 9wRfa3jfvdx8xTqoYLNm7DRaMgOSV9quD2f8cjUMwHh2gmNukhBBixeTqXcoD3AV3E Y8He40/cvtxiYsJ+s10HOJ67y+x0k3QMeaYSEVCfDfqzRyCinMnRGWh162qCV0z7ke QBFdRvMJKTuBDk2hCaVt6a8bJqb96VShH/17bFMsnQpyJ1pITFRlBhjIHzXo/RHHd/ mNDDe3JAbepSPxF8ImLKkfgUbKPuLX7f65gFGUE9a9P80kj7gPgRZnOkE9NJ2UppHM jwbTTWnzFSlhw== Message-ID: Date: Tue, 26 Oct 2021 15:20:38 +0000 MIME-Version: 1.0 Subject: Re: other arch Content-Language: de-DE To: xen-users@lists.xenproject.org References: <5eea9621-8be1-4a16-bc15-c63476b566cc@lucypher> From: Frank Schiebel In-Reply-To: <5eea9621-8be1-4a16-bc15-c63476b566cc@lucypher> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello, thank you all for your kind answers an tips. I think the problem is already explained in this post from september (which i read too late, sorry for that): https://lists.xenproject.org/archives/html/xen-users/2021-09/msg00028.html It boils down to: >> upstream Linux kernel at 5.10 does not support 32-bit Xen PV guests any more. So I have to crossgrade the kernel of your 32Bit DomUs for a short term solution - long term I will have to drop 32Bit Vms alltogether. At least, this worked for me: After updating the kernel to amd64 on the old xen hypervisor the domUs are now booting fine in bullseye. Thank you for helping out, Frank From xen-users-bounces@lists.xenproject.org Tue Oct 26 20:14:59 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Oct 2021 20:14:59 +0000 Received: from list by lists.xenproject.org with outflank-mailman.216580.376244 (Exim 4.92) (envelope-from ) id 1mfSpp-0003Jq-UI; Tue, 26 Oct 2021 20:14:13 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216580.376244; Tue, 26 Oct 2021 20:14:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfSpp-0003Ji-PF; Tue, 26 Oct 2021 20:14:13 +0000 Received: by outflank-mailman (input) for mailman id 216580; Tue, 26 Oct 2021 20:14:13 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfSpo-0003Jc-SQ for xen-users@lists.xenproject.org; Tue, 26 Oct 2021 20:14:13 +0000 Received: from mail.bitfolk.com (unknown [2001:ba8:1f1:f019::25]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id d02604a9-bab3-421f-9a00-36750f6d329e; Tue, 26 Oct 2021 20:14:11 +0000 (UTC) Received: from andy by mail.bitfolk.com with local (Exim 4.89) (envelope-from ) id 1mfSpm-0004J1-GK for xen-users@lists.xenproject.org; Tue, 26 Oct 2021 20:14:10 +0000 X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: d02604a9-bab3-421f-9a00-36750f6d329e DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com ; s=alpha; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=MWZ+ZqCYYNwcY9lcMYAmlW7n0+PYXWfP0GlSYzlx33A=; b=oc2V6lN2u4cjI2gxZUBtJfApuO 8XRnumER2025mi7FBEzPy+WHkzOKxxntlpJ04q+88w8n3X1U80C2tllRshz4AWUApVn9cVHUHR4Fy yyc/il1C4aW0PQpBncQDVLCL9CZDHD4S0ROIcR9Aonh1Bjw36bTkjaeyDw3nGWU5KVJxSYqe7pmMw 38KVJBEocVYeK+KCXpgF3PdtyZCxXd6w1FSfB6/jFYmj5OQeI6gzwdtJeTIBmYUahQn7V7Q8aq9rd vLemGCzjsksuEajI07gAFm64iqZU8jqpCCtKumDNEIJ/R+/NOKnDPTob4os60nXKu/fCCv9i5yiaC nkvRebYA==; Date: Tue, 26 Oct 2021 20:14:10 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: other arch Message-ID: <20211026201410.76ta3x2kvzmrc3si@bitfolk.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Hello, On Tue, Oct 26, 2021 at 03:20:38PM +0000, Frank Schiebel wrote: > I think the problem is already explained in this post from september (which > i read too late, sorry for that): > > https://lists.xenproject.org/archives/html/xen-users/2021-09/msg00028.html > > It boils down to: > > >> upstream Linux kernel at 5.10 does not > support 32-bit Xen PV guests any more. Going to 64-bit PV avoids your problem but I'm not convinced that the kernel is the cause of your problem. I am running 4.14 hypervisor (self-compiled) and it has capability xen-3.0-x86_32p and does still run 32-bit PV with domU kernel versions < 5.10. So I do not think we have got to the bottom of why your hypervisor does not have that capability and why it can't boot Debian buster or previous domU. As far as I am aware, the hypervisor only drops xen-3.0-x86_32p capability from version 4.15 onwards. You may want to ask on Debian's Xen team mailing list: https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel Cheers, Andy From xen-users-bounces@lists.xenproject.org Tue Oct 26 23:29:49 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 26 Oct 2021 23:29:49 +0000 Received: from list by lists.xenproject.org with outflank-mailman.216619.376293 (Exim 4.92) (envelope-from ) id 1mfVrs-0005NP-Iq; Tue, 26 Oct 2021 23:28:32 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216619.376293; Tue, 26 Oct 2021 23:28:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfVrs-0005NH-Ed; Tue, 26 Oct 2021 23:28:32 +0000 Received: by outflank-mailman (input) for mailman id 216619; Tue, 26 Oct 2021 23:28:31 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfVrq-0005NB-FQ for xen-users@lists.xenproject.org; Tue, 26 Oct 2021 23:28:31 +0000 Received: from sonic303-25.consmr.mail.gq1.yahoo.com (unknown [98.137.64.206]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id b8b8c88f-b24e-4e55-8b18-200e5afed4ce; Tue, 26 Oct 2021 23:28:29 +0000 (UTC) Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.gq1.yahoo.com with HTTP; Tue, 26 Oct 2021 23:28:28 +0000 Received: by kubenode550.mail-prod1.omega.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 0f022993dfb18a558d6d3ca773f23225; Tue, 26 Oct 2021 23:28:24 +0000 (UTC) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: b8b8c88f-b24e-4e55-8b18-200e5afed4ce DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netscape.net; s=a2048; t=1635290908; bh=1ZED6khFpAmrD5gpUwpxxWjs9XyinlqGroYUoTQ5ZzE=; h=Date:To:From:Subject:References:From:Subject:Reply-To; b=HPC57KwC7yAUhS/iKClqPFdbIlEHJfL5qOyualWqsJxmw+AGsE5Cn2/u6gXO72a3FDOaJKdA09wyDBqNC47QQlAiljeUgxF3wjkBR4EsIvd5Sfg1/CY6N7mXgtzMb6YMCMrsjors2W/D4hCqlB3W9F2dXjtT8qnkkLmeQLQARdiWpUo6M1iMzaVo77N0x9DiHOVwWrtosHCYXyWhmrMRiTshqk4PB8+YYilAZeUWVA0YkNVl23ppz0HIPr5zP09IzWoU04cXMen5d8c/8JRnICYmGXNaX5pBKnl6XCsJ9ClMDTWPcYow6t6mU1zqUli2CLNCJ43QpzDLhEbUHTeK1g== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635290908; bh=OP3EAZ1wD1gK2WwMIytAsutPaZrHKYVgc5qnJEZwQiC=; h=X-Sonic-MF:Date:To:From:Subject:From:Subject; b=ecuOXHftkKFUZgoIKsD+MNn2HhDwbw5cGPQFMNug0N3Ea2+F2KiOcX5ZDzZzlLZqcrI6gI/Y4163JI7EMn0yHmiukp/K+B8mYJFAySBRJOW8oWUOfVXreAtsIRiRStmXjUxvM1cGSwKk7y/JvlCj4t3FwmxLCar9W+UnOn2QbfFMy+dTp22fxsJvWnKkF4XWTyagIC6re1EdmGR/jPOs0wTt4zR6hB4+DOIdKJg4gv2tiNqyG+2v25ZEGLUyBFPpg4MCo1DZLZGvkBEa+ZfIibbQu32I0ckVytw+Y8gcf5StAmBhK0Q+Z5MeHP+hxl5U9zyf9S8BmRZzHQypI34fQg== X-YMail-OSG: 0TmAimIVM1klef_tv12fUW_bjqX91n7r5qNrqZavkHbGxlpaEYrmzYr7p6MfmRv nYrPwJv6GKHON1JerdgVF7HfDFZeOEs8iu.9sVwOYtskiDf3_sU3Zm9sVjgEEm52XNrDcxRQ9G7B oE3a_UWVNBjaRt9mjX1uZnc0KVf4PVdnXP9rTkt1Ch_c5Pe5jDQN4_NNUd1d2peEYLkSlCeo9vK7 EIlNNSOEXumz95cPfxBJWL3bjDsVBa0vo.sRJy2Tl_QojDw.AKNLG0dClTjfsWmO_SMGKxDcfbB3 Ddu2iaYykyf_VkqfitB9U50DsujvO2nyYok4j0jssGB_XIB5mECrt.N6QkTy2oSS8BWqRIveubVl 1A9g2oEDo7WWuc1kOPeDf45fVZBzioKFfI62rwJS2DPN_08I.MalVpsobELthiyjq_2CpkovgYgG ydOq.ML0fnO9T.Nahwmn4BxbXsQF3qu1OMpMHMjqietG8dxrpKcUMTnGGXimo0BjfVbMujkBcg7G miXllT2tRInMlrxrYZdvjJk9PmeMJftFm78Gnp_mYGQlLbKkl59eTBtB9T_8r_.TIyVoy242Sxoi VQ8rlUOcPagpV9Wh4ip547SvTbS63pKi4JIkkHPi1.I0yXoPpqD9Zr5IQHo37yx4Y0otoKB9BrvL dC6eSTo87Jg5IF7xo124gEFqA8nKeaAi2zoyh.NevKiRAIbvXtoBe8YsFlRSJ.ByitmMwTKJYlx1 8lFDKFK28rBAwopvONwFr6ct2sVUxkUj8MoMLem4TIzSns9bLmS82.MFB2360gejzvPzckRnMe5a hpMxD5.g.5W17LaKLAYtMtIFISqswoIWvQY9j0hNRK4H242YgaIRh99rPE4VgrI0NKBpuZf9LraZ 09FThCEwnoaJgX20E2LkfDI_olmd8lpGwmfKC6Z6gsJ8GAbFYjQVPUDhEbLQ3NhTAj816FQD_6LX nrvmzecY3FSfe6yPcRx7WpBt_EGu2fPSj58kG42W60WE7Nasq9vThq3xyHFMCavuZNQa6t5_wB3w KjaeKB4kkdNv.IsrXkHWfeAWYBDeuEIYSdP1pxMtk2XrmBNMTXtf3rvXgQFrXLlbbvBcGvZKJheC EjOiMvPbtQLwUq98Kh7zIeCWRnkJXCyt05YEBl9Jr91_RU59_pfvP3rMqnNGi.46xVtJd6O9GCbF ULIuD5rBxzEcQoFSmGtL7hJx03FgxmrTaWDMKidZXin83jmb6_G1aauUaRkFVjyMiWMTh8sg5ykX tqmi3i7CU0HXKLgQJrP_Bdzss6FeCEEkUFV5DnX6k.0d0UrNWaqOOhqxl033XOJ9HZndcivsaWP8 Tw1JvDLdtNPKQKDsRGRSPNOaKEFkmpsFnVUrNvLkxFJgsvz3zUFsobfMvaOp41KpEkbhyqT5RISQ UqCryOYJoDeZo6hu.wMhfxDvV7VinCIcLj3dZYaY0Cq3q7qbh00ckVgtZjqNkDuIL9ZGhc.tXvV3 WeIF8N.4YP.AxfsxrNJ9QVs8iIZKNz0BKSlrXqSIQBDQo6cE5E8u67dJXQE6rUqaaHTniWFh5x5I SjrKaDKxRhBxfQM2.E2GCIPEdu1o36FMEg_yckTS4C0SNntMtse4cay4WEOXjEvgOiEWHO.qLM__ OVsyF0DqmzV1yPh1UfP4Yg.A.SoGhUx_Bhh2vP5cq_OYYHLAkFH8zMRoAGi3qSnvcgRahQdyZE8X BLTNuuM_8VlD.aUL5PPpU0sXBOA6gwbJUU1.9sVtYvzfNsFB6NiMrgCA2spCl81YeWefiWqX8PGc 3dydPEAVCmiAA0tJwr4Wiy1wKf9NT1TE4NeXXNf5C5vuKjCPRsXa34fSiRXwczCQq4JvPxAjv8FU dfN7197HQMR3kH0FaNXPf4WYZpTVXFxOpPrZH.RHfpTyXiYo1Dujj2FxLXn__JGYZscMqVCACG8i .Nv4D.QAClQOFhBstMh7udp4nTAcHmJOl7dY_E0kz8MmggsETlNdp5OyO7rVWn78SmYhcCUX0Ecr LaLLLoeZIC8lV4Je0mhlAnZvk_5E3gR4mZV1hZa_zsS1cy5J1iLxJWvHPHevDH7Pl4rTOq9GczjO jXe2HfMYlIDkxXt7Tro_nWy44OCBY3JtLgZY6PBoElWharOkDKNTfbWCsR0gQv.x7mAlWjnG.AW5 kuFdk8oLoBQiZ3pewafi.4xCm9ixJxNf_jaO.P7F5OgEKldW1nAAKlWASKe4ORuPYrw-- X-Sonic-MF: Message-ID: <435766f5-ff4d-4f1a-cd20-e3ec2a985af7@netscape.net> Date: Tue, 26 Oct 2021 19:28:22 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Content-Language: en-US To: xen-users@lists.xenproject.org From: Chuck Zmudzinski Subject: Cannot pass through PCI/Intel IGD to Debian Bullseye Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit References: <435766f5-ff4d-4f1a-cd20-e3ec2a985af7.ref@netscape.net> X-Mailer: WebService/1.1.19198 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.aol Content-Length: 5068 Hello, I am using Xen for Desktop virtualization of Windows and Linux on an older Intel box with a Haswell (4th generation) Intel Integrated Graphics Device (IGD) for graphics which is now fairly old hardware. I use Debian for the dom0 and I also use Xen's Intel IGD passthrough feature for accelerated graphics in an HVM domU. With up-to-date Debian stable version 11.1 (Bullseye) for dom0, PCI/IGD passthrough works well with Windows HVM domUs, but not with modern Linux HVM domUs. I reported this several months ago as a bug to the Debian BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988333 A quick synopsis of that bug report: In the dom0: Debian 11.1 Bullseye version of Xen: 4.14.3-1~deb11u1 Debian 11.1 Bullseye version of Qemu: 5.2+dfsg-11+deb11u1 Debian 11.1 Bullseye version of Linux kernel: 5.10.70-1 Two kinds of guests configured for passthrough (a domain config I use for a Debian 11.1 HVM is added to the end of this message): 1. Windows 10 HVM domU: I can configure it to work well with passthrough of the Intel IGD, the on-board USB card, and the sound card to Windows 10, but only with the rdm_policy set to relaxed hack with my old hardware that, AFAICT, does not isolate passthrough devices optimally. 2. Bullseye Debian 11.1 HVM domU: Passthrough with Intel IGD, USB card and sound card does not work at all The main problem I see in the Debian 11.1 dom0 Journal when starting a Debian 11.1 HVM domU configured for PCI passthrough of the Intel IGD, the USB 3 controller, and the sound card is that IRQ 16 is disabled: ----------------- Start of Journal snippet from dom0 -------------- dom0 kernel: irq 16: nobody cared ... ... dom0 kernel: Call Trace: dom0 kernel:  dom0 kernel:  dump_stack+0x6b/0x83 dom0 kernel:  __report_bad_irq+0x35/0xa7 dom0 kernel:  note_interrupt.cold+0xb/0x61 dom0 kernel:  handle_irq_event+0xa8/0xb0 ... dom0 kernel: handlers: dom0 kernel: [<00000000ad934388>] usb_hcd_irq [usbcore] dom0 kernel: [<000000003087e3ca>] ath_isr [ath9k] dom0 kernel: Disabling IRQ #16 ---------------- End of Journal snippet from dom0 --------------- From what I have read this is caused by an IRQ being assigned to a device that does not respond to the IRQ. In the dom0, IRQ #16 has been disabled according to the log, but also according to the logs, IRQ #16 is assigned to a PCI device that I do not passthrough. I am thinking perhaps this device assigned to IRQ #16, which is a USB 2 controller, belongs to the same IOMMU group (in VFIO terminology) the USB 3 controller that I do pass through belongs to: dom0 kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf053c000 0000:00:14.0 is the usb 3 controller (xhci) I do passthrough. So I think the problem with the Linux HVM domU is caused by the Linux device drivers in the domU HVM not being as able to deal with the poor isolation of the devices on this old box as well as the Windows drivers do. Am I on the right track? Can this be solved by passing through both this USB 2 controller and the USB 3 controller to the domU? A few more questions: 1. Does anyone report Intel IGD passthrough with a Debian 11 dom0 and a Debian 11 domU working on Xen with newer Intel hardware, such as 8th generation or newer? 2. Since IGD passthrough works fine with a Windows HVM, and I also discovered [0] an unmodified Debian 11.1 HVM domU works fine with a slightly modified old version of Debian 8 for the dom0, which uses the old Xen 4.4 hypervisor, the old Linux 3.16 kernel, and the old qemu traditional device model for PCI/IGD passthrough, does anyone know if it is possible to configure or patch the modern Xen 4.14 hypervisor and/or the modern qemu upstream device model to get a modern Debian 11.1 HVM domU to enable PCI/IGD passthrough to work with newer software running in dom0 than what is available from the old Debian 8 release that is now way beyond EOL? I would prefer to be able to get PCI/IGD passthrough to Debian 11.1 to work on a supported dom0 configuration such as a Debian 11.1 dom0 with Xen 4.14 instead of unsupported Debian 8.x dom0 with unsupported Xen 4.4. 3. Is this problem likely to be only limited to certain hardware that does not isolate the devices as well as modern Linux-based software expects? Thanks in advance for any advice you can give me. Regards, Chuck Zmudzinski [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988333#10 My domain config file (private data such as mac and ip addresses are redacted): builder = 'hvm' memory = '3072' vcpus = '4' device_model_version = 'qemu-xen' # device_model_version = 'qemu-xen-traditional' # This is a bullseye system (Debian 11.1) disk = ['/dev/systems/linux,,xvda,w','/dev/data/linuxdata,,xvdb,w'] name = 'bullseye-hvm' vif = [ 'mac=xx:xx:xx:xx:xx:xx,model=e1000,script=vif-route,ip=A.B.X.Y' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' boot = 'c' acpi = '1' apic = '1' viridian = '1' xen_platform_pci = '1' serial = 'pty' vga = 'none' sdl = '0' vnc = '0' gfx_passthru = '1' pci = [ '00:1b.0', '00:14.0,rdm_policy=relaxed', '00:02.0' ] From xen-users-bounces@lists.xenproject.org Wed Oct 27 08:38:01 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Oct 2021 08:38:01 +0000 Received: from list by lists.xenproject.org with outflank-mailman.216713.376426 (Exim 4.92) (envelope-from ) id 1mfeQY-0004fl-Ai; Wed, 27 Oct 2021 08:36:54 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216713.376426; Wed, 27 Oct 2021 08:36:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfeQY-0004fc-5P; Wed, 27 Oct 2021 08:36:54 +0000 Received: by outflank-mailman (input) for mailman id 216713; Wed, 27 Oct 2021 08:36:52 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfeQW-0004fW-Jq for xen-users@lists.xenproject.org; Wed, 27 Oct 2021 08:36:52 +0000 Received: from mail-il1-x130.google.com (unknown [2607:f8b0:4864:20::130]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 08cc9289-bd6c-4d3b-b59c-fdc25b34d87d; Wed, 27 Oct 2021 08:36:51 +0000 (UTC) Received: by mail-il1-x130.google.com with SMTP id l13so2134631ilh.3 for ; Wed, 27 Oct 2021 01:36:51 -0700 (PDT) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: 08cc9289-bd6c-4d3b-b59c-fdc25b34d87d DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Km1CefX/SRwyRlsGrbeXVGnhGATsVbqtA1gU3BB4hP0=; b=SUj5cy07u2XDhsFrMtjeb8AXFLcAI4wpEfj4vEcgZvx6+MCacSRfzMaCa8djpdNq2U JEp1bYlQP615qo2IsIZWIJzc6kP62eHAeDWY3kluVUOgeLBZn9X8E5AgL1kdYpbKb+Pu PDkmgrpTyXXh9hVSibE6Hf4GTlm8ZaNdf9eGFSPExQxttIbD1jwCflbKpuRD2yc+ltxt NqqXNR2k4ErLOUh2/4P5Ou/PKtV6LsCcvWrT+W9cyXtggNvpf0+EZvwkE9U0bRC1xlZp DXa33hD9ciwAalAx8uWrpaAG2uKW3oJSLrWMMekH3gd0fdelcurHgt+tdXbaGllDGy1l m0pQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Km1CefX/SRwyRlsGrbeXVGnhGATsVbqtA1gU3BB4hP0=; b=FiTnENIRTg5eg+5l7oFSaaLyYGzfpc/IBTDUBEpxEcxD4eTOVy6sZBcnJknMCT4CkZ Tu6jBWqMT9OuWuXNQHURhqrzct6wrQvqElP5Yp3L/l1+hKmqpN/YISkVSWBAe6m4ynk8 w0ut5mfZoJImxgTMeh5cqg+YctRVrC4x1EMAb6WyllnZUc6sZ6ZK30tF4HqmWgRIh6vK wUFiD9fjHpMm9T24qFym2et+AzmfyK2SJC05sDyCsvzwvjgVj+aTrcpvpPglsqIQeMsT ZWAIvQmi4EkC/PCzcgyTyYJUpb3KaFUKJ/lvOatSeKJ3iz+931n3FFul+I4bQ9Z2j+hX Mbjw== X-Gm-Message-State: AOAM532ubTlEPGlgUmvM+rtw2QuI21WKkgqOhRXvGIwMafomFyFu7362 nD/SZqEZ/j5rMA/bs25GkQa4sfD8Ge/ldqOv648= X-Google-Smtp-Source: ABdhPJwXvtnAbqkkTNo+/37goi676xL5bhXstDlvjMdiyZz5WIda05PoFFkoQAB/4FqDPmZf/5AG94JV3n1YxcnQjR4= X-Received: by 2002:a05:6e02:19ca:: with SMTP id r10mr19599428ill.148.1635323810443; Wed, 27 Oct 2021 01:36:50 -0700 (PDT) MIME-Version: 1.0 References: <435766f5-ff4d-4f1a-cd20-e3ec2a985af7.ref@netscape.net> <435766f5-ff4d-4f1a-cd20-e3ec2a985af7@netscape.net> In-Reply-To: <435766f5-ff4d-4f1a-cd20-e3ec2a985af7@netscape.net> From: C Stainer Date: Wed, 27 Oct 2021 09:36:31 +0100 Message-ID: Subject: Re: Cannot pass through PCI/Intel IGD to Debian Bullseye To: Chuck Zmudzinski Cc: xen-users@lists.xenproject.org Content-Type: text/plain; charset="UTF-8" Hi Chuck, According to Xen Project 4.15 Feature List [0]... "Increase the maximum number of guests which can share a single IRQ from 7 to 16, and make this configurable with irq-max-guests" Compiling latest Xen 4.15 from source may be applicable to your use case? [1] [0] https://wiki.xenproject.org/wiki/Xen_Project_4.15_Feature_List [1] https://wiki.xenproject.org/wiki/Compiling_Xen_From_Source C On Wed, 27 Oct 2021 at 00:28, Chuck Zmudzinski wrote: > > Hello, > > I am using Xen for Desktop virtualization of Windows and Linux > on an older Intel box with a Haswell (4th generation) Intel > Integrated Graphics Device (IGD) for graphics which is > now fairly old hardware. > > I use Debian for the dom0 and I also use Xen's Intel IGD > passthrough feature for accelerated graphics in an HVM domU. > > With up-to-date Debian stable version 11.1 (Bullseye) for dom0, > PCI/IGD passthrough works well with Windows HVM domUs, but > not with modern Linux HVM domUs. I reported this several > months ago as a bug to the Debian BTS: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988333 > > A quick synopsis of that bug report: > > In the dom0: > > Debian 11.1 Bullseye version of Xen: 4.14.3-1~deb11u1 > Debian 11.1 Bullseye version of Qemu: 5.2+dfsg-11+deb11u1 > Debian 11.1 Bullseye version of Linux kernel: 5.10.70-1 > > Two kinds of guests configured for passthrough (a domain config > I use for a Debian 11.1 HVM is added to the end of this message): > > 1. Windows 10 HVM domU: I can configure it to work well with > passthrough of the Intel IGD, the on-board USB card, and the > sound card to Windows 10, but only with the rdm_policy set > to relaxed hack with my old hardware that, AFAICT, does not > isolate passthrough devices optimally. > > 2. Bullseye Debian 11.1 HVM domU: Passthrough with Intel IGD, USB card > and sound card does not work at all > > The main problem I see in the Debian 11.1 dom0 Journal when starting > a Debian 11.1 HVM domU configured for PCI passthrough of the Intel > IGD, the USB 3 controller, and the sound card is that IRQ 16 is > disabled: > > ----------------- Start of Journal snippet from dom0 -------------- > dom0 kernel: irq 16: nobody cared ... > ... > dom0 kernel: Call Trace: > dom0 kernel: > dom0 kernel: dump_stack+0x6b/0x83 > dom0 kernel: __report_bad_irq+0x35/0xa7 > dom0 kernel: note_interrupt.cold+0xb/0x61 > dom0 kernel: handle_irq_event+0xa8/0xb0 > ... > dom0 kernel: handlers: > dom0 kernel: [<00000000ad934388>] usb_hcd_irq [usbcore] > dom0 kernel: [<000000003087e3ca>] ath_isr [ath9k] > dom0 kernel: Disabling IRQ #16 > ---------------- End of Journal snippet from dom0 --------------- > > From what I have read this is caused by an IRQ being assigned > to a device that does not respond to the IRQ. In the dom0, IRQ > #16 has been disabled according to the log, but also according > to the logs, IRQ #16 is assigned to a PCI device that I do not > passthrough. I am thinking perhaps this device assigned to > IRQ #16, which is a USB 2 controller, belongs to the same > IOMMU group (in VFIO terminology) the USB 3 controller that > I do pass through belongs to: > > dom0 kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf053c000 > > 0000:00:14.0 is the usb 3 controller (xhci) I do passthrough. > > So I think the problem with the Linux HVM domU is caused by the > Linux device drivers in the domU HVM not being as able to deal > with the poor isolation of the devices on this old box as well > as the Windows drivers do. Am I on the right track? Can this be > solved by passing through both this USB 2 controller and the > USB 3 controller to the domU? > > A few more questions: > > 1. Does anyone report Intel IGD passthrough with a Debian 11 > dom0 and a Debian 11 domU working on Xen with newer Intel > hardware, such as 8th generation or newer? > > 2. Since IGD passthrough works fine with a Windows HVM, and > I also discovered [0] an unmodified Debian 11.1 HVM domU works > fine with a slightly modified old version of Debian 8 for > the dom0, which uses the old Xen 4.4 hypervisor, the old > Linux 3.16 kernel, and the old qemu traditional device model > for PCI/IGD passthrough, does anyone know if it is possible > to configure or patch the modern Xen 4.14 hypervisor and/or > the modern qemu upstream device model to get a modern Debian > 11.1 HVM domU to enable PCI/IGD passthrough to work with > newer software running in dom0 than what is available from > the old Debian 8 release that is now way beyond EOL? I > would prefer to be able to get PCI/IGD passthrough to Debian > 11.1 to work on a supported dom0 configuration such as a > Debian 11.1 dom0 with Xen 4.14 instead of unsupported > Debian 8.x dom0 with unsupported Xen 4.4. > > 3. Is this problem likely to be only limited to certain hardware > that does not isolate the devices as well as modern Linux-based > software expects? > > Thanks in advance for any advice you can give me. > > Regards, > > Chuck Zmudzinski > > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988333#10 > > My domain config file (private data such as mac and ip addresses > are redacted): > > builder = 'hvm' > memory = '3072' > vcpus = '4' > device_model_version = 'qemu-xen' > # device_model_version = 'qemu-xen-traditional' > # This is a bullseye system (Debian 11.1) > disk = ['/dev/systems/linux,,xvda,w','/dev/data/linuxdata,,xvdb,w'] > name = 'bullseye-hvm' > vif = [ 'mac=xx:xx:xx:xx:xx:xx,model=e1000,script=vif-route,ip=A.B.X.Y' ] > on_poweroff = 'destroy' > on_reboot = 'restart' > on_crash = 'restart' > boot = 'c' > acpi = '1' > apic = '1' > viridian = '1' > xen_platform_pci = '1' > serial = 'pty' > vga = 'none' > sdl = '0' > vnc = '0' > gfx_passthru = '1' > pci = [ '00:1b.0', '00:14.0,rdm_policy=relaxed', '00:02.0' ] > From xen-users-bounces@lists.xenproject.org Wed Oct 27 16:00:40 2021 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 27 Oct 2021 16:00:40 +0000 Received: from list by lists.xenproject.org with outflank-mailman.217091.376941 (Exim 4.92) (envelope-from ) id 1mflL7-0004YC-Jy; Wed, 27 Oct 2021 15:59:45 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 217091.376941; Wed, 27 Oct 2021 15:59:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mflL7-0004Y3-Fp; Wed, 27 Oct 2021 15:59:45 +0000 Received: by outflank-mailman (input) for mailman id 217091; Wed, 27 Oct 2021 15:59:44 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mflL5-0004Xx-Ll for xen-users@lists.xenproject.org; Wed, 27 Oct 2021 15:59:44 +0000 Received: from sonic304-24.consmr.mail.gq1.yahoo.com (unknown [98.137.68.205]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id e523479d-373e-11ec-8478-12813bfff9fa; Wed, 27 Oct 2021 15:59:42 +0000 (UTC) Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Wed, 27 Oct 2021 15:59:41 +0000 Received: by kubenode523.mail-prod1.omega.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID efe8e0c98db98422a49a83241da4b8ba; Wed, 27 Oct 2021 15:59:39 +0000 (UTC) X-BeenThere: xen-users@lists.xenproject.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-users-bounces@lists.xenproject.org Precedence: list Sender: "Xen-users" X-Inumbo-ID: e523479d-373e-11ec-8478-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netscape.net; s=a2048; t=1635350381; bh=x1hu/zsfr6dzanJ+ikDBHpfHl8hLtUx2t8PHUdKq9Nc=; h=Date:Subject:To:References:From:In-Reply-To:From:Subject:Reply-To; b=d5lZCrfZcYUC9F20l1V7PQnjj/+ysN+2Z2gG8p6dpY/5olgn5B/u1RBnb4MIfCOWJYLgr0sOH9tO7y6fgdb/HcMbpR19D5kqRY8ofQX93MlFbUcHhd1N1XFVD1WITuEsbZeIlcw5h8BcndIXNV9HtHE9ad1dS2S0dk6jMbFvvSCq5M9/iPwqUyIRxqYclrthb7lwmfQzCXE2vfJaPlJJSqG/mLYVUHwohMeh2w4C2SuE12imsyilaLTsLO5MtyZiteagVdod945CFVn+JLIb26R97d8jCDRz4s7P9rjixVZPS5Q2oecheROrVhjfT8Tl+JfnSvCymAetcOWnOPZpuQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635350381; bh=Gz7gjkyoUfccLlgTxeo4L/eHWh9cIsd/sj016se6Ehg=; h=X-Sonic-MF:Date:Subject:To:From:From:Subject; b=SuOFqXPUvH65Bewm5uQAFWVvSIjqAlPwRbdJl2qDBZdp3b+MskHPXXECpzR4cE9tqvB9tpWzHdY1sUEPXj89iMreWKRQ6oQEyMxygN2Fg2BLX7UAs0owg7CjlJFhwGoeJXArrAkCHcBfpKgJXxkvYVJQ3sA7tYyNfMoG0lF89gx2eLu9/5p9kRkdvSrpeMzUC7WUTYYVtcuGmxJ8Z4o20QhhoR6yLUB5QZhVxUha5y++i9okhmrzd0WhoRIcdd7DPrOBvQwpbeODA5EqljaOg5Yw+F3YQ/cV7rVg+IhHlQ7Z1UBB3sYX0LW/2OESb7+sAaca61YlNH+/JkRnJRCyYA== X-YMail-OSG: Fl7Nar4VM1nLQoPnINnFkyycMCvksgJ3B0mjZFhEPql_8QTJjlAlHW6.5dvT9yG 6YjwM3fCTGQBT6ZqkLfaFRaTSS4ZBUDISSMGOr3XYJ2DemRIpmeo3HwMkaCdf9TAjIF.9cYl_KR2 on6.Xa6Im9FRzWAFD3gY4m1S5F6bLdODHle7zpj1Faa92.GIWVmIJNpoNKqDVmqeBx9pWqhev3NY 3u.pm6wgy9bwG1kdxU3Y78KdcXDjtF_5oF1rBHqeFizChKgsabOJ6sgdTNDUTTKpa06.c0mqrMLE RNb3cc3BuxvSdmUdhrIr1GiY5MTvDKXSgBzTC16d.cCygWJ7_6hwPN4lmIi._3TMVjZ452OXgyv3 NhKBbFmwBHzdUiDSHkLr5rNWU_Gj2tdkpHrKUW7WopQfB8niEcMUAI7Q5h1TnTVqK1lA7Ac3BEdP 7JgK.NfiVjDYq_dhRxSt.EJmfQg7YrPtqCcYYCuQpkWWlKPcbW037w0Bk1jpSp0ii1FLmbU0kYAa yad.7hCAJYI2jIMaY2scEx2us4YyqUme_PT.pkbeN9Ou7UGNQCkAThaEYdb3RhaQdZ7JqAVGOpTD RW0urWIZEjWO2UeGcOlfXnAcv2m1yQ3_eqSQ3qzLz8DmgEUea3YnpOCw98seYvDT3gvEzvltLHOB cx0JZd8RP2t4P431nBGOKIHrae8nF_ZYMKEiXuSEfaG1_feg7gRUv9QWeexcwiOnO9djrW1HIfYa NFH8laTSDyNe4P58ul5zx.fSWnEgku3lN_qzdtgCUS.XGYCaWJ1T0Xesrlr0Qt3HLToS6Rm3.dX4 Da6yGbTNqegp63gPIAyE0AznOnpyNbaWu9kLuQ9BjTL8flX3rhmMP0O_MlyH9ZERCilcn2mY8f1r Ux9xeZMO5kAbILEDaBaH3nys39VnI64NZ0dwkIyH9bgCYe.X4jD5O9NZVtg698u_XjXwDJUR2sSg p8k7l4PTasf395B0c5BEjYdQKJ4AZ4cImIzIEj701dYiu2djK1totPUoJe09Ij81YgKiT2qegeEh YoGqvwx0E5fIaUQVQ2wKmstv15NQMmKqEi.Sys7D2J6bdbWHrcHN6vZZJJRsQtwKww5TUKp6MIGW Iq1rLm9niHEhQvK4vhG8E5zLtjcO7e3Luklgu_zxCPxseoKF298zbRkQqSjGm7x7_99hKwBQ9aBt JNZ9urWo8FygZGwJiCmTL.wu3i41wGOUwaZe1C1INUefHZU5ETkMGdOYaId3o0DKkpPG50GqQL_a sJw7z4hYD1ry6tNHUhP4K0Yt7V0DZWdjgb0oJs3zuTVElho2HRb1ZXuJkJd7iPC3_vuUUBzd66Eh 8dNKYqMrnxWyNXvAvTElk0NSALnVa0pDLXMQFNKKidb2KB4gKx5rTJeQsxiE52yeHfv9v3PmNaz4 z9HdD9xDWz3ZwbE3ogBHJgLpHmHEK.YTCOdRSRQJEYLFNOcQQuNAoMc2vudOQCtD8zavv1PJElMz ViFBL3fC887CMOpxwUlEGtw3f_Qi1jZWoTP_w0Sw7T267iDGqRKd18buek.yGW6GJV85zk5vdmts jAJWfpKqzUfFlYdTWF6iSQQYZ5EfU3Ur5B3mVgf6BhVwH6rf7Etur_SzM5ftYR4..8HiW5JV7WAT O2FyXbL7rxZJCPPa6eWDBgpph9hIAV6Jq44GEDDITl6dWccb08r.4PXAMtXIer5hpsyd4_rrHqIN 0UBk882iffYAUwe_NQ1N0wlauYySeTmXHlhW6LNNPANivPpoAcfN2xyl85jeeMuset5sHI1tHNmi Z.LTUh2osMZFkBtA_X7WQ5rvifYP9gR5TyjpiivF6L8PzV4e40cW1Hpqzq.h2pM05ub89eRmq3YZ vNMqoHp28A4jozM7DinrmMuuSeVbrD2JEA7YfW13jYUOpDRm3VY9UaxaRzrMYUBz598cM.wxA1Wl X1RG5gWsa2NDhZOv_lMLrdPwhwOHIh.M5DinOfpICmnr1_S0ynt96TLojMDFd.NyEfHkzAocLec0 IjOoKrZHH6W3RApniwf4_X5bab_INL.Wbki.d_kHTfrnIWPhyBbW2fiyUT2c2COO2VOBMODXlF_b JzJf0cnqrGjQGXlg93iuOn5RCUuLpxL2UXgVW0q7BRJCMZ5xXGSxXglGrQeYcaDxYBA3byfmwiUa AaclWb2tw.0waT3Rex3T5iD0xP83YwOE.B9sKggAigHjjb3ewMppuIjJ1otfbZC1RZcLi X-Sonic-MF: Message-ID: Date: Wed, 27 Oct 2021 11:59:37 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Cannot pass through PCI/Intel IGD to Debian Bullseye Content-Language: en-US To: xen-users@lists.xenproject.org References: <435766f5-ff4d-4f1a-cd20-e3ec2a985af7.ref@netscape.net> <435766f5-ff4d-4f1a-cd20-e3ec2a985af7@netscape.net> From: Chuck Zmudzinski In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailer: WebService/1.1.19198 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.aol Content-Length: 6472 On 10/27/2021 4:36 AM, C Stainer wrote: > Hi Chuck, > > According to Xen Project 4.15 Feature List [0]... > > "Increase the maximum number of guests which can share a single IRQ > from 7 to 16, and make this configurable with irq-max-guests" Hi C, Thanks for your reply. I think you misunderstand my question, maybe I need to simplify it. It is IRQ #16 that was disabled, it is not that I am trying to share an irq with up to 16 guests. I am doing desktop virtualization and run at most 4 guests at one time due to memory limitations on my system. I think this feature is for servers or workstations with enough memory to run more than seven guests at a time, but that is not my use case. Thanks, Chuck > > Compiling latest Xen 4.15 from source may be applicable to your use case? [1] > > [0] https://wiki.xenproject.org/wiki/Xen_Project_4.15_Feature_List > [1] https://wiki.xenproject.org/wiki/Compiling_Xen_From_Source > > > C > > On Wed, 27 Oct 2021 at 00:28, Chuck Zmudzinski wrote: >> Hello, >> >> I am using Xen for Desktop virtualization of Windows and Linux >> on an older Intel box with a Haswell (4th generation) Intel >> Integrated Graphics Device (IGD) for graphics which is >> now fairly old hardware. >> >> I use Debian for the dom0 and I also use Xen's Intel IGD >> passthrough feature for accelerated graphics in an HVM domU. >> >> With up-to-date Debian stable version 11.1 (Bullseye) for dom0, >> PCI/IGD passthrough works well with Windows HVM domUs, but >> not with modern Linux HVM domUs. I reported this several >> months ago as a bug to the Debian BTS: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988333 >> >> A quick synopsis of that bug report: >> >> In the dom0: >> >> Debian 11.1 Bullseye version of Xen: 4.14.3-1~deb11u1 >> Debian 11.1 Bullseye version of Qemu: 5.2+dfsg-11+deb11u1 >> Debian 11.1 Bullseye version of Linux kernel: 5.10.70-1 >> >> Two kinds of guests configured for passthrough (a domain config >> I use for a Debian 11.1 HVM is added to the end of this message): >> >> 1. Windows 10 HVM domU: I can configure it to work well with >> passthrough of the Intel IGD, the on-board USB card, and the >> sound card to Windows 10, but only with the rdm_policy set >> to relaxed hack with my old hardware that, AFAICT, does not >> isolate passthrough devices optimally. >> >> 2. Bullseye Debian 11.1 HVM domU: Passthrough with Intel IGD, USB card >> and sound card does not work at all >> >> The main problem I see in the Debian 11.1 dom0 Journal when starting >> a Debian 11.1 HVM domU configured for PCI passthrough of the Intel >> IGD, the USB 3 controller, and the sound card is that IRQ 16 is >> disabled: >> >> ----------------- Start of Journal snippet from dom0 -------------- >> dom0 kernel: irq 16: nobody cared ... >> ... >> dom0 kernel: Call Trace: >> dom0 kernel: >> dom0 kernel: dump_stack+0x6b/0x83 >> dom0 kernel: __report_bad_irq+0x35/0xa7 >> dom0 kernel: note_interrupt.cold+0xb/0x61 >> dom0 kernel: handle_irq_event+0xa8/0xb0 >> ... >> dom0 kernel: handlers: >> dom0 kernel: [<00000000ad934388>] usb_hcd_irq [usbcore] >> dom0 kernel: [<000000003087e3ca>] ath_isr [ath9k] >> dom0 kernel: Disabling IRQ #16 >> ---------------- End of Journal snippet from dom0 --------------- >> >> From what I have read this is caused by an IRQ being assigned >> to a device that does not respond to the IRQ. In the dom0, IRQ >> #16 has been disabled according to the log, but also according >> to the logs, IRQ #16 is assigned to a PCI device that I do not >> passthrough. I am thinking perhaps this device assigned to >> IRQ #16, which is a USB 2 controller, belongs to the same >> IOMMU group (in VFIO terminology) the USB 3 controller that >> I do pass through belongs to: >> >> dom0 kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf053c000 >> >> 0000:00:14.0 is the usb 3 controller (xhci) I do passthrough. >> >> So I think the problem with the Linux HVM domU is caused by the >> Linux device drivers in the domU HVM not being as able to deal >> with the poor isolation of the devices on this old box as well >> as the Windows drivers do. Am I on the right track? Can this be >> solved by passing through both this USB 2 controller and the >> USB 3 controller to the domU? >> >> A few more questions: >> >> 1. Does anyone report Intel IGD passthrough with a Debian 11 >> dom0 and a Debian 11 domU working on Xen with newer Intel >> hardware, such as 8th generation or newer? >> >> 2. Since IGD passthrough works fine with a Windows HVM, and >> I also discovered [0] an unmodified Debian 11.1 HVM domU works >> fine with a slightly modified old version of Debian 8 for >> the dom0, which uses the old Xen 4.4 hypervisor, the old >> Linux 3.16 kernel, and the old qemu traditional device model >> for PCI/IGD passthrough, does anyone know if it is possible >> to configure or patch the modern Xen 4.14 hypervisor and/or >> the modern qemu upstream device model to get a modern Debian >> 11.1 HVM domU to enable PCI/IGD passthrough to work with >> newer software running in dom0 than what is available from >> the old Debian 8 release that is now way beyond EOL? I >> would prefer to be able to get PCI/IGD passthrough to Debian >> 11.1 to work on a supported dom0 configuration such as a >> Debian 11.1 dom0 with Xen 4.14 instead of unsupported >> Debian 8.x dom0 with unsupported Xen 4.4. >> >> 3. Is this problem likely to be only limited to certain hardware >> that does not isolate the devices as well as modern Linux-based >> software expects? >> >> Thanks in advance for any advice you can give me. >> >> Regards, >> >> Chuck Zmudzinski >> >> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988333#10 >> >> My domain config file (private data such as mac and ip addresses >> are redacted): >> >> builder = 'hvm' >> memory = '3072' >> vcpus = '4' >> device_model_version = 'qemu-xen' >> # device_model_version = 'qemu-xen-traditional' >> # This is a bullseye system (Debian 11.1) >> disk = ['/dev/systems/linux,,xvda,w','/dev/data/linuxdata,,xvdb,w'] >> name = 'bullseye-hvm' >> vif = [ 'mac=xx:xx:xx:xx:xx:xx,model=e1000,script=vif-route,ip=A.B.X.Y' ] >> on_poweroff = 'destroy' >> on_reboot = 'restart' >> on_crash = 'restart' >> boot = 'c' >> acpi = '1' >> apic = '1' >> viridian = '1' >> xen_platform_pci = '1' >> serial = 'pty' >> vga = 'none' >> sdl = '0' >> vnc = '0' >> gfx_passthru = '1' >> pci = [ '00:1b.0', '00:14.0,rdm_policy=relaxed', '00:02.0' ] >>