too high latency would be displayed in ceph cluster health i suppose?
in total there are 3 VMs affected by the same problem until now.
all 3 VMs are Windows Server 2025 with now different versions of virtio-drivers.
All VMs are on differet Nodes...
No difference. I had initially created the fresh container with nesting enabled (by mistake as it doesn't really need it). But the old containers work without nesting.
Eigentlich ist die QEMU-Schicht die einzige logische Zwischenschicht, die VNC eben grundsätzlich mitbringt.
Nach längerer vorher vergeblicher Suche, habe ich auch eine Bestätigung gefunden:
https://www.qemu.org/docs/master/tools/qemu-vnc.html
Don't think it's the config. It matches the old container details.
arch: amd64
cores: 2
hostname: test
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.0.1,hwaddr=XX:XX:XX:XX:XX:XX,ip=192.168.0.29/24,type=veth
onboot: 1
ostype...
Das Update der Verschlüsselung hat nichts mit Ceph 20 zu tun. Das Ceph Upgrade musst du immer manuell machen. Du hast garantiert noch Ceph 19 und dass du jetzt das Upgrade der Schlüssel machen musst, steht in der Doku dazu.
Wenn du ein sauberes...
Was sagt lvmconfig? Die Meldung kommt nicht von PVE/LVM sondern von deinem Community Script. Du solltest dich daher am besten an dessen Entwickler wenden.
Ich bin zuversichtlich, dass du via PVE selbst ganz normal Gäste bzw. vdisks erstellen kannst.
Ich kann dir keinen detaillierten technischen Breakdown geben wie das alles genau implementiert ist in Proxmox. Aber noVNC ist ein JavaScript-basierter VNC-Client, der für die Proxmox-Webkonsole verwendet wird und die VNC-Ausgabe über...
Ich kann dir keinen detaillierten technischen Breakdown geben wie das alles genau implementiert ist in Proxmox. Aber noVNC ist ein JavaScript-basierter VNC-Client, der für die Proxmox-Webkonsole verwendet wird und die VNC-Ausgabe über...
With a little bit of playing you can probably find out by yourself if there is a better one (and use it in your apt sources or test via /etc/hosts).
dig +noall +answer +subnet=8.8.8.0/24 download.cdn.proxmox.com @$(dig +short NS cdn.proxmox.com...
hello,
just a short follow-up:
setting zeroing_mode to "writesame" seems to fix that (like describe in the link)
echo writesame_16_unmap > /sys/block/sde/device/scsi_disk/1\:0\:3\:0/zeroing_mode
echo writesame_16_unmap >...
This is most likely a different issue - discussed in:
https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/post-871933
the post links to a test-kernel that should...
It isn't something the .302 driver fixes, then. With a second VM now affected, it is most likely the shared Ceph/host path.
Did `ceph health detail` or the OSD logs show slow ops at the time of last night's 129 events?
Drafted with AI.
Is that so? I am not an expert. perhaps you can explain. there is nothing "fundamental" seperating docker from other userspace software.
Because in a non production environment it is the sweet spot of application deployability with namespace...
Ah, come on. Docker is a container platform that relies on many of the same Linux kernel features as LXC. You don't even have to be an expert on the underlying technologies to realize that this is fundamentally different from running just any...
Yes, but that is less likely to happen when Docker is running on bare metal or inside a VM. The reason is that nobody involved is specifically developing and testing for this exact use case (Docker inside LXC on Proxmox). As long as that remains...
Something I forgot: ProxmoxVE9 introduced a new, still in tech-preview-feature which allows converting oci ( aka docker ) container images to lxcs. To be honest I'm not a big fan since this procedure destroys the immutability which is the biggest...
No and propably never will be since they use the same features of the kernel ( namespaces, cgroups etc) and host system ( apparmor etc ) so any update might introduce a breaking change. This is more likely with major upgrades ( like PVE8 to...
Here's my current thoughts/opinions about running docker/podman in CTs
- It currently works fine (at least in a debian CT)
- It might break on docker (related) or kernel updates
- Breakage is likely to be fixed soon but you'll have to be patient...