I was having an issue with the video sizing (read: driver issue) as well on my existing Windows 11 QVM's and this resolved that issue *AND* helped with a couple of others I didn't know I was suffering from :-) Thanks for the great stuff. I'm not sure I would have found the RHEL VirtIO files on my own without your video and links. Very fluid instructions and helpful. BTW - after watching the first half of the video and downloading the RHEL .iso I built a test VM to follow along with your video *before* jacking with my existing Win11 QVM's. As part of that test build I deviated a little and configured the test QVM with 2- CD/DVD devices (the first with Win11 ISO, the second with the RHEL ISO you linked too) from the very beginning. I also pre-chose QXL video and VirtIO network. When the QVM booted and the installer squawked at me about "no drive available for installation" (no VirtIO drivers), I was able to simply tell it to go get updated drivers from the secondary CD (VirtIO .iso), at which point the Win11installer found the drivers needed, mounted the virtual drive (via the now installed VirtIO SCSI drivers) and then completed the Windows 11 as per usual. Interestingly enough the base installer did NOT go-looking-for nor install the QXL video drivers or VirtIO network drivers natively from the secondary .iso; so I still had to run the VirtIO Guest Tools executable, but that was a minor issue and your tutorial was SUPER helpful. Thanks again.
I've considered trying to find the QNAP guest tools .ISO via ssh, copy it out to a working share on the QNAP where I could get access to it with a Windows workstation. Once I have it copied to my Windows workstation, I'm planning on mounting it with UltraISO; extract and merge the files from the RHEL VirtIO .iso and add the RHEL guest tools .exe then save all of it back to the same QNAP guest tools .iso file name and put it back on the QNAP in the QNAP guest tools .iso location. That way, when I mount the QNAP guest tools .iso for future Windows QVM's I don't have to mount two (2) .iso files for drivers.
Thanks for the very complete description of your experience. It always helps me when I see detail to consider future adjustments and additions to tutorials. Consider coming by chat.scottibyte.com/ to participate in the chat or just to say hi. Thanks again.
Now that you've made this great video, QNAP has "updated" Virtualization Station and completely changed the interface and some of the terminology. Subscribed.
Thx for subscribing. I didn't address virtualization station in my lastest videos, but yes virtualization station now has a similar interface to the new container station 3.0. I tend to favor LXD containers rather than VMs. That being said, it's baffling why QNAP didn't support LXD VMs. Come by chat.scottibyte.com/ to chat.
I followed your instructions step by step and it worked perfectly. A couple of curves due to Virtualization Stn having now been updated to Version 4. Also, I found that using Windows Remote Desktop Connections works even better than connecting through Virtualization Stn. All in, it was a great learning experience with something that I am not at all familiar with. Thanks again.
Excellent. Yes the new virtualization station is quite different. Be sure to watch my videos on using LXDWare LXD Dashboard to manage LXD containers instead of container station. Stop by chat.scottibyte.com/ to chat and discuss.
Great video. There's actually an easier way: when configuring the new VM, add second CD with Integration Tools and then during the installation, when asked select VirtIO driver disk and allow Windows installer to install those VirtIO drivers prior formatting the first system disk. After that, the Windows installer will continue installation. Once Windows installed, just run Integration Tools again to install remaining drivers for graphic and net cards.
Thanks for the kudo. My intent was to cover folks with existing VM's and also new VM's and so that is why I followed this process. I have found the best effort is to cover as many use cases as you can in answering a question. You can mount the ISO and do as you say and I have. It's just not the simplest process for newer users.
The virtIO Drivers are built in to the Guest Tools CD. Add a CD/DVDROM then go to the main settings of virtualization station then click Insert guest tools once at desktop open that cd drive then your see a qnap exe file run it that installs the proper guest tools right from the virtulaztion station it'self
@@scottibyte - AGREED. The VirtIO .iso file you provided in the links are the missing link to this resolution. I've always used the "guest tools" .iso provided by QNAP and they don't resolve some of these issues that you addressed (thanks for the tutorial). @Scottibyte's links to RHEL's newer VirtIO drivers make a huge improvement on QNAP's included guest tools .iso.
set everything to virtio before starting the install of windows start setup go through the setup it will complain no hhd hit browse then go to virt folder then win10 then next click iscs redhat driver that installs the virtio HDD then do browse again then add the virtio ethernet redhat same way no need for downloading guest tools that way just insert guest tools cdrom follow these steps
I tried out my friends synology ds1522+ VM (Running Ubuntu) and, it really struggles to function at all. Its a decent nas but...idk. It just doesn't seem to compare when running a VM on your desktop pc. The nas was upgraded to 32GB ram as well.
The DS1522+ is only a Ryzen R1600 dual core system. Most NAS systems are horribly under-powered for VMs. This was for QNAP users looking to improve performance slightly. The QNAP NAS I am using in the video is on a Ryzen 7 1700 Pro which has 8 cores and 16 threads. If you are looking for a faster way to run a Windows VM, I suggest you watch my video entitled Windows 11 LXD Virtual Machine th-cam.com/video/r0WheXvADHk/w-d-xo.html. I also have a follow-on to it called More Windows 11 LXD Virtual Machine. In those videos, I am demonstrating a LXD VM running Windows 11 on only a Ryzen 5 3550H that is only quad core. That machine is also running 20+ LXD Containers as well and the LXD VM and it performs significantly faster.
Oh and to address the "Ubuntu" VM. I have run an Ubuntu Desktop in a LXD container on relatively low performing NAS units and Ubuntu in a LXD container far outperforms an Ubuntu VM by at least an order of magnitude. That's one huge reason why the channel is devoted to LXD containers.
@@scottibyte Thanks for the reply. Wow, that's quite impressive! I can't say that I've ever heard of LXD containers but, I'll definitely check out those videos you mentioned.
@@woolfy02 Be sure to join chat.scottibyte.com/ so that you can tag up and discuss your questions on container virtualization. LXD containers are like Virtual Machines, but since they share the host kernel they have far less overhead. Unlike a VM, a LXD container can be created in generally under 5 seconds and they boot almost instantly. That's because LXD containers run from images and also do not have to virtualize the hardware like a VM.
I was having an issue with the video sizing (read: driver issue) as well on my existing Windows 11 QVM's and this resolved that issue *AND* helped with a couple of others I didn't know I was suffering from :-) Thanks for the great stuff. I'm not sure I would have found the RHEL VirtIO files on my own without your video and links. Very fluid instructions and helpful. BTW - after watching the first half of the video and downloading the RHEL .iso I built a test VM to follow along with your video *before* jacking with my existing Win11 QVM's. As part of that test build I deviated a little and configured the test QVM with 2- CD/DVD devices (the first with Win11 ISO, the second with the RHEL ISO you linked too) from the very beginning. I also pre-chose QXL video and VirtIO network. When the QVM booted and the installer squawked at me about "no drive available for installation" (no VirtIO drivers), I was able to simply tell it to go get updated drivers from the secondary CD (VirtIO .iso), at which point the Win11installer found the drivers needed, mounted the virtual drive (via the now installed VirtIO SCSI drivers) and then completed the Windows 11 as per usual. Interestingly enough the base installer did NOT go-looking-for nor install the QXL video drivers or VirtIO network drivers natively from the secondary .iso; so I still had to run the VirtIO Guest Tools executable, but that was a minor issue and your tutorial was SUPER helpful. Thanks again.
I've considered trying to find the QNAP guest tools .ISO via ssh, copy it out to a working share on the QNAP where I could get access to it with a Windows workstation. Once I have it copied to my Windows workstation, I'm planning on mounting it with UltraISO; extract and merge the files from the RHEL VirtIO .iso and add the RHEL guest tools .exe then save all of it back to the same QNAP guest tools .iso file name and put it back on the QNAP in the QNAP guest tools .iso location. That way, when I mount the QNAP guest tools .iso for future Windows QVM's I don't have to mount two (2) .iso files for drivers.
Thanks for the very complete description of your experience. It always helps me when I see detail to consider future adjustments and additions to tutorials. Consider coming by chat.scottibyte.com/ to participate in the chat or just to say hi. Thanks again.
Now that you've made this great video, QNAP has "updated" Virtualization Station and completely changed the interface and some of the terminology. Subscribed.
Thx for subscribing. I didn't address virtualization station in my lastest videos, but yes virtualization station now has a similar interface to the new container station 3.0. I tend to favor LXD containers rather than VMs. That being said, it's baffling why QNAP didn't support LXD VMs. Come by chat.scottibyte.com/ to chat.
Great video, thanks a lot. Made a huge difference on two different QNAPs I run Windows VMs on.
Great to hear. I hope you subscribe and come by chat.scottibyte.com/ to chat.
I followed your instructions step by step and it worked perfectly. A couple of curves due to Virtualization Stn having now been updated to Version 4. Also, I found that using Windows Remote Desktop Connections works even better than connecting through Virtualization Stn. All in, it was a great learning experience with something that I am not at all familiar with. Thanks again.
Excellent. Yes the new virtualization station is quite different. Be sure to watch my videos on using LXDWare LXD Dashboard to manage LXD containers instead of container station. Stop by chat.scottibyte.com/ to chat and discuss.
Great video. There's actually an easier way: when configuring the new VM, add second CD with Integration Tools and then during the installation, when asked select VirtIO driver disk and allow Windows installer to install those VirtIO drivers prior formatting the first system disk. After that, the Windows installer will continue installation. Once Windows installed, just run Integration Tools again to install remaining drivers for graphic and net cards.
Thanks for the kudo. My intent was to cover folks with existing VM's and also new VM's and so that is why I followed this process. I have found the best effort is to cover as many use cases as you can in answering a question. You can mount the ISO and do as you say and I have. It's just not the simplest process for newer users.
The virtIO Drivers are built in to the Guest Tools CD. Add a CD/DVDROM then go to the main settings of virtualization station then click Insert guest tools once at desktop open that cd drive then your see a qnap exe file run it that installs the proper guest tools right from the virtulaztion station it'self
True, but not all of the Virtio drivers are included in the guest tools.
@@scottibyte - AGREED. The VirtIO .iso file you provided in the links are the missing link to this resolution. I've always used the "guest tools" .iso provided by QNAP and they don't resolve some of these issues that you addressed (thanks for the tutorial). @Scottibyte's links to RHEL's newer VirtIO drivers make a huge improvement on QNAP's included guest tools .iso.
set everything to virtio before starting the install of windows start setup go through the setup it will complain no hhd hit browse then go to virt folder then win10 then next click iscs redhat driver that installs the virtio HDD then do browse again then add the virtio ethernet redhat same way no need for downloading guest tools that way just insert guest tools cdrom follow these steps
I tried out my friends synology ds1522+ VM (Running Ubuntu) and, it really struggles to function at all. Its a decent nas but...idk. It just doesn't seem to compare when running a VM on your desktop pc. The nas was upgraded to 32GB ram as well.
The DS1522+ is only a Ryzen R1600 dual core system. Most NAS systems are horribly under-powered for VMs. This was for QNAP users looking to improve performance slightly. The QNAP NAS I am using in the video is on a Ryzen 7 1700 Pro which has 8 cores and 16 threads. If you are looking for a faster way to run a Windows VM, I suggest you watch my video entitled Windows 11 LXD Virtual Machine th-cam.com/video/r0WheXvADHk/w-d-xo.html. I also have a follow-on to it called More Windows 11 LXD Virtual Machine. In those videos, I am demonstrating a LXD VM running Windows 11 on only a Ryzen 5 3550H that is only quad core. That machine is also running 20+ LXD Containers as well and the LXD VM and it performs significantly faster.
Oh and to address the "Ubuntu" VM. I have run an Ubuntu Desktop in a LXD container on relatively low performing NAS units and Ubuntu in a LXD container far outperforms an Ubuntu VM by at least an order of magnitude. That's one huge reason why the channel is devoted to LXD containers.
@@scottibyte Thanks for the reply. Wow, that's quite impressive! I can't say that I've ever heard of LXD containers but, I'll definitely check out those videos you mentioned.
@@woolfy02 Be sure to join chat.scottibyte.com/ so that you can tag up and discuss your questions on container virtualization. LXD containers are like Virtual Machines, but since they share the host kernel they have far less overhead. Unlike a VM, a LXD container can be created in generally under 5 seconds and they boot almost instantly. That's because LXD containers run from images and also do not have to virtualize the hardware like a VM.