Technically, you do not "mount iSCSI". Once the sessions are configured/connected, you can place a filesystem on top of the raw block and mount it.
However, as we are discussing PVE - there will be no filesystem. The user should use LVM on top of...
Hi @Tycho_ , welcome to the forum.
There are many guides out there about connecting iSCSI storage to a PVE cluster. For example, https://www.youtube.com/watch?v=um31y0qVkLk
You can use PVE GUI to create iSCSI storage. There are other approaches...
Currently PVE does not provide live migration/recovery on node failure. The node is gone, there is simply nothing to recover.
There is no production-ready equivalent to VMware FT.
The VM will be restarted, but without the state prior to failure...
Hi @Jochem , none of the above except LVM is compatible with Shared Storage application.
The recommended option is LVM, it gives you RW access from all hosts to _different_ portions of the disk.
There are only two Open Source (Free) Cluster...
Hi @warlocksyno
This is excellent progress on getting Proxmox support working and its really nice to see the effort and attention to detail going into it.
I just wanted to help clarify one concept you mentioned regarding MaxOutstandingR2T. Any...
You can try :
a) force-reinstall openssh package. Continue working on trying to login locally.
b) reproduce the problem - install Debian as VM, confirm access. Install PVE via same steps as before. Did you break it? If yes, perhaps there is an...
I could be mistaken, but IIRC one installs over Debian using PVE repos via internet, not by using ISO. You can check whether PVE installation overwrote the openssh package or its configuration files by querying the package repo.
thank you for...
Do you mean password authentication? May be its disabled? Why don't you try to ssh to "localhost" from the server itself. You can also force password only client auth by using appropriate options. Keep an eye on sshd debug as you are trying to...
Hi @Logfro , congratulations on your first post.
The key message, so far, is "debug3: append_hostkey_type: ssh-rsa key not permitted by HostkeyAlgorithms [preauth]"
The client is trying to use an ssh-rsa key. The server’s HostKeyAlgorithms or...
Excellent, thank you for the update.
Continue your configuration with Multipath, using your storage vendor's recommendation as a guide. Once done, you can configure LVM, or find a guide on configuring 3rd party Clustered FS.
For LVM, you can use...
Thank you for the update, @tdemetriou. There could be many reasons for this behavior:
Wrong cable
Wrong transceiver
Faulty port on the FC switch
Incorrect BIOS settings on the FC cards
Firmware issues requiring update
Missing or incorrect...
@oldtimer, as an elite member of the PVE subscription-owning class, you have access to the support channel. If I were you, I’d compile and condense the issue description, include the package information (along with the full upgrade output), and...
In PVE this service updates the text file that displays the login banner:
systemctl |grep bann
pvebanner.service loaded active exited Proxmox VE Login Banner
Reboot...
Hi @Reartu24,
If the data is that valuable, I strongly recommend proceeding with extreme caution.
Here’s an example of what can happen when a QEMU block is not properly released: Data lost for time window
My recommendation is to address this...
Hi @SaltyMcBitters , welcome to the forum.
Cross-cluster migration is possible via "qm remote-migrate" CLI , or by using PDM (https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap). PDM uses "qm remote-migrate" in the background.
Good...
I think something like this would be better:
response = requests.post(
f"{PROXMOX_HOST}/api2/json/nodes/{NODE}/qemu/{VMID}/config",
headers=headers,
data={
"virtio5": "Storage1-ext4:50,format=qcow2"
},
verify=False
)...
Hi @BD-Nets, you were on point up until this sentence. There are no built-in, or even recommended, cluster-aware filesystems for PVE. Based on all the information OP has provided so far, they should not attempt to configure a CAF. Using LVM is...
You do not want PVE to be mapped to the same LUNs and Zones as your VMware. You need to create new LUNs, new Zones, new mappings.
If the LUNs are properly mapped , you should see the disks in "lsblk" and "lsscsi" output. If you don't - the...
You can do this: https://pve.proxmox.com/wiki/Root_Password_Reset
You can also undo anything related to SDN in /etc/network/ location.
Any locale should have a colon , you can just try all on-screen keys in user field first, so you can see what...