From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with UTF8SMTPS id 6A9F1601B0 for ; Wed, 7 Oct 2020 08:20:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with UTF8SMTP id 5D73F2B59B for ; Wed, 7 Oct 2020 08:20:56 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with UTF8SMTPS id 11AE02B58D for ; Wed, 7 Oct 2020 08:20:55 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with UTF8SMTP id D283645BC9 for ; Wed, 7 Oct 2020 08:20:54 +0200 (CEST) To: pve-user@lists.proxmox.com References: <1550328837.203739.1601999955107.JavaMail.zimbra@fws.fr> <497035042.203793.1602001437004.JavaMail.zimbra@fws.fr> From: Dominik Csapak Message-ID: Date: Wed, 7 Oct 2020 08:20:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:82.0) Gecko/20100101 Thunderbird/82.0 MIME-Version: 1.0 In-Reply-To: <497035042.203793.1602001437004.JavaMail.zimbra@fws.fr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.506 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] QEMU failing to start from the web with ZFS Over iSCSI X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Oct 2020 06:20:56 -0000 Hi, On 10/6/20 6:23 PM, Daniel Berteaud wrote: > ----- Le 6 Oct 20, à 17:59, Daniel Berteaud daniel@firewall-services.com a écrit : > >> Hi there. >> >> I've been migrating a few VM from an NFS storage to a ZFS over iSCSI one (using >> LIO backend) on a fully updated PVE6 cluster. Everything went fine while >> live-moving VM disks. There's also no problem starting VM from the CLI, eg >> >> qm start 105 >> >> But, starting the same VM from the web interface fails with the unhelpful >> message : >> >> TASK ERROR: start failed: QEMU exited with code -1 >> >> Seems there're some more checks somewhere which are failing when running through >> the web interface. How could I debug this ? I usually just start with qm or >> manually the qemu command (using the qm showcmd output), but as both are >> working here ... >> > > Some more info : > > * This cluster was using a ZFS over iSCSI storage a few months ago, without issue > * A VM with ZFS over iSCSI disk started with "qm start" can be migrated from the web interface (so, the start phase on the new node is not affected when done in a migration context) > * The problem goes away as soon as I replace the ZFS over iSCSI storage with a image on an NFS server (no other change) is there anything else in the task log of the start? ( you can obtain that by dobuble clicking the task) also maybe there are some hints in the pve log during that time? basically 'qm start ID' does the same think as the API so there should be no difference can you post your vm config? (qm config ID) Regards, Dominik