Search results

Whats the output of ceph -s cat /etc/pve/ceph.conf Please paste the output within tags or use the formatting buttons of the editor </>.

the ZFS message sounds like a red-herring. But the ext4 journal messages look somewhat more problematic. Can you log in to the host? Either via SSH (which would be nicer, as you could copy&paste output) or directly on the screen from which you made the screenshots? The outputs of lsblk mount...

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#user_mgmt You will need to give the user access to the resources they need. So if they should be able to edit virtual disks, or which ISO is used, access to the storages. For networks, you can give permissions on full zones or individual...

please look at the explanation at https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher and what has been discussed here. The behavior is as expected.

definitiv nicht getestet! Was spricht dagegen den jetzigen Cluster Node für Node upzugraden? Zuwenig Platz auf den anderen Nodes um eine Freizuräumen? Alternativ könnte man vlt auch ganz einen anderen Ansatz nehmen: PVE 7.4 sollte die remote-migration für VMs schon können. 1. Neue PVE 9 Node...

For stretch PVE + Ceph clusters we recommend a full PVE install for the tie-breaker node. See the newly published guide: https://pve.proxmox.com/wiki/Stretch_Cluster

Ich glaube nicht, dass wir ein Move Disk auf das gleiche Storage aktuell zulassen.

With a 3-node Ceph cluster you need to be careful when planning how many disks you add for OSDs. More but smaller is preferred, because if just a single disk fails, Ceph can only recover to the same node in such a small cluster. For example, if you use only 2 large OSDs per node, and one of them...

Wenn ich nichts falsch verstanden habe: Da die linked clones nur über die Disk Images mit dem Template verknüpft sind, könntest du die Disks der VMs (temporär) auf ein anderes Storage schieben (Disk Action -> Move Disk). Dadurch wird der gesamte Inhalt der Disk in das neue Image auf dem anderen...

Please. Threads in the forum can easily be missed with how much is going on.

Grundsätzlich empfiehlt es sich die VirtIO Geräte zu nehmen. Für Disks SCSI mit VirtIO-SCSI-single als Controller, oder den Virtio-Block. Bei NICs die VirtIO. Da muss dann kein ganzes Gerät emuliert werden für den Gast und die Performance sollte somit besser sein.

The API approach (e.g. with pvesh) is probably the best approach. If you are unsure which calls are of interest, do the procedure via the web UI and take a look at the browser's developer tools, especially the network tab, to see which API calls are involved in each step.

My guess is, since host mem usage and mem usage show the same value, that the VM does not report back any detailed information. You can check that in the Monitor submenu of the VM and run info balloon there. Compare the output from a VM that reports it correctly to see the difference in infos...

VLAN tag 1 is usually the default untagged VLAN. As in, those packets won't get a VLAN tag added when they leave the physical interface. But whenever you assign one of the SDN VNETs to a guets virtual NIC, any packet leaving the host should get the set VLAN tag assigned. One can check that with...

looks better :) the subnets are useful to define as the info there will pre-populate firewall aliases. you then need to apply it on the main SDN panel

Having multiple vmbr interfaces with the same physical bridge port doesn't sound like a good idea. I would definitely recommend that you set up a SDN VLAN zone with vmbr0 as the base bridge for it and go from there for all the VLANs that should be accessible by the guests.

VLANs can be tricky to debug. If your switch supports it, give it an IP in the VLAN, then you can check if the connection to the switch works. For guests, by now I recommend that you use the SDN VLAN zone. It is one easy place to have every VLAN. In a cluster it makes life a lot easier, but also...

The post-stop won't show up in the task log (if that is what you mean), as it will be run after that task has finished by the daemon cleaning up after a VM has shut down. Writing to a file would be one way to check if the post-stop ran. If there is a bug, please report it at our bugtracker...

This is a screenshot from pre PVE 9, though, right?

Sehr cool! Hast du überlegt, das, in welcher Form auch immer, direkt bei Virtio als Installationsschritt upzustreamen?