Search results

I've been playing with PMG this afternoon and whilst I like the idea and clustered setup of the platform, i'm not too sure if this is suitable for a hosting environment (many servers, users between them). The settings appear to be fairly global with no ability to add a domain and have specific...

Already using them for wider management and for our internal VMs but would like to do this filtering on customer VM which they cannot see or change which as far as I know won't help with. Some ports need to be blocked at the entry point to stop those customers who have VMs which are just not...

This isn't so much a support request but a feature improvement. Currently you can set firewall rules on the cluster/dc level, hv/node and VM. We would like to apply some rules at the highest level that filter down to VM, such as ports we want to block for all users (i.e malicious ports used...

As requested. proxmox-ve: 6.1-2 (running kernel: 5.0.15-1-pve) pve-manager: 6.1-3 (running version: 6.1-3/37248ce6) pve-kernel-5.3: 6.0-12 pve-kernel-helper: 6.0-12 pve-kernel-5.0: 6.0-11 pve-kernel-5.3.10-1-pve: 5.3.10-1 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.15-1-pve: 5.0.15-1...

Is there a fix on this? Still an issue on the latest release.

We had this issue with Deb 10 in latest proxmox. So with a bit of config changes and additions to cloud.cnf in the image now works fine. Add a known working resolver to resolv.conf in the image (i.e 8.8.8.8 - this will get overwritten). The the following to the bottom of cloud.cfg. I've left...

proxmox-ve: 6.0-2 (running kernel: 5.0.21-2-pve) pve-manager: 6.0-12 (running version: 6.0-12/0a603350) pve-kernel-helper: 6.0-12 pve-kernel-5.0: 6.0-11 pve-kernel-4.15: 5.4-6 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.21-2-pve: 5.0.21-7 pve-kernel-5.0.21-1-pve: 5.0.21-2...

We've upgraded to the latest release 0-12 but this still fails, even when setting the storage on the command line. root@i:/mnt/pve/images/dump# qmrestore vzdump-qemu-162-2019_11_22-02_35_22.vma.gz 90003 --storage core-hdd restore vma archive: zcat...

Sorry, I don't have the steps or any access to OnApp any longer.

Can be done, requires a bit of work but was a while ago now so don't have the exact steps. Essentially it was get the running VM on OnApp to an image, copy it over, mount the disk and dd it across. We have them all running now on Proxmox.

It may be worth posting what version of cloud-init should be used (as a minimum). The one in CentOS 7 seems to suffer the same issue.

Great thanks. Will wait for that to be pushed out to an update. :)

Done: vm-106-cloudinit vg-1 -wi------- 8.00m

Did it add the resolvers to the correct interface? I've been trying a manual build as the guide mentioned is best to be used so we know what software is installed but they're added to lo.

For that cloud-init: vm-106-cloudinit vg-1 -wi-ao---- 8.00m It has been running since it was used. If I was to stop the VM and then start again, it would fail. Would you like the output from the command after doing that?

For where it is stored. iscsi: c1-sp1 portal x.x.x.x target c1-sp1 content images lvm: storage-1 vgname vg-1 base c1-sp1:0.0.0.scsi-xxxxxx content rootdir,images shared 1

Where do you want the storage config from? VM: agent: 1 boot: dcn bootdisk: virtio0 cipassword: [removed] ciuser: [removed] cores: 3 hotplug: disk,network,usb,memory,cpu ide0: storage-1:vm-106-cloudinit,media=cdrom ipconfig0: ip=x.x.x.x/24,gw=x.x.x.x memory: 2048 name: xxxxxx net0...

Not at the moment I don't think. What OS did you try out of interest?

The docs for cloud-init are a little thin on the ground being such a new feature. What is the expected behaviour for this in proxmox? Should the cloud-init drive remain always connected? if so, after the machine is shut down and then started again, it fails with the error: qemu-img: Could not...

Maybe one to be worked on. Hooks would be nice to be able to run at any point on the hostnode via the API? ;) lvchange -ay /dev/vg-1/vm-xxx-disk-1 losetup -f (get next loop device) losetup /dev/loop0 /dev/vg-1/vm-xxx-disk-1 kpartx -av /dev/loop0 parted /dev/loop0 resizepart 1 100% (resize...