Search results

Yes need it . it works with latest. I'm just struggling with tine to submit it. Work gives my too many project's

Use the ceph F's to store your iso backups etc. Use the rbd pools for your vms eg the drives on them. If u have more than on pool you can use move disk function in proxmox to move the disk between pools. In fact you can use that to move disks on local storage to the ceph storage. You can set...

VMware DRS. I use the proxmox APi to kind of do this. But all the records of the VM are in an external system when it adds a new VM it works out the best host to use. Every so often it checks where they are as maybe someone manually migrated or some failure occurs. I can also check and move...

HA is your friend. As you are using shared storage all hypervisors have access to the VM disks so u don't need replication. If you use HA and the node that the VM is on fails it will move to a new node in the cluster if the HA is enabled

after you did that patch you did systemctl restart pvedaemon also once you installed the cloudbase-init you manually ran the sysprep cd C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf C:\Windows\System32\sysprep\sysprep.exe /generalize /oobe /unattend:Unattend.xml add in a serial...

You don't need the ssd. I have lab setup with spinning disks and not even E5 just some 4core E5620 32gb memory it works fine . Slow but fine and it's using bluestore

Like Dominik says only a couple of weeks but now since is seems that its working based on peoples feedback let me do that procedure I just need to find some time

The regular user in the image is centos unless you change its name in the user box in the proxmox ui. In that case it will make a new user and set it's password. Or if you don't change the user it will set the cents users password. It should never be setting the password for root. The new user...

Yes the centos7 cloud init is too old. If you edit the config file /etc/over/qemu and change CI password to plain text it will work. Or install a new cloud init In your template https://copr-be.cloud.fedoraproject.org/results/%40cloud-init/cloud-init-dev/epel-7-x86_64/

so sounds like it all works now great

yes sorry I forgot to say 5.3

OH btw it will only change that password for the that created user eg the [DEFAULT] username=Admin and you would have to have the create user plugin enabled also cloudbaseinit.plugins.windows.createuser.CreateUserPlugin

you can open the VM have a look at the cd drive for cloud init and see if the password is there should be under a key called admin_pass in /openstack/latest/meta_data.json

In the VM you set the Options to Windows OS right you have also added a serial device to the windows server and selected that com 1 when you did the install of cloudbase then when you start the VM you can see the output by going to the console and select the xterm.js Was the DNS setup...

You might also want to look at this Another user put some code to overcome the password issue https://forum.proxmox.com/threads/windows-guest-vm-with-cloudbase-init.48307/#post-235182

Thanks for that also now we have lost of options lol you should not have needed to change the cloudbase init just set like username=Admin groups=Administrators inject_user_password=true there is another variable also first_logon_behaviour first_logon_behaviour=no should do it also...

Please see this post https://forum.proxmox.com/threads/finally-cloudbase-init-windows-servers.48823/#post-235085

OK here is a patch I have used it for Windows 2012R2 and Windows 2016 I m now trying 2019 IT creates windows only functions in the Cloudinit.pm Linux nocloud and configdrive2 still works Make sure in your template you set the option to a windows one and then this comes into play Password kind...

Sorry for the delay on this I did a lot more looking and found some issues with the DNS servers and there are a few other things As there are a lot of differences I will refactor my changes so that IF its windows it will use a different set of functions that way it will not have a problem with...

Yes a lot depends on the VM;s and what they will be doing e.g do you have an idea of the number of vcpu per VM and the RAM for example if you have 20 VM per server and they are 2 GB ram and 1 VCPU you would need 40 GB RAM and 20 VCPU luckily you can over provision the RAM AND Physical CPU...