I've never encountered this particular error. Have you tried rescanning both SRs to see if the disk reappears?
Vates Tech Support
Operators from our Vates Pro Support
-
RE: Failed to migrate vdi
-
RE: Import from VMWARE gives error Cannot read properties of undefined (reading 'name')
There are a few requirements for the import from VMWare process to work correctly --
- Be sure to connect directly to the ESXi server, not vCenter
- The VM needs to have at least one snapshot
- The VM should be stopped prior to import when using ESXi versions newer than v6.5
-
RE: Import from VMWARE gives error Cannot read properties of undefined (reading 'name')
Hi,
Please test XOA on the "latest" release channel, that should work.
-
RE: can't get XOA to install
That's why I said about peering issue. We have 10G here and no bandwidth issue neither.
-
RE: Question on Sata pass through to Windows VM
Okay I missed the part where you said it worked with Linux but not Windows. So to me the issue is probably on Windows itself not detecting the device than an XCP-ng issue
-
RE: VM_BAD_POWER_STATE
@jmm said in VM_BAD_POWER_STATE:
2-full backup,snapshot without ram
Restore ok but at the end vm is in halted state, i think the vm should be in suspended state
I can start vm, not sure where the ram is goneWas the "without ram" above a typo? If not, then halted is the correct state since the memory wasn't captured during the backup.
-
RE: Same CPU XEON 4309Y but migration failed because some CPU features missing !
It could be microcode update and BIOS update making that change. Since they are not in the same pool, this can be expected. Indeed, migrate to the more recent, upgrade the old one/reboot and that should do the trick.
-
RE: Single disk backup
If a schedule parameter to ignore NOBAK is fine since you can create an extra schedule in the same job, that should be doable. What do you think @florent ?