You mean has Broadcom RAID controllers that have issues with kernel 7 when instead of using a hw-raidset doing zfs on the disks behind - that's quiet a difference.
This is typically the opposite of virtualization and then NO: it's not possible as the host/virtualization software requires some memory (and some cpu) at least.
You can of course run any operating system with some virtualization software and...
Why do you want to have ProxmoxVE on a workstation? If you don't happen to be a Proxmox developer (see: https://pve.proxmox.com/wiki/Developer_Workstations_with_Proxmox_VE_and_X11 ) ProxmoxVE isn't really suited to be a daily-driver Desktop OS...
Hi,
yes, I have now verified the path mapping again, and the sporadic NOP timeouts always affect the same iSCSI/SCSI path.
The connection number changed over time because the iSCSI sessions were recreated (connection2:0, later connection4:0...
Hi,
yes, I have now verified the path mapping again, and the sporadic NOP timeouts always affect the same iSCSI/SCSI path.
The connection number changed over time because the iSCSI sessions were recreated (connection2:0, later connection4:0...
Hi @huganega ,
Are you sure that you looked at the correct network interface? The one used by iSCSI?
If you've confirmed that there are no network layer errors, then issue is likely in the higher layer of the stack. A rolling network trace would...
Hi,
I am experiencing sporadic iSCSI connection interruptions on a Proxmox VE 9.2 host connected directly to a Dell PowerVault ME5224.
The issue manifests as ISCSI_ERR_NOP_TIMEDOUT, followed by DID_TRANSPORT_DISRUPTED. The affected iSCSI session...
You mean has Broadcom RAID controllers that have issues with kernel 7 when instead of using a hw-raidset doing zfs on the disks behind - that's quiet a difference.
Jup. Und das läuft auch auf einem 08/15-PC problemlos deutlich länger als 100 Tage, wahrscheinlich sogar jahrelang. Vorausgesetzt natürlich, der PC raucht nicht irgendwann ab. Ist ja schließlich Linux und nicht Windows, das man einmal pro Woche...
WENN man gute Hardware hat (!) UND man Updates nicht zwingend installieren muss/will, DANN sind ein paar hundert Tage Uptime gar kein Problem.
Willkommen in der Linux Welt ;)
This is great ! I have been looking for a way to manage my ZFS datasets in an LXC without bloating the proxmox host with additional packages!
I have slightly altered/limited the mountpoints
arch: arm64
hostname: AlpineZFSmanager
memory: 512...
Proxmox is not intended to do that, as an clustered enterprise hypervisor. Maybe using Debian with KVM/QEMU directly or libvirt to create a VM with the same specs (except for memory, as Linux also needs memory) as that gives your more detailed...
Jup. Und das läuft auch auf einem 08/15-PC problemlos deutlich länger als 100 Tage, wahrscheinlich sogar jahrelang. Vorausgesetzt natürlich, der PC raucht nicht irgendwann ab. Ist ja schließlich Linux und nicht Windows, das man einmal pro Woche...
I'll drop this here: https://pve.proxmox.com/wiki/Multipath
We are currently also working on getting iSCSI, LUN and multipathing integrated into the Proxmox VE tools and web UI. So keep an eye out for it in future release notes.
What do you mean by the same settings?
The same amount of CPU cores, sure. Same amount of memory: no, the hypervisor requires a couple of gigabytes as well. CPU feature flags: yes, set it to type host.
$(pwd) resolves to the current directory/path you're in. pwd tells you where that is.
I felt like that is the easiest way to give you something that definitely works. No need to make this complicated by involving weird paths.