Search results

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...

Looking through most recent threads on resizing, I can see wiki links on how to do this via commands within the VM but nothing specific outside of the VM. We want to automate this so if an order comes in for an increase it can happen without user involvement or needing to get in to the VM...

Whilst that may be the case, it appears others have adjusted around any issues with cloud-init. Given that CentOS is very popular, simply sticking your feet in and saying "not our problem, get them to fix" is not a workable solution. As someone else has done, we could patch but then this is...

Just to add, similar to the other report. We have the exact same problem. dns-nameservers and dns-search are added to lo instead of eth0 # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network...

Well, technically how it is done is as explained. So maybe you can add something where with a VM you set the IPs used and it creates the last example automatically based on the MAC and the IPs listed against the VM preferably via the API. Currently, in a shared environment, proxmox isn't great...

The GUI itself isn't relevant as i've explained how it works as you can see from the host node via the command line. The node sets what IPs can be used and communicate to/from the VM and this is regardless if the firewall is enabled or disabled on the VM. Even if the user sets their VM firewall...

What about where the system admin wants to limits what IPs a VM should be able to use but still allow the user to allow all traffic to those IPs? If we don't enable the firewall per VM, the IPsets where allowed IPs can be set don't work. Look at Onapp, which does do this. You set the IPs on the...

Hi All, So we're playing with "ipfilter-net*" to specifically state what IPs a VM is allowed to use - that works fine. However, if the INPUT firewall is set to ACCEPT, it allows all traffic to any IPs and not just those in the IPset. I would say that the INPUT needs to still honour what is...

Interesting. What if the user removes/stops the agent? What would then happen?

Not ideal, we don't want to do anything within the VM itself. Previous software set these rules on the host node. No, they are not. As noted, the only way to do this in the GUI would be for admin to create a rule in and out but users could then alter their own specific VM rules. There is no way...

I'm already aware of that but my question is not addressed, really. "Does Proxmox have any plans where an IP/or list of can be assigned to the VM in the interface and on the host node and ensure that only traffic to or from that/those addresses will flow." Not in the existing fire-wall rules...

With KVM VMs at least, the IPs are on a sort of free-for-all. We could create an inbound and outbound firewall route so they can only use their assigned IPs but that is quite labour intensive and still means they can at least add an IP alias and ARP will do nasty things. Does Proxmox have any...

That's all been checked. We run an identical configuration on another cluster too. Switch reports no errors in logs or errors on the ports. As the network is internal, there isn't any router to contend with.

Noted but sadly that's just not what we're seeing. I wish it was. :(

That still leaves some unanswered questions and also a possible solution, if any, to the issue where a single VM could saturate sessions, causing massive instability on a cluster with nodes rebooting all over the place. Could be hard to stop too if the nodes keep rebooting before you can...