Search results

So all you should need to do is configure your host with an IPv6 address. Configure the container network interface for IPv6 DHCP or static.

I don't see anything wrong with the ports, ips, or mount command. Enable nfs debugging: rpcdebug -m nfs -s all Go to PVE and watch Syslog attempt mounting nfs share Disable nfs debugging: rpcdebug -m nfs -c

You must mean public IPs from your ISP? If you mean local IPs then that's nearly impossible. You can just change your /24 subnet [255.255.255.0] to a /23 subnet [255.255.254.0] which would double your available IPs... All the way to a /16 subnet which would allow 65534 available IPs. For...

Could the "wrong media" be in the physical media? Perhaps you are trying to burn the ISO to a DVD+R on a DVD-R drive?

I found a bugzilla report #2384 with a patch in devel available.

I was testing my ZFS over ISCSI storage with different settings, compression, encryption, etc on different datasets on my ZFS pool and noticed the disk numbering convention numbers the disks per storage appliance. The first disk you create will be called vm-vmid-disk-0; attaching another disk...

I don't see any NFS mounts on storage.cfg Are you mounting manually via fstab? Can you share the results of: [/ICODE]nfsstat -m[/ICODE] Ensure your server can ping client7 and your container responds. I'm not sure your features line of your container config does anything. What I would do is...

I've also discovered that while creating a new VM, select OVMF as BIOS, and create the EFI Disk on the LIO iSCSI storage: the creation fails because both disks; it appears to be trying to use the same zvol name. TASK ERROR: unable to create VM 101 - error with cfs lock...

Might be GPT/UEFI only on that nvme? Try changing the VM Hardware> BIOS = OVMF and attach and EFI Disk Also, if that OS was not previously attached to a VM you will probably want to change the disk to sata0 If it boots, temporarily create and attach a small virtual disk to the VM as scsi and...

I just posted some information that may be useful to you [here]. That information is for unprivileged containers but should work for you as well. UID/GID would be different for privileged container because the root UID/GID should match the host. You can also try remounting with NFS'...

I don't think there is any problem in using partitions. Make sure they are GPT and I would suggest using /dev/disk/by-id intead of /dev/sdXx

I was writing a response to another thread and some error occurred and I can no longer find the post. This is not a question but may be useful for anyone else who may be attempting to add a network share within an unprivileged container as a mount point and wish to gain write access permissions...

ISO files are written to template/iso PVE is looking for ISO/IMG files in /mnt/pve/iso/template/iso in your case If you don't wish to move the ISO files then you could create a symbolic link to the root of the NFS mount umount the NFS share From the NFS server change directory to NFS export...

I used Rufus to USB flash. Rufus will prompt asking to burn in ISO or DD mode -- I had no success burning it in ISO mode, only DD mode would work to complete loading Proxmox into the installer. ISO mode made the PVE Installer fail to find the CD/DVD image that another secondary partition on the...

I've not yet moved onto setting up HA. Currently only clustered. I hope that's all that's needed. FYI: QEMU VMs do not experience this.

My downloaded ISO shows 741 MB... I'm guessing you have a corrupted download.

USB passthrough should work.

I don't think noVNC is turning on CAPS in the VM. It's acting as though SHIFT is being held. For those that think they solve it with the caps-lock: you can verify if it's the SHIFT key by inputting numbers. Are you still seeing special characters? If so, the VM is still holding shift and now...

I am having similar issues. I'm noticing it during password entry where I hold shift for special characters. It will act like the shift key is permanently held in the VM so letters become capitalized and numbers et al. become special characters.

He's already asked for your VM config at post #6