Xcage

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by Xcage

  1. > What i did was add VirtIO 10G disk, > boot the VM > add the drivers manually (installed viostor.inf) then checked disks via disk management , and saw Uninitialized disk which would mean that windows sees it , but doesn't actually needs to use it , therefore permanent driver addition wouldn't be necessary( from my understanding of windows) > so i initialized the disk , so its now connected as UNallocated space. > Restart via regular windows restart, checked if the disk is there after restart (which would mean that the drivers are still loaded on boot by windows and it didn't discard them) and it was there. > Then i created a new VM with OVMF , i440 and the same disk i used , but this time with VirtIO bus. everything like u would regularly do. booted the VM and it "just" worked. Checked the performance (attached) and i was right , VirtIO drivers are much better for NVME disks performance (twice better from my testing) So its all working now , and thanks for tremendous help! took me half a day to sort it out but i learned alot in the process too hope it will help some1 who stumbles upon this maybe some time later. on my way there i learned how to resize disks, change formats, take snapshots , copy stuff using terminal commands, learned to shrink , fix Windows recovery partition, change MBR to GPT
  2. First of all Thanks for the help , appreciate the time and effort regarding the backups - i have all of them, AND the original Windows machines, so that shouldn't be an issue. i did try to change to Virtio, also i tried to dism /image:f:\ /add-driver /driver:e:\viostor\w10\amd64\viostor.inf well i actually tried to dism /image:F:\ /add-driver /Driver:E:\ /Recurse for all drivers but dism didnt work , granted it was other VM image , but the principal stays the same, those VMs werent and will not be getting windows updates, those production machines with certain software installed that each windows update is a potential to break them. Going to try bcdedit be back with update
  3. THX! now i know how to convert that. so i did that but the speed is the same, how would i convert that to use Virtio bus? would that even help? UEFI - Sata Vbus Seabios - Sata Vbus Fresh Install -OVMF Virtio
  4. Hi all, I am experiencing real bad disk speeds on win10 VMs - AS SSD Benchmark even the sequential test stutters and is never above 80-90mbps. the VMs were originally copied from real WIN10 Machines using disk2VHD , then converted to qcow2 and those boot only with seabios with primaryVdisk bus set to SATA (ive 3 images like that , different sizes, all with performance issues) i tested them with separate disks be that SSD or NVME the performance is horrible. (i did install Virtio drivers) i did test and created new VM just now with OVMF and i440 and primary vdisk bus Virtio and the performance there is about 80-85% of bare metals speeds on NVME drive. attached 2 xmls one of freshly installed VM which works fine but doesnt help because i would need to rebuild the VM and its an issue and XML of a slow VM which i ran from the same Cache NVME but using seabios q3.5 and primary vdisk bus as SATA is there a way to fix the performance ? or maybe a way to convert them to work with OVMF and VirtIO because it feels like drivers issue Freshly installed fast XML.txt slow XML.txt 1ctower-diagnostics-20210820-1358.zip
  5. Heya , id like to help so i did a test and here are the settings i created new VM with. the only thing is i did NOT start VM after creation. After it was created , i clicked start then VNC and there was the boot from CD promt , i proceeded to windows installation choose virtio driver because windows install did not recognize the disk to install windows to hope it helps
  6. ok so maybe some1 will stumble upon this post in the future with same or similar issues, ill briefly explain what i tried to do , what were the goals and how it was achieved. so i had 3 windows machines , each separate windows server machine for different purposes in different places. ling story short those needed to be in 1 place mainly for backup transfers (locally in the same network much faster then over internet) so i used disk2vhd to make vhd vdisk then converted it to qcow2, then mounted it now after wiggling with the settings i got it working , used Seabios , q3.5 machine , and the setting that finally worked for me is changing Primary vDisk Bus: to Sata Hope it helps some1
  7. Had that issue with alot of VMs , i mostly made WIN VMS , win7 win10 , server etc some i created from a scratch some from vdisks etc and none of them worked properly from the GUI when pressed stop restart , except force stop which worked. So today when i finally got to the point when i want to setup a reliable VM backup, and make the VM backup script to work properly , i stumbled upon this post. My settings were proper tho , when pressing power button > shut down. so i changed the option to whatever , then back to shutdown , and now it works. TLDR - windows and its features
  8. Hi ppl, The issue here is that i cant make the imported WIN10 OS to work as VM the OS was originally installed on 2 SSDs which were configured as Raid 1 , i then used Disk2VHD (https://www.veeam.com/blog/how-to-convert-physical-machine-hyper-v-virtual-machine-disk2vhd.html) to make a image of the OS, then i used qemu-img to convert the image to qcow2 now i need to make it work, ive tried OVMF Bios with i440, changing manually to qcow2 name and location. it goes to shell , and if i exit the shell and try boot options none of them seem to boot. tried to create a VM with auto disk with seabios and q35 5.1 with qcow type, then manually change the disk to qcow2 name and location screen attached please enlighten me on how to proceed. also tried to add the driver via cmd , still cant see C drive to boot
  9. Thanks for the answer btw , looked through several posts , most of them being written by smart-asses who aren't for some reason interested in helping , instead teaching you to use search feature and waste their , and my time
  10. Thanks! i did some digging and it works, at first i did it manually with script , then found automatic plugin, now i dont know if we need to close this thread and open another one, since i do have another question regarding my whole setup and if its even optimal or can i ask stuff here?
  11. is it stable if u dont restart the VMs manually? and in general how is the stability of it? also would you say that ECC is a must for VMs that would be running for days?
  12. The final goal is to have a system with 3 VMs hosted, to have snapshots of it every week or so, along with daily backups to the backup drives. 3 WIN10 VMs will be accessed remotely couple hours a day with some basic tasks (called it intermediate browsing just because its not basic but its nothing complicated as well, stuff like office etc) will run a VPN on unraid for remote access in case of need. Worth mentioning that i dont intend to touch the server like ideally never but i do understand that from time to time need to check on it but would like the time between the checks be as long as possible (6 months maybe?) granted that VMs wont be getting updates on the regular basis anyways now the question is which hardware should i opt for? CPU - i thought of at-least 2 cores 4 threads for each machine something like 9900 , which would leave 2 more cores for unraid OS itself i dont mind going AMD, but never had any real expirience with VMs on amd so dont know if its a good idea. Mobo - doesn't really matter as long as it has 2 NVME slots on it for VM cache drives and fast storage cache. some 3/1GBps NVMEs and couple SSDs for backup pulls from local PCs on the network daily (there's like 2-5MB incremental daily backups) RAM - 16GB per machine, and like 4 or 8 for the unraid itself (don't know how much it actually needs) another big question , should i opt for ECC memory? and change the build completely? or is regular DDR4 RAM fine? (there will be UPS incase of power failures) case doesn't matter that much i guess. Please enlighten and any suggestions are welcome.
  13. Please guide me to where i can learn about different scripts i can run , or about common practices so i can start testing and see if what i want to achieve is actually possible
  14. Thank you for the info! now i am a total newb to the scripting part , especially if its linux , what and where would i even run a script to automatically create FULL snapshot and not incremental every lets say week? i assume that is all i would actually need, then in case i need to restore a snapshot id just replace the Vdisk in the running path with the Vdisk from the backup path right>?
  15. Hi people, i have a number of Unraid systems now and really happy with them but i've been only using them as NAS basically. Hardware differs, but i usually use duckdns docker for VPN access with open VPN docker. Now i started to explore VM options, and would like to know how to setup snapshots of VMs. Basically what i want to achieve is number of Windows 10(it shouldn't matter tho) VM machines. that would make a snapshot every month or so. and in case its needed ability to restore the snapshots remotely via Unraid without the need to physically be there. is it possible to do using unraid? if so please enlighten me, more details the better.