VM "start failed" during normal use

Tutbjun

Member
Aug 4, 2022
5
1
8
Hi all,

I woke up this morning to do some work, but my Linux VM didn't start. The problem have had me stomped a bit, so I hope to get some tips here.

My error message starting the VM:

Code:
kvm:/usr/share/qemu-server/pve-q35-4.0.cfg:5: Bus 'pcie.0' not found
TASK ERROR: start failed: QEMU exited with code 1

Here is My VM config:
Code:
args: -machine pc,max-ram-below-4g=1G
balloon: 0
bios: ovmf
boot: order=ide0;ide2;net0
cores: 16
cpu: kvm64
efidisk0: pve-newstorage:vm-100-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: pve-newstorage:vm-100-disk-0,size=128G
ide2: local:iso/ubuntu-22.04.3-desktop-amd64.iso,media=cdrom,size=4919592K
machine: q35
memory: 57344
meta: creation-qemu=8.0.2,ctime=1695409418
name: Ubuntu-compute
net0: virtio=1E:81:E3:4F:97:9D,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=92b2b995-dcf6-4cee-a31e-5bc7f220fed4
sockets: 1
vga: std
vmgenid: f08ce21a-90d7-48c5-bcd2-e2c3d9e092bf

Any help and guidance would be appreciated:)
 
Hi,
you are using a custom
Code:
args: -machine pc,max-ram-below-4g=1G
which will override the machine type, but Proxmox VE expects the machine to be q35
Code:
machine: q35
so it will try to configure stuff for q35.

Please try using the same machine type both times.

Out of intereset, why do you even need the special machine flag max-ram-below-4g?
 
Hello Tutbjun,

I'm new to Proxmox Forum. however the error output seems to indicate that there is a problem in
/usr/share/qemu-server/pve-q35-4.0.cfg
on line no.5

5: Bus 'pcie.0' not found

Have you checked the file below?
cat /usr/share/qemu-server/pve-q35-4.0.cfg

my output is here :

[device "ehci"]
driver = "ich9-usb-ehci1"
multifunction = "on"
bus = "pcie.0"
addr = "1d.7"

[device "uhci-1"]
driver = "ich9-usb-uhci1"
multifunction = "on"
bus = "pcie.0"
addr = "1d.0"
masterbus = "ehci.0"
firstport = "0"
....

When something happnes, I usually check the following commands to check for any issues.
I'm still learning about VE, Hope this can be helpful.

journalctl -u pvestatd.service -f
journalctl -u pvedaemon -f
journalctl -xe | grep qemu

Seiji
 
Hi,
you are using a custom
Code:
args: -machine pc,max-ram-below-4g=1G
which will override the machine type, but Proxmox VE expects the machine to be q35
Code:
machine: q35
so it will try to configure stuff for q35.

Please try using the same machine type both times.

Out of intereset, why do you even need the special machine flag max-ram-below-4g?
That fixed it, thank you very much!

I think the setting may have slipped in while toying with GPU passtrough. Still no luck with that, that is a todo project.
 

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!

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 yours easily in our online shop.

Buy now!