[GH-ISSUE #79] Can't snapshot a VM without disk #73

Closed
opened 2026-02-26 17:44:17 +03:00 by kerem · 4 comments
Owner

Originally created by @Impact123 on GitHub (Sep 5, 2023).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/79

What happened?

When attempting to snapshot a VM without a hard disk an error is thrown.
Skip VM problem storage space out of 95%

When a disk exists, whether attached or not, it works fine. As you can see below I also have enough space available.
A VM without a disk is very rare thing, of course, but since this works perfectly fine via the proxmox GUI I consider this a bug.

Expected behavior

A snapshot should be possible even without a disk attached.

Relevant log output

$ cv4pve-autosnap --host 'xxx' --vmid='104' --username 'xxx' --password 'xxx' snap --label daily --keep 7
ACTION Snap
PVE Version:      8.0.4
VMs:              104
Label:            daily
Keep:             7
State:            False
Only running:     False
Timeout:          30 sec.
Timestamp format: yyMMddHHmmss
Max % Storage :   95%
                  Storage      Type     Valid   Used %    Disk Size  Disk Usage
                pve/local       dir        Ok      13.1    98.25 GB    12.89 GB
             pve/ssdstore   lvmthin        Ok      19.2      800 GB   153.52 GB
----- VM 104 qemu stopped -----
VM 104 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent
Skip VM problem storage space out of 95%
Total execution 00:00:00.1896465


### Proxmox VE Version

8.0.4

### Version (bug)

1.14.8

### Version (working)

_No response_

### On what operating system are you experiencing the issue?

Linux

### Pull Request

- [ ] I would like to do a Pull Request
Originally created by @Impact123 on GitHub (Sep 5, 2023). Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/79 ### What happened? When attempting to snapshot a VM without a hard disk an error is thrown. `Skip VM problem storage space out of 95%` When a disk exists, whether attached or not, it works fine. As you can see below I also have enough space available. A VM without a disk is very rare thing, of course, but since this works perfectly fine via the proxmox GUI I consider this a bug. ### Expected behavior A snapshot should be possible even without a disk attached. ### Relevant log output ```shell $ cv4pve-autosnap --host 'xxx' --vmid='104' --username 'xxx' --password 'xxx' snap --label daily --keep 7 ACTION Snap PVE Version: 8.0.4 VMs: 104 Label: daily Keep: 7 State: False Only running: False Timeout: 30 sec. Timestamp format: yyMMddHHmmss Max % Storage : 95% Storage Type Valid Used % Disk Size Disk Usage pve/local dir Ok 13.1 98.25 GB 12.89 GB pve/ssdstore lvmthin Ok 19.2 800 GB 153.52 GB ----- VM 104 qemu stopped ----- VM 104 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent Skip VM problem storage space out of 95% Total execution 00:00:00.1896465 ``` ``` ### Proxmox VE Version 8.0.4 ### Version (bug) 1.14.8 ### Version (working) _No response_ ### On what operating system are you experiencing the issue? Linux ### Pull Request - [ ] I would like to do a Pull Request
kerem 2026-02-26 17:44:17 +03:00
Author
Owner

@franklupo commented on GitHub (Sep 5, 2023):

Hi,
Why vm without disks? You can exclude using "-104" from the vmid parameter.

Best regards

<!-- gh-comment-id:1706249083 --> @franklupo commented on GitHub (Sep 5, 2023): Hi, Why vm without disks? You can exclude using "-104" from the vmid parameter. Best regards
Author
Owner

@Impact123 commented on GitHub (Sep 5, 2023):

This particular VM is mostly used for testing various live distributions. I wanted to still be able to easily revert to older VM settings.
It took me a minute to figure out how to build this but it works fine. Thanks!

<!-- gh-comment-id:1706964852 --> @Impact123 commented on GitHub (Sep 5, 2023): This particular VM is mostly used for testing various live distributions. I wanted to still be able to easily revert to older VM settings. It took me a minute to figure out how to build this but it works fine. Thanks!
Author
Owner

@franklupo commented on GitHub (Sep 5, 2023):

I fix the problem

<!-- gh-comment-id:1707334089 --> @franklupo commented on GitHub (Sep 5, 2023): I fix the problem
Author
Owner

@Impact123 commented on GitHub (Sep 5, 2023):

You did. I just wanted to let you know that I tested the change and the issue is fixed.

<!-- gh-comment-id:1707352032 --> @Impact123 commented on GitHub (Sep 5, 2023): You did. I just wanted to let you know that I tested the change and the issue is fixed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cv4pve-autosnap#73
No description provided.