Recent content by jimmy1987

Could it be you have a broken disk?

I think the reason also was that you still have an ISO attached to that VM in your screenshot, I've been migrating vm's between lvm-thin and ZFS as well since we're migrating everything to ZFS and on online vm's that work fine.

When would this be promoted to the ent repo? Would rather not use testing packages on nodes using the ent repo in production.

I had a qdevice in our cluster for a short time (as we're migrating from a different solution to proxmox) so i didn't have 3 free servers. Now I've removed the qdevice as is mentioned on the wiki and I've added the 3rd server. That all works fine, but can I now safely remove the...

Hmm haven't tested that really, could try that still.

Yeah but that is still between intel :) I was migrating between a Xeon and an Epyc.

That is what I thought as well and when it calls that instruction it will crash the VM, I even had one crash after like 5 hours after the migration. I'm guessing you can migrate between slightly different intel cpu's then? (the other servers that will join this cluster have the exact same...

The cluster now only has an AMD and Intel machine, it will get additional machines added that have the exact same hardware config as the intel. I will try again with those hosts as well. Might be just something between intel and amd as well.

Hmm not sure which one as it doesn't have much options enabled, I only know that I migrated 4 vm's and 3 of them just completely froze, 2 of them like 4 minutes after the migration. Not sure if this has anything to do with it: kvm: warning: TSC frequency mismatch between VM (2449998 kHz) and...

When using host I expected this indeed, but I'm using x86_64 AES v2

I might think this just doesn't work as it should but anyway. When doing a live migration including storage from a E5-2640 v3 and a AMD EPYC 9534 it seems to work at first but then crashes the VM where it needs a reset in order to work again. My thought was to use the generic aes v2 cpu on the...

I tried using different args but as you mention, it either can't start the vm or doesn't sees the nic.

I'm wondering this too but then on an opnsense and Debian vm. -device 'virtio-net-pci,mac=,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=102' -machine 'type=q35+pve1'

Ah yes, now it shows, so i was being impatient.. :rolleyes:

This might have been answered already at some point but I couldn't find it. On some members here under their name you see a "Proxmox Subscriber" badge, does that only work if you get a subscription that includes support? (eg. standard) I'm using 2 community subs and when browsing my profile I...