[PVE-User] Some VM's are not able to start

Thu May 14 21:42:52 CEST 2020

The info is in the first line of the log

"kvm: -device vfio-pci,host=0000:5e:00.0,id=hostpci0,bus=pci.0,addr=0x10:
vfio 0000:5e:00.0: failed to open /dev/vfio/46: Device or resource busy"

This means the device is already passed through to another running VM, or
it is being locked by something else.

On Thu, 14 May 2020 at 18:22, Sivakumar SARAVANAN <
sivakumar.saravanan.jv.ext at valeo-siemens.com> wrote:

> Hello,
>
> Thank you for your support.
>
> But I am getting below error message after removing the 'hugepages =2'
> line in the VM config file.
>
> kvm: -device vfio-pci,host=0000:5e:00.0,id=hostpci0,bus=pci.0,addr=0x10:
> vfio 0000:5e:00.0: failed to open /dev/vfio/46: Device or resource busy
> TASK ERROR: start failed: command '/usr/bin/kvm -id 145 -name
> HIL-System151 -chardev
> 'socket,id=qmp,path=/var/run/qemu-server/145.qmp,server,nowait' -mon
> 'chardev=qmp,mode=control' -chardev
> 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon
> 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/145.pid
> -daemonize -smbios 'type=1,uuid=750b5d38-2fa0-4a9b-8b0f-c8b2d5ef769d' -smp
> '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot
> 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg'
> -vnc unix:/var/run/qemu-server/145.vnc,password -no-hpet -cpu
> 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi'
> -m 32768 -object 'memory-backend-ram,id=ram-node0,size=16384M' -numa
> 'node,nodeid=0,cpus=0-1,memdev=ram-node0' -object
> 'memory-backend-ram,id=ram-node1,size=16384M' -numa
> 'node,nodeid=1,cpus=2-3,memdev=ram-node1' -device
> 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device
> 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device
> 'vmgenid,guid=e256bf4d-f862-47d0-a1ab-25821f586542' -device
> 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device
> 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device
> 'vfio-pci,host=0000:5e:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device
> 'VGA,id=vga,bus=pci.0,addr=0x2' -chardev
> 'socket,path=/var/run/qemu-server/145.qga,server,nowait,id=qga0' -device
> 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device
> 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -iscsi
> 'initiator-name=iqn.1993-08.org.debian:01:29191a75ef5e' -drive
> '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=/dev/zvol/SSD-Storage-PRX002/vm-145-disk-0,if=none,id=drive-virtio0,cache=writethrough,format=raw,aio=threads,detect-zeroes=on'
> -device
> 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100'
> -drive
> 'file=/dev/zvol/HDD-Storage-PRX002/vm-145-disk-1,if=none,id=drive-virtio1,cache=writethrough,format=raw,aio=threads,detect-zeroes=on'
> -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb'
> -netdev
> 'type=tap,id=net0,ifname=tap145i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown'
> -device
> 'e1000,mac=3E:DE:DC:87:CE:75,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'
> -rtc 'driftfix=slew,base=localtime' -machine 'type=pc+pve1' -global
> 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1
>
>
> Best regards
> SK
>
>
> On Thu, May 14, 2020 at 6:37 PM Mark Adams via pve-user <
> pve-user at pve.proxmox.com> wrote:
>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Mark Adams <mark at openvs.co.uk>
>> To: PVE User List <pve-user at pve.proxmox.com>
>> Cc:
>> Bcc:
>> Date: Thu, 14 May 2020 17:36:19 +0100
>> Subject: Re: [PVE-User] Some VM's are not able to start
>> Remove the hugepages line from your vmid.conf (ie 100.conf)
>>
>> On Thu, 14 May 2020, 17:24 Sivakumar SARAVANAN, <
>> sivakumar.saravanan.jv.ext at valeo-siemens.com> wrote:
>>
>> > Thank you so much.
>> >
>> > What is the steps to disable the hugepage ?
>> >
>> >
>> > Best regards
>> > SK
>> >
>> > On Thu, May 14, 2020 at 6:20 PM Mark Adams via pve-user <
>> > pve-user at pve.proxmox.com> wrote:
>> >
>> > >
>> > >
>> > >
>> > > ---------- Forwarded message ----------
>> > > From: Mark Adams <mark at openvs.co.uk>
>> > > To: PVE User List <pve-user at pve.proxmox.com>
>> > > Cc:
>> > > Bcc:
>> > > Date: Thu, 14 May 2020 17:19:09 +0100
>> > > Subject: Re: [PVE-User] Some VM's are not able to start
>> > > Do you really need hugepages? if not disable it.
>> > >
>> > > On Thu, 14 May 2020 at 17:17, Sivakumar SARAVANAN <
>> > > sivakumar.saravanan.jv.ext at valeo-siemens.com> wrote:
>> > >
>> > > > Hello Daniel,
>> > > >
>> > > > Thanks for coming back.
>> > > >
>> > > > I mean, I am unable to power ON the VM until shutdown the other
>> VM's in
>> > > the
>> > > > same host.
>> > > >
>> > > > There are 6 VM's running on each Host, But sometimes all 6 VM's
>> would
>> > run
>> > > > without any issue. But Sometimes if I stop ( Shutdown) and Power ON
>> (
>> > > > Start) getting an error saying as below. But each will have 32 GB
>> > memory.
>> > > >
>> > > > start failed: hugepage allocation failed at
>> > > > /usr/share/perl5/PVE/QemuServer/Memory.pm line 541.
>> > > >
>> > > > Appreciating your suggestion.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > Best regards
>> > > > SK
>> > > >
>> > > > On Thu, May 14, 2020 at 5:46 PM Daniel Berteaud <
>> > > > daniel at firewall-services.com> wrote:
>> > > >
>> > > > >
>> > > > >
>> > > > > ----- Le 14 Mai 20, à 17:38, Sivakumar SARAVANAN
>> > > > > sivakumar.saravanan.jv.ext at valeo-siemens.com a écrit :
>> > > > >
>> > > > > > Hello,
>> > > > > >
>> > > > > > We have implemented the Proxmox VE in our environment.
>> > > > > >
>> > > > > > So each server will have a maximum 6 VM. But not able to start
>> the
>> > > few
>> > > > > VM's
>> > > > > > ON until we bring down the 1 or 2 VM's in the same Host.
>> > > > > >
>> > > > >
>> > > > > Please describe what you mean by "not able to start"
>> > > > >
>> > > > > 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
>> > > > ]
>> > > > >
>> > > > > _______________________________________________
>> > > > > pve-user mailing list
>> > > > > pve-user at pve.proxmox.com
>> > > > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> > > > >
>> > > >
>> > > > --
>> > > > *This e-mail message is intended for the internal use of the
>> intended
>> > > > recipient(s) only.
>> > > > The information contained herein is
>> > > > confidential/privileged. Its disclosure or reproduction is strictly
>> > > > prohibited.
>> > > > If you are not the intended recipient, please inform the sender
>> > > > immediately, do not disclose it internally or to third parties and
>> > > destroy
>> > > > it.
>> > > >
>> > > > In the course of our business relationship and for business purposes
>> > > > only, Valeo may need to process some of your personal data.
>> > > > For more
>> > > > information, please refer to the Valeo Data Protection Statement and
>> > > > Privacy notice available on Valeo.com
>> > > > <https://www.valeo.com/en/ethics-and-compliance/#principes>*
>> > > > _______________________________________________
>> > > > pve-user mailing list
>> > > > pve-user at pve.proxmox.com
>> > > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> > >
>> > >
>> > >
>> > > ---------- Forwarded message ----------
>> > > From: Mark Adams via pve-user <pve-user at pve.proxmox.com>
>> > > To: PVE User List <pve-user at pve.proxmox.com>
>> > > Cc: Mark Adams <mark at openvs.co.uk>
>> > > Bcc:
>> > > Date: Thu, 14 May 2020 17:19:09 +0100
>> > > Subject: Re: [PVE-User] Some VM's are not able to start
>> > > _______________________________________________
>> > > pve-user mailing list
>> > > pve-user at pve.proxmox.com
>> > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> > >
>> >
>> > --
>> > *This e-mail message is intended for the internal use of the intended
>> > recipient(s) only.
>> > The information contained herein is
>> > confidential/privileged. Its disclosure or reproduction is strictly
>> > prohibited.
>> > If you are not the intended recipient, please inform the sender
>> > immediately, do not disclose it internally or to third parties and
>> destroy
>> > it.
>> >
>> > In the course of our business relationship and for business purposes
>> > only, Valeo may need to process some of your personal data.
>> > For more
>> > information, please refer to the Valeo Data Protection Statement and
>> > Privacy notice available on Valeo.com
>> > <https://www.valeo.com/en/ethics-and-compliance/#principes>*
>> > _______________________________________________
>> > pve-user mailing list
>> > pve-user at pve.proxmox.com
>> > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> >
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Mark Adams via pve-user <pve-user at pve.proxmox.com>
>> To: PVE User List <pve-user at pve.proxmox.com>
>> Cc: Mark Adams <mark at openvs.co.uk>
>> Bcc:
>> Date: Thu, 14 May 2020 17:36:19 +0100
>> Subject: Re: [PVE-User] Some VM's are not able to start
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>
> *This e-mail message is intended for the internal use of the intended recipient(s) only.
> The information contained herein is confidential/privileged. Its disclosure or reproduction is strictly prohibited.
> If you are not the intended recipient, please inform the sender immediately, do not disclose it internally or to third parties and destroy it.
>
> In the course of our business relationship and for business purposes only, Valeo may need to process some of your personal data.
> For more information, please refer to the Valeo Data Protection Statement and Privacy notice available on Valeo.com <https://www.valeo.com/en/ethics-and-compliance/#principes>*
>
>