Cobragt88 Posted February 1 Share Posted February 1 on the VM tab it would be nice to set a time delay in seconds to allow vnc to fully work for each VM. Quote Link to comment
SimonF Posted February 6 Share Posted February 6 On 2/1/2024 at 6:51 PM, Cobragt88 said: on the VM tab it would be nice to set a time delay in seconds to allow vnc to fully work for each VM. The time delay on docker it for autostart sequence on array start. Do you mean a delay with start with vnc before the window opens? Quote Link to comment
Cobragt88 Posted February 6 Author Share Posted February 6 hi no sorry I mean what the picture shows on the advanced view you can choose in seconds a timed wait to allow dockers to wait before they start. I guess i shouldn't have added vnc..... hope this helps you understand what i was trying to say first. CPU: Ryzen 9 5950X @ 3.4GHZ M/B: Gigabyte X570S AORUS ELITE Memory: 64 GB Drives: 6 + 1 Parity(40Tb) + 2 NVME VM/Docker Raid 0 (500Gb) Quote Link to comment
SimonF Posted February 6 Share Posted February 6 15 minutes ago, Cobragt88 said: hi no sorry I mean what the picture shows on the advanced view you can choose in seconds a timed wait to allow dockers to wait before they start. I guess i shouldn't have added vnc..... hope this helps you understand what i was trying to say first. CPU: Ryzen 9 5950X @ 3.4GHZ M/B: Gigabyte X570S AORUS ELITE Memory: 64 GB Drives: 6 + 1 Parity(40Tb) + 2 NVME VM/Docker Raid 0 (500Gb) It will not be simple to add this to VMs as it is not an unraid process starting the VMs but libvirtd, Is there a reason why you want to stagger the start. You could look to do with a user script. But will look to see if there is a way to achieve this. Quote Link to comment
Cobragt88 Posted February 6 Author Share Posted February 6 so i'm having trouble with vm's auto starting it says vnc # is taken so basicly i have to manually start the vm's to get them running. Maybe there's something that needs to be looked at in my config to fix this? I just attached the diagnostics file. lowenas-diagnostics-20240206-1650.zip Quote Link to comment
SimonF Posted February 7 Share Posted February 7 10 hours ago, Cobragt88 said: so i'm having trouble with vm's auto starting it says vnc # is taken so basicly i have to manually start the vm's to get them running. Maybe there's something that needs to be looked at in my config to fix this? I just attached the diagnostics file. lowenas-diagnostics-20240206-1650.zip 180.5 kB · 0 downloads I cannot see anything in the logs. Where do you see vnc is taken? Can you provide a screen print of you vm page? XMLs for VMs have autoport set so there should not be a conflict. Quote Link to comment
Cobragt88 Posted February 7 Author Share Posted February 7 As funny as it seems i had to restart the server for another unraid change all the vms started this timeso hopefully its ok now. i tested auto starting all the vms too. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.