Search results

Hey :) In the same time of your error, what 's saying your Host ?

Hey :) Check Firmware BIOS update, and the same for hardware stuff you've in your server. :)

Say "hello" is never a bad idea. " E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 212.224.123.70 443]" Seem to be clear. Did you have any sub to proxmox ? If not, it's normal.

Hey :) NP hope this will now work for you :) Don't forget to close de topic ;)

https://superuser.com/questions/1134711/how-to-remove-menu-or-change-timeout-for-selecting-os-windows-7-in-grub-boot-m

Hey, If HW raid on, increase grub time ;)

Hey, i've by-passed that with a debian 10 installation with a proxmox-ve installed after ;)

Hé, On HyperV, did you used UEFI BIOS settings ? If yes, configures your New VM as q35 host ;)

Hey, Increase the grub-loading time ;)

Hey :) Did you done yours firmware BIOS update ? ^^ Had the same problem with older BIOS ;) Cordially,

Hey, For host situation, no really answer for you .... But, for yours VMs, check if: - cache on writeback - advances disk : SSD emulation, IO treads, asyncIO = treads Cordially,

HEy, Check how to convert your virtuals disk format before import. After, create manually a skeletton of your vm, and attach yours disks on ;)

hello, I take the liberty of reminding you that MS products are enormously IO consumer. So, what does your VMs do if you offload the disk IOs to the threads of your procos? (configure iothread in your virtual disk declarations) Ideally, depending on your configuration, MS Windows works best...

Hi, Did have you checked your BIOS version? This reminds me of a too old BIOS version problem on the motherboard. Cordially,

hello, had a same problem with a dead motherboard... If this can help you :)

Don't forguet to pass your post to solved please :)

Hey :) Hum ... Yours nodes are together in NAT mode ? If yes, it's normal that one VM cannot ping an another VM on the 2nd node. In your case, NAT mode allow only that: VMs node1 can ping NODE2, BUT NOT THESES VMs VMs node2 can ping NODE1, BUT NOT THESES VMs too Create another bridge on each...

Hey, first check if you're raid card is active. If yes, increase the defaut grub time, it may just too simple as that ^^

Hey, How are created yours declarations in /etc/fstab? Did you use ZFS? In the first case, can you try to edit your fstab with uuid dev definition ? Sincerely

hey, Bind to your vmbr0 each IP you need, and redirect each to the local IP of yours VM.