Search results

~# qm config 106 agent: 1 balloon: 1 bootdisk: virtio0 cores: 4 memory: 4096 name: wintest net0: virtio=A6:F7:3A:AF:ED:5E,bridge=vmbr1 numa: 0 ostype: win10 scsihw: virtio-scsi-pci smbios1: uuid=b0297f0f-1436-4e79-b59f-9640467b94f9 sockets: 1 virtio0: local-zfs:vm-106-disk-1,discard=on,size=30G...

You can use simple GET requests with curl, use something like Guzzle, or a wrapper like https://github.com/ZzAntares/ProxmoxVE

Did you take a look at https://pve.proxmox.com/pve-docs/api-viewer/index.html ? I believe you might be looking for HTTP: GET /api2/json/nodes/{node}/qemu/{vmid}/status/current CLI: pvesh get /nodes/{node}/qemu/{vmid}/status/current

I am backing up to an NFS server running Centos 7.3, is that the cause of the issue? @Alwin, the local system, is this referring to the host node? It's behaving normally during backup.

Got around to trying this again. Still not resolved using the latest VirtIO drivers. There are no errors in the Windows Event Log, VirtIO is up to date, QEMU installed and all services running for that, ballooning, vss, etc. Made sure that VSS has permissions and no access denied errors. When I...

Qemu Agent is checked in proxmox gui. 'vssadmin list writers' output is okay. I'll try with latest virtio drivers, I was using the stable branch.

Was able to solve that permission error. Now upon backup there is nothing in the Event Logs windows wise but still having the same lockup problem. We have about 350 windows guests to move over, but may have to just leave those in hyper-v.

Seems this is on the right track, still investigating. I appreciate the help thus far. Odd since the services are all running Local System, which has full access. I even added 'Network Service' to the COM Security Volume Shadow Copy Service error: Unexpected error querying for the...

Yes, that's responding okay from the node - anything else I can check? The guest itself seems to be running fine, issuing shutdown from proxmox works okay so QEMU is working okay there too.

I had the same issue though I recall reading that ipfilter will not stop ping due to different layer and conntrack elements. It also doesn't appear to stop inbound by way of the proxmox gui, only out. The GUI does not add inbound rule. For testing try using telnet instead of ping. Outbound...

>sc query "BalloonService" | find "RUNNING" STATE : 4 RUNNING >sc query "QEMU-GA" | find "RUNNING" STATE : 4 RUNNING >sc query "QEMU Guest Agent VSS Provider" | find "RUNNING" STATE : 4 RUNNING >vssadmin list providers vssadmin...

I've installed a Windows Server 2016 VM and followed the instructions to a T for enabling the additional drivers. QEMU agent is running and responding okay, as is Ballooning service. I'm having an issue where the guest will go completely unresponsive in the console, RDP, and even to ping...

Hi All, Just signed up for a subscription and looking to go production with Proxmox and migrate our existing infrastructure to it. Still have some confusion regarding IPFilter and IPSet options in the firewall. Ultimately trying to prevent IP spoofing for both VMs and containers. Does enabling...