Search results

Also where can I download the 3.12 to 4.x updates.

Having a discussion with another dev. He says that KVMs do not need to be updated or converted. That I can basically take the existing server. Back up all the KVM VMs. Then just update the nodes ONLY and when the nodes are up to 5.2, then simply restore the VMs to the nodes. Correct? I am...

So there is no other way? This is so arduous a process. I was hoping for a better way.

I have already ran that command. As stated above It tells me container not found. ie there are no OpenVZ containers. So they must just be KVM only. If so, Can I directly import them from a backup into 5.2? Please advise.

So what impact does container not found have on my original question? Does the absence of them mean I cannot import them directly into 5.2?

It reports container not found.

first code produced a list of the VMs Second code vzlist list produced the following message CT ID list is invalid. Please advise.

I don't understand the term KVM guest and OpenVZ. I have Proxmox 3.1.21 on 2 nodes. I have various Linux and windows VMs created under proxmox. I have a backup for the VMs. I have no idea if they are openVZ containers or not. How would I find that out? I checked out a few VMs, they all...

Not sure I understand the references to restoring openvx to LXC then restoring KVM ones into 5.2.1 Please explain when you get a moment the process steps so a neophyte can understand how to do it.

Can I directly import my old VMs into my new Proxmox 5.1 nodes? This is a brand new server. I am hoping that I can just bring them all back in via a restore. Please advise.

Winscp? I don't use windows. Not sure how to do what you suggest.

No raid on the backup, just a simple USB drive. No raid controller, using software raid. Not sure about lvm-thin. Where would I look to find out? Main drive is a raid 10 array. All working fine. Ran disc diag on all drives. Xeon CPU 8 core. 64GB ram. Version 3.1.21 It shouldn't be. SSH...

Backups work perfectly. Restores are what are failing. I am not at the DC and with this old version of Proxmox getting to a command prompt is difficult.

I wouldn't know. Where would I find it? It has worked in past but now it fails.

USB but we have never had any issues prior in several years. The USB drive is new. So I know the drive isn't at issue or shouldn't be.

What causes this & How do I fix it? I have plenty of space on the data drive. I simply am trying to restore an image from a backup. * (process:589853): ERROR * : restore failed - bdrv_write to drive-ide0 failed (-28) /bin/bash: line 1: 589852 Broken pipe How do I fix it? BTW if failed at...

That is the plan for sure. Just been trying to schedule the timing.

Any ideas? I do not see this in datacenter/storage

isn't the iso needed for the VM to run?

I am running V3.1.21 planning to upgrade in near future Feb 03 08:12:26 copying disk images Feb 03 08:12:27 ERROR: Failed to sync data - can't migrate local cdrom 'local_data:iso/ubuntu-16.04.2-server-amd64.iso' Feb 03 08:12:27 aborting phase 1 - cleanup resources Feb 03 08:12:27 ERROR...