From xen-users-bounces@lists.xenproject.org Sat Mar 01 20:49:11 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Mar 2025 20:49:11 +0000 Received: from list by lists.xenproject.org with outflank-mailman.899511.1307743 (Exim 4.92) (envelope-from ) id 1toTkw-00062n-86; Sat, 01 Mar 2025 20:48:18 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 899511.1307743; Sat, 01 Mar 2025 20:48: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 1toTkw-00062E-1a; Sat, 01 Mar 2025 20:48:18 +0000 Received: by outflank-mailman (input) for mailman id 899511; Sat, 01 Mar 2025 20:48:17 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1toTkv-000628-DV for xen-users@lists.xenproject.org; Sat, 01 Mar 2025 20:48:17 +0000 Received: from out.good-with-numbers.com (out.good-with-numbers.com [70.36.235.100]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 7ddb65ec-f6de-11ef-9898-31a8f345e629; Sat, 01 Mar 2025 21:48:15 +0100 (CET) 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: 7ddb65ec-f6de-11ef-9898-31a8f345e629 Date: Sat, 1 Mar 2025 20:45:21 +0000 From: Mike To: Elliott Mitchell Cc: xen-users@lists.xenproject.org Subject: Re: domU memory exceeded =?us-ascii?B?PT89?= =?us-ascii?Q?=3E?= spontaneous reboots Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Elliott, On Dec 9, 2024, Mike wrote: > > In order to eliminate software (Xen) bugs, what is really needed is to > > break out a null modem cable. Then hook up another computer or something > > else capable of functioning as a dumb terminal (ha! old tech to the > > rescue). Serial ports are rather more effective for observing Xen > > panicing. > > The motherboard doesn't have a serial port on its backpanel, just jumpers for > attaching one on the board. And the case doesn't offer a place to mount a > serial port. > > I'm not inclined to mess with the system to that degree at this point. It's > functioning for now. Since the problem has returned, I'm willing to dig into this a bit more before considering KVM. Is there a way to capture the failure output via the IPMI port instead? Since that hardware interface exists already. Not seeing it as a `console` option. There are also USB ports on this system. From xen-users-bounces@lists.xenproject.org Sat Mar 01 21:23:47 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Mar 2025 21:23:47 +0000 Received: from list by lists.xenproject.org with outflank-mailman.899555.1307759 (Exim 4.92) (envelope-from ) id 1toUIt-0003m6-Qb; Sat, 01 Mar 2025 21:23:23 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 899555.1307759; Sat, 01 Mar 2025 21:23:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1toUIt-0003lz-Nv; Sat, 01 Mar 2025 21:23:23 +0000 Received: by outflank-mailman (input) for mailman id 899555; Sat, 01 Mar 2025 21:23:22 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1toUIs-0003lt-Fs for xen-users@lists.xenproject.org; Sat, 01 Mar 2025 21:23:22 +0000 Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.221]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 64b269f8-f6e3-11ef-9898-31a8f345e629; Sat, 01 Mar 2025 22:23:18 +0100 (CET) Received: from mail.onlineschubla.de by smtp.strato.de (RZmta 51.2.23 DYNA|AUTH) with ESMTPSA id efa8c8121LNHqt2 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Sat, 1 Mar 2025 22:23:17 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.onlineschubla.de (Postfix) with ESMTP id 92D2420809 for ; Sat, 1 Mar 2025 22:23:16 +0100 (CET) Received: from mail.onlineschubla.de ([127.0.0.1]) by localhost (mail.onlineschubla.de [127.0.0.1]) (amavis, port 10024) with ESMTP id 9xim5b4Cjf90 for ; Sat, 1 Mar 2025 22:23:15 +0100 (CET) Received: from [10.0.0.105] (unknown [10.0.0.105]) by mail.onlineschubla.de (Postfix) with ESMTPA id 44C2C20043 for ; Sat, 1 Mar 2025 22:23:15 +0100 (CET) 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: 64b269f8-f6e3-11ef-9898-31a8f345e629 ARC-Seal: i=1; a=rsa-sha256; t=1740864197; cv=none; d=strato.com; s=strato-dkim-0002; b=nj2UYSM8Xc6bp4NYv/MWYhM1/h2Ai6j5ybqLRwGuVlCcgizAJiailPpneH6UiSoD3j nL7DCJPU5t9Ev/K2cnaoTHYXkdD1528DSzxwzYUjo5MTg637ZFU+HVhd/A3tp8cXw6rd FfBAG414HcMEpOdQapjlNPWs5lLTkmCx0QHc7of3m1Z8pU6ui7YIDmpPS3XyWzkM0zMp jsWe1AY4pJcjBzKjgK6OawEvgzMt3jdJNQ+yF71v929W8h+Z5+/l6qeqJ4WcsUXuxo1e Vpf39D1f871M15V00kHO4wTDAhty8w3d66WhCV9CSbwPy+UcfBt+6AGqA0m0NFtp+yLq 3fkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1740864197; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=9ua7cD73G/3cYc5KRId+W1wtd851x4vlC+iWimVKLoI=; b=jA1Y/g3KzTMubM9a6cXUPCoE4DxE0Xxi0DdTPbsgJyDjyhd4ykM2GsOHOBSln+gYzg G1Ud9H3pF4o7y5Y9lUG/h0nh49AGxL7MuzyipwxxHkYw4/JZaJdqZDkCcQQgcA2vK6JJ d2IFnKt4XR3edacbzd3y898bA/i887gRt4xJ04yYEi2pPLualX2WYF9zbjhIcO9g6QLo 5TtsXRItyZV+MOKLnNe8PdQr2BV58DI774eNWwrPJMCjQmS3H8oWxu3YimAWU8KTihTa TiZlUJ24YP1Q1SsBJgYq1EXJXl3JE20z4IDrBtvA7eHYDy2R+fKRAGA2AnZFez1lK0gn CAWw== ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none X-RZG-CLASS-ID: mo00 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1740864197; s=strato-dkim-0002; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=9ua7cD73G/3cYc5KRId+W1wtd851x4vlC+iWimVKLoI=; b=Jz+kUa7ZQ6KFUN6nvfZnWtBgGIy3oqnMN2/ALEElfyuyDQQ0DvFdGafLmi6lzyMphv Rz+m0XzWjGrZ8ix9bTlhl6kj1gQwqEsha1Rhw4Dh5jottj9tsXLaZT+WGg9h7gbFNmhn 2xp6+CnkrWIw3r3sErrcgm8SUsoh8xzBwBE7LChbr3qDFn5h1ms/7N5sXHIr1Vz+JnBv TdyStdFFbO1CPoLrbWvgoHpG6vocjAR2tujkxbYpI9S3GMzA+ufiqnrwLl7bG1TR8cVi CbN1dJMl596DWsc35IBU2Q+ybdN1GXpNd7eQhUNbaIWHwoQze4RNoc0qqKZvgTlx5FQi tLpA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1740864197; s=strato-dkim-0003; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=9ua7cD73G/3cYc5KRId+W1wtd851x4vlC+iWimVKLoI=; b=dGYLylSVsr1zgz8q4vI5mpqZtz/dwL+Ed8YCl1P6m5TXdJev/LF+rkyw1VAs3+W2t0 JmrCF2b6hn02b2Pmf1Ag== X-RZG-AUTH: ":PG0ReWCndfO3rCSML4AvNaDxJ7WJyilEI/NMX3IPpS4dskMFCImJEP1iWJS8AYnrHg9F" X-Virus-Scanned: Debian amavis at onlineschubla.de Message-ID: Date: Sat, 1 Mar 2025 22:23:09 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: domU memory exceeded =?=> spontaneous reboots To: xen-users@lists.xenproject.org References: Content-Language: en-US From: Paul Leiber In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 01.03.2025 um 21:45 schrieb Mike: > Elliott, > > On Dec 9, 2024, Mike wrote: >>> In order to eliminate software (Xen) bugs, what is really needed is to >>> break out a null modem cable. Then hook up another computer or something >>> else capable of functioning as a dumb terminal (ha! old tech to the >>> rescue). Serial ports are rather more effective for observing Xen >>> panicing. >> >> The motherboard doesn't have a serial port on its backpanel, just jumpers for >> attaching one on the board. And the case doesn't offer a place to mount a >> serial port. >> >> I'm not inclined to mess with the system to that degree at this point. It's >> functioning for now. > > Since the problem has returned, I'm willing to dig into this a bit more > before considering KVM. > > Is there a way to capture the failure output via the IPMI port instead? > Since that hardware interface exists already. Not seeing it as a `console` > option. There are also USB ports on this system. > AFAIK, Serial over LAN (SoL) is a standard function of IPMI and the likes. Wikipedia says that SoL is availabe since IPMI version 2.0 [1] On my Intel Xeon based server (which is approx. 10 years old), I can access Xen's serial console via SoL. I successfully tried Intel Manageability Commander and Mesh Commander [2]. Paul [1] https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface [2] https://www.meshcommander.com/ From xen-users-bounces@lists.xenproject.org Wed Mar 05 19:12:05 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Mar 2025 19:12:05 +0000 Received: from list by lists.xenproject.org with outflank-mailman.902675.1310694 (Exim 4.92) (envelope-from ) id 1tpu9T-0006Ao-5e; Wed, 05 Mar 2025 19:11:31 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 902675.1310694; Wed, 05 Mar 2025 19:11:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpu9T-0006Ah-2X; Wed, 05 Mar 2025 19:11:31 +0000 Received: by outflank-mailman (input) for mailman id 902675; Wed, 05 Mar 2025 19:11:29 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpu9R-0006AQ-5L for xen-users@lists.xen.org; Wed, 05 Mar 2025 19:11:29 +0000 Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [2a00:1450:4864:20::634]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id a2c8151c-f9f5-11ef-9898-31a8f345e629; Wed, 05 Mar 2025 20:11:27 +0100 (CET) Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-abbd96bef64so1113514166b.3 for ; Wed, 05 Mar 2025 11:11:26 -0800 (PST) Received: from [192.168.1.10] (host-92-26-98-202.as13285.net. [92.26.98.202]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-ac1ecafa17fsm368668266b.162.2025.03.05.11.11.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Mar 2025 11:11:24 -0800 (PST) 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: a2c8151c-f9f5-11ef-9898-31a8f345e629 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrix.com; s=google; t=1741201886; x=1741806686; darn=lists.xen.org; h=content-transfer-encoding:autocrypt:subject:from:cc:to :content-language:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=DZaame9Ci028tUxlPLSZYIhVkogn4h4VCrJpnOsb3QI=; b=WmyGD0RaYXSCLECeQ5nkN6CqoVkEauRgRGSoNCsH4dMmYa5MlzA2mDiE9uBXT5cm2m 4+OdGDHOoLThONEPGkwE9JiflPmorJq+sF6Q208dRJZXFuPQslidAJIWzKGfkpnQ4pNY JlEESiPpO363AFnmo0gZ2IHgh+S1cQBVJqlhU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741201886; x=1741806686; h=content-transfer-encoding:autocrypt:subject:from:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=DZaame9Ci028tUxlPLSZYIhVkogn4h4VCrJpnOsb3QI=; b=EHZ6Jg549lJSic0Vi1dj37ZstHhwbi1AFlQXQ9CjCng+LqfnRvLCUzJIkMzIYDAMGN brusEZ9gUwy9KTebEsuw+DJOEPFyQtDowzNZCTt8y7Xa5F/u0kYlgKOFyF5nXVu/ZPKl wEuAtPe2r6Sc8m2cpcVDsrv04C67xflicIMpopYznbYgoMHW40ojCtLZzfzJSsRPJuAc QIhqmKqZNIXnjb5NIUPltsaiGSR4kyekMmqc+IAB13kEWxo5xqcdZLCq72q/S6glXlJz k6GbEw0xp9tHXqYAbnaLmDVYm+sfecrKLs3AUV1YcbbOyuwV6UfzCFfrGPQuVU1Kmsr7 DYYA== X-Forwarded-Encrypted: i=1; AJvYcCUE9wSypIYI9FncxAoJaAJKxrwki0aRovyg7K+jBSnRKG51juSb0VnuqJKvJGwLofDB5IsEZRTL414=@lists.xen.org X-Gm-Message-State: AOJu0Yx1xugJ1RdAWGXCv64a88oc1az23BinP/8fErjrmzUPSzRMOwTP cK2iye7DMh461htZp89pVVCporVgJPjD3YmrOfzWr4yIxTKn+L8DdsOhQ8QJD6E= X-Gm-Gg: ASbGncumog2Y7HSj4f6eS/VbTVJy6F/YZBkjabn3oPEQQ/odfIhdCPOClWIGDJsxBub P1nzdScGYG2+9tzuiaWszOIPQSXn2WAWoHAhS+Ya8HGauJWhwJLHR/27gPvBiBVZMi9QcKE2urX VjsWScrLg7oBwMOVPcKs7K+rAyarGcdy/nrW8Y7fYJAZuia8jaRSvlKyMbvU8XEDBe1ssScKUpe BjhP8VRqtAppCW4H2yIA1IGung6iVhpG79ndsIxXms/97m/r/b+zjCjMcuoVMf0d/lu/TXX1k9W fCqCidJJGaQA/ryUMj4pUpfTRxtUKTaigmkvCngYYbkYxmFRkjIflPVvPetufdhJwTI9BU54dyg VcTUl8aLq X-Google-Smtp-Source: AGHT+IE4Oj0YBaW1g1qsSSQnSSCOaSMQmxLzlg0vhrLzGeXWTn120/RwT20dUywm3p5AOlyDXi21Kw== X-Received: by 2002:a17:907:3f25:b0:ac1:fcda:78c1 with SMTP id a640c23a62f3a-ac20d97e6b7mr466336266b.34.1741201885183; Wed, 05 Mar 2025 11:11:25 -0800 (PST) Message-ID: Date: Wed, 5 Mar 2025 19:11:23 +0000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: "xen-announce@lists.xen.org" , Xen-devel , "xen-users@lists.xen.org" , "oss-security@lists.openwall.com" Cc: "Xen.org security team" From: Andrew Cooper Subject: Xen Security Notice 2 (CVE-2024-35347) AMD CPU Microcode Signature Verification Vulnerability Autocrypt: addr=andrew.cooper3@citrix.com; keydata= xsFNBFLhNn8BEADVhE+Hb8i0GV6mihnnr/uiQQdPF8kUoFzCOPXkf7jQ5sLYeJa0cQi6Penp VtiFYznTairnVsN5J+ujSTIb+OlMSJUWV4opS7WVNnxHbFTPYZVQ3erv7NKc2iVizCRZ2Kxn srM1oPXWRic8BIAdYOKOloF2300SL/bIpeD+x7h3w9B/qez7nOin5NzkxgFoaUeIal12pXSR Q354FKFoy6Vh96gc4VRqte3jw8mPuJQpfws+Pb+swvSf/i1q1+1I4jsRQQh2m6OTADHIqg2E ofTYAEh7R5HfPx0EXoEDMdRjOeKn8+vvkAwhviWXTHlG3R1QkbE5M/oywnZ83udJmi+lxjJ5 YhQ5IzomvJ16H0Bq+TLyVLO/VRksp1VR9HxCzItLNCS8PdpYYz5TC204ViycobYU65WMpzWe LFAGn8jSS25XIpqv0Y9k87dLbctKKA14Ifw2kq5OIVu2FuX+3i446JOa2vpCI9GcjCzi3oHV e00bzYiHMIl0FICrNJU0Kjho8pdo0m2uxkn6SYEpogAy9pnatUlO+erL4LqFUO7GXSdBRbw5 gNt25XTLdSFuZtMxkY3tq8MFss5QnjhehCVPEpE6y9ZjI4XB8ad1G4oBHVGK5LMsvg22PfMJ ISWFSHoF/B5+lHkCKWkFxZ0gZn33ju5n6/FOdEx4B8cMJt+cWwARAQABzSlBbmRyZXcgQ29v cGVyIDxhbmRyZXcuY29vcGVyM0BjaXRyaXguY29tPsLBegQTAQgAJAIbAwULCQgHAwUVCgkI CwUWAgMBAAIeAQIXgAUCWKD95wIZAQAKCRBlw/kGpdefoHbdD/9AIoR3k6fKl+RFiFpyAhvO 59ttDFI7nIAnlYngev2XUR3acFElJATHSDO0ju+hqWqAb8kVijXLops0gOfqt3VPZq9cuHlh IMDquatGLzAadfFx2eQYIYT+FYuMoPZy/aTUazmJIDVxP7L383grjIkn+7tAv+qeDfE+txL4 SAm1UHNvmdfgL2/lcmL3xRh7sub3nJilM93RWX1Pe5LBSDXO45uzCGEdst6uSlzYR/MEr+5Z JQQ32JV64zwvf/aKaagSQSQMYNX9JFgfZ3TKWC1KJQbX5ssoX/5hNLqxMcZV3TN7kU8I3kjK mPec9+1nECOjjJSO/h4P0sBZyIUGfguwzhEeGf4sMCuSEM4xjCnwiBwftR17sr0spYcOpqET ZGcAmyYcNjy6CYadNCnfR40vhhWuCfNCBzWnUW0lFoo12wb0YnzoOLjvfD6OL3JjIUJNOmJy RCsJ5IA/Iz33RhSVRmROu+TztwuThClw63g7+hoyewv7BemKyuU6FTVhjjW+XUWmS/FzknSi dAG+insr0746cTPpSkGl3KAXeWDGJzve7/SBBfyznWCMGaf8E2P1oOdIZRxHgWj0zNr1+ooF /PzgLPiCI4OMUttTlEKChgbUTQ+5o0P080JojqfXwbPAyumbaYcQNiH1/xYbJdOFSiBv9rpt TQTBLzDKXok86M7BTQRS4TZ/ARAAkgqudHsp+hd82UVkvgnlqZjzz2vyrYfz7bkPtXaGb9H4 Rfo7mQsEQavEBdWWjbga6eMnDqtu+FC+qeTGYebToxEyp2lKDSoAsvt8w82tIlP/EbmRbDVn 7bhjBlfRcFjVYw8uVDPptT0TV47vpoCVkTwcyb6OltJrvg/QzV9f07DJswuda1JH3/qvYu0p vjPnYvCq4NsqY2XSdAJ02HrdYPFtNyPEntu1n1KK+gJrstjtw7KsZ4ygXYrsm/oCBiVW/OgU g/XIlGErkrxe4vQvJyVwg6YH653YTX5hLLUEL1NS4TCo47RP+wi6y+TnuAL36UtK/uFyEuPy wwrDVcC4cIFhYSfsO0BumEI65yu7a8aHbGfq2lW251UcoU48Z27ZUUZd2Dr6O/n8poQHbaTd 6bJJSjzGGHZVbRP9UQ3lkmkmc0+XCHmj5WhwNNYjgbbmML7y0fsJT5RgvefAIFfHBg7fTY/i kBEimoUsTEQz+N4hbKwo1hULfVxDJStE4sbPhjbsPCrlXf6W9CxSyQ0qmZ2bXsLQYRj2xqd1 bpA+1o1j2N4/au1R/uSiUFjewJdT/LX1EklKDcQwpk06Af/N7VZtSfEJeRV04unbsKVXWZAk uAJyDDKN99ziC0Wz5kcPyVD1HNf8bgaqGDzrv3TfYjwqayRFcMf7xJaL9xXedMcAEQEAAcLB XwQYAQgACQUCUuE2fwIbDAAKCRBlw/kGpdefoG4XEACD1Qf/er8EA7g23HMxYWd3FXHThrVQ HgiGdk5Yh632vjOm9L4sd/GCEACVQKjsu98e8o3ysitFlznEns5EAAXEbITrgKWXDDUWGYxd pnjj2u+GkVdsOAGk0kxczX6s+VRBhpbBI2PWnOsRJgU2n10PZ3mZD4Xu9kU2IXYmuW+e5KCA vTArRUdCrAtIa1k01sPipPPw6dfxx2e5asy21YOytzxuWFfJTGnVxZZSCyLUO83sh6OZhJkk b9rxL9wPmpN/t2IPaEKoAc0FTQZS36wAMOXkBh24PQ9gaLJvfPKpNzGD8XWR5HHF0NLIJhgg 4ZlEXQ2fVp3XrtocHqhu4UZR4koCijgB8sB7Tb0GCpwK+C4UePdFLfhKyRdSXuvY3AHJd4CP 4JzW0Bzq/WXY3XMOzUTYApGQpnUpdOmuQSfpV9MQO+/jo7r6yPbxT7CwRS5dcQPzUiuHLK9i nvjREdh84qycnx0/6dDroYhp0DFv4udxuAvt1h4wGwTPRQZerSm4xaYegEFusyhbZrI0U9tJ B8WrhBLXDiYlyJT6zOV2yZFuW47VrLsjYnHwn27hmxTC/7tvG3euCklmkn9Sl9IAKFu29RSo d5bD8kMSCYsTqtTfT6W4A3qHGvIDta3ptLYpIAOD2sY3GYq2nf3Bbzx81wZK14JdDDHUX2Rs 6+ahAA== Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit See: https://bughunters.google.com/blog/5424842357473280/zen-and-the-art-of-microcode-hacking https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7033.html Right now there are four known but (reasonably) benign microcodes from a non-AMD source.  However, there is a tool to sign arbitrary microcode. In Xen, we've provided a stopgap mitigation to perform extra checks on microcode load on affected CPU families.  This is a SHA2 digest check against hashes with believed-good provenance.  This is staging only for now, in case it is overly disruptive. This will not protect against an already-compromised platform, but it will prevent an uncompromised system becoming compromised via Xen's microcode loading capabilities. On affected systems, the only complete fix is a firmware update.  This is a very firmly recommended course of action. Sincerely, ~Andrew, on behalf of the Xen Security Team. From xen-users-bounces@lists.xenproject.org Wed Mar 05 22:07:01 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Mar 2025 22:07:01 +0000 Received: from list by lists.xenproject.org with outflank-mailman.902774.1310752 (Exim 4.92) (envelope-from ) id 1tpwsb-0006s8-Fl; Wed, 05 Mar 2025 22:06:17 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 902774.1310752; Wed, 05 Mar 2025 22:06: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 1tpwsb-0006s1-At; Wed, 05 Mar 2025 22:06:17 +0000 Received: by outflank-mailman (input) for mailman id 902774; Wed, 05 Mar 2025 22:06:16 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpwsa-0006ro-BO for xen-users@lists.xenproject.org; Wed, 05 Mar 2025 22:06:16 +0000 Received: from mail-oa1-x2f.google.com (mail-oa1-x2f.google.com [2001:4860:4864:20::2f]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 06762a75-fa0e-11ef-9898-31a8f345e629; Wed, 05 Mar 2025 23:06:02 +0100 (CET) Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2bcc5c887efso20977fac.2 for ; Wed, 05 Mar 2025 14:06:02 -0800 (PST) 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: 06762a75-fa0e-11ef-9898-31a8f345e629 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=malwation.com; s=google; t=1741212361; x=1741817161; darn=lists.xenproject.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=M5hCnZbYP5dUn03pFzViTItIx1J8XbSrIgN3JhUNevA=; b=iIdW+Sty/dizZlZ7NQSNMzmjH6GSBP7Lt4RxzgkEXYgzcvSbtGfbl2qx+6UHRwMc6G tLxSHBWqn9zoVch3ogVv64cT6IPk4aqOPzOUUyC+dcZ4qZSjt1ocKH0lG7qXBgHDZRHB FtmjSyxR8LRe3Rbd2ufh5jeQiU5m4N1bm6Dh3O0MUupRkeyqunzkQBl/1oRv+w/UK9A5 n5D7S58X5PsCUY5NYL/tjkmPbEDuMmh4+0FIh5H/xKWZhby0YzkvJL2mJhr9NmtxhVOg HKOLh4SssjN2GRntkMlKSHgPS49I8f4obe2IOf24kIYfgIstV/ics/zcKGjcsAODzZhc 1I4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741212361; x=1741817161; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=M5hCnZbYP5dUn03pFzViTItIx1J8XbSrIgN3JhUNevA=; b=I4RC2/aLvZOl3Ij2FLl/hw6ZwBxBp+yeQA/17T5bfApaMt6qHYDxacm+9Jd2v1b8KB QxJ2kJAU8lM+lSd2Wws4x62XBRaPr1wtKaHhNGYtTVYdXtbRujZ9YnwD7qZnH4SAAUt2 yf3BsSrKKFoZ2TpBom/CjoXoVsU8IxSlPZrq1gIhsJfGDlhkANv+nHo+iWbPM6F5WAre 2m8ZzwjJpl3332jbj5K2WhETLtzdz7K7zkPNT4WqoQhgrzik+m/uhwULY3kJ/weIjdfw QJse5Xe0uUcbaAHPOQrRQhyAXKVrDJ43M80uGxQfG0S/HYJYF7yUeHXfn6QR0uKFOFWu DmXg== X-Forwarded-Encrypted: i=1; AJvYcCW9ZfkyfeK/fKpjSmyY5aRsQt4otIAPV/eZWH5Hc6MmygPS6VesLiEHYd8di77sK9B3PE3FBnpkcjQ=@lists.xenproject.org X-Gm-Message-State: AOJu0YwHPRrjU14RrDZcemnfMn7xQ7VArXWwF0NeD60uKUa/lbjPQuPe frpb8lz2j1YNK7xBdtC9S+cHsyHSbGDVNsay1VF+2jMRAf5k9Y92p9mBMJW9SBM6iqAlYmDpBcm EFDxB3IRoOOuHdrjKU+RAFSGRlbsRS4Feg5UefR9hY0HzISyqV4D8v7PO X-Gm-Gg: ASbGncvTGJ0dXUDg1r0eV96MKsotdhSZSZ6U8p3pjupMxfIZj6zIj4rm8hnYIjMEAY/ TVMGEtElKVFK5cO6xilf1XD1zrKtCAQ2HC6fOxu8wP4ta2+c5EqFsXCnNeYRZq+l+AO+SyL/q+R 7xa12TbM/focK/JddaoEvknG0= X-Google-Smtp-Source: AGHT+IGRowsngn07NCsyZTcdbLfd6yMbnpb4znYTPW3Ym2gzPIIXMCq7jw26S3Qm2pxKTjGP6N9eaN2983BBxLZc6KI= X-Received: by 2002:a05:6870:2192:b0:29e:76c8:be2e with SMTP id 586e51a60fabf-2c21cd20179mr2887455fac.28.1741212361101; Wed, 05 Mar 2025 14:06:01 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?B?S0HEnkFOIEnFnklMREFL?= Date: Thu, 6 Mar 2025 01:05:50 +0300 X-Gm-Features: AQ5f1Jp0BZUIcsEM4ZJvNyQLKtAMwqyfxXDv55iUDWhh-tF4-ayiR9SrZrlpCaA Message-ID: Subject: BUG - running new version on nested virtualization To: xen-devel@lists.xenproject.org, xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="00000000000043304c062f9f986d" --00000000000043304c062f9f986d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey there I'm facing weird issue. At my lab env. i'm building xen 4.18 and make deb package than i use it on virtual machine which running on esxi with CPU features for nested virtualization and there's no problem. (I can create vm and able to do all operational things etc.) Last week i tried to migrate 4.19 and 4.20 but Xen get stuck on booting and at debug log i just see error about mounting /proc/xen (mount: /proc/xen: mount point does not exist.) I've no f... idea why it caused. (At my all tries, i used fresh install of ubuntu server 22.04, 24.04) Is there any one faced issue and is there special things to do in build phase for nested virtualization? (I didn't change anything while building 4.18, i'm just using stable branch) Regards Ka=C4=9Fan --00000000000043304c062f9f986d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey there

I'm facing weird issue. At my lab env. i'= m building xen 4.18 and make deb package than i use it on virtual machine w= hich running on esxi with CPU features for nested virtualization and there&= #39;s no problem. (I can create vm and able to do all operational things et= c.)

Last week i tried to migrate 4.19 and 4.20 but Xen get stuck= on booting and at debug log i just see error about mounting /proc/xen (mou= nt: /proc/xen: mount point does not exist.) I've no f... idea why it ca= used. (At my all tries, i used fresh install of ubuntu server 22.04, 24.04)=

Is there any one faced issue and is there special things to do in= build phase for nested virtualization? (I didn't change anything while= building 4.18, i'm just using stable branch)=C2=A0

=
Regards
= Ka=C4=9Fan

--00000000000043304c062f9f986d-- From xen-users-bounces@lists.xenproject.org Wed Mar 05 22:44:41 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Mar 2025 22:44:41 +0000 Received: from list by lists.xenproject.org with outflank-mailman.902829.1310794 (Exim 4.92) (envelope-from ) id 1tpxTS-0008FI-2f; Wed, 05 Mar 2025 22:44:22 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 902829.1310794; Wed, 05 Mar 2025 22:44:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpxTR-0008EU-Ua; Wed, 05 Mar 2025 22:44:21 +0000 Received: by outflank-mailman (input) for mailman id 902829; Wed, 05 Mar 2025 22:44:20 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpxTQ-0008Bt-2r for xen-users@lists.xenproject.org; Wed, 05 Mar 2025 22:44:20 +0000 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [2a00:1450:4864:20::632]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 5ec1fe23-fa13-11ef-9ab4-95dc52dad729; Wed, 05 Mar 2025 23:44:19 +0100 (CET) Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-abf5358984bso5574266b.3 for ; Wed, 05 Mar 2025 14:44:17 -0800 (PST) Received: from [192.168.1.10] (host-92-26-98-202.as13285.net. [92.26.98.202]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-abf4a3a19b2sm884386166b.44.2025.03.05.14.44.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Mar 2025 14:44:16 -0800 (PST) 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: 5ec1fe23-fa13-11ef-9ab4-95dc52dad729 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrix.com; s=google; t=1741214657; x=1741819457; darn=lists.xenproject.org; h=content-transfer-encoding:in-reply-to:autocrypt:from :content-language:references:to:subject:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=pTwmi0cUF3/pS1Hz6HN1qkSC3wILXQEsVZibWmbgZsw=; b=GDsw5eiW9Us/6AlzqmswcepX5qLKdzWhrQfqg05jP99+MW3caT7mJ+ykpxkoipKqs9 GtWsPOLAXmCYTOT8sjNSVD4nSoZGCZxeCZ3Jze42zRO0qvVwory9a95GTzFii3IGQbvu EPLOrF2K/MJsz4dWTT9EQ4AVTjy8P+NK/HFZg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741214657; x=1741819457; h=content-transfer-encoding:in-reply-to:autocrypt:from :content-language:references:to:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pTwmi0cUF3/pS1Hz6HN1qkSC3wILXQEsVZibWmbgZsw=; b=W9q/Y3B0k8lKOJOlBCQSL5q/tPji9Rncxz7udpS7Wx1FZQW2BHr1q9EDproi76fZZB 7vJZqP0m1UezT96YsXaZMNeNH0rU2q83MTTKcp8upNuMJbm7NJa2TxwW+I/gXrfKzuHL TUl2bIniMexxqF4W+ytx0ANul47+JXzJIo6ULBBOBtLL6jqhp8e43IGAGw94rPJhnZQ3 NpTcfB0o/DXCskqgek5BFXfCBATl1q1fwLsUM/sdoBVyJThzAlDp+9GrkHkYkf3aYGA/ zJFOk2yPC7e5Fh2VDoJtlZgpy0ALdzJMExiA+wBU7SeOT6pmqhQnwtcLaxu4qKmvHlXV 8tkQ== X-Forwarded-Encrypted: i=1; AJvYcCUku49Em+wB/EvF9B7W84mAVBSQCM7QMLy/HF1fSmzUsMmFGAOu1Ygz0Fk30M6qQKGGEixFuRqtT/Q=@lists.xenproject.org X-Gm-Message-State: AOJu0Yy7uog3ryPs3EDqoSBVlqZOkkhSA4xbjHzJAS7ataj+DtCsY2+K Ty5y3jmveA6KTUrWCxtPV3mFDIWD39fk0FpbwGbODPewBrTdN/+jjSWyDs4PYMuC9kXGs/IbxuC 3 X-Gm-Gg: ASbGncsRklQnsrOzwv+7Xyk62eNzzVpShcNQJ/1qhXq4x70I3qX4aAkCz0bZUdw/dXW IQk170SY1d8jNd+UWGD9KTIBpUSYY16cZVRT0XQzpREAvtaJrSn9LByCZ2jOKzYzn69/GDJEz2p gl79fKYk74mBRaVigXnfO1DVvNxNVphn45eMMcyRFPqzvXiH8KjeXrMhm4oAGBtSenLWDksKmlT 1JptSdyY8F6u4TwSe/b9v43q/nsL9qJFS7yMy9+pfguaghmlbwvH5FM4aEoimdLK0rnZ1XYdJUr SGcpSpcTDKzA6vUV5n4OOlkoGFioR3GCl4Ih0WyuMYFpu9hPadwcxLR2UrISc36P264XzQ32rRa 3Qq8iRqYQ X-Google-Smtp-Source: AGHT+IExbXJ+4eq9PD0aDX2d2JiRDM5bnenGWIBWXBnZSN/dT+RB1zbNtl+FBrcGy/UDgD9r+V6SPA== X-Received: by 2002:a17:906:7308:b0:abf:486a:5e0e with SMTP id a640c23a62f3a-ac20d8cdafdmr464943466b.22.1741214656816; Wed, 05 Mar 2025 14:44:16 -0800 (PST) Message-ID: Date: Wed, 5 Mar 2025 22:44:15 +0000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG - running new version on nested virtualization To: =?UTF-8?B?S0HEnkFOIEnFnklMREFL?= , xen-devel@lists.xenproject.org, xen-users@lists.xenproject.org References: Content-Language: en-GB From: Andrew Cooper Autocrypt: addr=andrew.cooper3@citrix.com; keydata= xsFNBFLhNn8BEADVhE+Hb8i0GV6mihnnr/uiQQdPF8kUoFzCOPXkf7jQ5sLYeJa0cQi6Penp VtiFYznTairnVsN5J+ujSTIb+OlMSJUWV4opS7WVNnxHbFTPYZVQ3erv7NKc2iVizCRZ2Kxn srM1oPXWRic8BIAdYOKOloF2300SL/bIpeD+x7h3w9B/qez7nOin5NzkxgFoaUeIal12pXSR Q354FKFoy6Vh96gc4VRqte3jw8mPuJQpfws+Pb+swvSf/i1q1+1I4jsRQQh2m6OTADHIqg2E ofTYAEh7R5HfPx0EXoEDMdRjOeKn8+vvkAwhviWXTHlG3R1QkbE5M/oywnZ83udJmi+lxjJ5 YhQ5IzomvJ16H0Bq+TLyVLO/VRksp1VR9HxCzItLNCS8PdpYYz5TC204ViycobYU65WMpzWe LFAGn8jSS25XIpqv0Y9k87dLbctKKA14Ifw2kq5OIVu2FuX+3i446JOa2vpCI9GcjCzi3oHV e00bzYiHMIl0FICrNJU0Kjho8pdo0m2uxkn6SYEpogAy9pnatUlO+erL4LqFUO7GXSdBRbw5 gNt25XTLdSFuZtMxkY3tq8MFss5QnjhehCVPEpE6y9ZjI4XB8ad1G4oBHVGK5LMsvg22PfMJ ISWFSHoF/B5+lHkCKWkFxZ0gZn33ju5n6/FOdEx4B8cMJt+cWwARAQABzSlBbmRyZXcgQ29v cGVyIDxhbmRyZXcuY29vcGVyM0BjaXRyaXguY29tPsLBegQTAQgAJAIbAwULCQgHAwUVCgkI CwUWAgMBAAIeAQIXgAUCWKD95wIZAQAKCRBlw/kGpdefoHbdD/9AIoR3k6fKl+RFiFpyAhvO 59ttDFI7nIAnlYngev2XUR3acFElJATHSDO0ju+hqWqAb8kVijXLops0gOfqt3VPZq9cuHlh IMDquatGLzAadfFx2eQYIYT+FYuMoPZy/aTUazmJIDVxP7L383grjIkn+7tAv+qeDfE+txL4 SAm1UHNvmdfgL2/lcmL3xRh7sub3nJilM93RWX1Pe5LBSDXO45uzCGEdst6uSlzYR/MEr+5Z JQQ32JV64zwvf/aKaagSQSQMYNX9JFgfZ3TKWC1KJQbX5ssoX/5hNLqxMcZV3TN7kU8I3kjK mPec9+1nECOjjJSO/h4P0sBZyIUGfguwzhEeGf4sMCuSEM4xjCnwiBwftR17sr0spYcOpqET ZGcAmyYcNjy6CYadNCnfR40vhhWuCfNCBzWnUW0lFoo12wb0YnzoOLjvfD6OL3JjIUJNOmJy RCsJ5IA/Iz33RhSVRmROu+TztwuThClw63g7+hoyewv7BemKyuU6FTVhjjW+XUWmS/FzknSi dAG+insr0746cTPpSkGl3KAXeWDGJzve7/SBBfyznWCMGaf8E2P1oOdIZRxHgWj0zNr1+ooF /PzgLPiCI4OMUttTlEKChgbUTQ+5o0P080JojqfXwbPAyumbaYcQNiH1/xYbJdOFSiBv9rpt TQTBLzDKXok86M7BTQRS4TZ/ARAAkgqudHsp+hd82UVkvgnlqZjzz2vyrYfz7bkPtXaGb9H4 Rfo7mQsEQavEBdWWjbga6eMnDqtu+FC+qeTGYebToxEyp2lKDSoAsvt8w82tIlP/EbmRbDVn 7bhjBlfRcFjVYw8uVDPptT0TV47vpoCVkTwcyb6OltJrvg/QzV9f07DJswuda1JH3/qvYu0p vjPnYvCq4NsqY2XSdAJ02HrdYPFtNyPEntu1n1KK+gJrstjtw7KsZ4ygXYrsm/oCBiVW/OgU g/XIlGErkrxe4vQvJyVwg6YH653YTX5hLLUEL1NS4TCo47RP+wi6y+TnuAL36UtK/uFyEuPy wwrDVcC4cIFhYSfsO0BumEI65yu7a8aHbGfq2lW251UcoU48Z27ZUUZd2Dr6O/n8poQHbaTd 6bJJSjzGGHZVbRP9UQ3lkmkmc0+XCHmj5WhwNNYjgbbmML7y0fsJT5RgvefAIFfHBg7fTY/i kBEimoUsTEQz+N4hbKwo1hULfVxDJStE4sbPhjbsPCrlXf6W9CxSyQ0qmZ2bXsLQYRj2xqd1 bpA+1o1j2N4/au1R/uSiUFjewJdT/LX1EklKDcQwpk06Af/N7VZtSfEJeRV04unbsKVXWZAk uAJyDDKN99ziC0Wz5kcPyVD1HNf8bgaqGDzrv3TfYjwqayRFcMf7xJaL9xXedMcAEQEAAcLB XwQYAQgACQUCUuE2fwIbDAAKCRBlw/kGpdefoG4XEACD1Qf/er8EA7g23HMxYWd3FXHThrVQ HgiGdk5Yh632vjOm9L4sd/GCEACVQKjsu98e8o3ysitFlznEns5EAAXEbITrgKWXDDUWGYxd pnjj2u+GkVdsOAGk0kxczX6s+VRBhpbBI2PWnOsRJgU2n10PZ3mZD4Xu9kU2IXYmuW+e5KCA vTArRUdCrAtIa1k01sPipPPw6dfxx2e5asy21YOytzxuWFfJTGnVxZZSCyLUO83sh6OZhJkk b9rxL9wPmpN/t2IPaEKoAc0FTQZS36wAMOXkBh24PQ9gaLJvfPKpNzGD8XWR5HHF0NLIJhgg 4ZlEXQ2fVp3XrtocHqhu4UZR4koCijgB8sB7Tb0GCpwK+C4UePdFLfhKyRdSXuvY3AHJd4CP 4JzW0Bzq/WXY3XMOzUTYApGQpnUpdOmuQSfpV9MQO+/jo7r6yPbxT7CwRS5dcQPzUiuHLK9i nvjREdh84qycnx0/6dDroYhp0DFv4udxuAvt1h4wGwTPRQZerSm4xaYegEFusyhbZrI0U9tJ B8WrhBLXDiYlyJT6zOV2yZFuW47VrLsjYnHwn27hmxTC/7tvG3euCklmkn9Sl9IAKFu29RSo d5bD8kMSCYsTqtTfT6W4A3qHGvIDta3ptLYpIAOD2sY3GYq2nf3Bbzx81wZK14JdDDHUX2Rs 6+ahAA== In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 05/03/2025 10:05 pm, KAĞAN IŞILDAK wrote: > Hey there > > I'm facing weird issue. At my lab env. i'm building xen 4.18 and make > deb package than i use it on virtual machine which running on esxi > with CPU features for nested virtualization and there's no problem. (I > can create vm and able to do all operational things etc.) > > Last week i tried to migrate 4.19 and 4.20 but Xen get stuck on > booting and at debug log i just see error about mounting /proc/xen > (mount: /proc/xen: mount point does not exist.) I've no f... idea why > it caused. (At my all tries, i used fresh install of ubuntu server > 22.04, 24.04) > > Is there any one faced issue and is there special things to do in > build phase for nested virtualization? (I didn't change anything while > building 4.18, i'm just using stable branch) /proc/xen isn't getting mounted, and that's necessary for the Xen tooling to work.  It's a custom filesystem of type "xenfs" in Linux. Check the status of proc-xen.mount ~Andrew From xen-users-bounces@lists.xenproject.org Wed Mar 05 23:30:54 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Mar 2025 23:30:54 +0000 Received: from list by lists.xenproject.org with outflank-mailman.902919.1310854 (Exim 4.92) (envelope-from ) id 1tpyBy-0004CJ-AC; Wed, 05 Mar 2025 23:30:22 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 902919.1310854; Wed, 05 Mar 2025 23:30:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpyBy-0004CC-75; Wed, 05 Mar 2025 23:30:22 +0000 Received: by outflank-mailman (input) for mailman id 902919; Wed, 05 Mar 2025 23:30:21 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tpyBx-0004C6-Eh for xen-users@lists.xenproject.org; Wed, 05 Mar 2025 23:30:21 +0000 Received: from mail-oa1-x29.google.com (mail-oa1-x29.google.com [2001:4860:4864:20::29]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id cd1c5b99-fa19-11ef-9ab4-95dc52dad729; Thu, 06 Mar 2025 00:30:20 +0100 (CET) Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-2bcceee7b41so32420fac.2 for ; Wed, 05 Mar 2025 15:30:20 -0800 (PST) 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: cd1c5b99-fa19-11ef-9ab4-95dc52dad729 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=malwation.com; s=google; t=1741217419; x=1741822219; darn=lists.xenproject.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CTd8hOx6xiqwGKVo4Wa2y2yMQTGx9NRrzd5ctSx/1fw=; b=aq5lRPlLW9QaujcfccBjjeQCbL9iRM87xFSNURgbuiNY/tOk1cbNy1wSec25vP5jXo qWTkK9mEu0WzDOEEQaJ+gs6F0TdMxNUD5FS4eWuLkLJ1fw+0Wnu/N7xGQ66Pwk5kYb3k IJ0tZW4TX0kNqM1ZKzXCaoJlbVOxzkToNSiXYVJcpCCgStcDbgO6MCVvcr+eEmMfKdjK lGkUPzO2lC1YdxtH0EvtLdYyTqzl9x2icM1HnMuY5edQ/aS9KYv1RAzevdojmIu9XIn3 kCIAKOdWJv6QuS6+VW4A1r9P0WagagqjO5RhRkS9pdtml+vPy4OwXtKP/HbJ8GuIaMX4 ZyZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741217419; x=1741822219; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CTd8hOx6xiqwGKVo4Wa2y2yMQTGx9NRrzd5ctSx/1fw=; b=ga1G1iQEp9WE15m3FONJprQQzJFBit2nFPQRUBu5MAk5VUA4GaoMQ84ESSRixVU8lx s3tlpy65mpkrZkh4g/SxW2RRnuK1J0wxjHcoNIiD5bz6n0jwvv3eBQcq6j8iNz8ipOcS wQJQbGF+YHEfgOYjNc7URWZC5Xknw286JjynynxoE/00laOIm/++TzvrWu+rdRMfI/5N oerl0f+mmczIOGsxePTsEzHUHQav9Afhf13hayEDESw1hNBA/5BYF9OCd+0/13Cx3rzr koLUfCyH76xNXaIplNzpLui2OKVxB8hYfsENd/GcNUdZOsGI33WyFE2AmoAYkDrak5QD i+5A== X-Forwarded-Encrypted: i=1; AJvYcCXiopdG8A0qRW7DoAwGQi3KrfZP8XNnEC0CTtJiU2CXv1QBCQQOa/qIZtsBWPsMzy6MxjohV421pek=@lists.xenproject.org X-Gm-Message-State: AOJu0Yxx/bvqStmysoQUagh1KYnKGySOHxdzn/c23viZeCk2TBZK3/Z9 EhKTul2IjrlhqSDwuyDvDdeG2xqJl8r3//a3oZHsASkDrJquo+xrwGrE642yfr4L9LpIspV5VYZ kVEbWLLw0vEqHyPZaAkaWkby8QtqkhO/t/RpGsw== X-Gm-Gg: ASbGnctaMjV35WoUaFySmNbF5h8szg7kHaqZCv3zwAJkpGIpYgQc3SoqJuaSBACZv0G GymBuVgZZpxsded0DgjYEIlFPkQNdJ7v34sv4MueX4t+9+DOthTOxObFMwq6nPYFvDSG6qvLLPK E/unfoRqaUL6OBYI59mUw7WimH X-Google-Smtp-Source: AGHT+IFr/OY62XosZ47UtBhuRB9uM6LIrzPnztlSOOfPwjsPfvzPS0bPzsEzQqDITP/S2eIruGpFktXTsszJl2ru1zA= X-Received: by 2002:a05:6870:9110:b0:29e:69d9:8834 with SMTP id 586e51a60fabf-2c21be86ea2mr2768323fac.0.1741217418760; Wed, 05 Mar 2025 15:30:18 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?S0HEnkFOIEnFnklMREFL?= Date: Thu, 6 Mar 2025 02:30:07 +0300 X-Gm-Features: AQ5f1JpcfCkb-k5pDbYy_u7335C7x4D-whHrZR-059hO4UhAdX0_AId8s4U7TmY Message-ID: Subject: Re: BUG - running new version on nested virtualization To: Andrew Cooper Cc: xen-devel@lists.xenproject.org, xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000b8f3d1062fa0c5d5" --000000000000b8f3d1062fa0c5d5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Andrew I know but as i said at 4.18 theres no problem, im mounting at /etc/fstab succ. Im facing this issue on newer versions (4.19, 4.20) These installation also same with 4.18(same /etc/fstab config) but main problem is why it raise error and cant mount Andrew Cooper , 6 Mar 2025 Per, 01:44 tarihinde =C5=9Funu yazd=C4=B1: > On 05/03/2025 10:05 pm, KA=C4=9EAN I=C5=9EILDAK wrote: > > Hey there > > > > I'm facing weird issue. At my lab env. i'm building xen 4.18 and make > > deb package than i use it on virtual machine which running on esxi > > with CPU features for nested virtualization and there's no problem. (I > > can create vm and able to do all operational things etc.) > > > > Last week i tried to migrate 4.19 and 4.20 but Xen get stuck on > > booting and at debug log i just see error about mounting /proc/xen > > (mount: /proc/xen: mount point does not exist.) I've no f... idea why > > it caused. (At my all tries, i used fresh install of ubuntu server > > 22.04, 24.04) > > > > Is there any one faced issue and is there special things to do in > > build phase for nested virtualization? (I didn't change anything while > > building 4.18, i'm just using stable branch) > > /proc/xen isn't getting mounted, and that's necessary for the Xen > tooling to work. It's a custom filesystem of type "xenfs" in Linux. > > Check the status of proc-xen.mount > > ~Andrew > --=20 Ka=C4=9Fan I=C5=9EILDAK Co-Founder 0553 839 2887 www.malwation.com kagan.isildak@malwation.com Bu e-posta mesaj=C4=B1 ve eklerinde yer alan i=C3=A7erikler g=C3=B6nderild= i=C4=9Fi ki=C5=9Fi ya da firmaya =C3=B6zeldir. Ayr=C4=B1ca hukuken de gizli olabilir. Hi=C3=A7bir = =C5=9Fekilde =C3=BC=C3=A7=C3=BCnc=C3=BC ki=C5=9Filere a=C3=A7=C4=B1klanamaz ve yay=C4=B1nlanamaz. E=C4=9Fer bu mesa= j=C4=B1 hataen ald=C4=B1ysan=C4=B1z l=C3=BCtfen durumu g=C3=B6nderen ki=C5=9Fiye derhal bildiriniz ve mesaj=C4= =B1 sisteminizden siliniz. Mesaj=C4=B1n yetkili al=C4=B1c=C4=B1s=C4=B1 de=C4=9Filseniz hi=C3= =A7bir k=C4=B1sm=C4=B1n=C4=B1 kopyalayamaz, ba=C5=9Fkas=C4=B1na g=C3=B6nderemez veya hi=C3=A7bir =C5=9Fekilde bu mesaj= =C4=B1 kullanamazs=C4=B1n=C4=B1z. E=C4=9Fer mesaj=C4=B1n yetkili al=C4=B1c=C4=B1s=C4=B1 veya yetkili al=C4=B1c=C4=B1s= =C4=B1na iletmekten sorumlu ki=C5=9Fi siz de=C4=9Filseniz, l=C3=BCtfen mesaj=C4=B1 sisteminizden siliniz ve g=C3=B6nd= ereni uyar=C4=B1n=C4=B1z. =C4=B0nternet ileti=C5=9Fiminde tam g=C3=BCvenlik ve hatas=C4=B1z g=C3=B6nd= erim garanti edilemeyece=C4=9Finden; mesaj=C4=B1n yerine ula=C5=9Fmamas=C4=B1, ge=C3=A7 = ula=C5=9Fmas=C4=B1 ya da i=C3=A7eri=C4=9Finin bozulmas=C4=B1 gibi problemler de olu=C5=9Fabilir. G=C3=B6nderen ve Malwati= on (Malwation Siber G=C3=BCvenlik Teknolojileri A.=C5=9E.) bu mesaj=C4=B1n i=C3=A7erdi=C4=9Fi b= ilgilerin do=C4=9Frulu=C4=9Fu, b=C3=BCt=C3=BCnl=C3=BC=C4=9F=C3=BC ve g=C3=BCncelli=C4=9Fi konusunda bir ga= ranti vermemektedir. Mesaj=C4=B1n i=C3=A7eri=C4=9Finden, iletilmesinden, al=C4=B1nmas=C4=B1ndan, saklanmas=C4= =B1ndan, gizlili=C4=9Finin korunmamas=C4=B1ndan, vir=C3=BCs i=C3=A7ermesinden ve sisteminizde yaratabi= lece=C4=9Fi olas=C4=B1 zararlardan Malwation sorumlu tutulamaz. --000000000000b8f3d1062fa0c5d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey Andrew

I know but as i said at 4.18 theres no problem, im mounting at /etc/fstab = succ.
Im = facing this issue on newer versions (4.19, 4.20)
These installation also same with 4= .18(same /etc/fstab config) but main problem is why it raise error and cant= mount

Andrew Cooper <andrew.cooper3@citrix.com>, 6 Mar 2025 Per, 01= :44 tarihinde =C5=9Funu yazd=C4=B1:
On 05/03/2025 10:05 pm, KA=C4=9EAN I=C5=9EILDAK wrote:<= br> > Hey there
>
> I'm facing weird issue. At my lab env. i'm building xen 4.18 a= nd make
> deb package than i use it on virtual machine which running on esxi
> with CPU features for nested virtualization and there's no problem= . (I
> can create vm and able to do all operational things etc.)
>
> Last week i tried to migrate 4.19 and 4.20 but Xen get stuck on
> booting and at debug log i just see error about mounting /proc/xen
> (mount: /proc/xen: mount point does not exist.) I've no f... idea = why
> it caused. (At my all tries, i used fresh install of ubuntu server
> 22.04, 24.04)
>
> Is there any one faced issue and is there special things to do in
> build phase for nested virtualization? (I didn't change anything w= hile
> building 4.18, i'm just using stable branch)

/proc/xen isn't getting mounted, and that's necessary for the Xen tooling to work.=C2=A0 It's a custom filesystem of type "xenfs&quo= t; in Linux.

Check the status of proc-xen.mount

~Andrew


--

<= tr>
Ka=C4=9Fan I=C5=9EILDAK

Co-Founder

0553 839 2887

www.malwation.com=C2=A0= =C2=A0=C2=A0kagan.isilda= k@malwation.com

=C2=A0=C2=A0= =C2=A0=C2=A0

=C2=A0

=C2=A0Bu e-posta mesaj=C4=B1 ve eklerinde yer alan i=C3=A7erikler g=C3=B6n= derildi=C4=9Fi ki=C5=9Fi ya da firmaya =C3=B6zeldir. Ayr=C4=B1ca hukuken de= gizli olabilir. Hi=C3=A7bir =C5=9Fekilde =C3=BC=C3=A7=C3=BCnc=C3=BC ki=C5= =9Filere a=C3=A7=C4=B1klanamaz ve yay=C4=B1nlanamaz. E=C4=9Fer bu mesaj=C4= =B1 hataen ald=C4=B1ysan=C4=B1z l=C3=BCtfen durumu g=C3=B6nderen ki=C5=9Fiy= e derhal bildiriniz ve mesaj=C4=B1 sisteminizden siliniz. Mesaj=C4=B1n yetk= ili al=C4=B1c=C4=B1s=C4=B1 de=C4=9Filseniz hi=C3=A7bir k=C4=B1sm=C4=B1n=C4= =B1 kopyalayamaz, ba=C5=9Fkas=C4=B1na g=C3=B6nderemez veya hi=C3=A7bir =C5= =9Fekilde bu mesaj=C4=B1 kullanamazs=C4=B1n=C4=B1z. E=C4=9Fer mesaj=C4=B1n = yetkili al=C4=B1c=C4=B1s=C4=B1 veya yetkili al=C4=B1c=C4=B1s=C4=B1na iletme= kten sorumlu ki=C5=9Fi siz de=C4=9Filseniz, l=C3=BCtfen mesaj=C4=B1 sistemi= nizden siliniz ve g=C3=B6ndereni uyar=C4=B1n=C4=B1z. =C4=B0nternet ileti=C5= =9Fiminde tam g=C3=BCvenlik ve hatas=C4=B1z g=C3=B6nderim garanti edilemeye= ce=C4=9Finden; mesaj=C4=B1n yerine ula=C5=9Fmamas=C4=B1, ge=C3=A7 ula=C5=9F= mas=C4=B1 ya da i=C3=A7eri=C4=9Finin bozulmas=C4=B1 gibi problemler de olu= =C5=9Fabilir. G=C3=B6nderen ve Malwation (Malwation=C2=A0Siber G=C3=BCvenlik Teknolojileri A.=C5=9E.) bu me= saj=C4=B1n i=C3=A7erdi=C4=9Fi bilgilerin do=C4=9Frulu=C4=9Fu, b=C3=BCt=C3= =BCnl=C3=BC=C4=9F=C3=BC ve g=C3=BCncelli=C4=9Fi konusunda bir garanti verme= mektedir. Mesaj=C4=B1n i=C3=A7eri=C4=9Finden, iletilmesinden, al=C4=B1nmas= =C4=B1ndan, saklanmas=C4=B1ndan, gizlili=C4=9Finin korunmamas=C4=B1ndan, vi= r=C3=BCs i=C3=A7ermesinden ve sisteminizde yaratabilece=C4=9Fi olas=C4=B1 z= ararlardan=C2=A0Malwation=C2=A0s= orumlu tutulamaz.

--000000000000b8f3d1062fa0c5d5-- From xen-users-bounces@lists.xenproject.org Thu Mar 06 15:25:15 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Mar 2025 15:25:15 +0000 Received: from list by lists.xenproject.org with outflank-mailman.903731.1311701 (Exim 4.92) (envelope-from ) id 1tqD5I-0001lt-2h; Thu, 06 Mar 2025 15:24:28 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 903731.1311701; Thu, 06 Mar 2025 15:24:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tqD5H-0001lm-VM; Thu, 06 Mar 2025 15:24:27 +0000 Received: by outflank-mailman (input) for mailman id 903731; Thu, 06 Mar 2025 15:24:26 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tqD5G-0001iS-07 for xen-users@lists.xenproject.org; Thu, 06 Mar 2025 15:24:26 +0000 Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [2a00:1450:4864:20::633]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 15b1dd31-fa9f-11ef-9898-31a8f345e629; Thu, 06 Mar 2025 16:24:24 +0100 (CET) Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-ab771575040so375675866b.1 for ; Thu, 06 Mar 2025 07:24:24 -0800 (PST) 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: 15b1dd31-fa9f-11ef-9898-31a8f345e629 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloud.com; s=cloud; t=1741274664; x=1741879464; darn=lists.xenproject.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=IfpRx+4HWti9bQdpi7v8SRUcygtKRPDlLQgeTFRrDpk=; b=HLqa9OUzCw/jlJ+LMV9/H5kjoMRUv5SDkukE4+RDgRfssueZ/8LDUC52FIx/W+2W2d VTANfr0OJRTwz0M0DTXzo7tDS3jLachmYkeFZcTQRxOvjj6ekBe5KPW7zrOpgQnO1GOa R+31wlmgKRUf3FN/1WKWOQdoUoaSuOv/j9r/E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741274664; x=1741879464; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=IfpRx+4HWti9bQdpi7v8SRUcygtKRPDlLQgeTFRrDpk=; b=YXXT62N0ehJU9t55HBtgOk+AuuRGSYoqXGQNvirr9G9IkPsC5mkelB7J4hMlj+l9uZ sotePl3zj2BB/s90j7+Qy+nn/qQRQ8PCAGj3Q6ecBOfWIH7ROf4Lhsm68X/zuWiNkYvp qvM/0hEM9kKYGjgpoZIKGsGh47Rsk2dVZf0WOcFehKNJZD3TZWHdw5eOzkm2Yr7XsiOU wjoETkYGz6FoxuWyDyNA7J7yWTjQ9hzvRxBy+QCl9Kg9CPv+xdymhc/l7XuqN5DaLvbw 5gtU4kWqZsCrQdKmxB4LLcQ3w/reTln6D39NyUUFcnHMebJ0Tl/oeoijTQlYZnIuas0K 6EvQ== X-Forwarded-Encrypted: i=1; AJvYcCVwMnCqx6XAL5MxMkLSFAAqFOEI6ZD2biLUY3aHrv3I0YVaU0SVV11OBI0emSVNsl+AnzGbWVNRr7U=@lists.xenproject.org X-Gm-Message-State: AOJu0Ywxc1d+tPH09lBpsfBi5awSf75RT/rdWrNffWxPTAt3sjafj0NQ E2QkGudguNyKzzM8WuZ355pH36cDQBG+/taWABicP9V5IFXlLVCFaetVNcS2LE0KGR2xsi4XDT2 sU0CBNArkqqYlCNwavvL6ub+kvsf0T25smCxCew== X-Gm-Gg: ASbGncvoX9QTO4H022Cg1Fvp6bvWHMnvmyS15aW08jdBZ5eMVTLGLTdtSvejzpAsWxu UN/Y5+ajSToWt2CQmr7zLoZfM8wbwq7XmzT1NZVIIX06kvxmD3422Iojxu2//+6mLDQQc5MWxG0 cS2HXcsYKLNVkiN39aOkpb/vPOcmX2eDJiKYI/EGpSRtAFpJ4LAEqVZfvKQIW9 X-Google-Smtp-Source: AGHT+IFG8Hjgc5IwezD9G4WANi05H7A6vd765haYU/2KUDPqtMpkkf7PCcNmWSZuCHXxJSr5Y8uCiqQTNf/S2ST6WCs= X-Received: by 2002:a17:907:961e:b0:abb:b411:5e02 with SMTP id a640c23a62f3a-ac22cbb5723mr423946866b.18.1741274663692; Thu, 06 Mar 2025 07:24:23 -0800 (PST) MIME-Version: 1.0 From: Kelly Choi Date: Thu, 6 Mar 2025 15:24:12 +0000 X-Gm-Features: AQ5f1JqOjxcHusnvwMlnFvSOng7ureYgflORoBCR2NJY5QGKAtSBtk7YNgoztow Message-ID: Subject: A Heartfelt Goodbye to the Xen Project Community To: xen-devel , xen-users@lists.xenproject.org Cc: Xen Project Advisory Board , "committers @ xenproject . org" Content-Type: multipart/alternative; boundary="000000000000c950a8062fae190b" --000000000000c950a8062fae190b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, It is with a heavy heart that I share that my time as the Community Manager for the Xen Project has come to an end due to redundancy. While this was an unexpected change, I want to take this opportunity to express my gratitude and reflect on what an incredible journey it has been. Being part of this community has been nothing short of amazing. I=E2=80=99v= e had the privilege of working alongside some of the most talented, passionate, and dedicated people in open source. From contributors and maintainers to users and advocates, every interaction has reinforced what makes Xen so special=E2=80=94it=E2=80=99s not just about technology; it=E2=80=99s also a= bout the people behind it. I=E2=80=99ve loved seeing the project evolve, celebrating its milestones, a= nd tackling challenges together. And while I may be stepping away from my official role, I=E2=80=99ll always be cheering for the Xen Project from the sidelines. I have no doubt that this community will continue to push boundaries and achieve great things. Watch out for more board members joining Xen Project soon! Thank you to everyone who has supported, collaborated, and shared this journey with me. Let=E2=80=99s stay in touch=E2=80=94you can connect with me on LinkedIn . Wishing you all the best, and hoping our paths cross again soon! Thanks, Kelly Choi Community Manager Xen Project --000000000000c950a8062fae190b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi all,=C2=A0

It is wi= th a heavy heart that I share that my time as the Community Manager for the= Xen Project has come to an end due to redundancy. While this was an unexpe= cted change, I want to take this opportunity to express my gratitude and re= flect on what an incredible journey it has been.

Being part of this c= ommunity has been nothing short of amazing. I=E2=80=99ve had the privilege = of working alongside some of the most talented, passionate, and dedicated p= eople in open source. From contributors and maintainers to users and advoca= tes, every interaction has reinforced what makes Xen so special=E2=80=94it= =E2=80=99s not just about technology; it=E2=80=99s also about the people be= hind it.

I=E2=80=99ve loved seeing the project evolve, celebrating it= s milestones, and tackling challenges together. And while I may be stepping= away from my official role, I=E2=80=99ll always be cheering for the Xen Pr= oject from the sidelines. I have no doubt that this community will continue= to push boundaries and achieve great things. Watch out for more board memb= ers joining Xen Project soon!=C2=A0

Thank you to everyone who has sup= ported, collaborated, and shared this journey with me.=C2=A0

Let=E2= =80=99s stay in touch=E2=80=94you can connect with me on LinkedIn.=C2=A0

Wishing you all the best, and hoping our paths cross again soon!

Thanks,
Kelly Choi
Community Manager
--000000000000c950a8062fae190b-- From xen-users-bounces@lists.xenproject.org Sun Mar 09 23:54:58 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Mar 2025 23:54:58 +0000 Received: from list by lists.xenproject.org with outflank-mailman.902626.1313392 (Exim 4.92) (envelope-from ) id 1trQSx-0002Q4-Uw; Sun, 09 Mar 2025 23:53:55 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 902626.1313392; Sun, 09 Mar 2025 23:53:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1trQSx-0002PV-N4; Sun, 09 Mar 2025 23:53:55 +0000 Received: by outflank-mailman (input) for mailman id 902626; Wed, 05 Mar 2025 18:24:48 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tptQG-0002Bv-57 for xen-users@lists.xenproject.org; Wed, 05 Mar 2025 18:24:48 +0000 Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [2a00:1450:4864:20::533]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 1a3efbf2-f9ef-11ef-9898-31a8f345e629; Wed, 05 Mar 2025 19:24:42 +0100 (CET) Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-5e4d50ed90aso8459464a12.0; Wed, 05 Mar 2025 10:24:40 -0800 (PST) Received: from [172.20.10.5] (public-gprs377817.centertel.pl. [37.47.107.26]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-5e4c43a55e0sm9956954a12.79.2025.03.05.10.24.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Mar 2025 10:24:38 -0800 (PST) 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: 1a3efbf2-f9ef-11ef-9898-31a8f345e629 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741199080; x=1741803880; darn=lists.xenproject.org; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=kizGuW1y8r26IEy4rhwW4XbhuTNeCtED17MvvM09fUw=; b=XiJ8leITbHfD2rP6P3yNHwxGyD9wPB/8+FIrfKZWBATE0ZzaVSikySVS2SwUk4eOqa HCYpNQM5vt8oQE1EcTLWPFNZrvBLYsbu15PhmU2TiBoBd6SYukQWC4tnixgL4wyWg2v9 0Ox6D1qRhWQpG4dUHU7OV8H9oEHpScfAiwUUIJD/1wkANaHPuq0tTGQcWXCdwzXhDRKz +AozQcEM67D+Ja5ogsC5wRCii5aM85zdhMHZiGwaS3K4OeoJfroVMxynupc4lS6YplEm c4PPYXe5tL7+MwxKdyhL6hFjAffGJy+OKzaOwX8YREpfQsA7nd4OS04qDz5WeKmBA6cd WLZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741199080; x=1741803880; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=kizGuW1y8r26IEy4rhwW4XbhuTNeCtED17MvvM09fUw=; b=n4LfrMN0fVLdRc+Rh1VfgvZWyzKnK8m0la9UBNyNPdKdXBKgdCmkqbaULVDoSvZWqB 5nWqMxwGq5LZya2/xjkDriDn1W8LwDoiQXhWTKYXp/lHni1ONKsi2KQkRF/DvEk9rnAR 17ldJYh5ckyRvGOpixJxnLiOFaVmi8mn1GbiKTgq6mtUhKir9gv8eDIQnTFEF1PlL3Ql 74yCEtWD1gde1hZ8pmERxmjEMkgcQ2urYIYGx2q8UBS63OIGxDpZuwyUQhSoP0sP2r0O UWx39KypJpRy0TZ2vBWtgMWdlZ5EIh9L0cl/4G/y9F1jTFs3+7RRyOAvm3ArFLEoGbXV G9/w== X-Forwarded-Encrypted: i=1; AJvYcCWxZHm/83G9LnGzNQzwcFRB+vjtHEjasjI95ZtDY9ew2+aIhsXteGj2iTLvUK7Z3EAQvOUlFjtpC+P7RzcS@lists.xenproject.org, AJvYcCX/9W62hXzVTlO9BCNyeg3QbKNl/JtdSmZVz1SUADR/mmKHnM+AwX4fH7S8Ko8fO2yH7fCmi5ED59Ug@lists.xenproject.org, AJvYcCXSnqzWPKgBhGamhFQFEXMBFnKw50C89bS4thgUR4vPq250D+Yzio3SBvgJ4+mUv/e79kRdEjCdzsY92/LdKQ==@lists.xenproject.org X-Gm-Message-State: AOJu0YzDtNo3dqywS16ZaZrAsEjrJLjr5KKAsdKCK4sEtka+wr+Acnah B1nlvwh842k3waLEWzP1Kq7aoHZpnW3ahA4howKIKMl7S6QFeo4zCIM4iA== X-Gm-Gg: ASbGnctEX1oeDzmPue+c6+eScOlCgQbxK1FYN5Ak4slnUjtKHHh5YzH00EHE4fvGdUt RHjBpFWuQM/xda2r3AHw3WdwQp68DIBI6K0jjSKh3aX3UyqIQ3ysDg9iRLIrdsK8IMkhnhkPUnP XO1YFgeQfYBDhZ/arvOW4NJrtfr1CqcKz0zQ40/hBZ1MmClLRsqnrhWDxL0RbQeHOgmLYkk/X7l RxXythGycXOOXbuTuBRU4LFA0DlM4OfhxBYoiwKzy5mSX+oQDQeoV7XtXnAfiGZBx36Z47xrZRp LW/i1gb5Qt0TsqciFg/oln0RPO5FrcewdEA/+FzpbauETFLC+yINGaR6IzLt80UL5n2rPpm4tkA E1WpokP9amA== X-Google-Smtp-Source: AGHT+IHel4usX22oqVEEWfsbSa/Wn+fVueF2skW49/SnjX8u5G3c6olM2+oclpnCRn7VjqswcElaDw== X-Received: by 2002:a05:6402:5c8:b0:5dc:5a34:1296 with SMTP id 4fb4d7f45d1cf-5e59f3d47f1mr4239848a12.16.1741199079156; Wed, 05 Mar 2025 10:24:39 -0800 (PST) Content-Type: multipart/alternative; boundary="------------Sfts9e0BljbIB0VHBbBpP0Sh" Message-ID: Date: Wed, 5 Mar 2025 19:24:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: xen-devel@lists.xenproject.org, xen-users@lists.xenproject.org, xen-announce@lists.xenproject.org, advisory-board@lists.xenproject.org, Community Manager From: Oleksii Kurochko Subject: Xen Project Releases Version 4.20 This is a multi-part message in MIME format. --------------Sfts9e0BljbIB0VHBbBpP0Sh Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hello everyone, It's with great pleasure that I announce our 4.20 PR release. I want to thank the whole community for their efforts in getting this release published! *Please find the PR article attached here * Please find the tarball and its signature at: https://downloads.xenproject.org/release/xen/4.20.0/ You can also check out the tag in xen.git:    git://xenbits.xen.org/xen.git RELEASE-4.20.0 Git checkout and build instructions can be found at: https://wiki.xenproject.org/wiki/Xen_Project_4.20_Release_Notes#Build_Requirements Release notes can be found at: https://wiki.xenproject.org/wiki/Xen_Project_4.20_Release_Notes A summary for 4.20 release documents can be found at: https://wiki.xenproject.org/wiki/Category:Xen_4.20 *Some notable features:*   - *Security Enhancements:*     - During the 4.20 development window, 8 new Xen Security Advisories (XSAs) were published.     - Expanded MISRA C compliance: Integrated ECLAIR MISRA C scanner in GitLab CI, enforcing 90       rules with zero unjustified violations.     - Enabled UBSAN (Undefined Behaviour Sanitiser) by default for x86, Arm64, RISC-V and PowerPC       in GitLab CI.     - Integrated two of our existing fuzzing harnesses into OSSFuzz.  - *Arm*     - Support for LLC (Last Level Cache) coloring for performance optimizations.     - Experimental support for Armv8-R.     - Support for NXP S32G3 Processors Family and LINFlexD UART driver.     - To enable Xen towards safety certification, 43 requirements have been added.  - *x86 Architecture:*     - On Intel CPUs, support the Paging-Write Feature.     - AMD Zen 5 CPU support, including mitigation for SRSO speculative vulnerability.     - Improve Xen ability to boot (and reboot) using the default configuration on possibly       quirky EFI firmware.     - Switched the xAPIC flat driver to use physical destination mode for external interrupts instead       of logical destination mode.     - Remove support for running on Xeon Phi processors.     - There has been a substantial overhaul to the way in which boot module handling works (part of the       Hyperlaunch work in progress), and a substantial overhaul to how the 32bit early boot code is built       and linked (part of the UEFI SecureBoot work in progress).  - *Other updates:*    - Fixes in the blkif protocol specification for non-512b sector sizes.    - Security and performance enhancements: The domain builder in libxenguest no longer un-gzips      secondary modules, leaving it to the guest kernel.    - Continued to improve the common/arch code split, including improved bit-operation helpers for bit      scanning and hamming weight. Aside from the updates mentioned, I would also like to note that we are still continue working on the PPC and RISC-V ports. Best regards,  Oleksii Come join the conversation on Matrix: XenProject:https://matrix.to/#/#XenProject:matrix.org XenDevel:https://matrix.to/#/#XenDevel:matrix.org XenSocial:https://matrix.to/#/#XenSocial:matrix.org --------------Sfts9e0BljbIB0VHBbBpP0Sh Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 
Hello everyone,

It's with great pleasure that I announce our 4.20 PR release.

I want to thank the whole community for their efforts in getting this
release published!

*Please find the PR article attached here
<https://www.linuxfoundation.org/press/xen-project-announces-xen-420-release
>*

Please find the tarball and its signature at:
   https://downloads.xenproject.org/release/xen/4.20.0/

You can also check out the tag in xen.git:
   git://xenbits.xen.org/xen.git RELEASE-4.20.0

Git checkout and build instructions can be found at:
   https://wiki.xenproject.org/wiki/Xen_Project_4.20_Release_Notes#Build_Requirements

Release notes can be found at:
   https://wiki.xenproject.org/wiki/Xen_Project_4.20_Release_Notes

A summary for 4.20 release documents can be found at:
   https://wiki.xenproject.org/wiki/Category:Xen_4.20

*Some notable features:*
  - *Security Enhancements:*
    - During the 4.20 development window, 8 new Xen Security Advisories (XSAs) were published.
    - Expanded MISRA C compliance: Integrated ECLAIR MISRA C scanner in GitLab CI, enforcing 90
      rules with zero unjustified violations.
    - Enabled UBSAN (Undefined Behaviour Sanitiser) by default for x86, Arm64, RISC-V and PowerPC
      in GitLab CI.
    - Integrated two of our existing fuzzing harnesses into OSSFuzz.
  
 - *Arm*
    - Support for LLC (Last Level Cache) coloring for performance optimizations.
    - Experimental support for Armv8-R.
    - Support for NXP S32G3 Processors Family and LINFlexD UART driver.
    - To enable Xen towards safety certification, 43 requirements have been added. 

 - *x86 Architecture:*
    - On Intel CPUs, support the Paging-Write Feature.
    - AMD Zen 5 CPU support, including mitigation for SRSO speculative vulnerability.
    - Improve Xen ability to boot (and reboot) using the default configuration on possibly
      quirky EFI firmware.
    - Switched the xAPIC flat driver to use physical destination mode for external interrupts instead
      of logical destination mode. 
    - Remove support for running on Xeon Phi processors.
    - There has been a substantial overhaul to the way in which boot module handling works (part of the
      Hyperlaunch work in progress), and a substantial overhaul to how the 32bit early boot code is built
      and linked (part of the UEFI SecureBoot work in progress).


 - *Other updates:*
   - Fixes in the blkif protocol specification for non-512b sector sizes.
   - Security and performance enhancements: The domain builder in libxenguest no longer un-gzips
     secondary modules, leaving it to the guest kernel.
   - Continued to improve the common/arch code split, including improved bit-operation helpers for bit
     scanning and hamming weight.

Aside from the updates mentioned, I would also like to note that we are
still continue working on the PPC and RISC-V ports.

Best regards,
 Oleksii

Come join the conversation on Matrix:

XenProject: https://matrix.to/#/#XenProject:matrix.org

XenDevel: https://matrix.to/#/#XenDevel:matrix.org

XenSocial: https://matrix.to/#/#XenSocial:matrix.org
--------------Sfts9e0BljbIB0VHBbBpP0Sh-- From xen-users-bounces@lists.xenproject.org Thu Mar 13 22:28:26 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Mar 2025 22:28:26 +0000 Received: from list by lists.xenproject.org with outflank-mailman.913531.1319533 (Exim 4.92) (envelope-from ) id 1tsr1d-0003JF-9l; Thu, 13 Mar 2025 22:27:37 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 913531.1319533; Thu, 13 Mar 2025 22:27: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 1tsr1d-0003J8-5w; Thu, 13 Mar 2025 22:27:37 +0000 Received: by outflank-mailman (input) for mailman id 913531; Thu, 13 Mar 2025 22:27:35 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tsr1b-0003J2-D1 for xen-users@lists.xenproject.org; Thu, 13 Mar 2025 22:27:35 +0000 Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [2607:f8b0:4864:20::d31]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 58ce20da-005a-11f0-9898-31a8f345e629; Thu, 13 Mar 2025 23:27:29 +0100 (CET) Received: by mail-io1-xd31.google.com with SMTP id ca18e2360f4ac-85b44094782so45114439f.3 for ; Thu, 13 Mar 2025 15:27:29 -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: 58ce20da-005a-11f0-9898-31a8f345e629 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741904848; x=1742509648; darn=lists.xenproject.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=s8hkkCvO3+vfwiuw7bqkWIJn/sSGfKl+qFHlEKX3Qro=; b=l3b6yJ/IPk5x2fkVq2QSNs7ePzpZXvQaZDPrrSXXdSb66jiiEYufcCBPvJvS/+WKEd Pm9ROoIr4RrbqcY3Vi15wEgWHFbi7iewzQPuweHtnL03BxdRwAPLDoz8O4uRx4YRlrPF TwYuZKQJuMUcvBwI9qIoGcXtk9g9aKEaFuuKs7I8k8wS0iDRyFK3aw3wnd5KFANFItQH XzsDkw02TEaEumMXtNOeSHx0t02cVbwgfdF4Ha4LDHOPHRqTHoQBa1gqBILapgViPYEb ySCJMvpq4f83fwlkGLYFMSKyDcfMG1KyeSAT7IC0Yj6Bsr3v+c9w9yeY/HmCjIA7c4q1 em3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741904848; x=1742509648; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=s8hkkCvO3+vfwiuw7bqkWIJn/sSGfKl+qFHlEKX3Qro=; b=b0oS0wyylX+5DxRPcYhrWeaXWgQD5IiGttZ+5OnGFDAcDvpBpUE+Q8trbQKkAG9NAw tAcr6dTucA0lWu6eAZP2UBKBiqP9JadaB+Znlj/9KJmDU0OalnpODXZPXV5rrVaE0TXC tDy8V+sr670PoO9pYprKK+ynyQ0KeNYAYtetzxwn7zkea9IRJOWDMRoLiZQwDYjlOkzy 6F/+xlEl7WVptyfDKghC4YddNmwXtNtXzY4pEQx3c58sB3/bvIHh6y/vChXUmn0ubymO 34wdVPZbMAnkQLiLV676TRlsI7J4Zu7QZAi1w49cu7LEMcl7u2tMYHKX5wlWOpVTxQWz 22Hg== X-Gm-Message-State: AOJu0YwePHZz/Ky9TsQFVaJURS6zvqbkD1P/loM3dVi9YM8PQeJkAqfJ JJkO3ZgyL6leUqwF9v6UeSW7LmdbNTxwQHA7j9cs5HxnxmyvCgbDi9fSu8OECAIBbniRaUw/TMK N432v9PoleyzsAUc6xwmLE9DQhGfegYOPULo= X-Gm-Gg: ASbGncs2MKbQqHcgLdwTdFrQheATscI4+/y74ZwZBBh+BiPKo8aTwSicvY2gIK2pDNj J7jTeVLuK9/KTj3WxCqcE8QEFxkGQW4IvlZPN5orTjnc+mMUhzm2SnHeCHhx42wXt378GAXG3Oq 1qm6stn9wDGAHtlttqS2d7vVDsvImvRaHaxX4DohjcrgFbSCVSiPUrtNpgt0gZe7ngyIgW X-Google-Smtp-Source: AGHT+IHX+ND2t/fsvexz/i966zlvYrESf9HrZy1go55v3AOHsopOCAXLUCyEqfYD7syBAmETihIkLrG6XWdvlHCAi58= X-Received: by 2002:a05:6e02:3209:b0:3d1:966c:fc8d with SMTP id e9e14a558f8ab-3d483a76e21mr1937555ab.22.1741904847692; Thu, 13 Mar 2025 15:27:27 -0700 (PDT) MIME-Version: 1.0 From: Gabriel Alpho Date: Thu, 13 Mar 2025 23:27:15 +0100 X-Gm-Features: AQ5f1JqukLMHNspvv4_I52G-2ohWCdDjOvlEyUVfQz4TlC2C_DYvqREVXJha3Rs Message-ID: Subject: How to Override hwp-internal as CPU Governor in QubesOS? To: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000adebb9063040d31d" --000000000000adebb9063040d31d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey everyone! [image: :blush:] I=E2=80=99ve been trying to gain full control over my CPU frequency scaling= in *QubesOS*, but I=E2=80=99m stuck with hwp-internal as the governor. No matt= er what I try, Xen (or the kernel) keeps forcing hwp-internal, preventing me from manually setting CPU frequencies. *[image: :hammer_and_wrench:] What I=E2=80=99ve Tried So Far:* [image: :white_check_mark:] *Disabled Turbo Boost* using xenpm disable-turbo-mode 0-15 =E2=80=93 Worked fine. [image: :x:] *Set max frequency with xenpm set-scaling-maxfreq* =E2=80=93 I= gnored, still running at max clock. [image: :x:] *Added hwp=3D0 to Xen GRUB parameters* =E2=80=93 No effect, st= ill stuck on hwp-internal. *[image: :question:] My Question:* [image: :point_right:] *Is it possible to fully disable or override hwp-internal so I can manually control CPU scaling?* [image: :point_right:] *Or is my CPU locked into hwp-internal with no way to change it in QubesOS?* *[image: :desktop_computer:] System Specs:* - *QubesOS Version:* 4.2 (R4.2) - *Kernel Version:* 6.6.77-1.qubes.fc37.x86_64 - *Scaling Driver:* hwp-cpufreq - *Current Governor:* hwp-internal - *CPU Model:* GenuineIntel 12th Gen Intel(R) Core(TM) i7-12650H If anyone has experience dealing with this in *QubesOS/Xen*, I=E2=80=99d re= ally appreciate any guidance! [image: :pray:][image: :fire:] Thanks in advance! Stevenn Create your own email signature --000000000000adebb9063040d31d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey everyone!

I=E2=80=99ve been trying to gain full control over my CPU frequency scal= ing in QubesOS, but I=E2=80=99m stuck with hwp-inter= nal as the governor. No matter what I try, Xen (or the kernel) keeps= forcing hwp-internal, preventing me from manually setting CPU= frequencies.

3D":hammer_and_wre= What I= =E2=80=99ve Tried So Far:

3D":white= = Disabled Turbo Boost using xenpm disable-turbo-mode = 0-15 =E2=80=93 Worked fine.
3D":x:" Set max frequency with xenpm set= -scaling-maxfreq =E2=80=93 Ignored, still running at max cl= ock.
3D":x:" Added hwp=3D0 to Xen GRUB= parameters =E2=80=93 No effect, still stuck on hwp-internal= .

3D":question:" My Question:

3D":point_right:" Is it p= ossible to fully disable or override hwp-internal so I can man= ually control CPU scaling?
3D":point_right:" Or is my C= PU locked into hwp-internal with no way to change it in QubesO= S?

3D":desktop_computer:" System Specs:

  • QubesOS Version: 4.2 (R4.2)
  • Kernel Version: 6.6.77-1.qubes.fc37.x86_= 64
  • Scaling Driver: hwp-cpufreq=
  • Current Governor: hwp-internal
    • <= li>CPU Model: GenuineIntel 12th Gen Intel(R) Core(TM= ) i7-12650H

If anyone has experience dealing with this in QubesOS/Xen, I=E2=80=99d really appreciate any guidance! 3D":pray:"3D":fire:"

Thanks in advance!

= Stevenn

--000000000000adebb9063040d31d-- From xen-users-bounces@lists.xenproject.org Mon Mar 17 15:03:01 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2025 15:03:01 +0000 Received: from list by lists.xenproject.org with outflank-mailman.917114.1322108 (Exim 4.92) (envelope-from ) id 1tuByE-0007xX-Q8; Mon, 17 Mar 2025 15:01:38 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 917114.1322108; Mon, 17 Mar 2025 15:01:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuByE-0007xQ-N4; Mon, 17 Mar 2025 15:01:38 +0000 Received: by outflank-mailman (input) for mailman id 917114; Mon, 17 Mar 2025 15:01:37 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuByD-0007xK-73 for xen-users@lists.xenproject.org; Mon, 17 Mar 2025 15:01:37 +0000 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [2a00:1450:4864:20::632]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id b6a77ba8-0340-11f0-9aba-95dc52dad729; Mon, 17 Mar 2025 16:01:34 +0100 (CET) Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-aaeec07b705so716790366b.2 for ; Mon, 17 Mar 2025 08:01:32 -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: b6a77ba8-0340-11f0-9aba-95dc52dad729 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leftsock.com; s=google; t=1742223692; x=1742828492; darn=lists.xenproject.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=zaMDUVOqHgJ0zy+lePSLLYsGRyHU6sjg8cXuA3DcFQc=; b=nWdgPWXom66nLNKSi9X0wBYE8YCYNKLvLsOMJkfhlgweV342SZ9c8Z73kgCf9dq3Yx fkadpNCnXDPNqCNdt3APdkcU7RDBgabQqLbCS1hEvkj0f+/sNsPwjTZ8GfjTHHVTyu+S CP0XR4by9ulNlLWQrgNWYRZFG7FpwFxANV/8E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742223692; x=1742828492; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=zaMDUVOqHgJ0zy+lePSLLYsGRyHU6sjg8cXuA3DcFQc=; b=WxIUcsptXjpoWKarIu5JSeQoF/A/qb4k+nk20TN5FpzzVFmpMT9sGMVhduyQltFKgT a6vlStoFxTMQxi3zsKzdN0vX3kOEWpFXT0LHyl8ncpCw6a7G/uLeUj/3OdPXlGFIpUGu zL/5r0/oRooEvR9eS0Sukxkc57ss30jSn4hiH6Ox0OLhH40To5HKHIfMKHgrY71eX/jX 8C9PqTK5rP8L/GG5YwuTQTG7y1XyAqhDdxUiMsGG7jGjT0gVqGFVdkng07fqsEyHPsQJ JrMqxNbhTqkUBU6IJgtzW6bu9voBUsG/I4U7Etxh0tctBUhbey6Ld2fJXYntwxWwEp5U eGEA== X-Gm-Message-State: AOJu0YyhIZR6iO9HY+6lLY3dH4n6MEy8rBM5cVc78Yzu6dtQUj0v5gZC 2xiXsiGrHXN+NMuczgbsJSpMzOunPRbKIxmkqxhqtK+xqD+rkPBxtH76qopbwiOV461QjHyvZ1p JRFp3SuGqn0Te7TXgDm5ORcij8vVFHahGdZySCKDbANGgkLK3vg== X-Gm-Gg: ASbGncu0jF7nK+NC9LogxG+LuZA0A05rYy8Q0O9VE8QL4tZn7Wqv9HULwibeC2Mpqj/ n3ltpHAThZZUxHTkAVgWj5/mRQCV1qvNTfgPxK+8aOefCVdfRpeAIOr+HulIyiEAyZhbI8bAdRt CjkgkblxlfQwoRTqRtEvxGhnUn4nk= X-Google-Smtp-Source: AGHT+IEpQ507n5MVKTM0LCl/J157LPl0HcJhtMuYsnHFkPtEWjRmlS7Cttx3SOzG8aU3RmYtcCz8/eQFE3jZTXGk8gg= X-Received: by 2002:a17:907:ec0d:b0:ac3:8897:eb75 with SMTP id a640c23a62f3a-ac38897ecdbmr76900366b.10.1742223691120; Mon, 17 Mar 2025 08:01:31 -0700 (PDT) MIME-Version: 1.0 From: Kevin Wang Date: Mon, 17 Mar 2025 08:01:20 -0700 X-Gm-Features: AQ5f1JrQT2eDw3beQjY5xZldFpLSTOW19V2T6N4IpLdVC81CF9P9Xz9Bv8-sptA Message-ID: Subject: can't start hvm with network To: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="0000000000003aa2f406308b1063" --0000000000003aa2f406308b1063 Content-Type: text/plain; charset="UTF-8" Installed ubuntu 24 onto E3-1225 v5 @ 3.30GHz (2C/4T) with one boring sata disk, but I can't get the vm to start the ubuntu24 server installer iso cat >/etc/xen/auto/couch5.hvm <<'__EOF__' builder = "hvm" name = "couch5" memory = "10240" vcpus = 2 #vif = [''] #vif = ['type=ioemu,model=e1000'] #vif = ['type=ioemu,model=rtl8139'] disk = ['phy:/dev/mapper/ubuntu--vg-couch--disk,hda,w','phy:/dev/mapper/ubuntu-- vg-couch--home,hdb,w','file:/d/dmg/ubuntu-24.04-live-server-amd64.iso,hdc:cdrom, r'] #disk = disk = ['phy:/dev/mapper/ubuntu--vg-couch--disk,hda,w','phy:/dev/mapper/ubuntu-- vg-couch--home,hdb,w'] vnc = 1 vncdisplay = 5901 boot="dc" __EOF__ As depicted here, commenting out all the vif= lines, it does boot (but a server without a network isn't useful). But if I include any of the vif= lines, it won't even start, I get: # xl create /etc/xen/auto/couch5.hvm Parsing config from /etc/xen/auto/couch5.hvm libxl: error: libxl_dm.c:3151:device_model_spawn_outcome: Domain 7:domain 7 devi ce model: spawn failed (rc=-3) libxl: error: libxl_dm.c:3371:device_model_postconfig_done: Domain 7:Post DM sta rtup configs failed, rc=-3 libxl: error: libxl_create.c:1896:domcreate_devmodel_started: Domain 7:device mo del did not start: -3 libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model already exit ed libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain 7:Non-existant do main libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain 7:Unable to de stroy guest libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 7:Destruction of dom ain failed >From a previous thread (which I haven't had a chance to try on that other 256GB ram machine), It was suggested that "big ram" vms may have trouble starting or start slowly, so I added: echo 'GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=min:4096M,max:4096 M"' >>/etc/default/grub grub-install /dev/sda though I don't know how to prove that it had an effect; # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 22019 4 r----- 32.5 Help? - Kevin xl -vvv create /etc/xen/auto/couch5.hvm Parsing config from /etc/xen/auto/couch5.hvm libxl: debug: libxl_create.c:2081:do_domain_create: ao 0x6199251022d0: create: how=(nil) callback=(nil) poller=0x619925102370 libxl: detail: libxl_create.c:662:libxl__domain_make: passthrough: disabled libxl: debug: libxl_device.c:415:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown specification=xen libxl: debug: libxl_device.c:452:libxl__device_disk_set_backend: Disk vdev=hda, using backend phy libxl: debug: libxl_device.c:415:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=unknown specification=xen libxl: debug: libxl_device.c:452:libxl__device_disk_set_backend: Disk vdev=hdb, using backend phy libxl: debug: libxl_create.c:1342:initiate_domain_create: Domain 10:running bootloader libxl: debug: libxl_bootloader.c:411:libxl__bootloader_run: Domain 10:not a PV/PVH domain, skipping bootloader libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x619925109818: deregister unregistered domainbuilder: detail: xc_dom_allocate: cmdline="", features="" domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen-4.17/boot/hvmloader" domainbuilder: detail: xc_dom_malloc_filemap : 170 kB libxl: debug: libxl_dom.c:810:libxl__load_hvm_firmware_module: Loading BIOS: /usr/share/seabios/bios-256k.bin domainbuilder: detail: xc_dom_boot_xen_init: ver 4.17, caps xen-3.0-x86_64 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=0x340c0 xc: detail: ELF: memory: 0x100000 -> 0x1340c0 domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 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: xc_dom_mem_init: mem 10232 MB, pages 0x27f800 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x27f800 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: range: start=0x0 end=0xf0000000 domainbuilder: detail: range: start=0x100000000 end=0x28f800000 xc: detail: PHYSICAL MEMORY ALLOCATION: xc: detail: 4KB PAGES: 0x0000000000000c00 xc: detail: 2MB PAGES: 0x00000000000005f6 xc: detail: 1GB PAGES: 0x0000000000000007 domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x100+0x35 at 0x728a09b11000 domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x100000 -> 0x135000 (pfn 0x100 + 0x35 pages) xc: detail: ELF: phdr 0 at 0x728a09adc000 -> 0x728a09b06640 domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x135+0x40 at 0x728a09ad1000 domainbuilder: detail: xc_dom_alloc_segment: System Firmware module : 0x135000 -> 0x175000 (pfn 0x135 + 0x40 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x175+0x1 at 0x728a0a0a4000 domainbuilder: detail: xc_dom_alloc_segment: HVM start info : 0x175000 -> 0x176000 (pfn 0x175 + 0x1 pages) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x176000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 5928 bytes domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 170 kB domainbuilder: detail: domU mmap : 472 kB domainbuilder: detail: vcpu_hvm: called domainbuilder: detail: xc_dom_set_gnttab_entry: d10 gnt[0] -> d0 0xfefff domainbuilder: detail: xc_dom_set_gnttab_entry: d10 gnt[1] -> d0 0xfeffc domainbuilder: detail: xc_dom_release: called libxl: debug: libxl_device.c:415:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=phy specification=xen libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=0x61992510b2e0 wpath=/local/domain/0/backend/vbd/10/768/state token=3/0: register slotnum=3 libxl: debug: libxl_device.c:415:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=phy specification=xen libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=0x61992510c390 wpath=/local/domain/0/backend/vbd/10/832/state token=2/1: register slotnum=2 libxl: debug: libxl_create.c:2120:do_domain_create: ao 0x6199251022d0: inprogress: poller=0x619925102370, flags=i libxl: debug: libxl_event.c:750:watchfd_callback: watch w=0x61992510b2e0 wpath=/local/domain/0/backend/vbd/10/768/state token=3/0: event epath=/local/domain/0/backend/vbd/10/768/state libxl: debug: libxl_event.c:1051:devstate_callback: backend /local/domain/0/backend/vbd/10/768/state wanted state 2 ok libxl: debug: libxl_event.c:849:libxl__ev_xswatch_deregister: watch w=0x61992510b2e0 wpath=/local/domain/0/backend/vbd/10/768/state token=3/0: deregister slotnum=3 libxl: debug: libxl_device.c:1150:device_backend_callback: Domain 10:calling device_backend_cleanup libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510b2e0: deregister unregistered libxl: debug: libxl_linux.c:194:libxl__hotplug_disk: Domain 10:Args and environment ready libxl: debug: libxl_device.c:1251:device_hotplug: Domain 10:calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_device.c:1252:device_hotplug: Domain 10:extra args: libxl: debug: libxl_device.c:1260:device_hotplug: Domain 10:env: libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: script: /etc/xen/scripts/block libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_TYPE: vbd libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_PATH: backend/vbd/10/768 libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_BASE_PATH: backend libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block add libxl: debug: libxl_event.c:720:watchfd_callback: watch epath=/local/domain/0/backend/vbd/10/768/state token=3/0: empty slot libxl: debug: libxl_event.c:750:watchfd_callback: watch w=0x61992510c390 wpath=/local/domain/0/backend/vbd/10/832/state token=2/1: event epath=/local/domain/0/backend/vbd/10/832/state libxl: debug: libxl_event.c:1051:devstate_callback: backend /local/domain/0/backend/vbd/10/832/state wanted state 2 ok libxl: debug: libxl_event.c:849:libxl__ev_xswatch_deregister: watch w=0x61992510c390 wpath=/local/domain/0/backend/vbd/10/832/state token=2/1: deregister slotnum=2 libxl: debug: libxl_device.c:1150:device_backend_callback: Domain 10:calling device_backend_cleanup libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510c390: deregister unregistered libxl: debug: libxl_linux.c:194:libxl__hotplug_disk: Domain 10:Args and environment ready libxl: debug: libxl_device.c:1251:device_hotplug: Domain 10:calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_device.c:1252:device_hotplug: Domain 10:extra args: libxl: debug: libxl_device.c:1260:device_hotplug: Domain 10:env: libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: script: /etc/xen/scripts/block libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_TYPE: vbd libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_PATH: backend/vbd/10/832 libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_BASE_PATH: backend libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block add libxl: debug: libxl_event.c:720:watchfd_callback: watch epath=/local/domain/0/backend/vbd/10/832/state token=2/1: empty slot libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510c490: deregister unregistered libxl: debug: libxl_linux.c:211:libxl__get_hotplug_script_info: Domain 10:num_exec 1, not running hotplug scripts libxl: debug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplug script to execute libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510c490: deregister unregistered libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510b3e0: deregister unregistered libxl: debug: libxl_linux.c:211:libxl__get_hotplug_script_info: Domain 10:num_exec 1, not running hotplug scripts libxl: debug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplug script to execute libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510b3e0: deregister unregistered libxl: debug: libxl_dm.c:179:libxl__domain_get_device_model_uid: Domain 10:dm_restrict disabled, starting QEMU as root libxl: debug: libxl_disk.c:1292:libxl__device_disk_find_local_path: Directly accessing local RAW disk /dev/mapper/ubuntu--vg-couch--disk libxl: debug: libxl_disk.c:1292:libxl__device_disk_find_local_path: Directly accessing local RAW disk /dev/mapper/ubuntu--vg-couch--home libxl: debug: libxl_dm.c:2995:libxl__spawn_local_dm: Domain 10:Spawning device-model /usr/libexec/xen-qemu-system-i386 with arguments: libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: /usr/libexec/xen-qemu-system-i386 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -xen-domid libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: 10 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -no-shutdown libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -chardev libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-10,server=on,wait=off libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -mon libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: chardev=libxl-cmd,mode=control libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -chardev libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-10,server=on,wait=off libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -mon libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: chardev=libxenstat-cmd,mode=control libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -nodefaults libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -no-user-config libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -name libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: couch5 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -vnc libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: 127.0.0.1:5901,to=99 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -display libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: none libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -device libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: cirrus-vga,vgamem_mb=8 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -boot libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: order=dc libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -smp libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: 2,maxcpus=2 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -device libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: rtl8139,id=nic0,netdev=net0,mac=00:16:3e:05:01:a0 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -netdev libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: type=tap,id=net0,ifname=vif10.0-emu,br=xenbr0,script=no,downscript=no libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -machine libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: xenfv,suppress-vmdesc=on libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -m libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: 10232 libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -drive libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: file=/dev/mapper/ubuntu--vg-couch--disk,if=ide,index=0,media=disk,format=raw,cache=writeback libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: -drive libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: file=/dev/mapper/ubuntu--vg-couch--home,if=ide,index=1,media=disk,format=raw,cache=writeback libxl: debug: libxl_dm.c:2999:libxl__spawn_local_dm: Domain 10:Spawning device-model /usr/libexec/xen-qemu-system-i386 with additional environment: libxl: debug: libxl_dm.c:3001:libxl__spawn_local_dm: Domain 10: XEN_QEMU_CONSOLE_LIMIT=1048576 libxl: debug: libxl_dm.c:3001:libxl__spawn_local_dm: Domain 10: XEN_DOMAIN_ID=10 libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=0x619925109b10 wpath=/local/domain/0/device-model/10/state token=2/2: register slotnum=2 libxl: debug: libxl_event.c:750:watchfd_callback: watch w=0x619925109b10 wpath=/local/domain/0/device-model/10/state token=2/2: event epath=/local/domain/0/device-model/10/state libxl: debug: libxl_exec.c:407:spawn_watch_event: domain 10 device model: spawn watch p=(null) libxl: debug: libxl_event.c:849:libxl__ev_xswatch_deregister: watch w=0x619925109b10 wpath=/local/domain/0/device-model/10/state token=2/2: deregister slotnum=2 libxl: error: libxl_dm.c:3151:device_model_spawn_outcome: Domain 10:domain 10 device model: spawn failed (rc=-3) libxl: error: libxl_dm.c:3371:device_model_postconfig_done: Domain 10:Post DM startup configs failed, rc=-3 libxl: debug: libxl_qmp.c:1920:libxl__ev_qmp_dispose: ev 0x619925109b28 libxl: error: libxl_create.c:1896:domcreate_devmodel_started: Domain 10:device model did not start: -3 libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510b1e0: deregister unregistered libxl: debug: libxl_dm.c:3585:libxl__destroy_device_model: Domain 10:Didn't find dm UID; destroying by pid libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model already exited libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=0x61992510ce50 wpath=/local/domain/0/backend/vbd/10/768/state token=2/3: register slotnum=2 libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=0x61992510d260 wpath=/local/domain/0/backend/vbd/10/832/state token=3/4: register slotnum=3 libxl: debug: libxl_event.c:750:watchfd_callback: watch w=0x61992510ce50 wpath=/local/domain/0/backend/vbd/10/768/state token=2/3: event epath=/local/domain/0/backend/vbd/10/768/state libxl: debug: libxl_event.c:1051:devstate_callback: backend /local/domain/0/backend/vbd/10/768/state wanted state 6 ok libxl: debug: libxl_event.c:849:libxl__ev_xswatch_deregister: watch w=0x61992510ce50 wpath=/local/domain/0/backend/vbd/10/768/state token=2/3: deregister slotnum=2 libxl: debug: libxl_device.c:1150:device_backend_callback: Domain 10:calling device_backend_cleanup libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510ce50: deregister unregistered libxl: debug: libxl_linux.c:194:libxl__hotplug_disk: Domain 10:Args and environment ready libxl: debug: libxl_device.c:1251:device_hotplug: Domain 10:calling hotplug script: /etc/xen/scripts/block remove libxl: debug: libxl_device.c:1252:device_hotplug: Domain 10:extra args: libxl: debug: libxl_device.c:1260:device_hotplug: Domain 10:env: libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: script: /etc/xen/scripts/block libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_TYPE: vbd libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_PATH: backend/vbd/10/768 libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_BASE_PATH: backend libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block remove libxl: debug: libxl_event.c:720:watchfd_callback: watch epath=/local/domain/0/backend/vbd/10/768/state token=2/3: empty slot libxl: debug: libxl_event.c:750:watchfd_callback: watch w=0x61992510d260 wpath=/local/domain/0/backend/vbd/10/832/state token=3/4: event epath=/local/domain/0/backend/vbd/10/832/state libxl: debug: libxl_event.c:1051:devstate_callback: backend /local/domain/0/backend/vbd/10/832/state wanted state 6 ok libxl: debug: libxl_event.c:849:libxl__ev_xswatch_deregister: watch w=0x61992510d260 wpath=/local/domain/0/backend/vbd/10/832/state token=3/4: deregister slotnum=3 libxl: debug: libxl_device.c:1150:device_backend_callback: Domain 10:calling device_backend_cleanup libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510d260: deregister unregistered libxl: debug: libxl_linux.c:194:libxl__hotplug_disk: Domain 10:Args and environment ready libxl: debug: libxl_device.c:1251:device_hotplug: Domain 10:calling hotplug script: /etc/xen/scripts/block remove libxl: debug: libxl_device.c:1252:device_hotplug: Domain 10:extra args: libxl: debug: libxl_device.c:1260:device_hotplug: Domain 10:env: libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: script: /etc/xen/scripts/block libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_TYPE: vbd libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_PATH: backend/vbd/10/832 libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_BASE_PATH: backend libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block remove libxl: debug: libxl_event.c:720:watchfd_callback: watch epath=/local/domain/0/backend/vbd/10/832/state token=3/4: empty slot libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510cf50: deregister unregistered libxl: debug: libxl_linux.c:211:libxl__get_hotplug_script_info: Domain 10:num_exec 1, not running hotplug scripts libxl: debug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplug script to execute libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510cf50: deregister unregistered libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510d360: deregister unregistered libxl: debug: libxl_linux.c:211:libxl__get_hotplug_script_info: Domain 10:num_exec 1, not running hotplug scripts libxl: debug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplug script to execute libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x61992510d360: deregister unregistered libxl: debug: libxl_linux.c:234:libxl__get_hotplug_script_info: Domain 10:backend_kind 6, no need to execute scripts libxl: debug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplug script to execute libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=0x619925111fd0: deregister unregistered libxl: debug: libxl_domain.c:1597:devices_destroy_cb: Domain 10:Forked pid 3242 for destroy of domain libxl: debug: libxl_event.c:2067:libxl__ao_complete: ao 0x6199251022d0: complete, rc=-3 libxl: debug: libxl_event.c:2036:libxl__ao__destroy: ao 0x6199251022d0: destroy libxl: debug: libxl_domain.c:1046:libxl_domain_destroy: Domain 10:ao 0x6199251105c0: create: how=(nil) callback=(nil) poller=0x619925102370 libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain 10:Non-existant domain libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain 10:Unable to destroy guest libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 10:Destruction of domain failed libxl: debug: libxl_event.c:2067:libxl__ao_complete: ao 0x6199251105c0: complete, rc=-21 libxl: debug: libxl_domain.c:1055:libxl_domain_destroy: Domain 10:ao 0x6199251105c0: inprogress: poller=0x619925102370, flags=ic libxl: debug: libxl_event.c:2036:libxl__ao__destroy: ao 0x6199251105c0: destroy xencall:buffer: debug: total allocations:1338 total releases:1338 xencall:buffer: debug: current allocations:0 maximum allocations:3 xencall:buffer: debug: cache current size:3 xencall:buffer: debug: cache hits:1322 misses:3 toobig:13 xencall:buffer: debug: total allocations:0 total releases:0 xencall:buffer: debug: current allocations:0 maximum allocations:0 xencall:buffer: debug: cache current size:0 xencall:buffer: debug: cache hits:0 misses:0 toobig:0 --0000000000003aa2f406308b1063 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Installed ubuntu 24 onto=C2=A0E3-1225 v5 = @ 3.30GHz (2C/4T) with one boring sata disk, but I can't get the vm to = start the ubuntu24 server installer iso

cat >/etc/xen/aut= o/couch5.hvm <<'__EOF__'
builder =3D "hvm"
name =3D "couch5"
memory =3D "10240"
vcpus =3D 2
#vif =3D ['']
#vif =3D ['type=3Dioemu,model=3De1000']
#vif =3D ['type=3Dioemu,model=3Drtl8139']
disk =3D ['phy:/dev/mapper/ubuntu--vg-couch--disk,hda,w','p= hy:/dev/mapper/ubuntu--
vg-couch--home,hdb,w','file:/d/dmg/ubunt= u-24.04-live-server-amd64.iso,hdc:cdrom,
r']
#disk =3D
disk =3D ['phy:/dev/mapper/ubuntu--vg-couch--disk,hda,w','p= hy:/dev/mapper/ubuntu--
vg-couch--home,hdb,w']
vnc =3D 1
vncdisplay =3D 5901
boot=3D"dc"
__EOF__

As depicted here, commenting out all the vif=3D l= ines, it does boot (but a server without a network isn't useful). But i= f I include any of the vif=3D lines, it won't even start, I get:
<= div>
# xl create /etc/xen/auto/couch5.hvm
Parsing config from /etc/xen/auto/couch5.hvm
libxl: error: libxl_dm.c:3151:device_model_spawn_outcome: Domain 7:doma= in 7 devi
ce model: spawn failed (rc=3D-3)
libxl: error: libxl_dm.c:3371:device_model_postconfig_done: Domain 7:Po= st DM sta
rtup configs failed, rc=3D-3
libxl: error: libxl_create.c:1896:domcreate_devmodel_started: Domain 7:= device mo
del did not start: -3
libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model alr= eady exit
ed
libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain 7:Non-ex= istant do
main
libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain 7:Una= ble to de
stroy guest
libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 7:Destructi= on of dom
ain failed

From a previous thread (which I haven't had a chance t= o try on that other 256GB ram machine), It was suggested that "big ram= " vms may have trouble starting or start slowly, so I added:
echo 'GRUB_CMDLINE_XEN_DEFAULT=3D"dom0_mem=3Dmin:4096M,ma= x:4096
M"' >>/etc/default/grub
grub-install /dev/sda

though I don't know how to prove th= at it had an effect;
# xl list
Name =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0ID =C2=A0=C2=A0Mem VCPUs =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0State= =C2=A0=C2=A0Time(s)
Domain-0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A00 22019 =C2=A0=C2=A0=C2=A0=C2=A04 =C2=A0=C2=A0=C2=A0=C2=A0r----- =C2= =A0=C2=A0=C2=A0=C2=A0=C2=A032.5

=
Help?

=C2=A0 =C2=A0- Kevin
xl -vvv create /etc/xen/auto/couch5.hvm
Parsing config from /etc/xen/auto/couch5.hvm
libxl: debug: libxl_creat= e.c:2081:do_domain_create: ao 0x6199251022d0: create: how=3D(nil) callback= =3D(nil) poller=3D0x619925102370
libxl: detail: libxl_create.c:662:libxl= __domain_make: passthrough: disabled
libxl: debug: libxl_device.c:415:li= bxl__device_disk_set_backend: Disk vdev=3Dhda spec.backend=3Dunknown specif= ication=3Dxen
libxl: debug: libxl_device.c:452:libxl__device_disk_set_ba= ckend: Disk vdev=3Dhda, using backend phy
libxl: debug: libxl_device.c:4= 15:libxl__device_disk_set_backend: Disk vdev=3Dhdb spec.backend=3Dunknown s= pecification=3Dxen
libxl: debug: libxl_device.c:452:libxl__device_disk_s= et_backend: Disk vdev=3Dhdb, using backend phy
libxl: debug: libxl_creat= e.c:1342:initiate_domain_create: Domain 10:running bootloader
libxl: deb= ug: libxl_bootloader.c:411:libxl__bootloader_run: Domain 10:not a PV/PVH do= main, skipping bootloader
libxl: debug: libxl_event.c:863:libxl__ev_xswa= tch_deregister: watch w=3D0x619925109818: deregister unregistered
domain= builder: detail: xc_dom_allocate: cmdline=3D"", features=3D"= "
domainbuilder: detail: xc_dom_kernel_file: filename=3D"/usr/= lib/xen-4.17/boot/hvmloader"
domainbuilder: detail: xc_dom_malloc_f= ilemap =C2=A0 =C2=A0: 170 kB
libxl: debug: libxl_dom.c:810:libxl__load_h= vm_firmware_module: Loading BIOS: /usr/share/seabios/bios-256k.bin
domai= nbuilder: detail: xc_dom_boot_xen_init: ver 4.17, caps xen-3.0-x86_64 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 mu= ltiboot-binary loader ...
domainbuilder: detail: loader probe faileddomainbuilder: detail: xc_dom_find_loader: trying HVM-generic loader ... <= br>domainbuilder: detail: loader probe OK
xc: detail: ELF: phdr: paddr= =3D0x100000 memsz=3D0x340c0
xc: detail: ELF: memory: 0x100000 -> 0x13= 40c0
domainbuilder: detail: xc_dom_compat_check: supported guest type: x= en-3.0-x86_64
domainbuilder: detail: xc_dom_compat_check: supported gues= t type: hvm-3.0-x86_32 <=3D matches
domainbuilder: detail: xc_dom_com= pat_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: xc_dom_mem_init: mem 10232 MB, pages 0x27f800 pages, 4k each
do= mainbuilder: detail: xc_dom_mem_init: 0x27f800 pages
domainbuilder: deta= il: xc_dom_boot_mem_init: called
domainbuilder: detail: range: start=3D0= x0 end=3D0xf0000000
domainbuilder: detail: range: start=3D0x100000000 en= d=3D0x28f800000
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail: = =C2=A0 4KB PAGES: 0x0000000000000c00
xc: detail: =C2=A0 2MB PAGES: 0x000= 00000000005f6
xc: detail: =C2=A0 1GB PAGES: 0x0000000000000007
domain= builder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_do= m_pfn_to_ptr_retcount: domU mapping: pfn 0x100+0x35 at 0x728a09b11000
do= mainbuilder: detail: xc_dom_alloc_segment: =C2=A0 kernel =C2=A0 =C2=A0 =C2= =A0 : 0x100000 -> 0x135000 =C2=A0(pfn 0x100 + 0x35 pages)
xc: detail:= ELF: phdr 0 at 0x728a09adc000 -> 0x728a09b06640
domainbuilder: detai= l: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x135+0x40 at 0x728a09ad10= 00
domainbuilder: detail: xc_dom_alloc_segment: =C2=A0 System Firmware m= odule : 0x135000 -> 0x175000 =C2=A0(pfn 0x135 + 0x40 pages)
domainbui= lder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x175+0x1 at 0x= 728a0a0a4000
domainbuilder: detail: xc_dom_alloc_segment: =C2=A0 HVM sta= rt info : 0x175000 -> 0x176000 =C2=A0(pfn 0x175 + 0x1 pages)
domainbu= ilder: detail: xc_dom_build_image =C2=A0: virt_alloc_end : 0x176000
doma= inbuilder: detail: xc_dom_build_image =C2=A0: virt_pgtab_end : 0x0
domai= nbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: domai= n builder memory footprint
domainbuilder: detail: =C2=A0 =C2=A0allocated=
domainbuilder: detail: =C2=A0 =C2=A0 =C2=A0 malloc =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 : 5928 bytes
domainbuilder: detail: =C2=A0 =C2=A0 = =C2=A0 anon mmap =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: 0 bytes
domainbuild= er: detail: =C2=A0 =C2=A0mapped
domainbuilder: detail: =C2=A0 =C2=A0 =C2= =A0 file mmap =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: 170 kB
domainbuilder: = detail: =C2=A0 =C2=A0 =C2=A0 domU mmap =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: = 472 kB
domainbuilder: detail: vcpu_hvm: called
domainbuilder: detail:= xc_dom_set_gnttab_entry: d10 gnt[0] -> d0 0xfefff
domainbuilder: det= ail: xc_dom_set_gnttab_entry: d10 gnt[1] -> d0 0xfeffc
domainbuilder:= detail: xc_dom_release: called
libxl: debug: libxl_device.c:415:libxl__= device_disk_set_backend: Disk vdev=3Dhda spec.backend=3Dphy specification= =3Dxen
libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch= w=3D0x61992510b2e0 wpath=3D/local/domain/0/backend/vbd/10/768/state token= =3D3/0: register slotnum=3D3
libxl: debug: libxl_device.c:415:libxl__dev= ice_disk_set_backend: Disk vdev=3Dhdb spec.backend=3Dphy specification=3Dxe= n
libxl: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=3D= 0x61992510c390 wpath=3D/local/domain/0/backend/vbd/10/832/state token=3D2/1= : register slotnum=3D2
libxl: debug: libxl_create.c:2120:do_domain_creat= e: ao 0x6199251022d0: inprogress: poller=3D0x619925102370, flags=3Di
lib= xl: debug: libxl_event.c:750:watchfd_callback: watch w=3D0x61992510b2e0 wpa= th=3D/local/domain/0/backend/vbd/10/768/state token=3D3/0: event epath=3D/l= ocal/domain/0/backend/vbd/10/768/state
libxl: debug: libxl_event.c:1051:= devstate_callback: backend /local/domain/0/backend/vbd/10/768/state wanted = state 2 ok
libxl: debug: libxl_event.c:849:libxl__ev_xswatch_deregister:= watch w=3D0x61992510b2e0 wpath=3D/local/domain/0/backend/vbd/10/768/state = token=3D3/0: deregister slotnum=3D3
libxl: debug: libxl_device.c:1150:de= vice_backend_callback: Domain 10:calling device_backend_cleanup
libxl: d= ebug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=3D0x61992510b= 2e0: deregister unregistered
libxl: debug: libxl_linux.c:194:libxl__hotp= lug_disk: Domain 10:Args and environment ready
libxl: debug: libxl_devic= e.c:1251:device_hotplug: Domain 10:calling hotplug script: /etc/xen/scripts= /block add
libxl: debug: libxl_device.c:1252:device_hotplug: Domain 10:e= xtra args:
libxl: debug: libxl_device.c:1260:device_hotplug: Domain 10:e= nv:
libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: script:= /etc/xen/scripts/block
libxl: debug: libxl_device.c:1267:device_hotplug= : Domain 10: XENBUS_TYPE: vbd
libxl: debug: libxl_device.c:1267:device_h= otplug: Domain 10: XENBUS_PATH: backend/vbd/10/768
libxl: debug: libxl_d= evice.c:1267:device_hotplug: Domain 10: XENBUS_BASE_PATH: backend
libxl:= debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /e= tc/xen/scripts/block add
libxl: debug: libxl_event.c:720:watchfd_callba= ck: watch epath=3D/local/domain/0/backend/vbd/10/768/state token=3D3/0: emp= ty slot
libxl: debug: libxl_event.c:750:watchfd_callback: watch w=3D0x61= 992510c390 wpath=3D/local/domain/0/backend/vbd/10/832/state token=3D2/1: ev= ent epath=3D/local/domain/0/backend/vbd/10/832/state
libxl: debug: libxl= _event.c:1051:devstate_callback: backend /local/domain/0/backend/vbd/10/832= /state wanted state 2 ok
libxl: debug: libxl_event.c:849:libxl__ev_xswat= ch_deregister: watch w=3D0x61992510c390 wpath=3D/local/domain/0/backend/vbd= /10/832/state token=3D2/1: deregister slotnum=3D2
libxl: debug: libxl_de= vice.c:1150:device_backend_callback: Domain 10:calling device_backend_clean= up
libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w= =3D0x61992510c390: deregister unregistered
libxl: debug: libxl_linux.c:1= 94:libxl__hotplug_disk: Domain 10:Args and environment ready
libxl: debu= g: libxl_device.c:1251:device_hotplug: Domain 10:calling hotplug script: /e= tc/xen/scripts/block add
libxl: debug: libxl_device.c:1252:device_hotplu= g: Domain 10:extra args:
libxl: debug: libxl_device.c:1260:device_hotplu= g: Domain 10:env:
libxl: debug: libxl_device.c:1267:device_hotplug: Doma= in 10: script: /etc/xen/scripts/block
libxl: debug: libxl_device.c:1267:= device_hotplug: Domain 10: XENBUS_TYPE: vbd
libxl: debug: libxl_device.c= :1267:device_hotplug: Domain 10: XENBUS_PATH: backend/vbd/10/832
libxl: = debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_BASE_PATH: bac= kend
libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking = to execute: /etc/xen/scripts/block add
libxl: debug: libxl_event.c:720:= watchfd_callback: watch epath=3D/local/domain/0/backend/vbd/10/832/state to= ken=3D2/1: empty slot
libxl: debug: libxl_event.c:863:libxl__ev_xswatch_= deregister: watch w=3D0x61992510c490: deregister unregistered
libxl: deb= ug: libxl_linux.c:211:libxl__get_hotplug_script_info: Domain 10:num_exec 1,= not running hotplug scripts
libxl: debug: libxl_device.c:1236:device_ho= tplug: Domain 10:No hotplug script to execute
libxl: debug: libxl_event.= c:863:libxl__ev_xswatch_deregister: watch w=3D0x61992510c490: deregister un= registered
libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister:= watch w=3D0x61992510b3e0: deregister unregistered
libxl: debug: libxl_l= inux.c:211:libxl__get_hotplug_script_info: Domain 10:num_exec 1, not runnin= g hotplug scripts
libxl: debug: libxl_device.c:1236:device_hotplug: Doma= in 10:No hotplug script to execute
libxl: debug: libxl_event.c:863:libxl= __ev_xswatch_deregister: watch w=3D0x61992510b3e0: deregister unregistered<= br>libxl: debug: libxl_dm.c:179:libxl__domain_get_device_model_uid: Domain = 10:dm_restrict disabled, starting QEMU as root
libxl: debug: libxl_disk.= c:1292:libxl__device_disk_find_local_path: Directly accessing local RAW dis= k /dev/mapper/ubuntu--vg-couch--disk
libxl: debug: libxl_disk.c:1292:lib= xl__device_disk_find_local_path: Directly accessing local RAW disk /dev/map= per/ubuntu--vg-couch--home
libxl: debug: libxl_dm.c:2995:libxl__spawn_lo= cal_dm: Domain 10:Spawning device-model /usr/libexec/xen-qemu-system-i386 w= ith arguments:
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Doma= in 10: =C2=A0/usr/libexec/xen-qemu-system-i386
libxl: debug: libxl_dm.c:= 2997:libxl__spawn_local_dm: Domain 10: =C2=A0-xen-domid
libxl: debug: li= bxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A010
libxl: debug: l= ibxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-no-shutdown
libx= l: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-chardev<= br>libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0so= cket,id=3Dlibxl-cmd,path=3D/var/run/xen/qmp-libxl-10,server=3Don,wait=3Doff=
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-= mon
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2= =A0chardev=3Dlibxl-cmd,mode=3Dcontrol
libxl: debug: libxl_dm.c:2997:libx= l__spawn_local_dm: Domain 10: =C2=A0-chardev
libxl: debug: libxl_dm.c:29= 97:libxl__spawn_local_dm: Domain 10: =C2=A0socket,id=3Dlibxenstat-cmd,path= =3D/var/run/xen/qmp-libxenstat-10,server=3Don,wait=3Doff
libxl: debug: l= ibxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-mon
libxl: debug= : libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0chardev=3Dlibxens= tat-cmd,mode=3Dcontrol
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_= dm: Domain 10: =C2=A0-nodefaults
libxl: debug: libxl_dm.c:2997:libxl__sp= awn_local_dm: Domain 10: =C2=A0-no-user-config
libxl: debug: libxl_dm.c:= 2997:libxl__spawn_local_dm: Domain 10: =C2=A0-name
libxl: debug: libxl_d= m.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0couch5
libxl: debug: li= bxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-vnc
libxl: debug:= libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0127.0.0.1:5901,to=3D99
libxl: debug: libxl_dm.c:2997= :libxl__spawn_local_dm: Domain 10: =C2=A0-display
libxl: debug: libxl_dm= .c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0none
libxl: debug: libxl= _dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-device
libxl: debug:= libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0cirrus-vga,vgamem_= mb=3D8
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: = =C2=A0-boot
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain = 10: =C2=A0order=3Ddc
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm= : Domain 10: =C2=A0-smp
libxl: debug: libxl_dm.c:2997:libxl__spawn_local= _dm: Domain 10: =C2=A02,maxcpus=3D2
libxl: debug: libxl_dm.c:2997:libxl_= _spawn_local_dm: Domain 10: =C2=A0-device
libxl: debug: libxl_dm.c:2997:= libxl__spawn_local_dm: Domain 10: =C2=A0rtl8139,id=3Dnic0,netdev=3Dnet0,mac= =3D00:16:3e:05:01:a0
libxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm= : Domain 10: =C2=A0-netdev
libxl: debug: libxl_dm.c:2997:libxl__spawn_lo= cal_dm: Domain 10: =C2=A0type=3Dtap,id=3Dnet0,ifname=3Dvif10.0-emu,br=3Dxen= br0,script=3Dno,downscript=3Dno
libxl: debug: libxl_dm.c:2997:libxl__spa= wn_local_dm: Domain 10: =C2=A0-machine
libxl: debug: libxl_dm.c:2997:lib= xl__spawn_local_dm: Domain 10: =C2=A0xenfv,suppress-vmdesc=3Don
libxl: d= ebug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-m
libxl: = debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A010232
lib= xl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0-drivelibxl: debug: libxl_dm.c:2997:libxl__spawn_local_dm: Domain 10: =C2=A0fil= e=3D/dev/mapper/ubuntu--vg-couch--disk,if=3Dide,index=3D0,media=3Ddisk,form= at=3Draw,cache=3Dwriteback
libxl: debug: libxl_dm.c:2997:libxl__spawn_lo= cal_dm: Domain 10: =C2=A0-drive
libxl: debug: libxl_dm.c:2997:libxl__spa= wn_local_dm: Domain 10: =C2=A0file=3D/dev/mapper/ubuntu--vg-couch--home,if= =3Dide,index=3D1,media=3Ddisk,format=3Draw,cache=3Dwriteback
libxl: debu= g: libxl_dm.c:2999:libxl__spawn_local_dm: Domain 10:Spawning device-model /= usr/libexec/xen-qemu-system-i386 with additional environment:
libxl: deb= ug: libxl_dm.c:3001:libxl__spawn_local_dm: Domain 10: =C2=A0XEN_QEMU_CONSOL= E_LIMIT=3D1048576
libxl: debug: libxl_dm.c:3001:libxl__spawn_local_dm: D= omain 10: =C2=A0XEN_DOMAIN_ID=3D10
libxl: debug: libxl_event.c:812:libxl= __ev_xswatch_register: watch w=3D0x619925109b10 wpath=3D/local/domain/0/dev= ice-model/10/state token=3D2/2: register slotnum=3D2
libxl: debug: libxl= _event.c:750:watchfd_callback: watch w=3D0x619925109b10 wpath=3D/local/doma= in/0/device-model/10/state token=3D2/2: event epath=3D/local/domain/0/devic= e-model/10/state
libxl: debug: libxl_exec.c:407:spawn_watch_event: domai= n 10 device model: spawn watch p=3D(null)
libxl: debug: libxl_event.c:84= 9:libxl__ev_xswatch_deregister: watch w=3D0x619925109b10 wpath=3D/local/dom= ain/0/device-model/10/state token=3D2/2: deregister slotnum=3D2
libxl: e= rror: libxl_dm.c:3151:device_model_spawn_outcome: Domain 10:domain 10 devic= e model: spawn failed (rc=3D-3)
libxl: error: libxl_dm.c:3371:device_mod= el_postconfig_done: Domain 10:Post DM startup configs failed, rc=3D-3
li= bxl: debug: libxl_qmp.c:1920:libxl__ev_qmp_dispose: =C2=A0ev 0x619925109b28=
libxl: error: libxl_create.c:1896:domcreate_devmodel_started: Domain 10= :device model did not start: -3
libxl: debug: libxl_event.c:863:libxl__e= v_xswatch_deregister: watch w=3D0x61992510b1e0: deregister unregistered
= libxl: debug: libxl_dm.c:3585:libxl__destroy_device_model: Domain 10:Didn&#= 39;t find dm UID; destroying by pid
libxl: error: libxl_aoutils.c:646:li= bxl__kill_xs_path: Device Model already exited
libxl: debug: libxl_event= .c:812:libxl__ev_xswatch_register: watch w=3D0x61992510ce50 wpath=3D/local/= domain/0/backend/vbd/10/768/state token=3D2/3: register slotnum=3D2
libx= l: debug: libxl_event.c:812:libxl__ev_xswatch_register: watch w=3D0x6199251= 0d260 wpath=3D/local/domain/0/backend/vbd/10/832/state token=3D3/4: registe= r slotnum=3D3
libxl: debug: libxl_event.c:750:watchfd_callback: watch w= =3D0x61992510ce50 wpath=3D/local/domain/0/backend/vbd/10/768/state token=3D= 2/3: event epath=3D/local/domain/0/backend/vbd/10/768/state
libxl: debug= : libxl_event.c:1051:devstate_callback: backend /local/domain/0/backend/vbd= /10/768/state wanted state 6 ok
libxl: debug: libxl_event.c:849:libxl__e= v_xswatch_deregister: watch w=3D0x61992510ce50 wpath=3D/local/domain/0/back= end/vbd/10/768/state token=3D2/3: deregister slotnum=3D2
libxl: debug: l= ibxl_device.c:1150:device_backend_callback: Domain 10:calling device_backen= d_cleanup
libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: = watch w=3D0x61992510ce50: deregister unregistered
libxl: debug: libxl_li= nux.c:194:libxl__hotplug_disk: Domain 10:Args and environment ready
libx= l: debug: libxl_device.c:1251:device_hotplug: Domain 10:calling hotplug scr= ipt: /etc/xen/scripts/block remove
libxl: debug: libxl_device.c:1252:dev= ice_hotplug: Domain 10:extra args:
libxl: debug: libxl_device.c:1260:dev= ice_hotplug: Domain 10:env:
libxl: debug: libxl_device.c:1267:device_hot= plug: Domain 10: script: /etc/xen/scripts/block
libxl: debug: libxl_devi= ce.c:1267:device_hotplug: Domain 10: XENBUS_TYPE: vbd
libxl: debug: libx= l_device.c:1267:device_hotplug: Domain 10: XENBUS_PATH: backend/vbd/10/768<= br>libxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_BASE= _PATH: backend
libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start= : forking to execute: /etc/xen/scripts/block remove
libxl: debug: libxl= _event.c:720:watchfd_callback: watch epath=3D/local/domain/0/backend/vbd/10= /768/state token=3D2/3: empty slot
libxl: debug: libxl_event.c:750:watch= fd_callback: watch w=3D0x61992510d260 wpath=3D/local/domain/0/backend/vbd/1= 0/832/state token=3D3/4: event epath=3D/local/domain/0/backend/vbd/10/832/s= tate
libxl: debug: libxl_event.c:1051:devstate_callback: backend /local/= domain/0/backend/vbd/10/832/state wanted state 6 ok
libxl: debug: libxl_= event.c:849:libxl__ev_xswatch_deregister: watch w=3D0x61992510d260 wpath=3D= /local/domain/0/backend/vbd/10/832/state token=3D3/4: deregister slotnum=3D= 3
libxl: debug: libxl_device.c:1150:device_backend_callback: Domain 10:c= alling device_backend_cleanup
libxl: debug: libxl_event.c:863:libxl__ev_= xswatch_deregister: watch w=3D0x61992510d260: deregister unregistered
li= bxl: debug: libxl_linux.c:194:libxl__hotplug_disk: Domain 10:Args and envir= onment ready
libxl: debug: libxl_device.c:1251:device_hotplug: Domain 10= :calling hotplug script: /etc/xen/scripts/block remove
libxl: debug: lib= xl_device.c:1252:device_hotplug: Domain 10:extra args:
libxl: debug: lib= xl_device.c:1260:device_hotplug: Domain 10:env:
libxl: debug: libxl_devi= ce.c:1267:device_hotplug: Domain 10: script: /etc/xen/scripts/block
libx= l: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_TYPE: vbdlibxl: debug: libxl_device.c:1267:device_hotplug: Domain 10: XENBUS_PATH:= backend/vbd/10/832
libxl: debug: libxl_device.c:1267:device_hotplug: Do= main 10: XENBUS_BASE_PATH: backend
libxl: debug: libxl_aoutils.c:593:lib= xl__async_exec_start: forking to execute: /etc/xen/scripts/block remove libxl: debug: libxl_event.c:720:watchfd_callback: watch epath=3D/local/dom= ain/0/backend/vbd/10/832/state token=3D3/4: empty slot
libxl: debug: lib= xl_event.c:863:libxl__ev_xswatch_deregister: watch w=3D0x61992510cf50: dere= gister unregistered
libxl: debug: libxl_linux.c:211:libxl__get_hotplug_s= cript_info: Domain 10:num_exec 1, not running hotplug scripts
libxl: deb= ug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplug script to exec= ute
libxl: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch = w=3D0x61992510cf50: deregister unregistered
libxl: debug: libxl_event.c:= 863:libxl__ev_xswatch_deregister: watch w=3D0x61992510d360: deregister unre= gistered
libxl: debug: libxl_linux.c:211:libxl__get_hotplug_script_info:= Domain 10:num_exec 1, not running hotplug scripts
libxl: debug: libxl_d= evice.c:1236:device_hotplug: Domain 10:No hotplug script to execute
libx= l: debug: libxl_event.c:863:libxl__ev_xswatch_deregister: watch w=3D0x61992= 510d360: deregister unregistered
libxl: debug: libxl_linux.c:234:libxl__= get_hotplug_script_info: Domain 10:backend_kind 6, no need to execute scrip= ts
libxl: debug: libxl_device.c:1236:device_hotplug: Domain 10:No hotplu= g script to execute
libxl: debug: libxl_event.c:863:libxl__ev_xswatch_de= register: watch w=3D0x619925111fd0: deregister unregistered
libxl: debug= : libxl_domain.c:1597:devices_destroy_cb: Domain 10:Forked pid 3242 for des= troy of domain
libxl: debug: libxl_event.c:2067:libxl__ao_complete: ao 0= x6199251022d0: complete, rc=3D-3
libxl: debug: libxl_event.c:2036:libxl_= _ao__destroy: ao 0x6199251022d0: destroy
libxl: debug: libxl_domain.c:10= 46:libxl_domain_destroy: Domain 10:ao 0x6199251105c0: create: how=3D(nil) c= allback=3D(nil) poller=3D0x619925102370
libxl: error: libxl_domain.c:118= 3:libxl__destroy_domid: Domain 10:Non-existant domain
libxl: error: libx= l_domain.c:1137:domain_destroy_callback: Domain 10:Unable to destroy guest<= br>libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 10:Destructi= on of domain failed
libxl: debug: libxl_event.c:2067:libxl__ao_complete:= ao 0x6199251105c0: complete, rc=3D-21
libxl: debug: libxl_domain.c:1055= :libxl_domain_destroy: Domain 10:ao 0x6199251105c0: inprogress: poller=3D0x= 619925102370, flags=3Dic
libxl: debug: libxl_event.c:2036:libxl__ao__des= troy: ao 0x6199251105c0: destroy
xencall:buffer: debug: total allocation= s:1338 total releases:1338
xencall:buffer: debug: current allocations:0 = maximum allocations:3
xencall:buffer: debug: cache current size:3
xen= call:buffer: debug: cache hits:1322 misses:3 toobig:13
xencall:buffer: d= ebug: total allocations:0 total releases:0
xencall:buffer: debug: curren= t allocations:0 maximum allocations:0
xencall:buffer: debug: cache curre= nt size:0
xencall:buffer: debug: cache hits:0 misses:0 toobig:0
--0000000000003aa2f406308b1063-- From xen-users-bounces@lists.xenproject.org Mon Mar 17 15:57:41 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2025 15:57:41 +0000 Received: from list by lists.xenproject.org with outflank-mailman.917297.1322260 (Exim 4.92) (envelope-from ) id 1tuCq2-0002kr-T5; Mon, 17 Mar 2025 15:57:14 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 917297.1322260; Mon, 17 Mar 2025 15:57:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuCq2-0002kk-QJ; Mon, 17 Mar 2025 15:57:14 +0000 Received: by outflank-mailman (input) for mailman id 917297; Mon, 17 Mar 2025 15:57:13 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuCq1-0001td-Dx for xen-users@lists.xenproject.org; Mon, 17 Mar 2025 15:57:13 +0000 Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.161]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 7ce3dae0-0348-11f0-9aba-95dc52dad729; Mon, 17 Mar 2025 16:57:12 +0100 (CET) Received: from mail.onlineschubla.de by smtp.strato.de (RZmta 51.3.0 AUTH) with ESMTPSA id e1a88e12HFvBhVm (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Mon, 17 Mar 2025 16:57:11 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.onlineschubla.de (Postfix) with ESMTP id 8DB882171D for ; Mon, 17 Mar 2025 16:57:10 +0100 (CET) Received: from mail.onlineschubla.de ([127.0.0.1]) by localhost (mail.onlineschubla.de [127.0.0.1]) (amavis, port 10024) with ESMTP id ygH0DRzDtR_y for ; Mon, 17 Mar 2025 16:57:09 +0100 (CET) Received: from [10.0.0.105] (unknown [10.0.0.105]) by mail.onlineschubla.de (Postfix) with ESMTPA id 7BC1D200BD for ; Mon, 17 Mar 2025 16:57:09 +0100 (CET) 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: 7ce3dae0-0348-11f0-9aba-95dc52dad729 ARC-Seal: i=1; a=rsa-sha256; t=1742227031; cv=none; d=strato.com; s=strato-dkim-0002; b=KnvDOb3dI8EklQD9xfCQddwdSGFfg3mp3Oxec23VycoLUUr23NRgx9sThIt95XSHYU RryptdPy8+IBLNBuM/G99C9ldi6v/rsUbOLYUNho9suWeg36dgPL0cFmEvDQdN/y2Q0B gRO/xAU2Z+h2g/dL61oZVI8WHHQjUzmO6QFyDIVu7LsTJNdTYCo05pORbYXeImAiJ1pu UdbiW+qYuTKF/65lRKEHTAJgBOhqo1M7COxxOgIn4yIYgT3ZFAWpXB3lCRNC4CTHhTSX OlSPkW+3kDZnAOswFBMDNI4P+sGBqOYE2wpaS48qE83SPPvpzwLecKsrhmj4I5gpl6+9 XaAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1742227031; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=eJLpb9hUOp2Qo3u72isrmoKLWp8xZgzOwpGf/Kf+Ivw=; b=W/IEAFyY2AGb3JqqG+4FQEnt9c5EsSTfzxxrAQCulC2wrr2V4pdpOB2GFdc0+PQMIi yhv/cxBid/aPiYLevjkZ4jgwb1p/4bKDp17KvEdfnF59OqsrljxMVib/qrnLIUKNX9Ol MJGZ+8Y8HLurXrmBavvcXBZbTawA6cRtJL4d2etlU99z903pAwFKC58L6zE6haKMu4Q/ xZRvbN0qH8/wDyYbTMQyMp+BmLUAnG/h2x4nYalqo4cuCLh0RdoVwJos/gjXDReRoNrS iC13HSbDQMs6ASDhack0pDYw0urkIY7a7ia/cRkjVqvHwIXsu1T/2kU+drKgvcPR3otd kKKw== ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none X-RZG-CLASS-ID: mo00 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1742227031; s=strato-dkim-0002; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=eJLpb9hUOp2Qo3u72isrmoKLWp8xZgzOwpGf/Kf+Ivw=; b=I0k98ceXbYbBoaUn1yL3b3EzQMoSkWJe8DPSFbY5BeqVvPLEEHkMeAxT21CRz2OcyI OVjRZ5yrG9P5uJkrOniCf7xn0ygf9bj0T6nhBgOZ3vb+Kh98bjUlZB1RxRNkzodLTnHk LQOWP7HrDWR+XCXvYnNB06InLuIZJ+lO+6oIyo/Grrs8gL28F+qEl59ab21FyG7E2qvB vtGEDNwbr38WJYqhxUQyglxV0HEEyKnbaePaE4YcNFEmfSArmL33ibSNsAWmK5T1gGnr oUJ2kjxzAhCQ4H5ljhY2/0CSIMam9VkVMzj0J/5gHV/8+5KN64wjUDIQbEQHwZ67V3XN ojXg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1742227031; s=strato-dkim-0003; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=eJLpb9hUOp2Qo3u72isrmoKLWp8xZgzOwpGf/Kf+Ivw=; b=AFlsHJ59oGwHvXjRHSuaEahIVf71/bN6r2btjUm3HrOgI6IMYp+o13Zyub4B3zRIpV OeGHEZ4Bj1cZD2sNNKDA== X-RZG-AUTH: ":PG0ReWCndfO3rCSML4AvNaDxJ7WJyilEI/NMX3IPpS4dskMFCImCETb1V6b0vc0G92bEmF8ud91fucO4/zkqxx3jaL98L288QoU=" X-Virus-Scanned: Debian amavis at onlineschubla.de Message-ID: Date: Mon, 17 Mar 2025 16:57:03 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: can't start hvm with network To: xen-users@lists.xenproject.org References: Content-Language: en-US From: Paul Leiber In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Kevin, Am 17.03.2025 um 16:01 schrieb Kevin Wang: > Installed ubuntu 24 onto E3-1225 v5 @ 3.30GHz (2C/4T) with one boring > sata disk, but I can't get the vm to start the ubuntu24 server installer iso > > cat >/etc/xen/auto/couch5.hvm <<'__EOF__' > builder = "hvm" > name = "couch5" > memory = "10240" > vcpus = 2 > #vif = [''] > #vif = ['type=ioemu,model=e1000'] > #vif = ['type=ioemu,model=rtl8139'] > disk = ['phy:/dev/mapper/ubuntu--vg-couch--disk,hda,w','phy:/dev/mapper/ > ubuntu-- > vg-couch--home,hdb,w','file:/d/dmg/ubuntu-24.04-live-server- > amd64.iso,hdc:cdrom, > r'] > #disk = > disk = ['phy:/dev/mapper/ubuntu--vg-couch--disk,hda,w','phy:/dev/mapper/ > ubuntu-- > vg-couch--home,hdb,w'] > vnc = 1 > vncdisplay = 5901 > boot="dc" > __EOF__ > > As depicted here, commenting out all the vif= lines, it does boot (but a > server without a network isn't useful). But if I include any of the vif= > lines, it won't even start, I get: > > # xl create /etc/xen/auto/couch5.hvm > Parsing config from /etc/xen/auto/couch5.hvm > libxl: error: libxl_dm.c:3151:device_model_spawn_outcome: Domain > 7:domain 7 devi > ce model: spawn failed (rc=-3) > libxl: error: libxl_dm.c:3371:device_model_postconfig_done: Domain > 7:Post DM sta > rtup configs failed, rc=-3 > libxl: error: libxl_create.c:1896:domcreate_devmodel_started: Domain > 7:device mo > del did not start: -3 > libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model > already exit > ed > libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain 7:Non- > existant do > main > libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain > 7:Unable to de > stroy guest > libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain > 7:Destruction of dom > ain failed Unfortunately, I don't have the knowledge to analyze the output you posted in detail. What comes to my mind, though: Did you set up a network bridge on Dom0? The default name of the bridge, if no other is given in the vif=... line (as in your examples), is xenbr0, as described in the docs [1]. My main guide is still the old wiki [2], the steps to create such a bridge are given there. On another note: Why are you using HVM for setting up a linux DomU? I never tested Ubuntu myself, but for Debian (and most likely Debian-based) distributions, PV should the better option. Again, [2] shows how to install a Debian PV DomU, and the procedure is still working (of course, wheezy is a bit outdated and needs to be replaced, e. g. with bookworm). The section even mentions Ubuntu distributions, so it's probably worth to dig deeper there. Paul [1] https://xenbits.xenproject.org/docs/unstable/man/xl-network-configuration.5.html [2] https://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide#Creating_a_Windows_HVM_(Hardware_Virtualized)_Guest From xen-users-bounces@lists.xenproject.org Mon Mar 17 17:50:52 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2025 17:50:52 +0000 Received: from list by lists.xenproject.org with outflank-mailman.917600.1322490 (Exim 4.92) (envelope-from ) id 1tuEbN-0001ce-Av; Mon, 17 Mar 2025 17:50:13 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 917600.1322490; Mon, 17 Mar 2025 17:50: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 1tuEbN-0001cX-7W; Mon, 17 Mar 2025 17:50:13 +0000 Received: by outflank-mailman (input) for mailman id 917600; Mon, 17 Mar 2025 17:50:11 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuEbL-0001cR-6p for xen-users@lists.xenproject.org; Mon, 17 Mar 2025 17:50:11 +0000 Received: from out.good-with-numbers.com (out.good-with-numbers.com [70.36.235.100]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 41980004-0358-11f0-9aba-95dc52dad729; Mon, 17 Mar 2025 18:50:08 +0100 (CET) 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: 41980004-0358-11f0-9aba-95dc52dad729 Date: Mon, 17 Mar 2025 17:47:17 +0000 From: Mike To: Paul Leiber Cc: xen-users@lists.xenproject.org Subject: Re: domU memory exceeded =?us-ascii?B?PT89?= =?us-ascii?Q?=3E?= spontaneous reboots Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Mar 1, 2025, Paul Leiber wrote: > I can access > Xen's serial console via SoL. I successfully tried Intel Manageability > Commander and Mesh Commander. I set up an IPMI connection to the Xen box. I set "loglvl=all" and "guest_loglvl=all", and am seeing accordingly more messages on the monitor. I set the BIOS setting for the P1 power level at 87W, the maximum dissipation that the fanless case is supposed to be able to handle. I did this just to prevent overheating, though I still don't believe that's an issue. I also set "noreboot=true", yet when the system failed spontaneously again, it rebooted as well. I know this setting works, because when I manually rebooted with "shutdown -r", the reboot didn't happen; I had to force it manually. This is concerning to me, since it suggests that the failure is happening at a lower level than what Xen controls. I'm still not seeing the boot output on the SOL console. I'm using the one that's built into the Supermicro IPMI web console, which is based on Java WebStart--a rather old and oddball technology. I should try using `ipmitool` or such. But I think the real issue with SOL is in the BIOS settings. It's a Supermicro board, and the settings appear to be in the "Advanced" menu bar. Under "Serial Port Console Redirection", "SOL Console Redirection" is already "Enabled"; under "AST2600SEC Super IO Configuration" > "SOL Configuration", "SOL" is already "Enabled" with "Device Settings" of "IO=2F8h; IRQ=3;". So I'm adding "com2=115200,8n1,0x2f8,3 console=com2,vga" to Xen. Yet I'm still seeing the output on the VGA monitor. It's not clear to me whether I need to redirect one of the COM ports as well. "dmesg | grep ttyS" gets me that ttyS1 (= COM2?) is at 0x2f8, IRQ 3. From xen-users-bounces@lists.xenproject.org Mon Mar 17 18:24:54 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2025 18:24:54 +0000 Received: from list by lists.xenproject.org with outflank-mailman.917653.1322515 (Exim 4.92) (envelope-from ) id 1tuF8W-0002YM-7O; Mon, 17 Mar 2025 18:24:28 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 917653.1322515; Mon, 17 Mar 2025 18:24:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuF8W-0002YF-4p; Mon, 17 Mar 2025 18:24:28 +0000 Received: by outflank-mailman (input) for mailman id 917653; Mon, 17 Mar 2025 18:24:26 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuF8U-0002Y9-6Q for xen-users@lists.xenproject.org; Mon, 17 Mar 2025 18:24:26 +0000 Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.161]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 0d28df60-035d-11f0-9aba-95dc52dad729; Mon, 17 Mar 2025 19:24:24 +0100 (CET) Received: from mail.onlineschubla.de by smtp.strato.de (RZmta 51.3.0 AUTH) with ESMTPSA id e1a88e12HIOMhp1 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Mon, 17 Mar 2025 19:24:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.onlineschubla.de (Postfix) with ESMTP id 6C8212171D for ; Mon, 17 Mar 2025 19:24:22 +0100 (CET) Received: from mail.onlineschubla.de ([127.0.0.1]) by localhost (mail.onlineschubla.de [127.0.0.1]) (amavis, port 10024) with ESMTP id qia7bVsBOhdW for ; Mon, 17 Mar 2025 19:24:21 +0100 (CET) Received: from [10.0.0.105] (unknown [10.0.0.105]) by mail.onlineschubla.de (Postfix) with ESMTPA id 74CCA200BD for ; Mon, 17 Mar 2025 19:24:21 +0100 (CET) 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: 0d28df60-035d-11f0-9aba-95dc52dad729 ARC-Seal: i=1; a=rsa-sha256; t=1742235863; cv=none; d=strato.com; s=strato-dkim-0002; b=N7kJ4WA/lL5YRUvz1+Gjs8xbEsRJqBdfxOnQ7fRw9TwZZmiIoe5nBixnJi0phaNQ6A sZ6sAo2L3sjjYeLmbiwl0OirP7VKA5rVeW7cBVgNfZ6R56JjH86s7KXbMxEyNqqjmVIY f5IRIKVnMLCf3odtp8txxFvxV25jeQKzRqjSWTUB87dRsRrtef+Mlil8rYrFtGr7wdBo 0YOOIbUdPVkgLx3d4xMxtNqpCd78gl5D1PHrm6qHqX0SksjakEP+iPDXOgzVmOdckjLi QtMpc2gDBu9BeYiDIGAI0sBUs/VybSzAeaZfhD4dKO+kdUjsVDlN/FCLu09lJeakuJIh H1xA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1742235863; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=GLD4Xvn/DfsENKkwMtNmnUNHJ5Y/Ut9h+qpAy8K0tVE=; b=bxM1rLlmgu1L1jJPBuRym7jM/AiUNhQOUGhPl0hbQRb3bSIDSCPvByBFYaO979cOQ3 jRNK/D6Jj41lEaziti6+8+czHi094BKnMOYOg5zvPXrJsaiemsukHDQLZfQirYY3S/ah Z+K1Va0HJprTJG+EqihnDy9h2nY/OXRXWcERdXR6h/JSlSx1pKgv7ttdIb0pJAqEqNxn GUg8VKwOnnYUYpWjTWLSH4btWxrDtLO46fBXKhga49rxERUPcLW0Zbt/d/fnm6nLKydJ +LzcJqySh2onCfB8fp94045MR9WuTD/TvZUAGEhOCabKjKOQWanrNdPnzwPaEmehXbM0 4vWg== ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none X-RZG-CLASS-ID: mo00 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1742235863; s=strato-dkim-0002; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=GLD4Xvn/DfsENKkwMtNmnUNHJ5Y/Ut9h+qpAy8K0tVE=; b=Rn8DDDalvu7SRqCuo2nKA0FcdoN0uXnVaQmOubSQhJCHx3obriY58C8FCTZW4MWLTV mY55rFBgWWtmenwoTiMqnlEJs025WzsfzRhQCRrKtQuSGEFfiOyQVLrvLZGvavZKKJGd V3D9FFtSDXkH29wvvor/2X2BLWyoOpVw6k8TxxrNaWRsk8lee7+gcdXPFz3fE021ZkIc 5xlK/328DDODAj1UrJ/ndtGH8FUsqGNw3gv2eDxcY2AWdkxsy5n3Uy8cDP1g1ZeiIpUp LJCVrPsBmD7yw/sHJ/Hd5Z7WrH9UOMQbMioHpX4dykwuHoR20AJBfyxjF5xDuvU9wKJN 7xfg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1742235863; s=strato-dkim-0003; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=GLD4Xvn/DfsENKkwMtNmnUNHJ5Y/Ut9h+qpAy8K0tVE=; b=vbJTk4bIY+a7dxPLF5NxKOsTmqF/chizs4U0FEsYRNaiNzxNKbYZi8iTJhErSyYllK VJLHBeYxlaEo43rHatBQ== X-RZG-AUTH: ":PG0ReWCndfO3rCSML4AvNaDxJ7WJyilEI/NMX3IPpS4dskMFCImCETb1V6b0vc0G92bEmF8ud91fucO4/zkqxx3jaL98L288QoU=" X-Virus-Scanned: Debian amavis at onlineschubla.de Message-ID: <13713ac1-3f53-4168-b427-3ec295942bbd@onlineschubla.de> Date: Mon, 17 Mar 2025 19:24:21 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: domU memory exceeded =?=> spontaneous reboots To: xen-users@lists.xenproject.org References: Content-Language: en-US From: Paul Leiber In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 17.03.2025 um 18:47 schrieb Mike: > On Mar 1, 2025, Paul Leiber wrote: >> I can access >> Xen's serial console via SoL. I successfully tried Intel Manageability >> Commander and Mesh Commander. > > I set up an IPMI connection to the Xen box. I set "loglvl=all" and > "guest_loglvl=all", and am seeing accordingly more messages on the monitor. > > I set the BIOS setting for the P1 power level at 87W, the maximum dissipation > that the fanless case is supposed to be able to handle. I did this just to > prevent overheating, though I still don't believe that's an issue. > > I also set "noreboot=true", yet when the system failed spontaneously again, > it rebooted as well. I know this setting works, because when I manually > rebooted with "shutdown -r", the reboot didn't happen; I had to force it > manually. This is concerning to me, since it suggests that the failure is > happening at a lower level than what Xen controls. > > I'm still not seeing the boot output on the SOL console. I'm using the one > that's built into the Supermicro IPMI web console, which is based on Java > WebStart--a rather old and oddball technology. I should try using `ipmitool` > or such. > > But I think the real issue with SOL is in the BIOS settings. It's a > Supermicro board, and the settings appear to be in the "Advanced" menu bar. > Under "Serial Port Console Redirection", "SOL Console Redirection" is already > "Enabled"; under "AST2600SEC Super IO Configuration" > "SOL Configuration", > "SOL" is already "Enabled" with "Device Settings" of "IO=2F8h; IRQ=3;". So > I'm adding "com2=115200,8n1,0x2f8,3 console=com2,vga" to Xen. Yet I'm still > seeing the output on the VGA monitor. It's not clear to me whether I need to > redirect one of the COM ports as well. "dmesg | grep ttyS" gets me that > ttyS1 (= COM2?) is at 0x2f8, IRQ 3. > Looks similar to what I am doing: loglvl=all guest_loglvl=all com1=115200,8n1,0xe2a0,17 console=vga,com1 Did you check the wiki on serial console [1]? It has a paragraph on SoL ("Configuring serial console for non-standard PCI serial ports (for example Intel AMT)"). Best regards, Paul [1] https://wiki.xenproject.org/wiki/Xen_Serial_Console From xen-users-bounces@lists.xenproject.org Mon Mar 17 18:28:20 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2025 18:28:20 +0000 Received: from list by lists.xenproject.org with outflank-mailman.917687.1322532 (Exim 4.92) (envelope-from ) id 1tuFCA-0003YY-Qh; Mon, 17 Mar 2025 18:28:14 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 917687.1322532; Mon, 17 Mar 2025 18:28:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuFCA-0003YR-NS; Mon, 17 Mar 2025 18:28:14 +0000 Received: by outflank-mailman (input) for mailman id 917687; Mon, 17 Mar 2025 18:28:13 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuFC9-0003YC-SD for xen-users@lists.xenproject.org; Mon, 17 Mar 2025 18:28:13 +0000 Received: from out.good-with-numbers.com (out.good-with-numbers.com [70.36.235.100]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 93ae1ff6-035d-11f0-9899-31a8f345e629; Mon, 17 Mar 2025 19:28:11 +0100 (CET) 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: 93ae1ff6-035d-11f0-9899-31a8f345e629 Date: Mon, 17 Mar 2025 18:25:17 +0000 From: Mike To: Paul Leiber Cc: xen-users@lists.xenproject.org Subject: Re: domU memory exceeded =?us-ascii?B?PT89?= =?us-ascii?Q?=3E?= spontaneous reboots Message-ID: References: <13713ac1-3f53-4168-b427-3ec295942bbd@onlineschubla.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13713ac1-3f53-4168-b427-3ec295942bbd@onlineschubla.de> Paul Leiber wrote: > Did you check the wiki on serial console [1]? It has a paragraph on SoL > ("Configuring serial console for non-standard PCI serial ports (for example > Intel AMT)"). Yes. I don't think I'm using the Intel AMT's SOL, but rather IPMI's SOL. From xen-users-bounces@lists.xenproject.org Tue Mar 18 03:23:40 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2025 03:23:40 +0000 Received: from list by lists.xenproject.org with outflank-mailman.918449.1323128 (Exim 4.92) (envelope-from ) id 1tuNXb-0007ja-EX; Tue, 18 Mar 2025 03:22:55 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 918449.1323128; Tue, 18 Mar 2025 03:22:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuNXb-0007jT-Aq; Tue, 18 Mar 2025 03:22:55 +0000 Received: by outflank-mailman (input) for mailman id 918449; Tue, 18 Mar 2025 03:22:53 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuNXZ-0007jN-KK for xen-users@lists.xenproject.org; Tue, 18 Mar 2025 03:22:53 +0000 Received: from out.good-with-numbers.com (out.good-with-numbers.com [70.36.235.100]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 45108a1f-03a8-11f0-9aba-95dc52dad729; Tue, 18 Mar 2025 04:22:51 +0100 (CET) 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: 45108a1f-03a8-11f0-9aba-95dc52dad729 Date: Tue, 18 Mar 2025 03:20:03 +0000 From: Mike To: xen-users@lists.xenproject.org Subject: who performs a domU fsck? Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline My Linux domUs each have a block device, an LVM volume, mounted as /. Where, if anywhere, does the file system on those volumes have a fsck run on it after a system crash, i.e., when the file system wasn't properly unmounted? For the dom0, I see that happen during the boot process. Not seeing anything logged in /var/log/xen/. I've been having spontaneous system reboots, and suspect that those have now corrupted the file systems as well because nothing was running fsck on reboot. I added the devices to the dom0 /etc/fstab now in hopes that that fixes it. One would think that the domU would behave just like the dom0 in this regard. I'd like to see evidence. From xen-users-bounces@lists.xenproject.org Tue Mar 18 11:01:04 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2025 11:01:04 +0000 Received: from list by lists.xenproject.org with outflank-mailman.918927.1323532 (Exim 4.92) (envelope-from ) id 1tuUgD-0007uI-Ta; Tue, 18 Mar 2025 11:00:17 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 918927.1323532; Tue, 18 Mar 2025 11:00: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 1tuUgD-0007uB-Qc; Tue, 18 Mar 2025 11:00:17 +0000 Received: by outflank-mailman (input) for mailman id 918927; Tue, 18 Mar 2025 11:00:16 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuUgB-0007u5-PN for xen-users@lists.xenproject.org; Tue, 18 Mar 2025 11:00:16 +0000 Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2071f.outbound.protection.outlook.com [2a01:111:f403:2613::71f]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 2a530358-03e8-11f0-9899-31a8f345e629; Tue, 18 Mar 2025 12:00:13 +0100 (CET) Received: from AS2PR03MB8866.eurprd03.prod.outlook.com (2603:10a6:20b:555::6) by AS2PR03MB9767.eurprd03.prod.outlook.com (2603:10a6:20b:60c::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8534.33; Tue, 18 Mar 2025 11:00:05 +0000 Received: from AS2PR03MB8866.eurprd03.prod.outlook.com ([fe80::6cf6:d635:ff88:ab5c]) by AS2PR03MB8866.eurprd03.prod.outlook.com ([fe80::6cf6:d635:ff88:ab5c%4]) with mapi id 15.20.8534.031; Tue, 18 Mar 2025 11:00:05 +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: 2a530358-03e8-11f0-9899-31a8f345e629 ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=AWxPIy36tN4hpZn4YQ2HY6ExE9wpq+PwaKUcVawFg4jGM59gOgGZwZ+WvCkXskajBEjpX9LB/NilL+r8S5VWwayx5UdnpyzOoOJnXTJTXxS8bzTfw1Z/qrIIAB1GUniwqI/Q3Ymvv9GLBgjfj7Yd+8/WIbpYY4DJbj6YzZkxC4DhKJrh+tn+BP6fYLMEK6rWD8HDcKqrgoPAMyU44VeHJCUJ7CWyQdncxjaggZRnG1yIDf4P0D+XtffFKpCbAsIWpPJzyxGUP/SbPb0IH/+qtXEqSWmHiS6+3bo4XJThirwAHDiCfLK2j7YXosQrYjqRkdHqCLiyhFTZ5UFgVn63YQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/tXBDHBBJSShKmjoPYhTJEFUh6A33jJ+lsl5Hh/AZAU=; b=vLUQDxmFpfTLCMDrhh6H/Fw6BwioWyP+5ozqFGxCu5o0ws+0GEAEG24hbxTzluAsnCkpLxDpb8N+t1GOY1A9uGX0R0nQxLnRXDxSCa1zB7U0HA4sRStC3mHCzq9cMM3FpRM0kJXOs21mUDsTD7f+FucId7fZ/skSBOxwlOTf2oaEid6+DuZYl7XmE5ktqx4z8oZKLt+5vAk1noKEU4ggsk0fI7MUnE5jJ6eM1QrAj1YaC/q35mfyeCLQOqYFeUDRm2qn9CML7MCV4UjDgt1f8HY9Jryr03EoiTk3ET4rLhImKV6I8oeRuXkH3SpIIVwqxhTkJ2ivEXpoE9lPYsbLeA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nic.at; dmarc=pass action=none header.from=nic.at; dkim=pass header.d=nic.at; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.at; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/tXBDHBBJSShKmjoPYhTJEFUh6A33jJ+lsl5Hh/AZAU=; b=WwJ6mh1ekOwM0wqhWONPjbpRo2i+X+Wt4qZWb9q9FBYwApEfeXwXerR2TuEg4pe6G6q717tXv/i7SzBbiv2gdDA+HA3tuAIINBKJnR5jYULHVhO46XwK3GNhsLX7yNtLrPQ+vT8QS3oasGBwYEPShmBVRlrf0ypKjZ3fDtrTe8qSPFoBGtZFn2LLiuC831dl3IUeu91aPTbeJHy5DkVsSxd88oE80LRnWfB0TUk2T+EKlf7Y21I9DFudI8cBYRup4A0KTohwIS4hdGQOClEAflqavXL3xdEEnBWmTCAdejTeckOvQ1pEaMkMdt+1qhWu0YBph/XjFPF1H+fbpdGjMQ== From: Klaus Darilion To: Mike , "xen-users@lists.xenproject.org" Subject: RE: who performs a domU fsck? Thread-Topic: who performs a domU fsck? Thread-Index: AQHbl7VADFcK58HtL0Caoo7sHt60pLN4uirA Date: Tue, 18 Mar 2025 11:00:05 +0000 Message-ID: References: In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=nic.at; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: AS2PR03MB8866:EE_|AS2PR03MB9767:EE_ x-ms-office365-filtering-correlation-id: c0d58c62-401d-4030-0dd1-08dd660c0a76 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230040|366016|1800799024|376014|38070700018; x-microsoft-antispam-message-info: =?iso-8859-1?Q?SlEjlS29xI657XXuxbgg9ziaoV4OeiM/g3tCOJXGqcloe8e4YqgiRePvIk?= =?iso-8859-1?Q?cuRfW87blRIsbmOlT5nqFT7FnpWqQEqkfpb4X6mMSRZ55IN2Ar4Iof0k0z?= =?iso-8859-1?Q?UoskKDWrb0C0udyJFEoMWCCf9kcCnWpEhjH/PqB3NWfpJH/zF0q8Z8IPxW?= =?iso-8859-1?Q?EXnXtpuTbjW1ovnboM1FU5xDE7hjj6sODPlYm3wJcvsap24oBV9cOm6YVn?= =?iso-8859-1?Q?yk/7booRBQ2YSSl8PT+DTh5fNnhS8ZXVQ9ptmeVXPua/hFqQoPkXBmYotf?= =?iso-8859-1?Q?95e585k85waC0sAumciNO4cIdqNtB4XFO/ETx/M2h0F9WbULLir9UDmmIV?= =?iso-8859-1?Q?s0yS6NshmOaao4Wo6RVWHpDeUCx4Hm2wd6tNHvmcv5wdub7R5j8buk6j0/?= =?iso-8859-1?Q?8zXP4tQf3P41dVKKUmALWXxw/JqJE/16KhU3Y7m4Bf27Wa8MERAoXbgTh/?= =?iso-8859-1?Q?Gzc0RmbeG2NKTWP4CIcK04SrKFNx2CRLJqt8CFfbvf7YxEGNl7yIkbYp8P?= =?iso-8859-1?Q?3Z5dFFI1UKo3I5epSw89m88aSsOnMUMeDY3P5pcQTivYUERlM+mWjNz047?= =?iso-8859-1?Q?Lw4Kh3IoIrvZk8mOegoVXB6ldBMxRsFojrKDMdCIrArb7ZWO7pL0Z6X8FS?= =?iso-8859-1?Q?G9DyLfzdjd8DcTYyotK1BIspnfZQxcEm+tGRDyJLkwgVFNqqFz/L0pe1Bb?= =?iso-8859-1?Q?L4D2Qq2LWLRjJi10qhga9ARaXGiDYqhmtdJe4NeU6t4/APlxuyBy3Om/Zl?= =?iso-8859-1?Q?JONy5hh7kXHRbYObtKXyMkexHK/33ol8+zwtUAcQcfNLW6e/+BKoVWtGn2?= =?iso-8859-1?Q?Twh1aKOchtW4SkcmySAYaVX4Q9AgVuPS0xwlMqABGeIVASpP6YWWfP772m?= =?iso-8859-1?Q?oy/V5uSlxfPnxcS2yG1nV5RXtp5NgoZpSG49zVBykeu4JtSCkUzmLv3Dzc?= =?iso-8859-1?Q?zNtQ/J8uEeK9XDQhOp5BqN4Hr+4rWiuoCP2gSWFpPP3860V0h3/+C0k1iO?= =?iso-8859-1?Q?eCdgul55mQgDwQWWgfxJjjmoUCkttu1FSRwXBMxpxoIFOrELilLvRVlEMb?= =?iso-8859-1?Q?h8RGWcRYkv0KnDIdhDk7AkhnmUuh+QOsSfuysgqvL+ptPKxylMX5M70ok4?= =?iso-8859-1?Q?2FUyB4t/O1U9t29wyKrRmloYlYtmvBmVEYZNN71w6gjEWpbUU63S+HdVC3?= =?iso-8859-1?Q?AcE7KfBk9uEbqF/Tk+jqaQVA4grvREDiknSUdgW0Uf3glYgnysb/ZiS/xO?= =?iso-8859-1?Q?7CQ4cMoWrACVSDqyGGco144l7pP+yWoFopq4irMfnjZAKXOBgJQ0x+NGld?= =?iso-8859-1?Q?wzq/NXJs7iX8E2/vZbkrGBKH8dYzYbtCH83eCeMl69lxjiFipzU5Qws2nV?= =?iso-8859-1?Q?Nod/P2Wp4YgubJxfpTSqlfJfts8YXittaxpRhbNxy0HTk22w4SuGMG2JE8?= =?iso-8859-1?Q?XIlgn7hiMX0GuVfmfp0uA81TITn01JPXa7bSbmpWZsC110ezG4D9GPyDdW?= =?iso-8859-1?Q?D8Lmrd47AKOALuprabH1Pw?= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:AS2PR03MB8866.eurprd03.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(1800799024)(376014)(38070700018);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?lOSkoQhYst54cwPifwpYIUlebxhijVHH6d63BTaUnkFES963y8HvfDvijM?= =?iso-8859-1?Q?e4JthVZDxy/3Fj35GNs4+PLzWCAfGCbc2RSl0D8I8QavM3CXoGrz1+iI58?= =?iso-8859-1?Q?RP21fiaywc0YaLQq6qSsNpKH65ZpYfyrYhx/40i3MxXTmCDYzSc10dVRNc?= =?iso-8859-1?Q?0psrFH/U5IrLIc+OuXHk9i+O/idpyTCxcj2palfdDqiSJpBkCulwQbYAog?= =?iso-8859-1?Q?/XgjMpbjOsuCDXotPGpdyjYX5aHGUt3OgA7B5rLLR0piX4yWAbo6jZclrd?= =?iso-8859-1?Q?HVUYu6+LqnUJG6ZNL1tRj21URhfffY4GvYSXmCA7mMnaH6vDuyLbVFg54j?= =?iso-8859-1?Q?1qoG69SofhuIlY+v3UmjfueH8K74FQc4mUjaK98OU9BbNkD/+l8RO4qNrH?= =?iso-8859-1?Q?zuSN2AbFINaWZzs1x4EqtJCUFeMqm5OR7TJq3HwFdTw7XxNHWLy+ez8+5Z?= =?iso-8859-1?Q?PH9+gq6GSmQlhBxYvj/n8YnNMBUiS/C6fniLcMG3Y1A784dOvTDu9Me3Te?= =?iso-8859-1?Q?73HWg4atiANKfhQBBHr1R3H3otge3wfE/7eT3SVZfriB8djUQ0PZUaRbm3?= =?iso-8859-1?Q?5bPTbgRR6kOlS1BHgBpF8P0PJXanB9OGMCwFamPjSvERNf/FX1gDzyOxM9?= =?iso-8859-1?Q?XUPd18t9owli5wBPsSNkl5OC4dTWxk8VkEbHX8FgEMJP4KicUNcvm11NnT?= =?iso-8859-1?Q?JuTzH9SaOlHXYXghAEl8ZJyWjk+WzhWmGXct0hXvR9YApYDZlQdOxZkera?= =?iso-8859-1?Q?YewvE8xANkedkI9m7zp9Orf9YqMyyuEstqLgXQ/uIgwfbPobHeKChhysHK?= =?iso-8859-1?Q?F6WMK3PWjryuui5PJczz9L3Ngm5nA2MVchGUAvl0w17foxPViPiX56xF1K?= =?iso-8859-1?Q?FflSbrrcuZuFTyoNMrJwcNZ+ZD6ynlcCsk4hzmiIO9ehEk76IjpNpR1n5k?= =?iso-8859-1?Q?/og/y+n0lWu5QOmiMiTXzBsfsLQpH/uCWD7zPLCbbIAvBW6CPOLkNZKS7m?= =?iso-8859-1?Q?ONYBXaz7TC+Wsc3MXB0qOJTBMgp3Ged0I8n56+6/3b9D1lghRJOdMSoZJE?= =?iso-8859-1?Q?mDarC5LBWuk1t6J8+vaYRUFhnmZ7xdjpzuqAUfdY19/c0oaRTHrIPEy2SM?= =?iso-8859-1?Q?Tlu4LOH2AhnpQmaaLAz6xEfFp/vOqaVhRDcIJwQW4IKP4MI8mZsVJT+/Xz?= =?iso-8859-1?Q?2gSf1WCT65q+dqf/E7beD/jLR0PjfXb/RDCbdGMoxOhkV3+kris0fz8xuS?= =?iso-8859-1?Q?G+k673BNdj+tx91cAXs/ifC4k3GLQjQr6PwoprAC68A5NXX7T18JnWiOhj?= =?iso-8859-1?Q?uz149JnpCbonpFQGR+O7oR+HUTEzutuyGp7qecpuGBi5Fmd67utlP3FStK?= =?iso-8859-1?Q?QnD8z4iIrdRKdwPCMA5K8DOqZiag8bv5kM3zjvbVKORTjYEDDUwMqrM16d?= =?iso-8859-1?Q?jpZ/NhA5PHzx3DSUVcePZZakqa5NJc6hUr3MXC9wiv8mB7v7/1vzCvzmfv?= =?iso-8859-1?Q?hVvsb3bgyc62HQNaCcWmdwJfjsHAbarO6Ip4r3PcYdUawmYBgrDo+69L0O?= =?iso-8859-1?Q?3kMqPrNqtoW/a0bZsfljJExr9gAZwKNZJpb5DY2fGT9NRKXlG8EkHq/nIE?= =?iso-8859-1?Q?wlY1svKMKEXJ7/B5cpXAZq2lO3BWBIlIfP?= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: nic.at X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: AS2PR03MB8866.eurprd03.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: c0d58c62-401d-4030-0dd1-08dd660c0a76 X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Mar 2025 11:00:05.7349 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 6da68bb1-2470-49a3-8e7a-a343d51e9234 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: gm5nKPBa80xE15uJtomzQpHQjJTIo0NzC+mJnI/o72KUY2x1/gYhFWb9qFS57nL32DsyF5rDfrxg1lFq2Q43Bg== X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS2PR03MB9767 You could do the fsck for the domU block device manually. Just shut down th= e domU, and then in the dom0 run fsck on the logical volume used for the VM= . Regards Klaus --=20 Klaus Darilion, Head of Operations nic.at GmbH, Jakob-Haringer-Stra=DFe 8/V 5020 Salzburg, Austria > -----Original Message----- > From: Xen-users On Behalf Of > Mike > Sent: Tuesday, March 18, 2025 4:20 AM > To: xen-users@lists.xenproject.org > Subject: who performs a domU fsck? >=20 > My Linux domUs each have a block device, an LVM volume, mounted as /. > Where, > if anywhere, does the file system on those volumes have a fsck run on it > after a system crash, i.e., when the file system wasn't properly unmounte= d? >=20 > For the dom0, I see that happen during the boot process. Not seeing anyt= hing > logged in /var/log/xen/. >=20 > I've been having spontaneous system reboots, and suspect that those have > now > corrupted the file systems as well because nothing was running fsck on > reboot. I added the devices to the dom0 /etc/fstab now in hopes that tha= t > fixes it. >=20 > One would think that the domU would behave just like the dom0 in this > regard. > I'd like to see evidence. From xen-users-bounces@lists.xenproject.org Tue Mar 18 11:22:46 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2025 11:22:46 +0000 Received: from list by lists.xenproject.org with outflank-mailman.918966.1323547 (Exim 4.92) (envelope-from ) id 1tuV1c-0005cT-PB; Tue, 18 Mar 2025 11:22:24 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 918966.1323547; Tue, 18 Mar 2025 11:22:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuV1c-0005cM-MZ; Tue, 18 Mar 2025 11:22:24 +0000 Received: by outflank-mailman (input) for mailman id 918966; Tue, 18 Mar 2025 11:22:23 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuV1b-0005cG-4f for xen-users@lists.xenproject.org; Tue, 18 Mar 2025 11:22:23 +0000 Received: from mail.bitfolk.com (mail.bitfolk.com [2001:ba8:1f1:f019::25]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 41ca5b52-03eb-11f0-9aba-95dc52dad729; Tue, 18 Mar 2025 12:22:21 +0100 (CET) Received: from andy by mail.bitfolk.com with local (Exim 4.94.2) (envelope-from ) id 1tuV1X-00016I-EG for xen-users@lists.xenproject.org; Tue, 18 Mar 2025 11:22:19 +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: 41ca5b52-03eb-11f0-9aba-95dc52dad729 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strugglers.net; s=alpha; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:To:From:Date:Content-Transfer-Encoding:Sender:Reply-To:Cc :Content-ID:Content-Description:Resent-To; bh=z+2vbRirrRtz0r6eKKW9BCduDC1115cdWrkhWc+aNfE=; b=ZIreoRLqMnqIkeFa40X7GfyRsA qwLKQZCP/s+ep7st7QBixF6jqR3RcDqCNZp0oMrGdI57+VI+QOUfAFDNKRe7N1Fx5h4N/ZwtWISPw UFYcR+NrCgXPOKaNl9lSVnYE//BOPXEs4YRIbFvgxcvinmsmLw8NmTHioD23+Eh/cENcTp7WVCMOi BTjvZFBf7PmpVcpitaEiMuT4nYvGo4Oh8VBxAgQzvZIz+gzxOSfCx1wShSw8MTbSA6zgx1cro5xO1 1ZXSmQPNzEPt7mOeQ5gCsvk9Uy+r3cPj4ZZQ+WlLJHwnrIe/Rc5gBU0yOCOxBtf9ZY5BDzbrda8Z4 InSKXjkw==; Date: Tue, 18 Mar 2025 11:22:19 +0000 From: Andy Smith To: xen-users@lists.xenproject.org Subject: Re: who performs a domU fsck? Message-ID: 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 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, On Tue, Mar 18, 2025 at 11:00:05AM +0000, Klaus Darilion wrote: > You could do the fsck for the domU block device manually. Just shut > down the domU, and then in the dom0 run fsck on the logical volume > used for the VM. This is fraught with danger. For a start, domU and dom0 may not be running the same version of the filesystem which can in extreme cases lead to damage or just a refusal to run an old fsck on a version of the fs that it doesn't understand (incompatible feature flags). Next up, no Linux in-kernel filesystem guarantees to be secure against crafted data, i.e. there is no promise that a domU block device does not contain something that causes the hackers to be in your Gibson when you run fsck on it from the dom0 (or mount it, even read-only). Generally, all domU filesystem operations should be done in domU context, which is a major reason why we don't use pygrub any more. Obviously if you are the person running both the domU and the dom0 then you're probably not trying to compromise yourself, but the risk of bad interaction is too high, so it's still a last resort. Regarding OP's question, domU should see dom0 crash like an abrupt poweroff and do a fsck on boot like any other Linux does. Mine do. The domU logs should confirm this. Mine do. Thanks, Andy From xen-users-bounces@lists.xenproject.org Tue Mar 18 15:41:19 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2025 15:41:19 +0000 Received: from list by lists.xenproject.org with outflank-mailman.919385.1323874 (Exim 4.92) (envelope-from ) id 1tuZ3S-0006iH-AA; Tue, 18 Mar 2025 15:40:34 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 919385.1323874; Tue, 18 Mar 2025 15:40: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 1tuZ3S-0006iA-6y; Tue, 18 Mar 2025 15:40:34 +0000 Received: by outflank-mailman (input) for mailman id 919385; Tue, 18 Mar 2025 15:40:32 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuYvc-0001q5-ML for xen-users@lists.xenproject.org; Tue, 18 Mar 2025 15:32:28 +0000 Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [2a00:1450:4864:20::631]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 324c8fb1-040e-11f0-9abb-95dc52dad729; Tue, 18 Mar 2025 16:32:27 +0100 (CET) Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-ac2b10bea16so523029166b.0 for ; Tue, 18 Mar 2025 08:32:27 -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: 324c8fb1-040e-11f0-9abb-95dc52dad729 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leftsock.com; s=google; t=1742311946; x=1742916746; darn=lists.xenproject.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=W0v5YdGFDv6c426i+YPkD7kLREzGtUo/F0XSBCMVU4U=; b=qglOqxd7v94KKxgtWybPa9qKaZ8GgivMYvRLmXdXvaROzN7Xz4dzQ1FDAfrJy7z27u oN8Wr9dEo6tXU99bhWQHg8KM8bajLgcZIOhRnkfnD0iaNqXBkUoZncOJsstCq7S2ACzA sRUbiByFNmCi/z4QTNBi2Q1iIsTsVto6xYlzU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742311946; x=1742916746; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=W0v5YdGFDv6c426i+YPkD7kLREzGtUo/F0XSBCMVU4U=; b=aeJxWStM8KXsS5CO7kOhOhHgdNILOFPVas3DofTZqBhY/kpiMtJPuqrDQVIvKlBfU/ th9P5XVu+GOToUvmVqRVZFVhkvNc4Cp/pSuy/biqrs4RjQMM9/JcsR9B9d66AffCCBzs vOFLnn5CucuiRxVMLaz3YLZf5S0J3+3Dy80oGW3ULx8ByMKMow+t9mNoQcpHEdw6TY7o ED9iCbFdKifxybV8/KhINrOZt665z3HU3IqEwtkzBbYCczI3prJC0XQvlcL5fttP870N e7koAgAbNvwTBbnqFGGjBtZ9e/bmwDaNqzvREhpjOnYShQpwXKM54hWXI19LUKFrkIk6 pK1w== X-Gm-Message-State: AOJu0YzLoPr0v9Piz1kXrBE3igvFtDfWCnGbwKIciYBUGxfFClwTyg/5 SfGnjcvkx9ufSdbNAT4ILriM6fep9iVlK1I/sSc1Ar4lFz2DEvQFe4pvaq9jg9cDF2qpLKZImTk 37QqDS50BCFnXO8qjNXIdeF6/B5TMAet4BhZEyXxAvpkuN1ictg== X-Gm-Gg: ASbGnct4qMpb4O/krgaSpcfqeNC3HpM1FjPhyDKERDktwpz2qCjVPkApcdosCUPiQCn 02mEbsoZ5A6JwCmDUDJLmiZTscrG2waIXcKb2xDpAT4D2dsXhduARhntv2phc+FhPu64NgO0e85 IoUfaSV6eWFJsf/67/Kmysh+qwmNY= X-Google-Smtp-Source: AGHT+IErtLQZsqzUXFx4CxUeVdXg93mIi0LqJ9Ct2zl7R6SVpEPvxyZkoURwqrTjp1GjbQ82asRTO5qNU62t9JQsU74= X-Received: by 2002:a17:906:3409:b0:ac3:4229:91da with SMTP id a640c23a62f3a-ac342299440mr1420507666b.16.1742311946089; Tue, 18 Mar 2025 08:32:26 -0700 (PDT) MIME-Version: 1.0 From: Kevin Wang Date: Tue, 18 Mar 2025 08:32:14 -0700 X-Gm-Features: AQ5f1Jr_ozJNhVlRKhPiGTPNfP6wLEa0n6XSjl7MTW3hpEpKH9VnUycwenApvFw Message-ID: Subject: can't start hvm with network To: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="000000000000a2948d06309f9ca4" --000000000000a2948d06309f9ca4 Content-Type: text/plain; charset="UTF-8" > > From: Paul Leiber > > Am 17.03.2025 um 16:01 schrieb Kevin Wang: > > Unfortunately, I don't have the knowledge to analyze the output you > posted in detail. What comes to my mind, though: Did you set up a > network bridge on Dom0? Duh, I thought I could setup xen from memory, so indeed I didn't have xenbr0 However, installing it didn't help, same failure. > On another note: Why are you using HVM for setting up a linux DomU? Partially because this is the ~10th server I've set up, and I've been mostly using the same set of instructions. ...PV should the better option > Took me two hours to find instructions (not just HOWTOs that have unexplained dependencies like what /tmp/filename is) but this seems to work to at least get me into the installer. I'll have to reboot and set the system up after I get home from work: mkdir /mnt/iso mount -o ro /d/dmg/ubuntu-24.04-live-server-amd64.iso /mnt/iso mkdir /d/dmg/ubuntu-24.04-casper cp /mnt/iso/casper/vmlinuz /d/dmg/ubuntu-24.04-casper/vmlinuz cp /mnt/iso/casper/initrd /d/dmg/ubuntu-24.04-casper/initrd umount /mnt/iso cat >/etc/xen/auto/couch5 <<'__EOF__' kernel = "/d/dmg/ubuntu-24.04-casper/vmlinuz" ramdisk = "/d/dmg/ubuntu-24.04-casper/initrd" extra="modules=loop,squashfs console=hvc0" disk = [ 'format=raw, vdev=xvda, access=w, target=/dev/mapper/ubuntu--vg-couch--disk', 'format=raw, vdev=xvdb, access=w, target=/dev/mapper/ubuntu--vg-couch--home', 'format=raw, vdev=xvdc, access=r, devtype=cdrom, target=/d/dmg/ubuntu-24.04-live-server-amd64.iso' ] vif = ['bridge=xenbr0'] memory = 12288 name = "couch" vcpus = 2 maxvcpus = 2 __EOF__ xl create /etc/xen/auto/couch5 xl console couch --000000000000a2948d06309f9ca4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
From: Paul Leiber <= paul@onlineschub= la.de>

Am 17.03.2025 um 16:01 schrieb Kevin Wang:

Unfortunately, I don't have the knowledge to analyze the output you posted in detail. What comes to my mind, though: Did you set up a
network bridge on Dom0?

Duh, I thought I c= ould setup xen from memory, so indeed I didn't have xenbr0
However, installing it didn't help, same failure.
=C2=A0
On another = note: Why are you using HVM for setting up a linux DomU?
<= br>
Partially because this is the ~10th server I've set up, a= nd I've been mostly using the same set of instructions.

<= /div>
...PV should the bet= ter option

Took me two hours to find in= structions (not just HOWTOs that have unexplained dependencies like what /t= mp/filename is) but this seems to work to at least get me into the installe= r. I'll have to reboot and set the system up after I get home from work= :

mkdir /mnt/iso
mount -o ro /d/dmg/ubuntu-24.04-live-server-amd64.iso /mnt/iso
mkdir /d/dmg/ubuntu-24.04-casper
cp /mnt/iso/casper/vmlinuz /d/dmg/ubuntu-24.04-casper/vmlinuz
cp /mnt/iso/casper/initrd /d/dmg/ubuntu-24.04-casper/initrd
umount /mnt/iso

cat >/etc/xen/auto/couch5 <<'__EOF__'
kernel =3D "/d/dmg/ubuntu-24.04-casper/vmlinuz"
ramdisk =3D "/d/dmg/ubuntu-24.04-casper/initrd"
extra=3D"modules=3Dloop,squashfs console=3Dhvc0"
disk =3D [
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0'format=3Draw, vdev=3Dxv= da, access=3Dw, target=3D/dev/mapper/ubuntu--vg-couch--disk',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0'format=3Draw, vdev=3Dxv= db, access=3Dw, target=3D/dev/mapper/ubuntu--vg-couch--home',
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0'format=3Draw, vdev=3Dxv= dc, access=3Dr, devtype=3Dcdrom, target=3D/d/dmg/ubuntu-24.04-live-server-a= md64.iso'
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0]
vif =3D ['bridge=3Dxenbr0']
memory =3D 12288
name =3D "couch"
vcpus =3D 2
maxvcpus =3D 2
__EOF__
xl create /etc/xen/auto/couch5
xl console couch

--000000000000a2948d06309f9ca4-- From xen-users-bounces@lists.xenproject.org Tue Mar 18 17:03:05 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2025 17:03:05 +0000 Received: from list by lists.xenproject.org with outflank-mailman.919525.1323950 (Exim 4.92) (envelope-from ) id 1tuaKj-0005PF-Js; Tue, 18 Mar 2025 17:02:29 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 919525.1323950; Tue, 18 Mar 2025 17:02:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuaKj-0005P8-HC; Tue, 18 Mar 2025 17:02:29 +0000 Received: by outflank-mailman (input) for mailman id 919525; Tue, 18 Mar 2025 17:02:28 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tuaKi-0004kL-Je for xen-users@lists.xenproject.org; Tue, 18 Mar 2025 17:02:28 +0000 Received: from out.good-with-numbers.com (out.good-with-numbers.com [70.36.235.100]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id c40eba24-041a-11f0-9899-31a8f345e629; Tue, 18 Mar 2025 18:02:26 +0100 (CET) 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: c40eba24-041a-11f0-9899-31a8f345e629 Date: Tue, 18 Mar 2025 16:59:39 +0000 From: Mike To: Andy Smith Cc: xen-users@lists.xenproject.org Subject: Re: who performs a domU fsck? Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Andy Smith wrote: > domU should see dom0 crash like an abrupt > poweroff and do a fsck on boot like any other Linux does. Mine do. The > domU logs should confirm this. Got it. Thanks, Andy. So I checked `journalctl -g fsck` in the domU, which led me to that systemd-fsck-root.service isn't running fsck because /run/initramfs/fsck-root exists, because initramfs already did the fsck and its output is in /run/initramfs/fsck.log. From xen-users-bounces@lists.xenproject.org Thu Mar 20 14:32:26 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Mar 2025 14:32:26 +0000 Received: from list by lists.xenproject.org with outflank-mailman.922203.1326105 (Exim 4.92) (envelope-from ) id 1tvGvz-0003BZ-8I; Thu, 20 Mar 2025 14:31:47 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 922203.1326105; Thu, 20 Mar 2025 14:31:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tvGvz-0003BS-4x; Thu, 20 Mar 2025 14:31:47 +0000 Received: by outflank-mailman (input) for mailman id 922203; Thu, 20 Mar 2025 14:31:45 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tvGvx-0003BI-BZ for xen-users@lists.xenproject.org; Thu, 20 Mar 2025 14:31:45 +0000 Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [2a00:1450:4864:20::534]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 0af75001-0598-11f0-9ea0-5ba50f476ded; Thu, 20 Mar 2025 15:31:43 +0100 (CET) Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-5e4d50ed90aso1261844a12.0 for ; Thu, 20 Mar 2025 07:31:42 -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: 0af75001-0598-11f0-9ea0-5ba50f476ded DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leftsock.com; s=google; t=1742481102; x=1743085902; darn=lists.xenproject.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=388tqJA2sVGSxx0UEC5TW93wDT1rmV/O5+acwB0z9JI=; b=ZpIbh0La14PdQQhh1oK4l92XjwpQCZqiC8PmMauQZcSPYteZTkkz2PFZCXaNe0HT+B X++XWyBrM4hVOognKWryAI1TqyWfuX1nziCnJZkmNc2mvLYv02nSgTi650Jl1F0zDDtO uQKz3Kp3CLCdfnxTl+WqYnA+ED50csp2BvV1w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742481102; x=1743085902; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=388tqJA2sVGSxx0UEC5TW93wDT1rmV/O5+acwB0z9JI=; b=DrQ5xhpEjGHLf4EDwaXN7efgYX/uOCME9LRacpdOOYsj6ozN7yD5ldODA8xQyDg6nT B8KBYkhmYiKyIEtJxn9brSprhI+Db0wafmGTvxgACKc33Fo8xyhI39F47nabwSH+/g78 AkXIKmoD0a7YfuK2S0Ack6Hd+pDaLyr09X4obzoGkg6Ah6KHXvb33TkxpYLLmfFIeUB+ CsVW3aGBAwCJAPtZvHGYToSgsnyxka+OOFbOMR+O9hcqj0OTrYbgkRny2rkgNiEt5BIc /A8gCOfWWdfuGS6o8VLYaTs64vfvci2LYUqmsoyCeHYZ9DXsQ9xfyp0YYKbtKod1onBX W1WQ== X-Gm-Message-State: AOJu0YyHwc3pqZPegbynr88Iq49wYKnz21saJ9HotJ4TAnlgL45dguut oNHGrLKprhV/aXMuI22UrxF4D2Sue7D9eyRdElDTaVXFFLy2XcAdXiQTbAjKd23DDrkkVbL0pxx sTnkf4BsxdyVCYu4B/a2Qo19Wqe5aqfr2TeV724Fz8L6T7sKGgA== X-Gm-Gg: ASbGncttN3K5+4gKuyPnH4zeS6TcmdgS9+gC5WLYV4PqnZmCj+6SJ7a2feqxlRE9kyk c3xwl1XogahCBLWgscp5r/X4FcIjjE1AUcc+2OEqtrrjhFRUdqExHFflCEaF1P/kW8MAlvCEocu 09uDm34B4+zzhFEDxa3o7JZjd60bQ4c6EYZhtJ2Q== X-Google-Smtp-Source: AGHT+IFLYjFNyZaNHQwNCDAdwTW+ia6XQ6kCXDxjKSYxPMQZd0iojG72p7dmuH3k/TzFrzm4lqPQl5P5sGEPL0hs/Uo= X-Received: by 2002:a17:907:97d5:b0:abf:6f87:c720 with SMTP id a640c23a62f3a-ac3ce04d7c7mr432821966b.29.1742481101509; Thu, 20 Mar 2025 07:31:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Wang Date: Thu, 20 Mar 2025 07:31:29 -0700 X-Gm-Features: AQ5f1JrMOXPTuMx_ieDIVg-2wTUvPpdLMHEk9bKyYGxxDJ9w_HiR5HGCqUvgrrU Message-ID: Subject: can't start hvm with network To: xen-users@lists.xenproject.org Content-Type: multipart/alternative; boundary="0000000000001578db0630c6ffca" --0000000000001578db0630c6ffca Content-Type: text/plain; charset="UTF-8" > > From: Kevin Wang > >From a previous thread (which I haven't had a chance to try on that other > 256GB ram machine), It was suggested that "big ram" vms may have trouble > starting or start slowly, so I added: > echo 'GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=min:4096M,max:4096 > M"' >>/etc/default/grub > grub-install /dev/sda > dur, update-grub. and now dom0 shows only 4G ram. however, it still takes ~75 seconds at boot before ram is allocated to this "small" 12GB vm, and is then allowed to start running (note 'couch' cpu time still says 0.0) # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 4096 4 r----- 74.9 couch 1 12288 2 --p--- 0.0 (The machine has 32GB physical RAM, so the kernel argument does work.) - Kevin --0000000000001578db0630c6ffca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: base64 PGRpdiBkaXI9Imx0ciI+PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUgZ21haWxfcXVvdGVfY29udGFp bmVyIj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MHB4IDBw eCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYigyMDQsMjA0LDIwNCk7cGFkZGlu Zy1sZWZ0OjFleCI+RnJvbTogS2V2aW4gV2FuZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmtqd0BsZWZ0 c29jay5jb20iIHRhcmdldD0iX2JsYW5rIj5randAbGVmdHNvY2suY29tPC9hPiZndDs8YnI+DQom Z3Q7RnJvbSBhIHByZXZpb3VzIHRocmVhZCAod2hpY2ggSSBoYXZlbiYjMzk7dCBoYWQgYSBjaGFu Y2UgdG8gdHJ5IG9uIHRoYXQgb3RoZXI8YnI+DQoyNTZHQiByYW0gbWFjaGluZSksIEl0IHdhcyBz dWdnZXN0ZWQgdGhhdCAmcXVvdDtiaWcgcmFtJnF1b3Q7IHZtcyBtYXkgaGF2ZSB0cm91YmxlPGJy Pg0Kc3RhcnRpbmcgb3Igc3RhcnQgc2xvd2x5LCBzbyBJIGFkZGVkOjxicj4NCmVjaG8gJiMzOTtH UlVCX0NNRExJTkVfWEVOX0RFRkFVTFQ9JnF1b3Q7ZG9tMF9tZW09bWluOjQwOTZNLG1heDo0MDk2 PGJyPg0KTSZxdW90OyYjMzk7ICZndDsmZ3Q7L2V0Yy9kZWZhdWx0L2dydWI8YnI+DQpncnViLWlu c3RhbGwgL2Rldi9zZGE8YnI+PC9ibG9ja3F1b3RlPjxkaXY+PGJyPjwvZGl2PjxkaXY+ZHVyLCB1 cGRhdGUtZ3J1Yi4gYW5kIG5vdyBkb20wIHNob3dzIG9ubHkgNEcgcmFtLjwvZGl2PjxkaXY+PGJy PjwvZGl2PjxkaXY+aG93ZXZlciwgaXQgc3RpbGwgdGFrZXMgfjc1IHNlY29uZHMgYXQgYm9vdCBi ZWZvcmUgcmFtIGlzIGFsbG9jYXRlZCB0byB0aGlzICZxdW90O3NtYWxsJnF1b3Q7IDEyR0Igdm0s IGFuZCBpcyB0aGVuIGFsbG93ZWQgdG8gc3RhcnQgcnVubmluZyAobm90ZSAmIzM5O2NvdWNoJiMz OTsgY3B1IHRpbWUgc3RpbGwgc2F5cyAwLjApPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48c3Bh biBzdHlsZT0iZm9udC1mYW1pbHk6bW9ub3NwYWNlIj48Zm9udCBzaXplPSIxIj48c3BhbiBzdHls ZT0iY29sb3I6cmdiKDAsMCwwKSI+IyB4bCBsaXN0DQo8L3NwYW4+PGJyPk5hbWUgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoMKgwqDCoMKgSUQgwqDCoE1lbSBWQ1BVcyDCoMKgwqDCoMKgU3RhdGUgwqDCoFRpbWUocykN Cjxicj5Eb21haW4tMCDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAwIMKgNDA5NiDCoMKgwqDCoDQgwqDCoMKgwqBy LS0tLS0gwqDCoMKgwqDCoDc0LjkNCjxicj5jb3VjaCDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAxIDEy Mjg4IMKgwqDCoMKgMiDCoMKgwqDCoC0tcC0tLSDCoMKgwqDCoMKgwqAwLjA8YnI+PC9mb250Pg0K PGJyPjwvc3Bhbj48L2Rpdj48ZGl2PihUaGUgbWFjaGluZSBoYXMgMzJHQiBwaHlzaWNhbCBSQU0s IHNvIHRoZSBrZXJuZWwgYXJndW1lbnQgZG9lcyB3b3JrLik8L2Rpdj48ZGl2Pjxicj48L2Rpdj48 ZGl2PsKgIMKgLSBLZXZpbjwvZGl2PjwvZGl2PjwvZGl2Pg0K --0000000000001578db0630c6ffca-- From xen-users-bounces@lists.xenproject.org Fri Mar 21 05:11:11 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Mar 2025 05:11:11 +0000 Received: from list by lists.xenproject.org with outflank-mailman.923292.1326857 (Exim 4.92) (envelope-from ) id 1tvUdx-0003KT-Go; Fri, 21 Mar 2025 05:10:05 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 923292.1326857; Fri, 21 Mar 2025 05:10: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 1tvUdx-0003Hu-82; Fri, 21 Mar 2025 05:10:05 +0000 Received: by outflank-mailman (input) for mailman id 923292; Fri, 21 Mar 2025 05:10:04 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tvUdw-00032f-4K for xen-users@lists.xenproject.org; Fri, 21 Mar 2025 05:10:04 +0000 Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id bd085b07-0612-11f0-9ea1-5ba50f476ded; Fri, 21 Mar 2025 06:10:01 +0100 (CET) Received: from m5p.com (mailhost.m5p.com [IPv6:2001:470:8ac4:0:0:0:0:f7]) by mailhost.m5p.com (8.18.1/8.17.1) with ESMTPS id 52L59qFB012360 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 21 Mar 2025 01:09:58 -0400 (EDT) (envelope-from ehem@m5p.com) Received: (from ehem@localhost) by m5p.com (8.18.1/8.15.2/Submit) id 52L59qit012359; Thu, 20 Mar 2025 22:09:52 -0700 (PDT) (envelope-from ehem) 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: bd085b07-0612-11f0-9ea1-5ba50f476ded Date: Thu, 20 Mar 2025 22:09:52 -0700 From: Elliott Mitchell To: Paul Leiber Cc: xen-users@lists.xenproject.org Subject: Re: can't start hvm with network Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=0.4 required=10.0 tests=KHOP_HELO_FCRDNS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on mattapan.m5p.com On Mon, Mar 17, 2025 at 04:57:03PM +0100, Paul Leiber wrote: > Hi Kevin, > > Am 17.03.2025 um 16:01 schrieb Kevin Wang: > > On another note: Why are you using HVM for setting up a linux DomU? I never > tested Ubuntu myself, but for Debian (and most likely Debian-based) > distributions, PV should the better option. Again, [2] shows how to install > a Debian PV DomU, and the procedure is still working (of course, wheezy is a > bit outdated and needs to be replaced, e. g. with bookworm). The section > even mentions Ubuntu distributions, so it's probably worth to dig deeper > there. If you have even fairly old hardware, rather superior to PV mode is PVH mode. After a few generations of AMD64 hardware all the processors started adding an extra page table level. PVH mode lets the kernel use PV drivers, but then use normal page tables on top. Needs a bit of adjustment from PV mode, but yields rather better performance. I've found HVM mode somewhat handier for initial installation, but once installed PVH mode is better (except for the issue of booting non-Linux). -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445 From xen-users-bounces@lists.xenproject.org Fri Mar 21 20:00:40 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Mar 2025 20:00:40 +0000 Received: from list by lists.xenproject.org with outflank-mailman.924422.1327621 (Exim 4.92) (envelope-from ) id 1tviWz-00009R-92; Fri, 21 Mar 2025 19:59:49 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 924422.1327621; Fri, 21 Mar 2025 19:59: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 1tviWz-00009K-54; Fri, 21 Mar 2025 19:59:49 +0000 Received: by outflank-mailman (input) for mailman id 924422; Fri, 21 Mar 2025 19:59:48 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tviWy-00009E-2a for xen-users@lists.xenproject.org; Fri, 21 Mar 2025 19:59:48 +0000 Received: from mail.euronap.de (mail.euronap.de [84.38.78.210]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 092e1385-068f-11f0-9ffa-bf95429c2676; Fri, 21 Mar 2025 20:59:45 +0100 (CET) Received: from home.tangomaris.de (ip-130-180-058-238.um40.pools.vodafone-ip.de [130.180.58.238]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by mail.euronap.de (Postfix) with ESMTPSA id 4ZKCw10rGfz6tcg for ; Fri, 21 Mar 2025 20:59:45 +0100 (CET) Received: from [192.168.222.26] (ip-109-091-129-157.um37.pools.vodafone-ip.de [109.91.129.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gw.tangomaris.de (Postfix) with ESMTPSA id 4ZKCw05Bt3z3wrR for ; Fri, 21 Mar 2025 20:59:44 +0100 (CET) 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: 092e1385-068f-11f0-9ffa-bf95429c2676 Message-ID: Date: Fri, 21 Mar 2025 20:59:44 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Shen Long Subject: VIF network definition does not work with backend=domnet To: xen-users@lists.xenproject.org Content-Language: de-CH Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello, I use XEN on a gentoo home-lab/home-network server. I installed the Dom0 with gentoo with a dedicated network card. I gave a spare network card on the machine to a dedicated network driver domain which also runs gentoo. Now i discovered an issue with the VIF spec for new domUs. Following problem. If i start a domu with a vif spec to connect to a backend domu it does fail with an error. If i omit the vif spec, create the domu and immediately attach a network card with xl network-attach backend=netbackend it works. Here's the netbackend.cfg, if i may forgot something: > name = "netbackend" > builder = "hvm" > vcpus = 4 > memory = 4096 > pci = [ '03:00.0' ] > disk = [ 'phy:/dev/mapper/xenhost-netbackend,xvda,w' ] > netif="yes" > usbdevice = [ "tablet" ] > serial = "pty" > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" My backend have several bridge-networks configured with associated network-vlans on my physical interface. - home - dmz - foo - infra Here the test.cfg domu which "works": > name = "test" > builder = "hvm" > vcpus = 1 > memory = 4096 > #vif = [ 'backend=netbackend,bridge=dmz' ] > disk = [ 'file:/isos/systemrescue-11.03-amd64.iso,hda:cdrom,r' ] > usbdevice = [ "tablet" ] > serial = "pty" > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" It does not have a proper disk yet, because testing. The Problem is, if i remove the hash from the vif spec, i get this error on `xl create test.cfg`: > # xl create /etc/xen/domuconfig/test.cnf > Parsing config from /etc/xen/domuconfig/test.cnf > libxl: error: libxl_dm.c:3157:device_model_spawn_outcome: Domain 89:domain 89 device model: spawn failed (rc=-3) > libxl: error: libxl_dm.c:3377:device_model_postconfig_done: Domain 89:Post DM startup configs failed, rc=-3 > libxl: error: libxl_create.c:1937:domcreate_devmodel_started: Domain 89:device model did not start: -3 > libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model already exited > libxl: error: libxl_xshelp.c:206:libxl__xs_read_mandatory: xenstore read failed: `/libxl/89/type': No such file or directory > libxl: warning: libxl_dom.c:49:libxl__domain_type: unable to get domain type for domid=89, assuming HVM > libxl: error: libxl_domain.c:1616:domain_destroy_domid_cb: Domain 89:xc_domain_destroy failed: No such process > libxl: error: libxl_domain.c:1133:domain_destroy_callback: Domain 89:Unable to destroy guest > libxl: error: libxl_domain.c:1060:domain_destroy_cb: Domain 89:Destruction of domain failed As mentioned, i can comment out the vif spec and attach a network card with `xl network-attach test bridge=dmz backend=netbackend` which works perfectly fine. But i according to the man-page it is possible to define the networks with a netbackend in the domu cfg files and autostart it with that. If you need more information, just ask me. Do i have an error in my setup or overlooked something? Do we have a proper bug in this scenario? Or is it not implemented in that way, a missing feature or do i overlook something? Best regards Shen Long From xen-users-bounces@lists.xenproject.org Fri Mar 21 22:08:27 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Mar 2025 22:08:27 +0000 Received: from list by lists.xenproject.org with outflank-mailman.924499.1327657 (Exim 4.92) (envelope-from ) id 1tvkWV-0002Ha-DA; Fri, 21 Mar 2025 22:07:27 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 924499.1327657; Fri, 21 Mar 2025 22:07: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 1tvkWV-0002HT-A0; Fri, 21 Mar 2025 22:07:27 +0000 Received: by outflank-mailman (input) for mailman id 924499; Fri, 21 Mar 2025 22:07:25 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tvkWT-0002HN-Mw for xen-users@lists.xenproject.org; Fri, 21 Mar 2025 22:07:25 +0000 Received: from mail.euronap.de (mail.euronap.de [84.38.78.210]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id de372c2c-06a0-11f0-9ea1-5ba50f476ded; Fri, 21 Mar 2025 23:07:24 +0100 (CET) Received: from home.tangomaris.de (ip-130-180-058-238.um40.pools.vodafone-ip.de [130.180.58.238]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.euronap.de (Postfix) with ESMTPSA id 4ZKGlH2r81z6tcf for ; Fri, 21 Mar 2025 23:07:23 +0100 (CET) Received: from [192.168.222.26] (ip-109-091-129-157.um37.pools.vodafone-ip.de [109.91.129.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gw.tangomaris.de (Postfix) with ESMTPSA id 4ZKGlG3VS3z3wrR for ; Fri, 21 Mar 2025 23:07:22 +0100 (CET) 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: de372c2c-06a0-11f0-9ea1-5ba50f476ded Message-ID: <42fc1cce-85ce-4c94-9b94-ca66a975f328@sl.nospam.tangomaris.de> Date: Fri, 21 Mar 2025 23:07:21 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Shen Long Subject: Re: VIF network definition does not work with backend=domnet To: xen-users@lists.xenproject.org References: Content-Language: de-CH In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello again, i promise i'm working on it since yesterday to get anything useful done... Now i tried it with a new vif and set vif.default.backend in xl.conf... Now it does work... But i dont know if it does, because i did once another try... or by putting type=vif in there... What i tried: 1. set vif.default.backend = netbackend and vif = [ 'backend=netbackend,bridge=dmz' ] 2. vif = [ 'type=vif,script=vif-nat' ] 3. vif = [ 'type=vif,bridge=dmz' ] It does work now. Like i said. I dont know if it does now. because of the vif-nat middle step. Or because i did start the network with vif.default.backend and omit the backend setting in the domu.cfg However, i'll try it, with a reboot later that day (the xenhost also hosts my opnsense firewall with all networks with a separate network card from the others). So wish me luck for later that day. Best regards Shen Long Am 21.03.25 um 20:59 schrieb Shen Long: > Hello, > > I use XEN on a gentoo home-lab/home-network server. I installed the Dom0 > with gentoo with a dedicated network card. I gave a spare network card > on the machine to a dedicated network driver domain which also runs gentoo. > > Now i discovered an issue with the VIF spec for new domUs. > > Following problem. If i start a domu with a vif spec to connect to a > backend domu it does fail with an error. > If i omit the vif spec, create the domu and immediately attach a network > card with xl network-attach backend=netbackend it works. > > Here's the netbackend.cfg, if i may forgot something: > >> name = "netbackend" >> builder = "hvm" >> vcpus = 4 >> memory = 4096 >> pci = [ '03:00.0' ] >> disk = [ 'phy:/dev/mapper/xenhost-netbackend,xvda,w' ] >> netif="yes" >> usbdevice = [ "tablet" ] >> serial = "pty" >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" > > My backend have several bridge-networks configured with associated > network-vlans on my physical interface. > - home > - dmz > - foo > - infra > > Here the test.cfg domu which "works": > >> name = "test" >> builder = "hvm" >> vcpus = 1 >> memory = 4096 >> #vif = [ 'backend=netbackend,bridge=dmz' ] >> disk = [ 'file:/isos/systemrescue-11.03-amd64.iso,hda:cdrom,r' ] >> usbdevice = [ "tablet" ] >> serial = "pty" >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" > > It does not have a proper disk yet, because testing. > The Problem is, if i remove the hash from the vif spec, i get this error > on `xl create test.cfg`: > >> # xl create /etc/xen/domuconfig/test.cnf >> Parsing config from /etc/xen/domuconfig/test.cnf >> libxl: error: libxl_dm.c:3157:device_model_spawn_outcome: Domain > 89:domain 89 device model: spawn failed (rc=-3) >> libxl: error: libxl_dm.c:3377:device_model_postconfig_done: Domain > 89:Post DM startup configs failed, rc=-3 >> libxl: error: libxl_create.c:1937:domcreate_devmodel_started: Domain > 89:device model did not start: -3 >> libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model > already exited >> libxl: error: libxl_xshelp.c:206:libxl__xs_read_mandatory: xenstore > read failed: `/libxl/89/type': No such file or directory >> libxl: warning: libxl_dom.c:49:libxl__domain_type: unable to get > domain type for domid=89, assuming HVM >> libxl: error: libxl_domain.c:1616:domain_destroy_domid_cb: Domain > 89:xc_domain_destroy failed: No such process >> libxl: error: libxl_domain.c:1133:domain_destroy_callback: Domain > 89:Unable to destroy guest >> libxl: error: libxl_domain.c:1060:domain_destroy_cb: Domain > 89:Destruction of domain failed > > As mentioned, i can comment out the vif spec and attach a network card > with `xl network-attach test bridge=dmz backend=netbackend` which works > perfectly fine. But i according to the man-page it is possible to define > the networks with a netbackend in the domu cfg files and autostart it > with that. > > If you need more information, just ask me. > > Do i have an error in my setup or overlooked something? > Do we have a proper bug in this scenario? > Or is it not implemented in that way, a missing feature or do i overlook > something? > > Best regards > Shen Long > From xen-users-bounces@lists.xenproject.org Sun Mar 23 09:23:29 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Mar 2025 09:23:29 +0000 Received: from list by lists.xenproject.org with outflank-mailman.924910.1327859 (Exim 4.92) (envelope-from ) id 1twHXW-0006x4-78; Sun, 23 Mar 2025 09:22:42 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 924910.1327859; Sun, 23 Mar 2025 09:22: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 1twHXW-0006wx-3U; Sun, 23 Mar 2025 09:22:42 +0000 Received: by outflank-mailman (input) for mailman id 924910; Sun, 23 Mar 2025 09:22:40 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1twHXU-0006wr-C8 for xen-users@lists.xenproject.org; Sun, 23 Mar 2025 09:22:40 +0000 Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.160]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 5b6b248c-07c8-11f0-9ffa-bf95429c2676; Sun, 23 Mar 2025 10:22:37 +0100 (CET) Received: from mail.onlineschubla.de by smtp.strato.de (RZmta 51.3.0 DYNA|AUTH) with ESMTPSA id e1a88e12N9MZx06 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Sun, 23 Mar 2025 10:22:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.onlineschubla.de (Postfix) with ESMTP id D521220FFC for ; Sun, 23 Mar 2025 10:22:34 +0100 (CET) Received: from mail.onlineschubla.de ([127.0.0.1]) by localhost (mail.onlineschubla.de [127.0.0.1]) (amavis, port 10024) with ESMTP id cNsZI0OtubxI for ; Sun, 23 Mar 2025 10:22:34 +0100 (CET) Received: from [10.0.0.120] (unknown [10.0.0.120]) by mail.onlineschubla.de (Postfix) with ESMTPA id 1C14B200EA for ; Sun, 23 Mar 2025 10:22:33 +0100 (CET) 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: 5b6b248c-07c8-11f0-9ffa-bf95429c2676 ARC-Seal: i=1; a=rsa-sha256; t=1742721755; cv=none; d=strato.com; s=strato-dkim-0002; b=QHl48pwWzhehUta3IbXn6vQjHj4U5wD38aW/sKZbwiyN6w6c64Cas8ou89o4g9uE9w Q+kiEQli/P+hEynN5rChEROlrab55xhaklgY0WgfdkO6QgtJ2ACGvYQgdNzIcu0QsIvr ZGu5ZDVqwrMSFsCIcGfefs6k4dA6fipE43oOnKvrYyGk7d+8JSEYQA+0dIlpltIjoJvM 5X3uulmPrJB+hTLt1/+QW6fvpph80o3o6k7CG6/qgkAFUIokOgIX6rxjDo1LDnmkMZPi 2ijxGPRr8T707yhD7JYuAzo49ZC+qeoEcexn/bmUwiLt/+u33s20OULM4H6D9YbcY5IB mbSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1742721755; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=RclkR3nKZnNg4jm+xRAGSPclZWa/3FPypyAaCEQJbvo=; b=cNhbqdwcROd3FE4lRX5lgH1aH9T5hzfgThwo2tNYG8mE14ihSp5ZYYgvUnWaim+rFp ovWfajSpz4yy6P+NKW4z6KfhdFBO1vUKYbu67u5XOfzcn+BxgQViBJ8cmdlLxrFyiy+H rR4Afx8dWQ7MiGw2frSLO5PvTh1aiGZMvxay+5vVsXPQpa3PjjTyEeDBn8ee0fd4WBc/ teAVHcodb/8keLrkZTRLFZYpU4QxKE5VF+0W5JpBgLywDVy8900oWy1lXHaXnOk6xcjV BE1dO98ixogwWG+hkMgmg85dfsR9bmbq0+vDm9H4d/O8x3yQ83WWs6d6qw9rkXRDBgMR dX9Q== ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none X-RZG-CLASS-ID: mo00 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1742721755; s=strato-dkim-0002; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=RclkR3nKZnNg4jm+xRAGSPclZWa/3FPypyAaCEQJbvo=; b=ibV+4IZ68uWipz7mjInXxzqYtbS5MvnOyYy3Lz5lAbVhVDWvnNdtGFevh4LYwU69pb Vx9C+lBOHqGuNdrELtwalSVT+nuvSXww2J1ugCVPJVRjZdetlKTQwLu4Wqg5f36jeKPR Ac7luWQ9iUx5ri7QtuoHK372AEUAbKkO8Hhs6IHrHKl5DtzCCE8zMAnkgGBQ3QwEz+/F A3HdhiHz7S2ZRUWaMeZWgIFjlCgf5nGB7BvR4V5MUo1c3zBokgOwtvck2CqUiwPv/Ctz SP2v+l2SvMkrbbgE9t+B9DkvIfXZe9t+TxvWPd04RemCGuPmX7ZWYJN/4/wB7hp7a6bQ 0GEw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1742721755; s=strato-dkim-0003; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=RclkR3nKZnNg4jm+xRAGSPclZWa/3FPypyAaCEQJbvo=; b=18i8FGdCtNy3BTvJV+R/kaldn5gFwOovonP2rkGccPZJdule4kfvbpWfFMQGfcu/L7 JUvLJi+/gIZd7YqcVJCw== X-RZG-AUTH: ":PG0ReWCndfO3rCSML4AvNaDxJ7WJyilEI/NMX3IPpS4dskMFCImJEP1iWJS8C4noE/Q=" X-Virus-Scanned: Debian amavis at onlineschubla.de Message-ID: <94a84cea-c301-45a2-aeb3-8e1afb885a47@onlineschubla.de> Date: Sun, 23 Mar 2025 10:22:27 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: can't start hvm with network To: xen-users@lists.xenproject.org References: From: Paul Leiber In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 21.03.2025 um 06:09 schrieb Elliott Mitchell: > On Mon, Mar 17, 2025 at 04:57:03PM +0100, Paul Leiber wrote: >> Hi Kevin, >> >> Am 17.03.2025 um 16:01 schrieb Kevin Wang: >> >> On another note: Why are you using HVM for setting up a linux DomU? I never >> tested Ubuntu myself, but for Debian (and most likely Debian-based) >> distributions, PV should the better option. Again, [2] shows how to install >> a Debian PV DomU, and the procedure is still working (of course, wheezy is a >> bit outdated and needs to be replaced, e. g. with bookworm). The section >> even mentions Ubuntu distributions, so it's probably worth to dig deeper >> there. > If you have even fairly old hardware, rather superior to PV mode is PVH > mode. After a few generations of AMD64 hardware all the processors > started adding an extra page table level. PVH mode lets the kernel use > PV drivers, but then use normal page tables on top. Needs a bit of > adjustment from PV mode, but yields rather better performance. > > I've found HVM mode somewhat handier for initial installation, but once > installed PVH mode is better (except for the issue of booting non-Linux). > I actually meant PVH, not PV. Thanks for the correction! Paul From xen-users-bounces@lists.xenproject.org Sun Mar 23 11:48:43 2025 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Mar 2025 11:48:43 +0000 Received: from list by lists.xenproject.org with outflank-mailman.924463.1327885 (Exim 4.92) (envelope-from ) id 1twJoB-0001ek-Hj; Sun, 23 Mar 2025 11:48:03 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 924463.1327885; Sun, 23 Mar 2025 11:48:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1twJoB-0001ed-F0; Sun, 23 Mar 2025 11:48:03 +0000 Received: by outflank-mailman (input) for mailman id 924463; Fri, 21 Mar 2025 20:15:02 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tvili-0004xK-Ih for xen-users@lists.xenproject.org; Fri, 21 Mar 2025 20:15:02 +0000 Received: from mail.euronap.de (mail.euronap.de [84.38.78.210]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 2ab2ab2b-0691-11f0-9ea1-5ba50f476ded; Fri, 21 Mar 2025 21:15:01 +0100 (CET) Received: from home.tangomaris.de (ip-130-180-058-238.um40.pools.vodafone-ip.de [130.180.58.238]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.euronap.de (Postfix) with ESMTPSA id 4ZKDFb4SYxz6tVs for ; Fri, 21 Mar 2025 21:14:59 +0100 (CET) Received: from [192.168.222.26] (ip-109-091-129-157.um37.pools.vodafone-ip.de [109.91.129.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gw.tangomaris.de (Postfix) with ESMTPSA id 4ZKDFZ5FLqz3wrR for ; Fri, 21 Mar 2025 21:14:58 +0100 (CET) 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: 2ab2ab2b-0691-11f0-9ea1-5ba50f476ded Message-ID: <1d989435-4aac-4307-bb21-b37015f02758@tangomaris.de> Date: Fri, 21 Mar 2025 21:14:57 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: VIF network definition does not work with backend=domnet To: xen-users@lists.xenproject.org References: Content-Language: de-CH From: Norbert Ronecker In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello again, i promise i'm working on it since yesterday to get anything useful done... Now i tried it with a new vif and set vif.default.backend in xl.conf... Now it does work... But i dont know if it does, because i did once another try... or by putting type=vif in there... What i tried: 1. set vif.default.backend = netbackend and vif = [ 'backend=netbackend,bridge=dmz' ] 2. vif = [ 'type=vif,script=vif-nat' ] 3. vif = [ 'type=vif,bridge=dmz' ] It does work now. Like i said. I dont know if it does now. because of the vif-nat middle step. Or because i did start the network with vif.default.backend and omit the backend setting in the domu.cfg However, i'll try it, with a reboot later that day (the xenhost also hosts my opnsense firewall with all networks with a separate network card from the others). So wish me luck for later that day. Best regards Shen Long Am 21.03.25 um 20:59 schrieb Shen Long: > Hello, > > I use XEN on a gentoo home-lab/home-network server. I installed the Dom0 > with gentoo with a dedicated network card. I gave a spare network card > on the machine to a dedicated network driver domain which also runs gentoo. > > Now i discovered an issue with the VIF spec for new domUs. > > Following problem. If i start a domu with a vif spec to connect to a > backend domu it does fail with an error. > If i omit the vif spec, create the domu and immediately attach a network > card with xl network-attach backend=netbackend it works. > > Here's the netbackend.cfg, if i may forgot something: > >> name = "netbackend" >> builder = "hvm" >> vcpus = 4 >> memory = 4096 >> pci = [ '03:00.0' ] >> disk = [ 'phy:/dev/mapper/xenhost-netbackend,xvda,w' ] >> netif="yes" >> usbdevice = [ "tablet" ] >> serial = "pty" >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" > > My backend have several bridge-networks configured with associated > network-vlans on my physical interface. > - home > - dmz > - foo > - infra > > Here the test.cfg domu which "works": > >> name = "test" >> builder = "hvm" >> vcpus = 1 >> memory = 4096 >> #vif = [ 'backend=netbackend,bridge=dmz' ] >> disk = [ 'file:/isos/systemrescue-11.03-amd64.iso,hda:cdrom,r' ] >> usbdevice = [ "tablet" ] >> serial = "pty" >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" > > It does not have a proper disk yet, because testing. > The Problem is, if i remove the hash from the vif spec, i get this error > on `xl create test.cfg`: > >> # xl create /etc/xen/domuconfig/test.cnf >> Parsing config from /etc/xen/domuconfig/test.cnf >> libxl: error: libxl_dm.c:3157:device_model_spawn_outcome: Domain > 89:domain 89 device model: spawn failed (rc=-3) >> libxl: error: libxl_dm.c:3377:device_model_postconfig_done: Domain > 89:Post DM startup configs failed, rc=-3 >> libxl: error: libxl_create.c:1937:domcreate_devmodel_started: Domain > 89:device model did not start: -3 >> libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model > already exited >> libxl: error: libxl_xshelp.c:206:libxl__xs_read_mandatory: xenstore > read failed: `/libxl/89/type': No such file or directory >> libxl: warning: libxl_dom.c:49:libxl__domain_type: unable to get > domain type for domid=89, assuming HVM >> libxl: error: libxl_domain.c:1616:domain_destroy_domid_cb: Domain > 89:xc_domain_destroy failed: No such process >> libxl: error: libxl_domain.c:1133:domain_destroy_callback: Domain > 89:Unable to destroy guest >> libxl: error: libxl_domain.c:1060:domain_destroy_cb: Domain > 89:Destruction of domain failed > > As mentioned, i can comment out the vif spec and attach a network card > with `xl network-attach test bridge=dmz backend=netbackend` which works > perfectly fine. But i according to the man-page it is possible to define > the networks with a netbackend in the domu cfg files and autostart it > with that. > > If you need more information, just ask me. > > Do i have an error in my setup or overlooked something? > Do we have a proper bug in this scenario? > Or is it not implemented in that way, a missing feature or do i overlook > something? > > Best regards > Shen Long >