start error code 1

[LeMaAt]

after rebooting my host one of the VMs doesnt want to start any more:

Failed to create message: Input/output error
TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 112 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 112 -chardev 'socket,id=qmp,path=/var/run/qemu-server/112.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/112.vnc,x509,password -pidfile /var/run/qemu-server/112.pid -daemonize -smbios 'type=1,uuid=257fee98-b4ef-4ca2-a5a0-83742667ca0e' -name ServerTwo -smp '24,sockets=2,cores=12,maxcpus=24' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 40960 -k de -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -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:e3a47ebb694c' -drive 'file=/var/lib/vz/images/112/vm-112-disk-1.raw,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/virtio-win-0.1.141.iso,if=none,id=drive-ide1,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=200' -drive 'file=/var/lib/vz/template/iso/SW_DVD9_Win_Server_STD_CORE_2019_1809.1_64Bit_German_DC_STD_MLF_X22-02972.ISO,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201' -drive 'file=/var/lib/vz/template/iso/SW_DVD9_Exchange_Svr_2019_CU_MultiLang_-2_Std_Ent_.iso_MLF_X22-11774.ISO,if=none,id=drive-ide3,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=1,drive=drive-ide3,id=ide3,bootindex=202' -netdev 'type=tap,id=net0,ifname=tap112i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=36:38:65:65:62:36,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

i would be glad to hear your ideas.

 

[dietmar]

What error message do you get when you start on the console?

# qm start 112

 

[LeMaAt]

the same as above with one line more:
ipcc_send_rec failed: file too large

 

[dietmar]

Strange. Are there any large files on /etc/pve/? How large is the VM config file?

 

[LeMaAt]

well basically it's still a proxmox 4.1
5 VMs in the machine, before the reboot all of them were running without problems.
currently 3 of them running, 112 doesnt want to start although i reduced ram and cores and shut down another (111).
in /etc/pce there are no config files, i found themn in /etc/pve/nodes/proxmox/qemu-server
112.conf is 539, biggest is 101.conf with 1.4k

the setting is a change-win2008-to-win2016-servers
machines 100,101 and 102 will be replaced with 111 and 112.
of course the proxmox update is planned too.
i already tried the backup of 112 with no success. the 112.conf file looks okay, at least not corrupt or so.

 

[LeMaAt]

thank you dietmar for your suggestions.
if i try
#qm start 112
now i still get the error lines, but no 'file too large' now

 

[LeMaAt]

strange: when i restored a backup it didn't work.
when i made a clone the VM is running again.

can i safely delete the original VM and all its files?

 

[LeMaAt]

... if i may ask?

 

[fiona]

Hi,

strange: when i restored a backup it didn't work.
when i made a clone the VM is running again.

can i safely delete the original VM and all its files?

If you created a full clone (you can check the task log for the clone operation), it should be save to delete the original VM. If you delete the VM via PVE its configuration and virtual disks will be deleted. Which files do you mean by

all its files

?