Search results

Thanks for your help but I think I have figured out where is the problem while I was trying to execute qemu-ga.exe commands. We don't have that Qemu-ga folders after installation finish. I have noticed that during installation there isn't any path for installation files and that the browse...

I just want to add that we have the same problem with Windows 2016 and Windows 2012 R2.

The last window from installation wizard is saying that it finished and there isn't any error mentioned so I am assuming that it went without errors. I didn't try to add Ballooning service since I don't yet have the main QEMU service.

I will add a resolution to avoid scrolling down. This is just for the ISO file that installs agent 0.1.173. Don't run the installation from the root of the ISO folder. Go to folder Guest Agent and then run MSI file from there. It is quite a different procedure with that MSI file. It is quicker...

The 3rd node has corosync-qnetd installed on it and acts as Qdevice only. I don't have anything in its logs. So I don't know what went wrong there. We will soon add 3rd full proxmox server to the testing environment so next time I will test it properly. Thanks a lot for your help. Much more is...

Thanks again. Just one more question and then I will stop asking. I just need clarification about fencing. Logs from both servers are in the attachment. Documentation quote: "On node failures, fencing ensures that the erroneous node is guaranteed to be offline. " So fencing occurs on erroneous...

Thanks for your answer mate. We didn't separate network because this is just testing environment. In production we will have a lot more nodes and networks available. I think I understand fencing and HA but correct me if I am wrong. This is my ha-manager status: quorum OK master node1 (active...

I just need to check if this is the bug or the feature. In testing environment we have proxmox cluster with 2 nodes and one Linux machine that acts as Qdevice. As documentation would said: 2 +1 setup. When we lost network on one of the nodes we had expected that other would be still functional...

I guess you where right about corrupted export. We have exported again but this time with VMwares ovftool and import to proxmox whent fine. Thanks for your help.

Well, I have managed to import back to VMware from the same files that I am using on Proxmox. So I am not sure about vmdk corruption. Any other Idea?

Hello, We are in the process of migrating from Vmware 6.5 to Proxmox 6.1.2 and we are having migration problem with one of the VMs. We have two servers in a cluster and we get same problems on both servers. Outputs of ha-manager st and service statuses are also the same on both servers. Does any...