You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently ran into an issue with a Windows 10 VM, ESET EndPoint Security 7.2 and XCP-ng 8.0.0:
We created a new virtual drive for the VM. It showed up in the Windows drive manager and we were able to initialize it. But when we tried to format it, Windows raised an error message, that it is not possible to access this drive. After two hours we had the idea to check the media control log of the ESET Virus EndPoint Security Software. The result: XCP-ng virtual drives seem to look like an USB drive to the Virtual machine. Thus the Virus Software is blocking the device. This does not happen when using e.g. VMware. There seems to be some difference how the Hypervisors declare drives to the system.
The text was updated successfully, but these errors were encountered:
Hi folks!
Thanks for your great work!
We recently ran into an issue with a Windows 10 VM, ESET EndPoint Security 7.2 and XCP-ng 8.0.0:
We created a new virtual drive for the VM. It showed up in the Windows drive manager and we were able to initialize it. But when we tried to format it, Windows raised an error message, that it is not possible to access this drive. After two hours we had the idea to check the media control log of the ESET Virus EndPoint Security Software. The result: XCP-ng virtual drives seem to look like an USB drive to the Virtual machine. Thus the Virus Software is blocking the device. This does not happen when using e.g. VMware. There seems to be some difference how the Hypervisors declare drives to the system.
The text was updated successfully, but these errors were encountered: