From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 82E12C433E0 for ; Fri, 29 Jan 2021 14:17:07 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3885D64DF1 for ; Fri, 29 Jan 2021 14:17:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3885D64DF1 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.78178.142098 (Exim 4.92) (envelope-from ) id 1l5Ua0-0000Xb-Ol; Fri, 29 Jan 2021 14:16:56 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 78178.142098; Fri, 29 Jan 2021 14:16:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1l5Ua0-0000XU-L9; Fri, 29 Jan 2021 14:16:56 +0000 Received: by outflank-mailman (input) for mailman id 78178; Fri, 29 Jan 2021 14:16:55 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1l5UZz-0000XN-My for xen-devel@lists.xenproject.org; Fri, 29 Jan 2021 14:16:55 +0000 Received: from mx2.suse.de (unknown [195.135.220.15]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id dfb4f3be-6755-4440-aae2-dc5be60d0f89; Fri, 29 Jan 2021 14:16:54 +0000 (UTC) Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 4B8AAABDA; Fri, 29 Jan 2021 14:16:53 +0000 (UTC) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: dfb4f3be-6755-4440-aae2-dc5be60d0f89 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1611929813; 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=GYU9AnLJ0CmMxvc6Bs6flLDFq+IrjaZVrAxTy6Oy/T0=; b=RiF8Odvze3hqiIyFk0NDL4i78Byz+MmGGp9ogxFvkw9fcQHJ0N/tdP8hv4S+QZ33brNsG5 yo16UIOy6Qn5bgylJSq6/S41/fM8B8oi5I3dhuK7eyG5oKGJSOPkvNKWPvALIYM3zuF45H XHprWk5oIMHvQnPXOoJ8QBW8ub7b2Q0= Subject: Re: Problems starting Xen domU after latest stable update To: Michael Labriola Cc: =?UTF-8?Q?Marek_Marczykowski-G=c3=b3recki?= , Boris Ostrovsky , David Woodhouse , Sasha Levin , Konrad Rzeszutek Wilk , Roger Pau Monne , xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org References: <2nft2kipqg.fsf@aragorn.infrastructure.cah> <983b87d6-edb8-21ea-7d6f-f653f5c0d048@oracle.com> <20210129005129.GA2452@mail-itl> <44068a70-8940-824b-9e39-b800635b92c7@suse.com> From: =?UTF-8?B?SsO8cmdlbiBHcm/Dnw==?= Message-ID: <16a2f371-1c39-13f5-c214-e054b08abbab@suse.com> Date: Fri, 29 Jan 2021 15:16:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NdtiXIueJY5Zfv7OjBCV5lEkGkEd53vvJ" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NdtiXIueJY5Zfv7OjBCV5lEkGkEd53vvJ Content-Type: multipart/mixed; boundary="tjkuZXxXv3VLDH9RmKvu7JB73Ys6zl5fu"; protected-headers="v1" From: =?UTF-8?B?SsO8cmdlbiBHcm/Dnw==?= To: Michael Labriola Cc: =?UTF-8?Q?Marek_Marczykowski-G=c3=b3recki?= , Boris Ostrovsky , David Woodhouse , Sasha Levin , Konrad Rzeszutek Wilk , Roger Pau Monne , xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org Message-ID: <16a2f371-1c39-13f5-c214-e054b08abbab@suse.com> Subject: Re: Problems starting Xen domU after latest stable update References: <2nft2kipqg.fsf@aragorn.infrastructure.cah> <983b87d6-edb8-21ea-7d6f-f653f5c0d048@oracle.com> <20210129005129.GA2452@mail-itl> <44068a70-8940-824b-9e39-b800635b92c7@suse.com> In-Reply-To: --tjkuZXxXv3VLDH9RmKvu7JB73Ys6zl5fu Content-Type: multipart/mixed; boundary="------------42C6587E6E24D886442930BF" Content-Language: en-US This is a multi-part message in MIME format. --------------42C6587E6E24D886442930BF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable On 29.01.21 15:13, Michael Labriola wrote: > On Fri, Jan 29, 2021 at 12:26 AM J=C3=BCrgen Gro=C3=9F wrote: >> >> On 29.01.21 01:51, Marek Marczykowski-G=C3=B3recki wrote: >>> On Thu, Jan 28, 2021 at 07:03:00PM -0500, Boris Ostrovsky wrote: >>>> >>>> On 1/28/21 6:52 PM, Michael D Labriola wrote: >>>>> Hey, everyone. I've run into problems starting up my Xen domUs as = of >>>>> the latest batch of stable updates. Whenever I try to create one, = I >>>>> get a bunch of block device errors like this: >>>>> >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to add device with path /local/domain/0/backend/vbd/4/51712 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to add device with path /local/domain/0/backend/vbd/4/51728 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to add device with path /local/domain/0/backend/vbd/4/51744 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to add device with path /local/domain/0/backend/vbd/4/51760 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to add device with path /local/domain/0/backend/vbd/4/51776 >>>>> libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain 4:una= ble to add disk devices >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to remove device with path /local/domain/0/backend/vbd/4/51712 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to remove device with path /local/domain/0/backend/vbd/4/51728 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to remove device with path /local/domain/0/backend/vbd/4/51744 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to remove device with path /local/domain/0/backend/vbd/4/51760 >>>>> libxl: error: libxl_device.c:1105:device_backend_callback: Domain 4= :unable to remove device with path /local/domain/0/backend/vbd/4/51776 >>>>> libxl: error: libxl_domain.c:1290:devices_destroy_cb: Domain 4:libx= l__devices_destroy failed >>>>> libxl: error: libxl_domain.c:1177:libxl__destroy_domid: Domain 4:No= n-existant domain >>>>> libxl: error: libxl_domain.c:1131:domain_destroy_callback: Domain 4= :Unable to destroy guest >>>>> libxl: error: libxl_domain.c:1058:domain_destroy_cb: Domain 4:Destr= uction of domain failed >>>>> >>>>> I'm using Xen 4.13.1 on the box I've been testing with. >>>>> >>>>> I bisected down to this commit, and reverting it does indeed fix my= >>>>> problem. Well, this commit upstream and it's cherry-picked variant= s >>>>> on linux-5.4.y and linux-5.10.y. >>>> >>>> >>>> You most likely need 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1. It hi= t Linus tree a few hours ago. >>> >>> I can confirm this fixes the same issue for me (too?), thanks! >>> Shouldn't this patch have Cc: stable? >> >> No, I don't think so. >> >> The issue being fixed by the patch has been introduced only in 5.11 >=20 > For the record, the issue is also in the latest stable 5.4.y and > 5.10.y releases (I assume older ones as well, but those are the only 2 > I tested). That's where I ran into it initially. >=20 >> and the fixing patch references the buggy patch via a Fixes: tag. >> >> If the buggy patch has been put into stable this Fixes: tag should >> result in the fix being put into the same stable branches as well. >=20 > I've never done this before... does this happen automatically? Or is > there somebody we should ping to make sure it happens? This happens automatically (I think). I have seen mails for the patch been taken for 4.14, 4.19, 5.4 and 5.10. Juergen --------------42C6587E6E24D886442930BF Content-Type: application/pgp-keys; name="OpenPGP_0xB0DE9DD628BF132F.asc" Content-Transfer-Encoding: quoted-printable 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----- --------------42C6587E6E24D886442930BF-- --tjkuZXxXv3VLDH9RmKvu7JB73Ys6zl5fu-- --NdtiXIueJY5Zfv7OjBCV5lEkGkEd53vvJ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEhRJncuj2BJSl0Jf3sN6d1ii/Ey8FAmAUGNQFAwAAAAAACgkQsN6d1ii/Ey8S Dgf9Hl56bDtrt1IrsmAcujYq9IvEmKJ32NBfPuMlyCcu8Kkxuw6tIu77AuzMdzSNZdFkScHggZRf HKUJRdv83mnE1gXRE8gJnRCQ5hPD4o+VWsKHpZlfy+73MVKbidmTdnPqrbQDGrbUukdEQE3m7ddb JVDrCHpR67YEe0q6+4MhGu4BL4FOC27UWKORjs64DJxPvVP6bBjZa/XiPaiCmUxs+/CEHcQOtV+V HZZY8CbmMqgREKnmDL75b3I+XeqD2uoefO4jTyHNdXxOEUF+aFMHpWlWqDXmFVkBwFiC7fZ64ABy QdFqEaI3TVANeUH2YpOwtrGV7DN7D5n0sr1PKBjtYA== =AVI1 -----END PGP SIGNATURE----- --NdtiXIueJY5Zfv7OjBCV5lEkGkEd53vvJ--