dear proxmox experts,
since a while i am getting two error lines when booting up my pve (please see screenshot). after boot everything runs fine. checking my 3 zfs pools in the webui shows their status as online and green. the 4tb pool does no longer exist, the 12tb pool exists but my guess is...
after digging into my bios settings i guess i found the root cause for not booting after kernel upgrade however i have no idea how it occured. hp microserver bios requires to define a boot controller where (as i wrote earlier) a bootable drive is supposed to be connected on its first port. the...
in fact i wonder a little why it reports currently not to be booted by uefi, as the partition structure indicates an uefi installation:
but the bios of this generation of hp microservers (ML10v2) is more than a little bitchy. i spent hours in order to find out it will only boot from a bootable...
hey friedrich, thanks for guiding me. the original installation is indeed a pve 7. right after the release of pve 8 i did an upgrade according the proxmox wiki. everything went well without any error messages. since then i had several kernel updates but this is the first resulting in an...
dear proxmox experts, today i did the proxmox kernel update via webui from 6.2.16-10 to 6.2.16-14. after reboot my hp microserver does no longer found its boot media. i downloaded the most current pve install iso 8.0-2 and did a rescue boot. now i have my pve installation back to life again :)...
dear proxmox community,
we have had some test-installations of proxmox ve 3.4 where connecting the vm's via spice has been working flawlessly but setting up several proxmox ve 4.2 nodes gives me headaches when trying to connect via spice. whenever i try to do it via the webgui virt-viewer is...
hello proxmox community,
i wonder if there is a way to create a browser favorite adding user credentials in order to enter webgui by just one mouse click. i have searched around but no success. is there a way to do this?
thank you
peter
what a shame, it seems i did the mistake to convert ova-files directly to qcow2 or raw using qemu-img and this caused the problem. what i did now is extracting the vdmk out of the ova and only converted the vdmk and voilá my proxmox vm is able to boot that image.
these are the file permissions:
-rw-r----- 1 root root 34416623616 Apr 28 16:56 ubuntu_vm-100-disk-1.qcow2
-rw-r--r-- 1 root root 433324032 Apr 28 17:00 vm-100-disk-1.qcow2
the first line shows the working disk-image and the second one is my converted image which does not boot. however...
dear community,
i did a fresh install of proxmox ve 4.2 and tried to import some existing appliances in ova-format like i used to do using proxmox ve 3.4 by pushing the disk image whether converted in qcow2 or raw format to it's respective place in /var/lib/vz/vm-id/images replacing the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.