Search results

It seems to be effecting Windows systems (maybe Win 10 only?) I opened two noVNC consoles, one Windows 10 and the other Linux Mint, and the linux VM syncs properly. Win 10 was always opposite. I tried your solution with no joy. 1) Turned client desktop Num Lock OFF 2) Started VM 3) Opened VM...

Thanks! Seems everyone is right. Since @H4R0 gave his suggestion, I am seeing numbers I didn't expect to see on my ZFS mirrored vdevs storage. I must be doing something wrong and will now have to dissect my storage systems because I would expect much better performance than a single disk in a...

Haha! Yes I know. ‍♂️ I ran top before the cluster came back online and noticed a kworker was using a lot of CPU. kworker/u132:3-ib-comp-unb-wq My systems are connected to storage via 40Gbe infiniband. After getting the cluster back online and storage mouted cluster-wide, that kworker is not...

root@node05:~# find /raid10bak/encrypted_data /raid10bak/encrypted_data /raid10bak/encrypted_data/pve /raid10bak/encrypted_data/pve/backups /raid10bak/encrypted_data/pve/backups/dump /raid10bak/encrypted_data/pve/backups/dump/vzdump-lxc-101-2020_05_16-05_34_43.log...

Sorry for the delay. I ran into some serious work-stoppage with the latest kernel. As you requested @Stoiko Ivanov Showing zfs filesystems/datasets root@node05:~# zfs list NAME USED AVAIL REFER MOUNTPOINT raid10bak 2.21T...

@Alwin Okay I am starting to get somewhere now It does appear to be a kernel issue -- or an issue with pvesm / corosync and the later kernels. That, I am not sure. What I did was bring up ONE node (node04) with pve-kernel-5.3.18-3-pve (all other nodes remained on latest...

Thanks for that suggestion :) Because it's happening to local storage and not only network attached storage it would seem to me something else is at play? I cannot see the contents of local /var/lib/vz or of any other storage be it local or networked. After clicking Summary or Contents of...

It's semi-local. Its a PVE installation with ZFS exported as NFS. Of course the other systems access it remotely. Having it join the cluster allows me to monitor the storage through PVE like a PVE Storage Appliance. Thanks for taking the time to respond @Alwin >>> Both services are running...

pvesm status hangs NFS not mounting on all PVE nodes cat /proc/mounts sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=99011432k,nr_inodes=24752858,mode=755 0 0 devpts /dev/pts devpts...

@Alwin local storage is accessible in console/CLI; but not NFS I am noticing strange things. NFS remains unmounted but yet I see PVE claims HA is successfully starting HA containers with resources on NFS storage (that wont mount) Timestamp in picture are minutes ago.

Thanks for your replies. It may be related but its not exactly what I am experiencing. I tried the previous kernel with no joy. All of my nodes boot. I can access each node Summary page on PVE GUI. >>> This appears to be storage related. I am having trouble accessing ALL storage (including...

So I'm in a huge rut. I updated my nodes and everything seems to have broke. ZFS wont mount encrypted datasets (separate post for this created) NFS wont mount NFS wont export No syslog (in GUI) Local storage wont load (communication failure) Datacenter shows quorum and active nodes -- all...

After an update to ZFS 0.8.4-pve now two storage systems with encrypted datasets will not mount child datasets. ZFS is treating child/sub datasets as directories. Both systems have an 'encrypted_data' dataset with underlying datasets inheriting encryption details. root@node05:~# zfs load-key...

I am getting miserable speeds while doing backups. My backup-storage is NFS over RDMA. Speeds while writing to the NFS shared storage is much much better than VZDUMP. I tested writing directly to backup-storage, twice system memory: root@node02:/mnt/pve/backup-storage# time dd if=/dev/zero...

Proxmox works on just about everything. It seems your needs are fairly minimal. Almost everything will work in your use case as you described it. If you add the SSD/SAS disks and ensure the CPU meets the demands of the VMs -- you're set.

I've had some passthrough devices that work best not on machine: q35 Have you tried default/i440fx instead of q35? Then try again with and without the rom file. args: -cpu 'host,hv_time,kvm=off,hv_vendor_id=1234567890ab' bios: ovmf bootdisk: scsi0 cores: 2 cpu: host,hidden=1,flags=+pcid...

My initial post was concerning CAPS and NUM locks; but since, CAPS is fine. NUM-lock remains effected. If I change the NUM lock off focus or within noVNC -- it does change in the VM - albeit, exactly opposite to my client/PC. oot@node01:~# pveversion -v proxmox-ve: 6.2-1 (running kernel...

Mostly, yes. The only significant difference is that you will have then also installed the VirtIO drivers onto that physical disk. But otherwise, the disk would still boot without proxmox because those previous drivers are also present.

SATA mode works well. VirtIO SCSI or VirtIO Block will be better paravirtualized with the host. Did you try adding a VirtIO device? 1) attach the physical disk as SATA (which you said works) 2) attach a second disk as a VirtIO hard disk 3) Power on VM and boot into Windows 4) Install VirtIO...

Still having this problem and scouring the web for answers led me back to this post I made in late 2019. Num-lock appears to be oppositely synced on my end.