Search results

This has now also been reported on the MariaDB bug tracker https://jira.mariadb.org/browse/MDEV-27196

I have the exact same problem, Debian and MariaDB from their own Repo. Debian 11 MariaDB 10.7 Only setup the VM last week, so far no other Debian VM have been effected. I did reinstall the agent on the MariaDB VM, which got it working for a while but eventually issue comes back. Have you...

You can try downgrading qemu as the new qemu 6.1 that has shipped with PVE7.1 maybe what's causing you issues # Download old qemu wget http://download.proxmox.com/debian/dists/bullseye/pve-no-subscription/binary-amd64/pve-qemu-kvm_6.0.0-4_amd64.deb # Install old qemu dpkg -i...

Are the VMs with the issue virtio scsi or virtio block?

Up to you really, I do it on the PBS backup dataset.

Issues with Virtio IO errors in guests have been reported on Bugzilla and upstream on QEMU. The issue doesn't look to be isolated to just Proxmox. https://bugzilla.proxmox.com/show_bug.cgi?id=3738 https://gitlab.com/qemu-project/qemu/-/issues/649

You'll also want to amend the default postfix configuration so Proxmox can send emails, you'll want to create a GMAIL account or something to send as. Otherwise email delivery probably won't work. Guide: https://www.vayelan.org/proxmoxpostfix/ Create a gmail account called like...

That strategy is perfectly fine, just means more downtime as all. I assume its a personal setup so you'll be fine. Don't forget to monitor yours disks with smartctl or something, so you get alerted hopefully before they fail. EDIT: if you setup your install using ZFS with a single drive, I...

May want to refer to this thread where other people are reporting issues on 7.1 VM disks. https://forum.proxmox.com/threads/proxmox-ve-7-1-released.99847/page-4 Not sure if the topic for this should be moved other to that one or not.

That'll run Proxmox for sure, just make sure you turn on AMD's virtualisation feature in the bios/uefi, I've had a few systems where its off by default. I recommend you try get dual NVMe drives and then you can mirror them for boot, so if your SSD dies you hopefully won't loose any data...

I'm now having VM Disk issues since upgrading to 7.1, tried loading up kernel 5.11.22-7-pve, but the issues still remain. I've now tried using SCSI over virtio and the issue seems to go away, at least for now. I also tried using "threads" on the Async for VirtIO Block, but didn't help. I can...

Stayed on PVE 5.11 but I've changed some of the VMs over to using SCSI instead of VirtIO Block. When I download large files off the internet, the VM will error for those using VirtIO and the ones using SCSI do not. So I think its issue with VirtIO Block @jeannotp can you test this on your side...

Update, still seems to error with Linux 5.11.22-7-pve

I've just installed kernel 5.11 again and reboot back in to that kernel. To see if the older kernel helps.

Set my 'Async IO' to "threads", downloaded a large package and it still gets 'Input/output error', so maybe its not apart of that regression.

I too am getting similar issues, I've created my own topic as it maybe different issue but maybe its the same one. https://forum.proxmox.com/threads/i-o-errors-since-upgrading-to-pve-7-1.100079/ Edit: Done some testing with SCSI instead of virtio, and it seems like it no longer happens of SCSI

I think my issue maybe related to this 5.13 potential kernel regression. https://forum.proxmox.com/threads/sporadic-buffer-i-o-error-on-device-vda1-inside-guest-raw-on-lvm-on-top-of-drbd.21051/post-431567 # pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-5...

Hey, I've recently updated from PVE 7.0 to PVE 7.1, since then I've been getting IO issues in my VMs, docker images getting downloaded and then being corrupt or deb files being corrupted when trying to upgrade packages in VMs. I thought the issue was my two NVMe disks dying so I've had them...

Used the the script on my Proxmox server, as it sits on the edge in a OVH DC. It error'd the first few times with the following error, but I'm sure its because the IPset didn't contain any IPs with the comment of a passed domain. ./setdynfw.sh: line 9: [: argument expected Many thanks for the...

I've found how to resolve the issue! I've been looking at this the wrong way, I think due to how the Linux Bridge works and OVH's network, you have to set the VM's (OPNsense's) gateway to the host's (bridge's IPv6 address). Firstly we'll need to set that up. First add a IPv6 Address to your...