Search results

hm, ok i see. So the question should be, why did the connection drop down in the first place. well, will reboot the complete node and see if we are getting somewhere from there. thanks Sascha

Hi, Jan 8 00:46:33 pve vzdump[21653]: INFO: Finished Backup of VM 101 (00:21:16) Jan 8 00:46:33 pve vzdump[21653]: INFO: Starting Backup of VM 102 (qemu) Jan 8 00:46:34 pve qm[27379]: <root@pam> update VM 102: -lock backup Jan 8 00:58:07 pve kernel: [95606.157217] perf: interrupt took too...

Will do, only would like to not experience this again. Happened a couple of times allready on this system.

hm, well forgot to say, that we're experiencing this on a one node system, no cluster. But it could well be, that using a different NIC for the VMs may help. Will try this out as soon as possible. However, if you have more ideas, again, any reccomendation is welcome. cheers Sascha

Hi everyone, we're experiencing the backup hangs as well here, with completely updated packages. Our pve-qemu-kvm is at 4.1.1-2, so that is high above the expected fix with 4.0.0-7 i suppose. The backup hangs at INFO: Starting Backup of VM 102 (qemu) INFO: Backup started at 2020-01-08 00:46:33...

sorry for hijacking this after so many years. but is there any option to change the default by now? Snapshots with RAM included take a lot of time to finish, and most of the time, RAM is not necessarily needed. So some way to change the default behaviour would be great. trhanks Sascha

Well, we're talking about Hetzner here, so we have no access to their switches. I thought that maybe implementing some rule like iptables -A OUTPUT -i enp4s0 -m mac ! --mac-source AB:AB:AB:AB:AB -j DROP would be cool. Just an example of course, this command will not work, as it seems not...

Sorry for hijacking this. But is there any way to do Macfiltering for the host too? I only find this for the VMs. It would be great, if we could disallow the Host to send packets via unknown Mac-Adresses. thanks Sascha

damn...same here again. Using virtio-scsi and scsi VD's doesn't fix the problem. This is really dangerous! maybe better switch from qcow2 to raw?

Hi Bien, no not really. We had the PVE Support look into this, but they found no issues on PVE side. Our problem seem to be related to some misconfiguration of dovecot...we're still working on it. For now, we force the vm to be restarted every morning...so we don't get alarmed by a non working...

Great had the same issue...helped me a lot, Thank you Sascha

Hi, just wondering...noone has any idea? This is urgent, really... Our VM freezes (only some ports like 25 and 587 not reachable, others still working) every 2 days the latest... Please help us, thanks Sascha

Hi there, we're experiencing the same error message here with our LXC VM. Additionally this VM will crash completely everey 4-5 days, all by a sudden. The VM holds an ISPConfig guest, running mysql dovecot, postfix and apache services. So, when the freezing happens, no mail services are...

Hi, we seem to have something very similar here on a debian jessie lxc guest with ISPConfig: apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=7435 comm="mount" flags="rw, remount, relatime" We allready added this line to...

very cool, thank you very much! cheers Sascha

hm, i know that page, but that's still all about virtio drivers. from what i have understood, virtio is not being worked on anymore, so i thought that the complete driver set from fedorapeople would not be the way to go anymore. Did i get that wrong? thanks Sascha

Hi, quick question: After p2v migration of a win2012 server i wanted to use scsi for the disks as well, but the VM will only boot in with the VD added as IDE0. Additional SCSI VDs are not even shown in window's device manager. What would be the correct driver to add for scsi support, and where...

yes just what I thought at first, but I have my doubts this could be just some misinterpretation error maybe: http://www.users.on.net/~fzabkar/HDD/Seagate_SER_RRER_HEC.html what do you think? best and thanks Sascha

Just got news from the datacenter (Hetzner). Both HD passed their extended tests and don't show any critical errors. So i guess we have something else here? Thanks Sascha

yes, seems so. will replace that one. But if that's not the main problem, then we should investigate the real cause of qcow2 failing, i guess. Such a worrying issue... thanks Sascha