Search results

Multi monitors work fine for me using xrdp on Debian with the regular Windows client or with krdc. Xrdp is much easier to set up now on Debian 13 since there is now "pipewire-module-xrdp" so you don't have to compile stuff to get sound.

Somebody makes a RAM stick called "G Skill Ripjaws RAM"? LOL! The way PC vendors name things, especially in the gaming space, is pretty hilarious. I mean, wow, it is just a memory stick. Off-topic, sorry, but I found it funny.

This isn't a question about PVE, it is about configuring your thin client. From the thin client point of view the VMs are the same as 40 machines. It might be more productive to ask on that vendor forum.

You might also want to look into Apache Guacamole.

Maybe you should ask the provider of your support subscription.

What would be the difference security-wise? You will either have to open a port or go through a third-party server that your customers may or may not trust. Either way support people will need root access.

You did at one time, and one of them installed a hook to reinstall the mod.

First, please search the forum before posting. Somebody (always "new member") asks this question every few days. First, if you have any PCIe devices passed in to the VM, then all VM memory must be pinned at startup to avoid issues with DMA. That's one thing. The other thing is that VM's that...

I don't know. Maybe someone else can chime in.

You know, there is a thing called a "cross compiler" where you compile on a PC for a foreign target. This is very popular in the embedded space because most embedded chips are slow and have limited resources compared with a PC. If you do that you'd only need to test on the Pi. On Debian machines...

I don't use iGPU passthrough. VirGL meets my needs and I don't like the idea of having no console when something goes wrong.

That is an ARM chip. PVE does not support ARM.

I don't know what the defaults would be for a 10 TB drive. But you almost certainly don't need 98 GB for the rootfs. I'm running with a 64 GB rootfs, 8GB of swap, and 2 TB of LVM-thin.

You really need to read that manual. PVE tends to use block storage for VM's, not a filesystem. It is different from VMWare that way.

You want the local-lvm to be maximized. Which, since you have only one pretty small drive, that the rootfs has to be minimized. I think the minimum is around 8 GB, but 16 would allow some space for storing ISO's and the like.

It is using the full size. The "local-lvm" is a logical volume where you are supposed to put your VM disks. Please read the manual: https://pve.proxmox.com/pve-docs/chapter-pvesm.html

You didn't answer any of my questions. Can you ping 8.8.8.8? Can you ping google.com? Can you ping the gateway? That all has to work before NTP can work. I have never seen an ISP router set up like you say yours is.

What are you talking about? An override of what IP's? According to what you posted earlier you have vmbr0 at 192.168.5.10/16 with gateway 192.168.5.189. This is, um, unusual in two ways, but it is legal. One unusual thing is that 192.168 is usually a /24, not /16, the other is that the gateway...

If DNS isn't working then chrony won't be able to get the IP address of the server. Can you ping the DNS server that you put in /etc/resolv.conf? Can you ping google.com? Can you ping 8.8.8.8? Your problem is DNS and/or your network settings, not NTP.

If New York is correct please leave it alone. So we are down to either you don't have a proper server in chrony.conf or your network isn't working right: DNS can't find the server (you claim this is fixed) Chrony has no server listed (did you check this?) Chrony can't reach the server (can you...