StarWind Software

iSCSI, FCoE, AoE solutions for SMBs and Corporations. VTL, CDP and other advanced features.
http://forums.starwindsoftware.com/

Unable to create new VM's using the same ID

http://forums.starwindsoftware.com/viewtopic.php?f=5&t=7442

Page 1 of 1

Unable to create new VM's using the same ID

Posted: Tue Jul 14, 2026 6:45 am
by nvanaert
Hello everyone,

We're using the Starwind starlvm plugin in Proxmox VE and are experiencing issues. It seems that after we've deleted a virtual machine and try to re-create a virtual machine with the same ID, we're getting the error message below.

I haven´t cleaned it up yet with dmsetup as the plugin explicitly states not to do so and decided to ask the question here. Is it safe to clean this up?

Code: Select all

()
unsupported storage of vg 'standard'
unsupported storage of vg 'standard'
 creating vm-1001-disk-0 (size 528K) from storeid standard, vg standard
 creating lv vm-1001-disk-0 (size 0.515625M) from pool standard/lvmth-1001
  Rounding up size to full physical extent 4.00 MiB
  device-mapper: message ioctl on  (252:19) failed: Device or resource busy
  Failed to process message "delete 2".
TASK ERROR: unable to create VM 1001 - lvcreate thin lv 'standard/vm-1001-disk-0' error:   Failed to suspend standard/lvmth-1001 with queued messages.
Some additional information

Code: Select all

root@hv02:~# pvesm list standard --vmid 1001
unsupported storage of vg 'standard'
Volid Format  Type      Size VMID

Code: Select all

 Size VMID
root@hv02:~#   for i in 20 21 22 23; do     echo "=== dm-$i ===";     cat /sys/block/dm-$i/dm/name;     dmsetup table /dev/dm-$i;   done
=== dm-20 ===
standard-lvmth--1001
0 134225920 linear 252:19 0
=== dm-21 ===
standard-vm--1001--disk--0
0 8192 thin 252:19 1
=== dm-22 ===
standard-vm--1001--disk--1
0 134217728 thin 252:19 2
=== dm-23 ===
standard-vm--1001--disk--2
0 8192 thin 252:19 3

Code: Select all

root@hv02:~#   dmsetup status standard-lvmth--1001-tpool
0 134225920 thin-pool 3 3178/17408 323687/1048640 - rw no_discard_passdown queue_if_no_space - 1024

Re: Unable to create new VM's using the same ID

Posted: Wed Jul 15, 2026 4:40 am
by yaroslav (staff)
Welcome to StarWind Forum. Please share the following info
- The message plugin shows that it was interpreted as a plugin's "don't do so".
- Proxmox version
- Plugin version.
- Storage provider.

Thanks!

Re: Unable to create new VM's using the same ID

Posted: Wed Jul 15, 2026 6:39 am
by nvanaert
yaroslav (staff) wrote: ↑
Wed Jul 15, 2026 4:40 am
 Welcome to StarWind Forum. Please share the following info
- The message plugin shows that it was interpreted as a plugin's "don't do so".
- Proxmox version
- Plugin version.
- Storage provider.

Thanks!
Yaroslav,

Thank you for your reply.
- The Proxmox VE Version is 9.2.3
- The Plugin version is starwind-proxmox-plugin-pve9/trixie,now 1.1.41 amd64 [installed] This was updated yesterday. It was 1.1.39.
- The Storage Provider is starlvm in the Proxmox GUI, which was installed using: https://www.starwindsoftware.com/resour ... ion-guide/ as the manual.

Re: Unable to create new VM's using the same ID

Posted: Wed Jul 15, 2026 6:52 am
by yaroslav (staff)
Thanks for your update. Please share the storage vendor that is masked behind starlvm.
The newest plugin might not work with 9.2.3; we are working on compatibility.

Re: Unable to create new VM's using the same ID

Posted: Wed Jul 15, 2026 7:31 am
by nvanaert
Yaroslav,

If you mean the actual device type with storage vendor:
- It's a Fujitsu Eternus DX200 M5 SAN connected via 10Gbps iSCSI to 5 hosts (all in the same Proxmox VE cluster).
- This is configured into 1 RAID Group with 2x RAID-5+0 arrays with 2 active hot spare.
- This is divided into 2 LUN's A 60TB LUN for standard virtual machines and a legacy 5TB LUN for old virtual machines on a separate cluster (this is divided by LUN so not of influence).
- This is all connected via FS switches via dual 10Gbps iSCSI links with Jumbo Frames enabled

Code: Select all

multipath -ll
3600000e00d3200000032a20000010000 dm-2 FUJITSU,ETERNUS_DXL
size=55T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 12:0:0:0 sde 8:64 active ready running
| `- 14:0:0:0 sdf 8:80 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
  |- 11:0:0:0 sdc 8:32 active ready running
  `- 13:0:0:0 sdd 8:48 active ready running

Code: Select all

pvesm status
unsupported storage of vg 'standard'
Name            Type     Status     Total (KiB)      Used (KiB) Available (KiB)        %
dump             dir     active      1152069324         6676880      1086796812    0.58%
local            dir     active       758719520         7722104       719055340    1.02%
pbs-test         pbs     active       463330076        20824652       418896136    4.49%
standard     starlvm     active     59055796224      3648397312     55407398912    6.18%

Code: Select all

starlvm: standard
        vgname standard
        content images
        shared 1

Code: Select all

pvdisplay -m --config 'devices { filter = [ "a|.*|" ] }' /dev/mapper/3600000e00d3200000032a20000010000 2>/dev/null
  --- Physical volume ---
  PV Name               /dev/mapper/3600000e00d3200000032a20000010000
  VG Name               standard
  PV Size               55.00 TiB / not usable 4.00 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              14417919
  Free PE               13527197
  Allocated PE          890722
  PV UUID               osT7V0-tnwI-djTD-JRep-tohi-VWqj-gyiV7i
   
  --- Physical Segments ---
  Physical extent 0 to 15:
    Logical volume      /dev/standard/lvol0_pmspare
    Logical extents     0 to 15
  Physical extent 16 to 32833:
    FREE
  Physical extent 32834 to 32834:
    Logical volume      /dev/standard/lvol0_pmspare
    Logical extents     16 to 16
  Physical extent 32835 to 32835:
    Logical volume      /dev/standard/lvmth-1000_tdata
    Logical extents     0 to 0
  Physical extent 32836 to 32863:
    Logical volume      /dev/standard/lvmth-1000_tmeta
    Logical extents     0 to 27
  Physical extent 32864 to 32864:
    Logical volume      /dev/standard/lvmth-1003_tdata
    Logical extents     0 to 0
  Physical extent 32865 to 32890:
    Logical volume      /dev/standard/lvmth-1003_tmeta
    Logical extents     0 to 25
  Physical extent 32891 to 32891:
    Logical volume      /dev/standard/lvmth-1004_tdata
    Logical extents     0 to 0
  Physical extent 32892 to 32917:
    Logical volume      /dev/standard/lvmth-1004_tmeta
    Logical extents     0 to 25
  Physical extent 32918 to 32918:
    Logical volume      /dev/standard/lvmth-1005_tdata
    Logical extents     0 to 0
  Physical extent 32919 to 32944:
    Logical volume      /dev/standard/lvmth-1005_tmeta
    Logical extents     0 to 25
  Physical extent 32945 to 32945:
    Logical volume      /dev/standard/lvmth-1010_tdata
    Logical extents     0 to 0
  Physical extent 32946 to 33321:
    Logical volume      /dev/standard/lvmth-1010_tmeta
    Logical extents     0 to 375
  Physical extent 33322 to 33322:
    Logical volume      /dev/standard/lvmth-1011_tdata
    Logical extents     0 to 0
  Physical extent 33323 to 33698:
    Logical volume      /dev/standard/lvmth-1011_tmeta
    Logical extents     0 to 375
  Physical extent 33699 to 49218:
    FREE
  Physical extent 49219 to 49219:
    Logical volume      /dev/standard/lvmth-1001_tdata
    Logical extents     0 to 0
  Physical extent 49220 to 49236:
    Logical volume      /dev/standard/lvmth-1001_tmeta
    Logical extents     0 to 16
  Physical extent 49237 to 65620:
    Logical volume      /dev/standard/lvmth-1001_tdata
    Logical extents     1 to 16384
  Physical extent 65621 to 65629:
    Logical volume      /dev/standard/lvol0_pmspare
    Logical extents     17 to 25
  Physical extent 65630 to 91229:
    Logical volume      /dev/standard/lvmth-1000_tdata
    Logical extents     1 to 25600
  Physical extent 91230 to 91231:
    Logical volume      /dev/standard/lvol0_pmspare
    Logical extents     26 to 27
  Physical extent 91232 to 93911:
    Logical volume      /dev/standard/lvmth-1000_tdata
    Logical extents     25601 to 28280
  Physical extent 93912 to 119511:
    Logical volume      /dev/standard/lvmth-1003_tdata
    Logical extents     1 to 25600
  Physical extent 119512 to 145111:
    Logical volume      /dev/standard/lvmth-1004_tdata
    Logical extents     1 to 25600
  Physical extent 145112 to 170711:
    Logical volume      /dev/standard/lvmth-1005_tdata
    Logical extents     1 to 25600
  Physical extent 170712 to 171059:
    Logical volume      /dev/standard/lvol0_pmspare
    Logical extents     28 to 375
  Physical extent 171060 to 555059:
    Logical volume      /dev/standard/lvmth-1010_tdata
    Logical extents     1 to 384000
  Physical extent 555060 to 939059:
    Logical volume      /dev/standard/lvmth-1011_tdata
    Logical extents     1 to 384000
  Physical extent 939060 to 14417918:
    FREE

Code: Select all

cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,import,backup,vztmpl

dir: dump
        path /mnt/dump
        content iso,vztmpl,import,images,snippets
        prune-backups keep-all=1
        shared 0

starlvm: standard
        vgname standard
        content images
        shared 1

pbs: pbs-test
        datastore backup-test
        server 10.255.15.252
        fingerprint bc:a1:92:4f:d1:ae:b3:17:e4:63:fd:13:a2:ad:f2:d4:bb:e4:ae:d1:53:f2:38:b1:a5:c4:75:7b:2d:ac:2e:d0
        username root@pam

Re: Unable to create new VM's using the same ID

Posted: Wed Jul 15, 2026 9:40 am
by yaroslav (staff)
Please pull the plugin logs and share them with me here or https://www.starwindsoftware.com/support-form (your case number is 1521461)
/opt/starwind/starwind-proxmox-plugin/collect_pve_logs.sh
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited