Search results

Give me an email to send the script to

Please give me an emaol

You have a private message.

There is a *much* faster way, in just 1 single step, that i've developed some months ago and tested successfully by migrating about 25 Xen VMs. If you are interested I can send you the script to test.

My biggest issue is with Go, a language that I don't know. Probably, a Go programmer could write a proxmox driver in a couple of hours (i've looked at some other drivers and are nothing more than calls to service APIs to create/destroy/start and so on VMs)

Interested in this too... There is a XenServer driver for docker-machine, and OpenNebula driver but nothing about proxmox. I really hate XenServer, OpenNebula is really cool but needs to many components (a working cluster, multiple controller nodes, and so on) to be used properly (I don't think...

This works only as long you have storage as files, if you use LVM you don't have these files

https://docs.lizardfs.com

Did it right now. I have to reboot every VM ?

When trying to use xterm.js, connection is automatically closed with error "unable to find a serial interface" noVNC is working properly.

Bump

No, it isn't fixed. I still have to ping from "inside"

Updated right now. Let's see if this fix the issue

# pveversion -v proxmox-ve: 5.1-28 (running kernel: 4.13.4-1-pve) pve-manager: 5.1-36 (running version: 5.1-36/131401db) pve-kernel-4.13.4-1-pve: 4.13.4-26 pve-kernel-4.13.8-2-pve: 4.13.8-28 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster...

Hi to all I have a strange issue with a network interface. When traffic is running, all is working properly. If, for whatever reason, traffic is stopped (the issue is with an interface used for backups, thus traffic is going through only during the night), the interfaces seems to be brought down...

@shantanu Sure, you don't need a reboot when creating the VM with agen enabled. Mine was just a suggestion to make a better documentation.

I think that adding a warning on official docs should not hurt anyone, because you are saying: is not a simple install, you also need a reboot. Just a single line in offical docs shouldn't hurt, something like: If VM was created without the agent flag set, you also need to reboot the VM...

There isn't any problem, simply put, official docs doesn't say that a reboot is needed, thus I've installed our VM (and put it in production) thinking to add the agent in a second time..............

Can't you check the agent by using something like "qm agent <vmid> ping" instead checking only the flag?

Probably because you created the VM with agent enabled. Why that flag isn't enabled automatically ? Anyway, i'll plan a scheduled maintenance for a reboot