[PVE-User] VM Power Issue

Mark Adams mark at openvs.co.uk
Mon Jun 8 16:38:48 CEST 2020


Sivakumar - This is a "known issue" as far as I am aware, usually when you
are allocating quite a bit of memory (although 16G is not a lot in your
case, but maybe the server doesn't have much ram?) when starting a vm with
a PCI device passed through to it. It also only seems to happen when you
are nearing "peak" ram usage, so getting close to running out. It never
happens on a fresh boot.

I don't know if it has been acknowledged or even reported to redhat, or
whether simply the timeout should be longer in proxmox.

I wrote to this list about it not long ago and never received a response,
and I have seen at least 1 forum post about it.

Anyway to cut a long story short, just start it manually on the cli, which
has no timeout. "qm showcmd VMID | bash" should start it fine. IE "qm
showcmd 101 | bash"

Regards,
Mark

On Mon, 8 Jun 2020 at 15:31, Arjen via pve-user <pve-user at pve.proxmox.com>
wrote:

>
>
>
> ---------- Forwarded message ----------
> From: Arjen <leesteken at protonmail.ch>
> To: PVE User List <pve-user at pve.proxmox.com>
> Cc:
> Bcc:
> Date: Mon, 08 Jun 2020 14:30:57 +0000
> Subject: Re: [PVE-User] VM Power Issue
> On Monday, June 8, 2020 10:14 AM, Sivakumar SARAVANAN <
> sivakumar.saravanan.jv.ext at valeo-siemens.com> wrote:
>
> > Hello,
> >
> > I am not able to start the VM after adding the PCI device to VM.
> > I can see the below error message.
>
> Maybe your system is very busy? Maybe it takes a while to allocate the
> memory?
> Maybe you could give more information about the VM configuration and your
> PVE setup?
>
> Can you try running the command below from the command line of your PVE
> host, to see if it works and how long it takes?
> Sometimes (often memory-size related), it just works but takes longer than
> the time-out.
>
> > TASK ERROR: start failed: command '/usr/bin/kvm -id 175 -name
> > HIL-System096Planned -chardev
> > 'socket,id=qmp,path=/var/run/qemu-server/175.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/175.pid
> > -daemonize -smbios 'type=1,uuid=1ab2409d-4b67-4d3c-822a-7a024d05d9bf'
> -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/175.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=c98f392f-13af-43d9-b26e-ca070177f6bb' -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:1b: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/175.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:626ca038d6c7' -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-PRX018/vm-175-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-PRX018/vm-175-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=tap175i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown'
> > -device
> >
> 'e1000,mac=F2:3F:4D:48:7B:68,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: got timeout
> >
> > Appreciating your suggestion.
> >
> > Best regards,
> >
> > SK
> >
> >
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> > 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
>
> Am I the intended recipient? Otherwise, consider yourself informed
> immediately. I apologize for disclosing this information on the same
> mailing-list you sent the original e-mail. Valeo is not allowed to process
> my personal data, according to the General Data Protection Regulation
> (GDPR), without prior written consent. Please consider removing such
> statements when sending email to a (public) mailing list, as it makes it
> difficult to help you without violating your rules.
>
>
>
> ---------- Forwarded message ----------
> From: Arjen via pve-user <pve-user at pve.proxmox.com>
> To: PVE User List <pve-user at pve.proxmox.com>
> Cc: Arjen <leesteken at protonmail.ch>
> Bcc:
> Date: Mon, 08 Jun 2020 14:30:57 +0000
> Subject: Re: [PVE-User] VM Power Issue
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user


More information about the pve-user mailing list