Oryzaki

I set up QEMU for the first time today and everything was working mostly fine. However, whenever I boot into Windows 10 pro there is only 1 core. This is despite the fact that I set it as 1 Socket 4 cores. Trying to runvirsh setvcpus Windows 6 --current results in a domain error and virsh list --all results in nothing.

Its got some pretty large names behind it and the GUI has a nice polished look. It also helps that it has an IOS app. Also, it's only 5$ for all creators on the platform instead of the ridiculous 3$ per creator that Floatplane is currently using. Overall seems like a solid platform though I haven't used it myself.

Hard to tell it might. Are you already using an ethernet connection to your PC?

Having a higher upload would definitely help 17mbps is abysmally bad.

Would you not normally want hyper-v on?

After plugging in my 8TB WD Red my computer, which uses an NVME as the boot drive took almost 30 minutes to boot. Now it's doing it again does anyone know why this is happening and if there is any way to avoid it?

I would try what NinJake is suggesting then.

Okay, what's your PSU though. Also if you have an unstable CPU overclock it can cause this to happen.

Should be almost if not completely the same.

That certainly doesn't sound like a faulty PSU to me. Does you PSU supply enough wattage and do you have a CPU overclock?

Basically, I need to know if it is possible to run a display on another card, in this case, a GTX 750 ti, than the one it is plugged into, in this case, a GTX 1080. The reason for this is I want to use the display port on my GTX 1080 to drive my 4k monitor at 60hertz rather than with an HDMI that only supports 30hertz.

No Its on the same drive. However reseting windows seemed to do the trick thanks for trying to help me.

I tried but my secondary install of windows seems to stop me from beong able to do that. I tried this command bcdedit /set {default} safeboot minimal

Baisically I go too use my computer and it wont boot saying what failed amdryzenmaster

have you tried shorting the motherboard's pins to turn it on instead of using the power button cause that's all I can think of