FIRST LOOK | QNAP Virtualization Station 4.0 BETA Complete Overview + WINDOWS 11 Setup Guide

[@speedbird737]

thanks Craig fantastic instructional video - high standard as usual - many thanks!

[@orangediveteam]

Thanks Craig for introducing the beta version.

[@MikeFaucher]

Excellent Demo! Look forward to testing this out.

[@QNAPUK]

Thanks Mike!

[@DavidM2002]

What a great walk through and teaching / learning experience. If you make another video now that the final version of VS has been released, I'd love to see you create a VM from an existing Windows desktop installation. There is also a good video from SpaceRex on using Windows Remote Desktop Connection to connect to and use your VM that I find really helpful and preferred rather than logging into the VM via QTS. Many thanks Craig.

[@QNAPUK]

You mean porting a physical Windows installation over to being virtual in Virtualisation Station?

[@DavidM2002]

@@QNAPUK Yes, I think people abbreviate that as P2V. I managed to use VMware to convert my physical Windows 10 to vmx \ vmdk in order to then import it to my QNAP NAS. However, once I started got into the import process in Virtualization Stn, I got as far as " Import Virtual Machine \ Local device \ vmx file ", but then the "Next" button stayed grayed out so I could not proceed. I'm guessing that's why this is still in beta so I'll have to wait for final release.

[@byrd203]

at the Moment on this screen 12:30, you click sign in Options Local account is under there

[@frostmedia]

is there a feedback-hub or i have to write the support am i using the beta version?

[@michelecastellazzi8271]

Hi, By default, the maximum number of snapshots of VMs is defined by disk size. But, there is a way to limit this number (ie. if I define 3 max VMs snapshots, when planification wants to create a new one, virtualization station deletes the oldest and create a new snapshot) ? Thanks

[@tizianofi]

If there is a folder selected as media content in multimedia console , Virtualization Station 4.0 isn't able to browse folders for selecting disk path, or default vm folder. Before with Virtualization Station 3 all worked. That's what happen on my QNAP.

[@draukuxan1081]

Thanks for the video, the update looks promising.

[@DavidM2002]

I'm a little confused by the location of the new VM. At 4:03 File Location is shown as /Virtual which appears to be a default. When you go ahead to 4:44 there is a setting for Image Path and the folder icon which appears to allow that location to be changed. How is the location set at 4:03 different from that at 4:44 ?

[@QNAPUK]

I looked at the video... I created a share called Virtual, so I set this as my path. Not sure what you mean at 4:44 because there is no paths shown there. But this box for selecting an image is if you already have a HDD image you want to select, I chose new image as I want a new image for this VM that has not been used before. I sometimes will add a second HDD into the VM using my own image, often have test data in a second img file that I mount into each VM and this way just mounting it saves me having to copy it into the VM each time.

[@DavidM2002]

@@QNAPUKThanks Craig, I think I figured it out. It looks like you set your /Virtual share in Preferences as your default location.

[@TSOGSocial]

Will there ever be an option for network boot PXE so we can use things like FOG Project or etc?

[@QNAPUK]

I'll submit a feature request and see what the response is.

[@SilesianWarrior]

Is it possible for other files to infringe upon VM? Let's say i created a VM with 512GB disk, but in the meantime someone filled the NAS Volume with data, so there's not actually 512GB for it left. What happens if i fire up the VM and try to fill it to the brim? The windows inside won't know there's not enough space. Made that blunder in proxmox once, i'd like to avoid it.

[@QNAPUK]

Probably similar to Proxmox, VM won't be able to function. I'd recommend creating a separate volume/share for your VM's that is a Thick Volume, this way it pre-allocates the space from the rest of the NAS just for the VM volume/share, no matter what others do elsewhere, it will not interrupt the VM.

[@ChavdarIvanov4]

No end of problems running the beta version under QTS 5.1. The latest one, which is a show-stopper, stops me from running any guest with a network adapter configured, with the message "Failed to start virtual machine "...". Error message: 'VSwitch' object has no attribute 'vswitch_name'". If I remove all the network adapters, the VM starts, but is obviously useless. This is most likely some incompatibility between QTS 5.1 and this beta, which hasn't been addressed properly. Running QTS 5.1 beta at one stage forces you to upgrade to the beta version of Virtualisation Station, claiming that v.3 is incompatible (even if v.3 ran OK immediately after my update to QTS 5.1); thereafter v.4 ran OK initially, but stopped working as described following a restart of my TS-453E.

[@QNAPUK]

Beta software is definitely going have some thing that need to be sorted, try again when it is released as a final version or perhaps roll back to QTS 5.0.x

[@ChavdarIvanov4]

@@QNAPUK The problem is, anybody who is willing to test QTS5.1 beta is likely to be interested in Virtualisation Station as well. QTS5.1beta was released in March 2023, the latest beta of Virtualisation Station - in December 2022. There should have been a closer issued and at least cursory tested beta of the latter, suitable for testing under QTS5.1. Disappointing a bit, this is my first Qnap device after having used a lot of other similar solutions, I am still to decide on it.

[@QNAPUK]

If you are evaluating us as a NAS vendor, my recommendation would be to not use the Beta software as the experience is not the same as final release.

[@quocd6171]

For me, the performance on Windows is still bad because there is still no 3D acceleration for iGPU, so it uses very high CPU usage. I know VS is based on QEMU, it never supported 3D acceleration, only GPU passthrough that only very expensive NAS support it. I guess the problem would be solved if QNAP added VirtualBox as an alternative VM engine.