[SOLVED] New To Proxmox and KVM: Error: Start Failed

mattlach

Well-Known Member
Mar 23, 2016
169
17
58
Boston, MA
Hey all,

I'm brand new to Proxmox and to KVM, so I am probably overlooking something dead simple here, but I'd appreciate any assistance. I've been running ESXi since 5.0 first came out, and I finally got tired of their shit, and decided it was time to migrate to something else.

I have spent time reading and rereading wiki's and guides and am not making any progress, so I'd appreciate any help I can get.

Unfortunately my setup requires me to create my most complicated VM first (FreeNAS) as all of my other VM's depend on it for storage (not for drive images, mind you, just for file sharing storage mounted using NFS), and FreeNAS requires that my LSI controllers are passed through.

So, because of this, my first VM in proxmox is also a relatively complicated one.

First off, host specs:
- SuperMicro X8DTE with dual Xeon L5640's
- 96GB RAM
- Boot drives: ZFS Mirror consisting of 2x 500GB Samsung 850 SSD's connected to on board SATA
- 2x LSI 9211-8i SAS controllers in IT/HBA mode
- Dual onboard Intel 82574L Ethernet
- Dual port Intel Ethernet 82571EB expansion card
- Single Brocade BR1020 for 10gig fiber

I have gone through the PCI Passthrough wiki added the correct boot options, loaded the appropriate modules, and verified in dmesg that I have functioning IOMMU, Interrupt remapping, and IOMMU isolation.

I have configured my VM as follows:
Code:
root@proxmox:/etc/pve/qemu-server# cat 100.conf
bootdisk: virtio0
cores: 6
hostpci0: 07:00.0,pcie=1
hostpci1: 08:00.0,pcie=1
ide2: local:iso/FreeNAS-9.10-STABLE-201604111739.iso,media=cdrom,size=431746K
machine: q35
memory: 65536
name: FreeNAS
net0: virtio=32:62:63:66:36:39,bridge=vmbr0
net1: virtio=3A:37:30:33:38:39,bridge=vmbr1
numa: 0
ostype: other
smbios1: uuid=c68019e1-2b10-49ce-8554-06cea3e94552
sockets: 1
virtio0: local:100/vm-100-disk-1.qcow2,size=4G

When I try to start the VM in order to install the OS I get the following error message:
Code:
root@proxmox:~# qm start 100
Use of uninitialized value $kvmver in pattern match (m//) at /usr/share/perl5/PVE/QemuServer.pm line 6378.
Use of uninitialized value $current_major in numeric ge (>=) at /usr/share/perl5/PVE/QemuServer.pm line 6384.
Running as unit 100.scope.
kvm: -drive file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,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-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on: Could not open '/var/lib/vz/images/100/vm-100-disk-1.qcow2': Invalid argument
start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 100 -p 'KillMode=none' -p 'CPUShares=1000' /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=c68019e1-2b10-49ce-8554-06cea3e94552' -name FreeNAS -smp '6,sockets=1,cores=6,maxcpus=6' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 65536 -k en-us -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=07:00.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0' -device 'vfio-pci,host=08:00.0,id=hostpci1,bus=ich9-pcie-port-2,addr=0x0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:bf923e1082af' -drive 'file=/var/lib/vz/template/iso/FreeNAS-9.10-STABLE-201604111739.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -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-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=32:62:63:66:36:39,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300,romfile=pxe-virtio.rom' -netdev 'type=tap,id=net1,ifname=tap100i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=3A:37:30:33:38:39,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301,romfile=pxe-virtio.rom' -machine 'type=q35'' failed: exit code 1

I'm a little bit confused currently how to interpret this error message, as I have not yet learned which of these are just warnings that can be disregarded and which are fatal errors.

Are the "use of uninitialized value" errors causing this issue?

Or maybe the file system warnings about O_DIRECT and not being able to open the qcow2 image?

I'd appreciate any assistance!

Thanks,
Matt
 

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!