Search results

Sorted out. I didn't find a function like this in proxmox, but the problem with windows getting the machine's local time was due to the delay with the ntp server, so it was getting locally.

Hello people, I'm having trouble keeping my active directory schedule on windows server 2016 synchronized with the ntp server, I researched some micorsoft forums and what I saw most was people saying it might be due to hypevision. In hypeV they have a function that they disable called "time...

Did you manage to solve this problem? I'm facing this on windows server 2016.

Did you manage to solve this problem? I'm facing this on windows server 2016.

Guys, I had commented this line on sshd, that was what was causing the problem, after uncommenting it the problem was solved. AcceptEnv LANG LC_*

Yes, I have already tested it on other browsers. I also generated new ssl ceriticados on each pve host and I still have the same problem.

Good morning everyone, my pve cluster is configured in proxmox 6.4-4, but when I get access to vm via normal vnc right away in pve01, when I log in to the second vm that is in pve02 I get authentication failed, by Spice I also get normal access. Is anyone experiencing this problem?

Hi people, I tested it with version 5.4-3 it is working normally with the discard set in the vm, when it cleans the data in the vm it is automatically cleaned in the storage no longer corrupting the vms. However on hosts pve I sometimes get the messganes below. Should I worry about it? Jul 1...

I tested it with proxmox version 6.0-4 with discard enabled and had the same problem with trim -v --all to clear from storage: Jul 1 16:06:23 ubu1 kernel: [ 1113.189618] EXT4-fs error (device sda2): ext4_validate_block_bitmap:384: comm fstrim: bg 34: bad block bitmap checksum Jul 1 16:06:23...

Hello proxmox, could you release the 6.0 version link? So that I can test it, to see if I can solve this problem apparently and version compatibility issue.

I set up a zeroed vm.

Today I was doing some performance testing with the wire and I had these errors again even with the discard turned off: Jun 29 15:39:45 teste4 kernel: [ 7114.998104] EXT4-fs error (device sda2): ext4_lookup:1701: inode #11410343: comm vim: iget: checksum invalid Jun 29 15:39:45 teste4 kernel: [...

What tool did you run to validate this test?

Do you think it would have any problem to work without using the discard?

Hey guys, After some tests, I disabled the vm discard and it's no longer crashing the machines. Does anyone have any idea why this is? With this configuration, is it running normally: root@pve01:/var/lib/vz/template# qm config 101 boot: cdn bootdisk: scsi0 cores: 4 ide2: none,media=cdrom...

I followed your tip to test only on one but I still have the same problem. "Jun 24 15:52:07 UBUTESTE kernel: [65400.310058] EXT4-fs warning (device sda2): ext4_trim_all_free:5198: Error -117 loading buddy information for 333 Jun 24 15:52:09 UBUTESTE kernel: [65401.549693] EXT4-fs warning...

Guys after two hours the problem came back, so on this line it was not the MTU on the interfaces: Jun 22 16:20:12 graylog kernel: [7722.329015] EXT4-fs error (device sda2): ext4_validate_block_bitmap:384: comm kworker/u16:1: bg 873: bad block bitmap checksum Jun 22 16:20:12 graylog kernel: [...

Ola amigo, Na verdade a mensagem é de uma vm instalada no proxmox. Eu já configurei o cluster proxmox com lvm via iscsi, no hypervisior não aparece nenhum erro. Eu estou achando que é o MTU que eu tinha aplicado somente na interface física agora eu coloquei também nas vmbrs. (MTU 8900...

Hello friends, I have a dell ME4084 storage, where I'm exporting a LUN to my proxmox 6.4-1 cluster with 3 nodes, I performed the configuration according to the proxmox documentation, apparently it is working normally according to the output of mutipath -ll below: mpath_dell_vol_proxmox...