Search results

I'm also stuck with this, wondering if there's a way to identify the correct smbus/i2c devices, mobo is ASUS TRX40-pro. From what I see, there's no support for it @ OpenRGB :( By the way, there's a i2c passthrough patch, I'm wondering if there's any chance of this being integrated into the PVE...

I also had some problems with nvme - an A-DATA XPG. It was causing a complete freeze at random times w/o anything in the log, reboot fixed it temporarily (it also disappeared from bios a few times). Switched to Samsung and all problems went away.

Any plans for iOS ?

Try going into /etc/pve/qemu-server Find the VM ID you added passthrough to, edit the .cfg file and remove the line with the passed NIC. You can also backup all the .cfg's to /root/ before doing any changes. Thenr reboot, see if that helps.

I'm also interested in this becoming an "on/off" option @ gui

Setting any limits in "Datacenter/Options/Bandwith Limits" ---- does nothing, currently have: Bandwidth Limits clone: 50.00 MiB/s,default: 50.00 MiB/s,move: 50.00 MiB/s,restore: 50.00 MiB/s And this is during a backup (NOT RESTORE), doesn't seem the limits did anything: INFO: status: 0% (1.3...

I'll check it tomorrow, it's 04:33 here @ the moment..

Where do you see speed limit on backing up? I don't see such option @ the UI, there is only a limit on restore. And where do I see a problem in the log: - Normal - INFO: status: 23% (69.2 GiB of 300.0 GiB), duration 264, read: 276.4 MiB/s, write: 238.3 MiB/s - A problem - INFO: status: 63%...

Hey guys, I'm experiencing some issues backing up from NVME to a SATA hdd. The SATA drive just can't keep up. Is it possible to implement a backup read/write speed limiter for similar situations? Here's the log:

Thanks

Hey guys, I switched to a new nvme SSD today (the last one - ADATA XPG had some troubles). The new SSD is Samsung SSD 970 EVO Plus 1TB All good so far, but I noticed the following in the log: # dmesg |grep "nvm" [ 0.757426] nvme nvme0: pci function 0000:47:00.0 [ 0.977430] nvme nvme0...

Yes, all works okay, it was my fault :) In any case, if anyone is interested in a similar setup - let me know and I'll show you the mikrotik config.

My bad, I think I've found the culprit.. testing now.

Hey guys, I think there is a bug @ PVE's firewall when doing vlans. Here's my setup: Home "server" - PVE 6.2-4 - only has 1 Ethernet interface. 1. Mikrotik router connected to fiber-ONT bridged port - gets an external IP via DHCP and does nat / masq on 192.168.100.0/24 for the internal...

I actually got rid of the freezes/lockups I was experiencing, right now 14 days uptime @ kernel 5.4.34-1-pve, 4 VMs running (and by 4 VMs I mean 1 Windows vm that I run as a "daily driver", including gaming, and 1 linux VM for pentests, and 2 linux VMs (ubuntu) - web servers & etc. - Disabled...

@H4R0 This dmesg log is from the boot after the freeze, not before. The ssd is used only for the VM disks, the host is on a HDD: Content Disk image, Container Type LVM Usage 92.47% (882.02 GiB of 953.87 GiB) There is no heavy read/write on any of the VMs. As far as the freezes - once...

Here's my experience so far: https://forum.proxmox.com/threads/weird-errors-in-dmesg.69747/

Here are some other messages from the log:

Well, I do get full system freezes every 2-4 days.. Can't figure out whats causing them, because - there is nothing in the logs, and the freezes occur randomly. There are 2 GPUs but they are allocated to VMs, there's no PVE GPU. Once the system freezes - there's nothing to do but a hard reset...

So far, after replugging the ram modules, no freeze (yet): Linux proxmox 5.4.30-1-pve #1 SMP PVE 5.4.30-1 (Fri, 10 Apr 2020 09:12:42 +0200) x86_64 GNU/Linux 22:21:47 up 3 days, 10:28, 1 user, load average: 3.87, 4.20, 4.28