Search results

Update on this, I did try that and also been trying it on a Minisforum MS-A1, both replace and append. No luck either

I was hoping this would fix it on my Lenovo M920Q, but sadly even after appending it to my Lenovo it didn't make UEFI SecureBoot work. So I just disabled Secure Boot. Hopefully it'll help others. Proxmox: 8.2

Issue is upstream

Hi Mach, Disable the QEMU agent on the VM options, that'll allow the backup to run. I'm not sure if the issue is Debian or the MariaDB builds. If you could kindly report upstream links here that would be great, as I would love to get this fixed.

Like this then run the script and the IP should change to the DNS record

still working for me. In your IPSet have you create some blank entries with the comment as the fqdn that you want to use then run the script?

So it effects 10.3 as well. Please report this upstream to mariadb as well https://jira.mariadb.org/browse/MDEV-27196 Also upstream to qemu project https://gitlab.com/qemu-project/qemu/-/issues/881 At the moment we don't know which side the issue lays with, more people who report it, more...

Which MariaDB version does ubuntu 20.04 carry?

Are you using mariadb's own repo or ubuntu's?

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