Recent content by jbedgood

After a few more tests I found the following. It happens only when I attempt to make the windows VM use efi boot disk and bios type OVMF. Is there something wrong with how I'm building the EFI disk and attaching it?

I removed the display part that I had as it was giving the exact same error. So I removed it and got the same errors. Tried several other display settings none work. qm set 1022 --vga std,memory=16

Hello, I've been working on trying to automate the building of windows VM's in proxmox but I keep running into the same issue when I do it with a bash script. When I attempt to start the VM after using this bash script I get the following error: Any suggestions on what I'm doing wrong?

I gave up trying to figure that out. No matter what my network settings are if I reboot the Host I can start the Container one time. So seems to me its not the network. But I've tried to add additional local drives to the HOST to make a bigger filesystem for containers. The issue is that I can't...

This is all now after I've started the container once logged in ran some commands and then shut it down. Now it won't start. I can get it to start again if I reboot the Host machine. Debug root@kvm2:~# cat /tmp/lxc.log lxc-start 103 20201116153725.272 INFO confile -...

Ok I've tried both 802.3ad as the LACP link agg protocol and just active-backup. It seems that the Containers will start once then they won't start again. What kind of information do I need to get this resolved?

ok I see one problem in my network already. I'm working to fix that will update as soon as I have that resolved.

lxc.log root@kvm2:~# cat /tmp/lxc.log lxc-start 103 20201112160507.510 INFO confile - confile.c:set_config_idmaps:2051 - Read uid map: type u nsid 0 hostid 100000 range 65536 lxc-start 103 20201112160507.510 INFO confile - confile.c:set_config_idmaps:2051 - Read uid map: type g nsid 0...

You are correct. I don't know why I was thinking the bridge was the same as a bond. But I have configured a BOND and put my interfaces into it. But the Container still fails to start. Not sure what to look at now.

Maybe I'm missing something. But I see one bridge configured with the 172.16.0.31/23 address. and that is also what is showing int he GUI. Here is a picture of it.

The CIFS are my local synology NAS devices. They are on the same switch as my proxmox servers. /etc/network/interfaces auto lo iface lo inet loopback iface enp1s0f0 inet manual iface enp1s0f1 inet manual iface ens6f0 inet manual iface ens6f1 inet manual auto vmbr0 iface vmbr0 inet static...

root@kvm2:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,backup,vztmpl lvmthin: local-lvm thinpool data vgname pve content rootdir,images cifs: Syn2 path /mnt/pve/Syn2 server 172.16.0.22 share prox...

I'm not sure that is the issue since I have 2 different network storage devices and both of them exibit the same issue of containers with disks on them won't start. I am still researching if fsck can be run on the remote network storage but if anyone can think of any other reason I'd greatly...

So based on the thought that it might be related to my storage. I created another container and put it on local storage and it works fine. How do I determine what needs to be done to get the containers to work on my remote storage?

when trying to move the disk this is what I got. Logical volume "vm-103-disk-0" created. mke2fs 1.44.5 (15-Dec-2018) Discarding device blocks: 4096/2097152 done Creating filesystem with 2097152 4k blocks and 524288 inodes Filesystem UUID...