Search results

I fixed it. For anyone who googles this issue... It was UEFI messing up the boot. I exported the image without the UEFI (my software lets me strip it) and it boots fine in proxmox.

For the record, I have also tried this (using the same steps as above) on a proxmox 5.2-1 server as well and got the same results. I don't have a 7.0 server setup to test with nor the hardware to do so.

That is the exact guide I followed. I mentioned that in my first post. The only errors related to my VM of 310 are related to the network boot that it tries after the hard drive. There is nothing else listed with any errors. It simply tries to boot and never does anything until I run the STOP...

Yes, it is the correct boot order. Text from config: agent: 1 bootdisk: ide0 cores: 4 ide0: vm_storage:vm-310-disk-0,size=120G ide2: none,media=cdrom memory: 8192 name: userPC net0: e1000=7E:8A:0A:79:2E:31,bridge=vmbr1 numa: 0 ostype: win10 scsihw: virtio-scsi-pci smbios1...

Proxmox version 6.3-3 Issue: I have a .raw image that I made of a user's computer (windows 10). When I create a VM with this, proxmox will not boot it. In Depth: I have backup software (MSP360) on one of the user's computers here because they have programs installed that cannot be installed...

I actually ended up fixing this myself before either of these replies were made. I'll give my answer to my issue because copying the config and migrating the LXC was the first thing I tried weeks ago when this issue first happened. It doesn't work because the storage on Node 5 was "stale"...

Bear with me as I do my best to explain the situation. We have ProxMox setup on 5 physical machines hosting over 20 VMs. Several weeks ago we lost power to the building and unbeknownst to us, one of the physical servers (a node in ProxMox) apparently had a failed migration of a VM that was...