vzdump to stdout

[michabbs]

I try to send backup images to stdout for further processing. Example:

vzdump 111 --mode snapshot --dumpdir /tmp --stdout >test.tst

It works very well with LXC containers. But for qemu vm's it finishes with error:

ERROR: Backup of VM 200 failed - command '/usr/bin/vma create -v -c /tmp/vzdump-qemu-200-2020_05_06-09_24_39.tmp/qemu-server.conf exec:cat' failed: Bad filehandle: =5 at /usr/share/perl/5.28/IPC/Open3.pm line 58.

Any ideas?

 

[fabian]

please include the VM config, the storage config and pveversion -v output.

 

[michabbs]

Here it is:

pve-manager/6.1-8/806edfe1 (running kernel: 5.3.18-3-pve)
root@zahadum:/home/abackup/bin# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-23
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

 

[fabian]

the config contents are still missing

 

[fabian]

does your VM not have a single disk that is included in the backup?

 

[michabbs]

It's diskless vm...

bios: ovmf
boot: n
cores: 1
hotplug: network,usb
memory: 1024
name: diskless100
net0: virtio=08:00:27:6D:56:10,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=130e79ce-9591-48b6-9b83-a0b0692146b7
sockets: 1
vmgenid: 38b8d8f6-997c-46f3-a3a5-8d490b730769
vmstatestorage: rpool

 

[fabian]

should hopefully be fixed soon: https://pve.proxmox.com/pipermail/pve-devel/2020-May/043395.html

 

[michabbs]

Excellent! (well, kind of...)
Thank you!

 

[michabbs]

By the way... Why are there plenty of warnings regarding uninitialized values? Generally everything works fine, but looks really ugly... :-(

INFO: starting new backup job: vzdump 106 --dumpdir /tmp --mode snapshot
Use of uninitialized value in string eq at /usr/share/perl5/PVE/VZDump.pm line 645.
Use of uninitialized value in string ne at /usr/share/perl5/PVE/VZDump.pm line 704.
Use of uninitialized value in string eq at /usr/share/perl5/PVE/VZDump.pm line 714.
Use of uninitialized value in string eq at /usr/share/perl5/PVE/VZDump.pm line 729.
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp1435 for temporary files
INFO: Starting Backup of VM 106 (lxc)
INFO: Backup started at 2020-05-06 15:50:12
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: test1
INFO: excluding volume mount point mp1 ('/mnt/xyz') from backup
Use of uninitialized value in string eq at /usr/share/perl5/PVE/VZDump/LXC.pm line 301.
INFO: sending archive to stdout
Use of uninitialized value in string eq at /usr/share/perl5/PVE/VZDump/LXC.pm line 354.
INFO: Total bytes written: 688291840 (657MiB, 13MiB/s)
INFO: Finished Backup of VM 106 (00:00:54)
INFO: Backup finished at 2020-05-06 15:51:06
Use of uninitialized value in string eq at /usr/share/perl5/PVE/VZDump.pm line 1006.
INFO: Backup job finished successfully

 

[fabian]

I saw those as well and already sent fixes to the list - they are harmless though.