Hello, I've been testing my HA config lately (3 nodes with 10 VMs distributed) I configured with HA two of my VMs on the node-3; needing to reboot the node-3 server, I migrated these two VM, one on node-1 and one one node-2, I then rebooted the node-3 server via reboot command line.
My question...
Ok I managed to start the VM imported with the OVMF (UEFI) BIOS and it works perfectly while still not working with SeaBios... Is it a problem if I keep it as OVMF ?
I tried booting it using UEFI but it says that the Windows needs to be repaired but it can't be done via the Windows GUI
It is a Windows 10 (64 bits) guest.
Here is my VM config:
root@pve01:~# qm config 102
boot: cdn
bootdisk: ide0
cores: 2
ide0: pve_pool:vm-102-disk-0,size=50G
memory: 2048...
If I have a .vmdk, I only have to use the qm importdisk command and I can start the VM created earlier ?
Because I keep having :
Nothing to boot: No such file or directory
No bootable device
Hello guys,
I've been trying to import VMs recently, I got the .vmdk file and I followed the tutorial given on Proxmox Wiki but I still have questions. When I create a VM within Proxmox GUI, I can choose my pve_pool (rbd disk shared by my three nodes) ressource as a storage disk.
But when...
I already got a pool created as shown here:
But as you can see here:
On each node I have a pve_pool (pve0n) that has approximately 10 TiB of storage, and I'd like to know if it is possible to have a disk or shared storage solution that can combine pve_pool(pve01), pve_pool(pve02)...
Hello !
I created a cluster with 3 nodes on Proxmox 6, and I'm trying to get a pool that is composed of all the nodes, because I only got a pool for each node but not a main one with combined storage !
So do you guys know how to create a pool with all of my nodes in it ?
Thanks in advance for...
I managed to find an answer to my problem, after making a "pveceph purge" I reinstalled Ceph on each node, then I created the monitors.
After this I fast formated the disks that I wanted to use as OSDs, and used this tutorial to create an OSD manually...
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.