Search results

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...

Local time: Tue 2025-11-25 04:37:56 EST Universal time: Tue 2025-11-25 09:37:56 UTC RTC time: Tue 2025-11-25 09:37:57 Time zone: America/New_York (EST, -0500) System clock synchronized: no NTP service: active RTC in local TZ: no This says that your time zone is EST (America/New_York). Is that...

What is the output of "chrony sources"? Please use the </> code tags.

Did you try "systemctl restart chrony"?

When it first boots the system will set the time from the BIOS clock (aka CMOS). That clock should be set to UTC, NOT to your local time. That would explain the 5 hours as you are in GMT-5. The other systems probably have the same error in their BIOS but you don't notice because NTP corrects it...

It would seem that: Your CMOS clock is way off (that's where the system gets its initial time). You have no servers or pools listed in /etc/chrony/chrony.conf, or else your DNS is not able to resolve them.

What is the output of "chronyc sources", "timedatectl", "ip a" and "ip route"? Do you have the CMOS clock set to local time or UTC (preferred)?

This is why it is generally not a good idea to have multiple interfaces on the same subnet. The kernel considers them to be "the same" in the sense that both are equally good to reach destinations on that network or gatewayed through it. Which means it will just pick one, usually the first one...

If you look at the hardware requirements in the PVE documentation, you will see that Chrome 109 and Firefox 115 are WAY too old. I mean, maybe you could try Internet Explorer while you're at it. ETA: https://www.proxmox.com/en/products/proxmox-virtual-environment/requirements