Task error start failed qemu exited with code 1

Stopped: Start failed: QEMU exited with code 1 [Win 10 — Wi-Fi PCIe adapter passthrough]

krish

New Member

Hello, I recently added a Wi-Fi adapter (Asus PCE-AC68) to my system. I first installed the drivers on Windows 10 VM and then added the «PCI Device» from «Hardware» settings.

The adapter shows up when I run the lscpci

However, when I start the VM after adding the PCIe adapter, I am getting an error — Stopped: Start failed: QEMU exited with code.

Here is the output:

I have successfully enabled PCI(e) Passthrough based on the guidance and SATA controller is running seamlessly. I didn’t find any drivers for Linux or Proxmox, but is it required since I have already installed it on the Win 10 VM?

I could not find any relevant discussions on this forum. Can you please help troubleshoot this issue? Please note I don’t have much experience, and this is my first setup. If you need any further details, please let me know.

Stefan_R

Proxmox Retired Staff

Please post the output of lspci -nnk . Is suspect what is happening here is that the host kernel has a built-in driver that is claiming the device, thus blocking the VM from using it. Follow the guide on GPU passthrough (substitute «GPU» with «WiFi Controller») to force bind vfio-pci to the device at boot time.

Also check that your device is in an isolated IOMMU group. Please post the output of the command described here.

Best regards,
Stefan

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Stefan_R

Proxmox Retired Staff

Sorry, that was unclear on my part. I didn’t mean literally subsitute, just «follow the instructions for your WiFi card, even though it says GPU». But the ‘lspci’ output you posted shows the ‘vfio-pci’ driver already bound, so forget that part, that shouldn’t be the problem.

Looking at the IOMMU grouping, it would seem as if the overlapping groups are what cause the error. IOMMU groups and VMs have a 1:1 mapping, that means, that when you assign a PCI device to a VM, *all* the devices in that IOMMU group (1 for your WiFi controller) are assigned to that VM (even if not visible in the guest) and cannot be assigned to a different one. Are you assigning your 0000:02:00.0 SAS device to a VM too? The same one? Please also post your VM config ( qm config ).

At your own risk, you can try adding the pcie_acs_override=downstream to your kernel commandline. This will force seperate IOMMU groups at the expense of potentially stability and security.

Best regards,
Stefan

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Источник

[SOLVED] cannot start VM after upgraded to 7.0-11

New Member

need help after upgraded the proxmox version from 6 to 7 when I created a new VM it’s failed to start with the error below

the Iso file is in place:

thanks in advance

Moayad

Proxmox Staff Member

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

New Member

thanks for your reply

this is the output for both command

Moayad

Proxmox Staff Member

Why you are running your host from the old pve-kernel?

Could you please try to run your PVE host from the latest pve-kernel version and see if the issue still occurs?

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

New Member

On the weekend I also got this problem.

lvscan shows all vms inactive.

The /dev/vms folder is missing.
lvchange -ay /dev/vms activates all disks and machines start.
After rebooting the server, everything is the same — the disks are inactive.

The logs contain the following:

New Member

Why you are running your host from the old pve-kernel?

Could you please try to run your PVE host from the latest pve-kernel version and see if the issue still occurs?

after the server reboot now I can start the VM. as per the version the kernel is updated.

thanksfor your help Moayad.

Moayad

Proxmox Staff Member

Glad that you solved your issue

I’ll go ahead and set your thread as [SOLVED] to help other people who have the same issue.

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Источник

Before installation of Win1O.. Qemu exits with error code 1

ssldn

Member

Hi,
mainly I am long time in the topic already, but it was with version 4. I made experiences, but many things gotten a lot better, fine grained and there for a bit more complicated.
I cannot start the install process of the guest system windows 10, I hope someone can spot the mistake easily. This is the first VM I start to setup. Somethings arent ready till here, which is the second HDD must still be added to the lvm. Then I have to care for network things still, cause the routed (bridged) solution I think then after it the firewall and last the setup of VMs, that can be duplicated.

Thanks upfront.
Here my settings:

/proxmox # qm config 100 agent: 1,fstrim_cloned_disks=1,type=virtio boot: cdn bootdisk: scsi1 cores: 4 cpu: kvm64,flags=+md-clear;+spec-ctrl;+ssbd;+virt-ssbd;+amd-no-ssb;+hv-tlbflush;+hv-evmcs ide1: local:iso/virtio-win.iso,media=cdrom,size=402812K ide2: local:iso/Win10_2004_German_x64.iso,media=cdrom localtime: 1 memory: 4096 name: GhostVMTest numa: 1 ostype: win10 scsi1: local:100/vm-100-disk-0.qcow2,cache=unsafe,discard=on,size=35G,ssd=1 scsihw: virtio-scsi-pci smbios1: uuid=2a150652-88c4-4e6b-b1a5-9d44b4307671 sockets: 2 unused0: local:100/vm-100-disk-1.qcow2 vga: qxl vmgenid: 6a8da2a0-265a-44e1-bd76-5e2cac83182f vmstatestorage: local ______________________________________________________
root@ghost0

/proxmox # cat /sys/module/kvm_intel/parameters/nested N ____________________________________________________

/proxmox # pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve) pve-manager: 6.2-10 (running version: 6.2-10/a20769ed) pve-kernel-5.4: 6.2-4 pve-kernel-helper: 6.2-4 pve-kernel-5.4.44-2-pve: 5.4.44-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 libjs-extjs: 6.0.1-10 libknet1: 1.16-pve1 libproxmox-acme-perl: 1.0.4 libpve-access-control: 6.1-2 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.1-5 libpve-guest-common-perl: 3.1-1 libpve-http-server-perl: 3.0-6 libpve-storage-perl: 6.2-5 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4

pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-1 lxcfs: 4.0.3-pve3 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-9 pve-cluster: 6.1-8 pve-container: 3.1-12 pve-docs: 6.2-5 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-2 pve-firmware: 3.1-1 pve-ha-manager: 3.0-9 pve-i18n: 2.1-3 pve-qemu-kvm: 5.0.0-11 pve-xtermjs: 4.3.0-1 qemu-server: 6.2-11 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 __________________________________________________

# cat /etc/network/interfaces source /etc/network/interfaces.d/* auto lo iface lo inet loopback iface lo inet6 loopback auto eKp0s33A88 iface eKp0s33A88 inet static address 88.99.210.91 netmask 255.255.255.192 gateway 88.99.210.65 # route 88.99.210.64/26 via 88.99.210.65 up route add -net 88.99.210.64 netmask 255.255.255.192 gw 587.101.210.65 dev eKp0s33A88 iface eKp0s33A88 inet6 static address 2a01:4f8:1bbbb:3b5a::2 netmask 64 gateway fe80::1 ________________________________________________________________
root@ghost0

# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 94 Model name: Intel(R) Xeon(R) CPU E3-1275 v5 @ 3.60GHz Stepping: 3 CPU MHz: 3904.416 CPU max MHz: 4000.0000 CPU min MHz: 800.0000 BogoMIPS: 7200.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d ________________________________________________________________

Источник

[SOLVED] can’t start kvm machine — exit code 1

nzimas

New Member

After upgrading from PVE 3.2 to 3,3, my KVM guests ceased to boot.
Tried a few suggestions fond on a few related threads, but none really worked for me.

The task error message reads as follows:

dietmar

Proxmox Staff Member

To you get better error description if you start from command line?

Best regards,
Dietmar

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

nzimas

New Member

# qm start 111
kvm: -drive file=/var/lib/vz/images/111/vm-111-disk-1.qcow2,if=none,id=drive-ide1,format=qcow2,cache=writethrough,aio=native,detect-zeroes=on: could not open disk image /var/lib/vz/images/111/vm-111-disk-1.qcow2: Block format ‘qcow2’ used by device ‘drive-ide1’ doesn’t support the option ‘detect-zeroes’
start failed: command ‘/usr/bin/kvm -id 111 -chardev ‘socket,id=qmp,path=/var/run/qemu-server/111.qmp,server,nowait’ -mon ‘chardev=qmp,mode=control’ -vnc unix:/var/run/qemu-server/111.vnc,x509,password -pidfile /var/run/qemu-server/111.pid -daemonize -name spops -smp ‘sockets=1,cores=2’ -nodefaults -boot ‘menu=on’ -vga std -no-hpet -cpu ‘kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep’ -k pt -m 2048 -cpuunits 1000 -device ‘piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2’ -device ‘usb-tablet,id=tablet,bus=uhci.0,port=1’ -device ‘virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3’ -iscsi ‘initiator-name=iqn.1993-08.org.debian:01:ff67a0bdb55d’ -drive ‘file=/var/lib/vz/images/111/vm-111-disk-1.qcow2,if=none,id=drive-ide1,format=qcow2,cache=writethrough,aio=native,detect-zeroes=on’ -device ‘ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=100’ -netdev ‘type=user,id=net0,hostname=spops’ -device ‘e1000,mac=B2:67:42:45:4F:4A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300’ -rtc ‘driftfix=slew,base=localtime’ -global ‘kvm-pit.lost_tick_policy=discard» failed: exit code 1

spirit

Famous Member

# qm start 111
kvm: -drive file=/var/lib/vz/images/111/vm-111-disk-1.qcow2,if=none,id=drive-ide1,format=qcow2,cache=writethrough,aio=native,detect-zeroes=on: could not open disk image /var/lib/vz/images/111/vm-111-disk-1.qcow2: Block format ‘qcow2’ used by device ‘drive-ide1’ doesn’t support the option ‘detect-zeroes’
start failed: command ‘/usr/bin/kvm -id 111 -chardev ‘socket,id=qmp,path=/var/run/qemu-server/111.qmp,server,nowait’ -mon ‘chardev=qmp,mode=control’ -vnc unix:/var/run/qemu-server/111.vnc,x509,password -pidfile /var/run/qemu-server/111.pid -daemonize -name spops -smp ‘sockets=1,cores=2’ -nodefaults -boot ‘menu=on’ -vga std -no-hpet -cpu ‘kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep’ -k pt -m 2048 -cpuunits 1000 -device ‘piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2’ -device ‘usb-tablet,id=tablet,bus=uhci.0,port=1’ -device ‘virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3’ -iscsi ‘initiator-name=iqn.1993-08.org.debian:01:ff67a0bdb55d’ -drive ‘file=/var/lib/vz/images/111/vm-111-disk-1.qcow2,if=none,id=drive-ide1,format=qcow2,cache=writethrough,aio=native,detect-zeroes=on’ -device ‘ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=100’ -netdev ‘type=user,id=net0,hostname=spops’ -device ‘e1000,mac=B2:67:42:45:4F:4A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300’ -rtc ‘driftfix=slew,base=localtime’ -global ‘kvm-pit.lost_tick_policy=discard» failed: exit code 1

Hi, detect-zeroes is a new option added recently in proxmox, but it should works with qcow2.

what is your qemu version ?

«Are you looking for a French Proxmox training center?

Источник

TASK ERROR: start failed: QEMU exited with code 1 #18

After the successful installation of Proxmox server on Raspberry Pi 4 B (4GB RAM), navigated to the web browser and pointed the host server with port 8006 and I was successful at the login as well.

But when I tried to create the VM I was hit by the following error.

kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101: Bus ‘ide.1’ not found TASK ERROR: start failed: QEMU exited with code 1

Help me to fix this issue.

The text was updated successfully, but these errors were encountered:

This is an easy fix IDE drivers are not avaivable on the pi so delete your ide-cdrom and readd it as scsi-cd, then it should start up. Hope I could help.

Thanks for writing-up. I need to do this while creating the VM or while installing the proxmox to Pi?

I’m pretty new to this, so a decent tutorial will help me.

@TuxfeatMac — Good news. Managed to run the VM successfully but when I navigate to console, it always says, guest has not initialized the display (yet)

Am I missing something?

I think you have to adjust te boot order.

I am also seeing this issue after adjusting the boot order.

Same here, console does not work.

@TuxfeatMac Does the console work for you? What OS are you visualizing?

I managed to get the console to work by using the OVMF bios (UEFI) instead of the default (seabios). However I couldn’t get it to boot from an ISO / CD drive: failed to load boot0001 uefi qemu cd-rom

It’s taking me to the interactive shell.

It’s taking me to the interactive shell

You can type exit to get to the boot selection screen. I found this post by one of the devs who says this was a working config (in the pimox v6 build). I haven’t tried it yet though: https://old.reddit.com/r/Proxmox/comments/n4d7ev/now_running_proxmox_on_a_raspberry_pi_4_cluster/gwzr4h4/

Unfortunately, it take me to here.

I just needed to set the cpu to host. One way of doing this is to ssh into the machine and run
$ sudo qm set —cpu=host

This worked for me. Cheers!

Thanks for writing-up. I need to do this while creating the VM or while installing the proxmox to Pi?

I’m pretty new to this, so a decent tutorial will help me.

hey, I have the same issue, what did you do in the end?

nvm, found a YouTube video for us n00bs:

This is an easy fix IDE drivers are not avaivable on the pi so delete your ide-cdrom and readd it as scsi-cd, then it should start up. Hope I could help.

This worked for me. Thanks

I had the same issue where QEMU exited with code 1.
My constellation is a proxmox cluster with 3 nodes, and 2 network bridges (vmbr1 on node 1, and vmbr0 on node2).

The fault was the wrong chosen LinuxBridge on the networkdevise of the VM.

After i migrated the VM which was well connected on vmbr1 from node 1 it couldn´t connect on node2 because the bridge vmbr0.
Therefore The bridgenames of the nodes has to match in the name.
If not, you have to change the network setting of the VM manually, otherwhise the VM won´t start.

I changed the bridge from vmbr1 (Bridge from the other node) to vmbr0 and the VM starts again 🙂
Changing the settings of other Hardware like the cdrom bus or other changes were not nessecary.

Thank you all for this issue, your discussion helped me to find the right path to the solution (to change the vm settings)

Источник

При запуски появляется ошибка:

kvm: -drive file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,aio=native,cache=none,detect-zeroes=on: file system may not support O_DIRECT

kvm: -drive file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,aio=native,cache=none,detect-zeroes=on: could not open disk image /var/lib/vz/images/100/vm-100-disk-1.qcow2: Could not open ‘/var/lib/vz/images/100/vm-100-disk-1.qcow2’: Invalid argument

TASK ERROR: start failed: command ‘/usr/bin/kvm -id 100 -chardev ‘socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait’ -mon ‘chardev=qmp,mode=control’ -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios ‘type=1,uuid=23f1d264-91c8-408e-bb84-9ac94cf529fc’ -name TServer -smp ‘4,sockets=1,cores=4,maxcpus=4’ -nodefaults -boot ‘menu=on,strict=on,reboot-timeout=1000’ -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 10240 -k en-us -cpuunits 1000 -device ‘piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2’ -device ‘usb-tablet,id=tablet,bus=uhci.0,port=1’ -device ‘virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3’ -iscsi ‘initiator-name=iqn.1993-08.org.debian:01:5ed3e1eb441e’ -drive ‘file=/var/lib/vz/template/iso/debian-8.0.0-amd64-DVD-1.iso,if=none,id=drive-ide2,media=cdrom,aio=native’ -device ‘ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200’ -drive ‘file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,aio=native,cache=none,detect-zeroes=on’ -device ‘ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100’ -netdev ‘type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown’ -device ‘e1000,mac=E6:03:E9:F0:74:81,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300» failed: exit code 1

В консоле показывает:

root@pve:~# kvm

Could not initialize SDL(No available video device) — exiting

root@pve:~# lspci | grep VGA

07:0b.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10)

Сервер DELL PowerEdge 1100, никто с такой проблемой не сталкивался?