Search results

My goal is to have another copy on another node in the same cluster but at a different location. In looking at the chart on the zsync page: I wouldn't want my VMs replicated to every node in the cluster, nor would I want them replicated to every node that's running ZFS and SSH. Then again...

I've done a significant amount of work myself given that OpenBSD itself isn't Proxmox's responsibility, but the part that remains is the configuration of Proxmox. I'm not likely to find much assistance with that anywhere outside of Proxmox. Most other platforms use libvirt, which is what I find...

*bump*

*bump*

Just thought I'd check in to see if the bit of config I posted above would do what I'm trying to do.

Right. I've already installed the Qemu package in OpenBSD (required to get the guest agent) and had related discussions on their mailing list. However, I've circled back to Proxmox because from what I understand, OpenBSD doesn't have drivers for the default device Qemu uses (I just woke up, but...

ACPI has reduced functionality as compared to the agent. ACPI isn't going to flush the filesystem to give me a clean backup. Per this page: http://www.linux-kvm.org/page/VMchannel_Requirements Would I add something like this: opts: -device virtio-serial \-device...

That obviously would clear the error, but wouldn't really solve the problem.

102: May 15 01:00:05 ERROR: VM 102 qmp command 'guest-fsfreeze-freeze' failed - unable to connect to VM 102 qga socket - timeout after 35827 retries 102: May 15 01:00:15 ERROR: VM 102 qmp command 'guest-fsfreeze-thaw' failed - unable to connect to VM 102 qga socket - timeout after 101 retries...

Ah, it appears the in-deployment help button contained the answer I needed. Across the industry, it's rare that in-app help is more useful than Google. Sorry for overlooking that. Backup works now.

ERROR: Backup of VM 102 failed - disk 'virtio0' 'local-lvm:vm-102-disk-1' (iothread=on) can't use backup feature currently. Please set backup=no for this drive at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 77. I have an OpenBSD 6.0 guest and I'm trying to backup the VM. I'm getting the...

Seems to still be an issue. ERROR: Backup of VM 102 failed - disk 'virtio0' 'local-lvm:vm-102-disk-1' (iothread=on) can't use backup feature currently. Please set backup=no for this drive at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 77.

I don't see any built-in methods to clone a CT. What's the best way of going about this? IIRC, it was fairly straight forward in the 1.x days, but I'm not so sure anymore.

A newer version of Proxmox fixed whatever caused this to happen.

I deleted the new interface so I could get back to work until someone more experienced could look over my shoulder. When I went through the steps I did with a friend over TeamViewer, I didn't have issues with ifup eth1 hanging anymore, though I did have issues with it coming up automatically at...

I now see where it says on the downloads page to use dist-upgrade. It's just habit to do an upgrade.

I did an apt-get upgrade, resulting in the below errors. Thoughts? Processing triggers for pve-manager (4.4-5) ... Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for...

I have a CT where I added a second Ethernet port. One is for management and the other is for public access. I can't manage to get the second one to come up. When I do an ifup eth1, it hangs for about a minute and then reports `Failed to bring up eth1.` Thoughts? root@libre:/etc/network# ifup...

I see a comment that makes it PVE 4 friendly, but I'm now stuck at: INFO: trying to get global lock - waiting... Ideas?

I found this: http://www.jamescoyle.net/how-to/1632-move-proxmox-container-to-different-storage but it is for OpenVZ containers and not LXC containers.