Recent content by Republicus

Like CRCinAU, Ive issued SMTP certs successfully but a checktls.com test reports certificate failures due to self signed certificates. Debug does indeed show the Proxmox Mail Gateway self signed certificate. I never issued API certs but do have SMTP certs. Mail Gateway 8.0.7

You must not be installing vgpu properly. I have no problems through updates to proxmox and my VMs game and encode/decode 24/7.

I want to add that you should remove the PCI spoofing, in addition to changing frl_enabled to disabled (frl_enabled = 0), when you try the vGPU GRID driver in your profile override conf. If you went the route you went, like I initially did, due to licensing costs, I would note that my...

Try the driver included in the vgpu KVM driver bundle that you downloaded for the host. It will give you 20 minutes before the driver disables features and starts acting like trash. But 20 minutes should be long enough to verify your needs. If that works then I can help you get licensing setup...

I can't answer to PVE 8 issues. I wont upgrade until drivers catch up for my network hardware. Wish we had an LTS edition.. Anyway, what driver are you using in the VM? I think the frl_enabled config should be on (1) or off (0). It looks like you're spoofing the PCI ID and NVIDIA may be making...

It looks like its a Win driver issue with kvm64 and vmx. Windows guest OS crashes once I add the vmx flag to cpu args. It wont even boot into the OS installer. On the other hand Linux handles it fine. But again either it is your disks preforming slowly or something else going on that I can not...

Youve sparked my interest so I am installing a fresh Win 10 vm with the args added to a default kvm64 cpu args: -cpu kvm64,vmx=on I'll let you know what I find out. Because I'm not on PVE 8 I cant tell you if kvm64 = x86-64-v2-[AES] or if it aught to be args: -cpu x86-64-v2-[AES],vmx=on

vmx is the flags needed for nested virtualization. args: -cpu kvm64,vmx=on This does report vmx flags once added (and absent without that argument in conf) but you may need to install Win10 from scratch with that CPU change. My VM wanted to boot loop and repair with that CPU change. But the...

Can you try these changes to your VM conf file, add args line and adjust CPU type to Broadwell: args: -cpu Broadwell,vmx=on cpu: Broadwell PS I'm not qualified to answer your question concerning the kvm64 or other CPU types

So I'm not seeing the sluggishness you are reporting in the Windows HyperV "host" VM or the nested guest VM inside it. My test is on a PVE 7.4-13 node.

I just enabled cpu type host and have no flags set. My VM boots fine and HyperV is now installed. I will install a VM in HyperV to verify. I think something else is amiss that is causing your VM to be so slow. My CPUs are v2 of the same E5 series. What is your problem in HyperV?

What reply do you get from (?) (intel cpu): # cat /sys/module/kvm_intel/parameters/nested (amd cpu): # cat /sys/module/kvm_amd/parameters/nested

As long as you intend on the VM owning one or all the public IPs then this is how it should be configured. It appears this issue is solved?

What flags are you using? I haven't had the same problems since my early reply when we discussed using the other OS Type. See the first page of that thread. Have you tried playing around with the CPU type to match your physical CPU type? For example Ive had success with host and Penryn...

I experienced some "anticheat" VM detection in Lost Ark that could only be resolved by emulating the virtual hardware components as physical ones. Such as CPU Host, LSI SCSI Controller, Intel network adapter. If you are expecting low latency through the noVNC console then you will be...