Remote Gaming and Streaming w/ Proxmox - Proxmox Walk-Through: Part 2

preview_player
Показать описание
#homeserver #proxmox #virtualmachines

---------------------------------------------------
Music (in order):
---------------------------------------------------
Gear I Use: (affiliate links)
---------------------------------------------------
Timestamps:
0:00 Intro
1:40 Part 1 Fixes
10:28 Windows VM and GPU Pass-Thru
28:01 iSCSI Setup
32:58 Windows 10
44:30 Jellyfin
Рекомендации по теме
Комментарии
Автор

It’s 5 am, I don’t know what year it is, I just can’t stop watching his videos

emiljanoharizi
Автор

Hey mate, really enjoying watching your videos. I'm currently looking/trying to do this sort of stuff myself and watching you tinker around with it has been a great help, not just knowledge wise but also just confidence/inspiration to just get in and mess around. Appreciate the videos, i imagine they aren't the easiest to bang out, keep up the great content!

MrMellow
Автор

IMPORTANT NOTE. This stumped me for like 2 weeks trying to figure out what was wrong. Certain docker containers use SQL databases to work and you have to add "nolock" to the line in /etc/fstab. Otherwise these databases will default to being locked and docker will not be able to use them

bloxboss
Автор

This guy is amazing! He actually took the time to respond and help me with the proxmox setup.

crimsionCoder
Автор

Love your videos! Very calming and informative

UNITYMusics
Автор

Nice series. One comment right for the start, when you set the delay for the startup-at-boot, you set it to the wrong VM. You want it to pause AFTER (or while) truenas starts, so you need to set the delay there. From the docs: "Defines the interval between this VM start and subsequent VMs starts", so it's a delay apllied after the start of the VM you're setting it in.
A second thing I notices is when setting up the windows VM (around 22:00), you didn't notice that the CPU was set to "host" in the reference screen. That's relevant for gaming since the KVM64 is a much simpler CPU-model. Basically, your real CPU might be able to do stuff that games might be able to take advantage of, but the KVM64 doesn't pass this capability to the VM. That CPU-Type is primarily useful for live-migrating VMs between hosts, where you really want the CPU seen by the guest to be the same. Maybe you did change it later, since windows did show the "correct/real" CPU in Task Manager, but kvm might just pass on the original name anyway.

TheCreat
Автор

I finally got gpu passthrough working after a month long struggle. Thanks for the guide. It helped me succeed where others have failed.

darthkielbasa
Автор

Thank you for this series, hope to get the parts for my new server next week, my plan is to set it up in a similar way.

dgriffejoen
Автор

Great video! I can't wait to build this myself!

davidshields
Автор

If you add another disc drive during the VM setup, you can mount both the Windows iso and the Virtio iso. Saves you swapping mid install.

akurenda
Автор

Very cool, I´m hoping to set up something similar after I upgrade my main rig (wich will be a while), but this was really inspiring and ideas on what I wan´t to do is flowing! Good job!

petersoderman
Автор

Thank you, VERY interesting! Keep up the good Work!

micjauamd
Автор

Very strange but it seems my previous comment Vanished, I guess it was the URL in the comment :)
So I would like to point to a small mistake. If you want the Debian Machine to start 300secs after the Truenas machine, then you need to add the up delay on the truneas vm, not on the Debian.
Please see below:

- Startup delay: Defines the interval between this VM start and SUBSEQUENT VMs starts . E.g. set it to 240 if you want to wait 240 seconds before starting other VMs.

The full doc can be found by presing the "? HELP" when choosing the booting order.

Love your videos, keep up the good work.

Psyts
Автор

OH i love it! I was going to go with a synology before, but it is too awesome what you can do on a "real server". Now I just need a server :D

wohfab
Автор

Q: Why do you want to automount that share instead of just mount it at boot? Is there a particular advantage? Thanks!

LouisGiliberto
Автор

Proxmox is pure love.

Wasted for much energy and lifetime (and small bucks that add ontop of each other to a giant pile) with a dedicated Kubernetes Cluster trying out various arm7, arm8 and even x86 SBCs until I realized the trouble I'm putting myself into.

Well at least I learned a shit ton there ... including distributed block storage, Docker Container architecure, Infrastructure management and all the fancy shit that can happen to your servers. Especially distro related (yikes).

Full Machine Backups and Scaling virtually are a godsend.

Nothing is better then freezing an VM, creating a COW Snapshot of an LXC Container, cloning them, rolling back ...

simons.-xbtf
Автор

Love it!! I'm gonna see it as soon as I have a minute to spare
I had that minute stolen from my sleep time, but, it was worth the time 😛
Now, I'll do try and replicate that in my own devices. Thank you for the vids and/or research/links ...

JoseTorresMates
Автор

Nice video ❤ this is very helpful and lots of love

RealJustPotato
Автор

i am impressed by your communication skills although you got down syndrom. Really nice content

daveking
Автор

Hi, followed your suggestions for wireguard to remotely access the jellyfin server, but I am having some problem accessing the server. I saw that a variable ALLOWEDIPS by default routes all traffic to the internet and blocks other connections from/to the local network, but you seem not to have this problem, even if you did not specify the variable and your ALLOWEDIPS in the logs are 0.0.0.0. do you have any cluw how to solve this?

Filotto