public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Berteaud <daniel@firewall-services.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] QEMU failing to start from the web with ZFS Over iSCSI
Date: Wed, 7 Oct 2020 09:55:26 +0200 (CEST)	[thread overview]
Message-ID: <970746267.205741.1602057326034.JavaMail.zimbra@fws.fr> (raw)
In-Reply-To: <f12dd670-8e30-067a-9dbf-3cfbaf371d17@proxmox.com>

----- Le 7 Oct 20, à 8:20, Dominik Csapak d.csapak@proxmox.com a écrit :

> 
> is there anything else in the task log of the start? ( you can obtain
> that by dobuble clicking the task)

Nop, nothing else

> 
> also maybe there are some hints in the pve log during that time?

Nothing relevant. Syslog just show :

Oct 06 16:15:00 pvo1 pvedaemon[15956]: start failed: QEMU exited with code -1
Oct 06 16:15:00 pvo1 pvedaemon[14869]: <dani@pam> end task UPID:pvo1:00003E54:029AB217:5F7C7BE3:qmstart:149:dani@pam: start failed: QEMU exited with code -1


And the task log in /var/log/pve/tasks just

TASK ERROR: start failed: QEMU exited with code -1


> 
> basically 'qm start ID' does the same think as the API so
> there should be no difference

I agree, that's why I do not understand what's going on

> 
> can you post your vm config? (qm config ID)


Here's one exmple :

agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 3072
bootdisk: scsi0
cores: 4
cpu: Skylake-Client
cpuunits: 512
ide0: none,media=cdrom
memory: 4096
name: win10-test.fws.fr
net0: virtio=32:8B:E2:AD:90:03,bridge=tests
numa: 0
ostype: win10
scsi0: iscsi-zfs-zol1-prd:vm-115-disk-0,discard=on,size=33G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=fb7d5364-6cfa-46f7-8866-4dedb3427605
sockets: 1
usb0: spice
vga: qxl

(changing other settings, like discard, CPU model, SPICE vs VNC etc has no effect)


And my storage :

zfs: iscsi-zfs-zol1-prd
        blocksize 16k
        iscsiprovider LIO
        pool pool/pve/prod
        portal 10.29.255.252
        target iqn.2019-10.fr.fws.pve:prod
        content images
        lio_tpg tpg1
        nowritecache 1
        sparse 1



Cheers,
Daniel


-- 
[ https://www.firewall-services.com/ ] 	
Daniel Berteaud 
FIREWALL-SERVICES SAS, La sécurité des réseaux 
Société de Services en Logiciels Libres 
Tél : +33.5 56 64 15 32 
Matrix: @dani:fws.fr 
[ https://www.firewall-services.com/ | https://www.firewall-services.com ]




  reply	other threads:[~2020-10-07  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 15:59 Daniel Berteaud
2020-10-06 16:23 ` Daniel Berteaud
2020-10-07  6:20   ` Dominik Csapak
2020-10-07  7:55     ` Daniel Berteaud [this message]
2020-10-07 12:55       ` Daniel Berteaud
2020-10-09 15:18         ` Stoiko Ivanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=970746267.205741.1602057326034.JavaMail.zimbra@fws.fr \
    --to=daniel@firewall-services.com \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal