Search results

Thanks @oguz, thats work like a charm for me too

Issue still be there upon update to Proxmox 7.1.10 Synology DSM7 (behind NAT), external port are directly redirected to the NAS according to latest fix, perl code look like it will use rpcinfo or show mount depending of the NFS version - tried both, default or v4.x => no result - tried to...

for someone arrived here, pvesm command is as follow pvesm set STORAGE_NAME -is_mountpoint yes make /etc/pve/storage.cfg looks like, with added is_mountpoint yes dir: STORAGE_NAME path /path/to/my/directory content images,vztmpl,snippets,iso,backup,rootdir...

An other way to achieve pve6to7 upgrade on SYS EFI machine is to change enoXX to old ethXX name and do not change the grub settings on my server today : - install pve6 - add ifupdown2 as recommended per Proxmox wiki - remove resolvconf and cloud-init package as asked per ifupdown2 - adapt the...

nice to see many brains can find a good solution. as I struggled with my server, I went to the point I also stop "ooh monitoring" to avoid technician going down to DC to check my PC and reboot it in rescue while I was testing my procedure... what sound strange is that the server (SYS-1-SAT32)...

do I need to do this by touching a file inside the /data or do I need to edit the storage.cfg ?

that nearly what I have found and then done (on my test lab) just create a directory inside a dataset, and ask PVE to use it as "storage -> directory" that's a bit strange but it works, and within the zroot, you can assign quota to a dataset, thus to the directory below

When I setup a ZFS storage on my Proxmox cluster I can only tick "VM disks and Container" I'm partition based as my system is also running from the hard drive as raid partition. Is it possible to use a zfs storage for local backup or do I need to repartition my hardrive to add local raid5 (or...

as per my experience, yesterday from fresh SYS server Sata drives I had to follow the Proxmox wiki upgrade with ifupdown2 and hwaddress in /etc/network/interfaces PLUS I had to remove net.ifnames=0 from /etc/default/grub then reboot is fine if using ZFS, you may need timeout option as...

Thanks Thomas P. Went the difficult way to upgrade from pve6 to pve7 on OVH as upgrade has also added net.ifname=0 1°) new machine so default pve6 as ovh install 2°) login as root and follow the white rabit (aka pve6 to pve7 wiki) => failed at reboot in fact upgrade added...

same here, SYNOLOGY 6.2.4, NFSv4 shared enable (also tried with NFSv3) from LAN, Proxmox 6.3.6 => webUI, add NFS : OK from WAN (port forwarding enable, firewall OK): - Proxmox 5.4 => webUI, add NFS : OK - Proxmox 6.3.6 => webUI, storage -> add NFS => wait and spin, and nothing my workaround...

When I asked them earlier this year, they told me that hold on Proxmox v5 with ZFS due to some UEFI boot server issue. But maybe they didn't know this "timeout" post.

Of course not, I keep my modified version as I only see this line has been modified.

Here is the same, Proxmox 6.1.8 I start uploading an big ISO (6.8Go), it takes time, then my session timeout, even if I click or move the upload window around If I reload, the upload keep going on but if i'm too long, ticket expires, upload fails Is there any place to change session timeout ?

I confirm this worked fine with ESXi 6.5.0 as guest inside a Proxmox v6.1.8 on my small LAB (sandy bridge, 16Go, 500Go HDD) Activate NESTED Virtualisation as per Proxmox Wiki ( https://pve.proxmox.com/mediawiki/index.php?title=Special:Search&search=Nested+Virtualization ) Set your KVM machine...

Thanks for this TIPs, as COVID19 gives me some free time, and I have a Proxmox available, I done this test I provide here my way to upgrade, in doing it BEFORE upgrade Edit ZFS config : nano /etc/default/zfs to set ZFS_INITRD_PRE_MOUNTROOT_SLEEP at value from 0 to 4 (i.e...

the real name of the file doesn't matter if you keep the .conf at the end this is only for you to remember what it does as pve-blacklist.conf might be provided by "proxmox package", I would use a gpu-passthrough-blacklist.conf to keep proxmox able to update his own file and keep mine separate...

I don't know if it is expected or related to my hardware no having a 'rom bar' to get mapped but this is NOT what I have on my system. on MY system : rombar=0 hide my proxmox boot logo and system only show at "login screen" rombar=1 show me proxmox boot/bios logo and progress bar, then GRUB...

Thanks for this info, as per rombar=0/1 : 0 mean you wont see bootscreen until OS is ready, thus hidding proxmox boot logo 1 mean you want to see proxmox bootlog to know your VM is firing up yep, i may give a trial this way first

Worked fine here with linux Guest (my windows ISO won't boot in EFI mode) exactly as you have done, but this line GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on" without the efifboot=off vm config file added STEP1 bios: ovmf #(from GUI, select BIOS = OVMF) machine: q35 #(from CLI) then...