Search results

Oh I see, just found that option, yeah I guess that can accomplish the same thing.

I just found this while searching google. Any chance such a feature is in fact added to the GUI? It would also be nice to be able to do it at the VM level, so that you can shut down a VM and HA would ignore it.

Yeah I think the whole cluster just got corrupted somehow. Now I don't even see anything. Just the datacentre node. How did this happen and is there any way to recover this? Edit: Shutdown both new nodes. Then everything started to work again. Decided to turn one node up only to see what...

I was playing around with Proxmox by virtualizing 2 nodes on my existing ESXi infrastructure, since it was taking forever for my new hardware to come through the mail and I was getting annoyed I started migrating VMs over anyway by converting the vmdks and creating new VMs. Things were going...

Currently my VM storage infrastructure is all NFS based, and so are all my general purpose file shares on my workstation etc. All going towards my NAS. Been toying with doing more of a SAN approach where the storage is on it's separate network and uses dedicated NICs to each VM host, and for...

Oh ok that's good to know, with vmware I found a vmdk that is over 3TB even though the drive is only 40GB in reality. But maybe Proxmox is better to avoid that from happening. So I will just leave the setting alone then.

I'm using all HDDs for mass storage, mostly raid 10. Raid 5 for stuff that's less performance critical. Although is there a way to cap the thin allocation so it never grows beyond the set size? I'd be fine with that too.

i want to setup my stores to preallocate disks, that way they will not grow out of range like with thin provision. I have 40GB disks in vmware that are well over 2TB as they have just grown over time. So I want to avoid that. There is an option for "Full" and also an option for "Full...

This is not really a support question or anything just a good news story I guess. A little over 10 years ago I worked IT and we had a ESXi environment with HA and such and naturally I wanted something like that at home too but also didn't want to pay anything so I put the free version of ESXi...

Ok so I only thought of doing this now, but tested it in Virtualbox. I installed proxmox in a VM, as Virtualbox does support passing VT-D, while my current ESXi setup doesn't. So I installed an OS without KVM acceleration, then proceeded to turn it on, and the OS still boots. So I think I am...

Yeah I just figured that out now, editing it and then assigning a sata port did the trick. I do have other VMs though but they're on another host so guess only the ones on same host show up. I just migrated a VM over to same host and it shows up in list now.

Had to cut the last log short as forum as a limit for text.

Here's all the output. Nothing special happens when I try to reassign, as I never get any option in the drop down to try to reassign to. I also tried with a disk that was created within PVE, to rule out an issue with the conversion I did. root@proxmoxtemp02:~# qm list VMID NAME...

I'm very new to this myself and just getting into Proxmox so maybe I'm missing something, but can't you just migrate VMs manually off both hosts you want to work on? Of course the other host needs to have enough ram to run all the VMs.

If I have an unused disk, how do i go about assigning it to a VM? When I use the option, no VMs show up in the list to assign it to. I'm experimenting with converting vmdk files and found the command to convert, I placed the disks with a test VM and named the converted disks the same naming...

If you install an OS in a VM that has KVM acceleration turned off because VT-D is not available on the node, but later on add a node where it is available, can you migrate the VM over and then turn KVM acceleration on, or will the guest OS need to be reinstalled? I have a temporary cluster...

Running ifreload -a -d seems to have fixed it. Without -d I was getting these errors but -d somehow fixed it. I just want to be clear though, by setting the vmbr1 (vlan aware) trunk interface on a vm, and specifying the vlan at the vm level, the VM is still only seeing that vlan correct...

I'm trying to figure out networking but running into issues. So the node has two NICs, ens32 is management, connected to my management vlan, as a regular connection. Ens34 is a trunk port to the switch. So I tried to follow various tutorials on how to setup the vlans, but no matter what I did...

This is not the best setup but is temporary as I plan to get off ESXi once I buy more hardware and then build more nodes then migrate to them. But in the meantime I decided to just setup my first node as a VM on my existing standalone ESXi server so any new VMs I create I can do them on Proxmox...

Oh ok guess I'm out of luck then. Well hopefully they add that version as an option to install later down the road. I guess I will just need to find a different way to backup for now. Technically I only need an initial backup of the OS once everything is configured so I will just do some...