Jump to content
Updated Privacy Statement
  • 0

Xenserver 7 “xe vdi-resize" this VDI is in use by some other operation


norman horn

Question

The Xenserver 7 has 5 VMs (W2K12R2). I can't not expand the disk of a VM. The message appears:

This operation cannot be performed because this VDI is in use by some other operation
vdi: 8de90b86-4318-409a-8b33-28d066fd1484 (Windows Server 2012 R2 (64-bit) 0)
operation: resize

How can I find out which operation prevents expansion?

 

Link to comment

4 answers to this question

Recommended Posts

  • 0

I can't find anything. Maybe you see something?
power-state ( RO): halted - looks normal or what should stand here?
The other VMs I can extend all. Only this VM unfortunately not.

xe vm-list uuid=52080f94-c66b-42a5-b94a-8a7c6056ea9f params=all
uuid ( RO)                          : 52080f94-c66b-42a5-b94a-8a7c6056ea9f
                    name-label ( RW): Fileserver
              name-description ( RW):
                  user-version ( RW): 1
                 is-a-template ( RW): false
                 is-a-snapshot ( RO): false
                   snapshot-of ( RO): <not in database>
                     snapshots ( RO):
                 snapshot-time ( RO): 19700101T00:00:00Z
                 snapshot-info ( RO):
                        parent ( RO): <not in database>
                      children ( RO):
             is-control-domain ( RO): false
                   power-state ( RO): halted
                 memory-actual ( RO): 15340212224
                 memory-target ( RO): <expensive field>
               memory-overhead ( RO): 133169152
             memory-static-max ( RW): 16106127360
            memory-dynamic-max ( RW): 16106127360
            memory-dynamic-min ( RW): 10737418240
             memory-static-min ( RW): 1073741824
              suspend-VDI-uuid ( RW): <not in database>
               suspend-SR-uuid ( RW): 71d52379-7d45-f593-0fce-6bcc95db9b8c
                  VCPUs-params (MRW): weight: 256
                     VCPUs-max ( RW): 5
              VCPUs-at-startup ( RW): 5
        actions-after-shutdown ( RW): Destroy
          actions-after-reboot ( RW): Restart
           actions-after-crash ( RW): Restart
                 console-uuids (SRO): 5fee240c-e7d9-bedb-1644-b47619210735
                      platform (MRW): timeoffset: 7215; videoram: 8; cores-per-socket: 1; nx: true; viridian_reference_tsc: true; device_id: 0002; acpi: 1; apic: true; viridian_time_ref_count: true; hpet: true; viridian: true; pae: true; vga: std
            allowed-operations (SRO): changing_dynamic_range; migrate_send; pool_migrate; changing_VCPUs_live; suspend; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause; checkpoint; snapshot
            current-operations (SRO):
            blocked-operations (MRW):
           allowed-VBD-devices (SRO): <expensive field>
           allowed-VIF-devices (SRO): <expensive field>
                possible-hosts ( RO): <expensive field>
               HVM-boot-policy ( RW): BIOS order
               HVM-boot-params (MRW): order: c
         HVM-shadow-multiplier ( RW): 1.000
                     PV-kernel ( RW):
                    PV-ramdisk ( RW):
                       PV-args ( RW):
                PV-legacy-args ( RW):
                 PV-bootloader ( RW):
            PV-bootloader-args ( RW):
           last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 17cbfbff-f7fa3223-2d93fbff-00000123-00000001-001c0fbb-00000000-00000000-00000000
              last-boot-record ( RO): <expensive field>
                   resident-on ( RO): a422614f-5403-4469-b6dc-8f29d01108d0
                      affinity ( RW): a422614f-5403-4469-b6dc-8f29d01108d0
                  other-config (MRW): vgpu_pci: ; auto_poweron: false; XenCenter.CustomFields.XSB_del_standby_VM_after: 3; XenCenter.CustomFields.XSB_restore_srname: <Name of SR>; XenCenter.CustomFields.XSB_vmrestore: false; XenCenter.CustomFields.XSB_keep_versions: 3; XenCenter.CustomFields.XSB_kill_job_at: NEVER; XenCenter.CustomFields.XSB_Last_Backup: NEVER; XenCenter.CustomFields.XSB_State: IDLE; XenCenter.CustomFields.XSB_Schedule: online@MANUAL; XenCenter.CustomFields.XSB_mailuser: ; XenCenter.CustomFields.XSB_mailsubject: ; XenCenter.CustomFields.XSB_mailserver: ; XenCenter.CustomFields.XSB_mailto: ; XenCenter.CustomFields.XSB_mailfrom: ; XenCenter.CustomFields.XSB_rsync: ; XenCenter.CustomFields.XSB_restore_sources: ; XenCenter.CustomFields.XSB_UseSTARTTLS: ; XenCenter.CustomFields.XSB_UseTLS: ; XenCenter.CustomFields.XSB_switchoff: ; XenCenter.CustomFields.XSB_language: ; mac_seed: 4a670dfc-2f1c-73ff-d322-4f49416abd39; install-methods: cdrom; base_template_name: Windows Server 2012 R2 (64-bit)
                        dom-id ( RO): 58
               recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1610612736000" /><restriction field="vcpus-max" max="32" /><restriction property="number-of-vbds" max="255" /><restriction property="number-of-vifs" max="7" /><restriction field="has-vendor-device" value="true" /></restrictions>
                 xenstore-data (MRW): vm-data:
    ha-always-run ( RW) [DEPRECATED]: false
           ha-restart-priority ( RW):
                         blobs ( RO):
                    start-time ( RO): 20190609T15:25:36Z
                  install-time ( RO): 20170216T15:08:15Z
                  VCPUs-number ( RO): 5
             VCPUs-utilisation (MRO): <expensive field>
                    os-version (MRO): name: Microsoft Windows Server 2012 R2 Standard|C:\Windows|\Device\Harddisk0\Partition2; distro: windows; major: 6; minor: 2; spmajor: 0; spminor: 0
            PV-drivers-version (MRO): major: 7; minor: 0; micro: 0; build: 20000
         PV-drivers-up-to-date ( RO): true
                        memory (MRO):
                         disks (MRO):
                      networks (MRO): 0/ip: 192.168.0.8
           PV-drivers-detected ( RO): true
                         other (MRO): platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-suspend: 1; feature-balloon: 1; balloon-active: 0; feature-shutdown: 1; error: SLGetWindowsInformationDWORD : -1073418222 failed.; feature-setcomputername: 1; feature-xs-batcmd: 1; feature-ts2: 1; feature-ts: 1; feature-static-ip-setting: 1; data-ts: 1
                          live ( RO): true
    guest-metrics-last-updated ( RO): 20190610T06:30:52Z
           can-use-hotplug-vbd ( RO): true
           can-use-hotplug-vif ( RO): true
      cooperative ( RO) [DEPRECATED]: <expensive field>
                          tags (SRW):
                     appliance ( RW): <not in database>
                   start-delay ( RW): 0
                shutdown-delay ( RW): 0
                         order ( RW): 0
                       version ( RO): 0
                 generation-id ( RO): 8971170721576378551:2759743669619205232
     hardware-platform-version ( RO): 0
             has-vendor-device ( RW): false

 

Link to comment
  • 0

I've ejected DVDs, even several times. The VM had displayed the DVD at the last reboot. He didn't want to restart. I removed the DVD and then he started.

 


xe vm-cd-eject --force vm=Fileserver
Operation could not be performed because the drive is empty
vbd: c686b6f1-1450-c533-4090-a09d1cee41eb

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...