ok, well, i solved it.
deleted the config in /etc/pve/nodes/%nodename%/qemu-server/%borken_id.conf%
this one deleted it from all my nodes and removed the node and vm from web gui too
btw tested to, reinstall same machine same hostname same ip and put back to the same cluster, there was no...
but there is nothing about vm 103 in other nodes lxc or qemu-server folders.
i only found data about px02 and vm 103:
/etc/pve/nodes
is it safe to delete a folder and all of it's data?
if i want to put a node back to the cluster i already had inside it and removed, can i give the same IP and...
well yes i removed the node with delnode
now if i try to do it again:
and in status:
so yes i already deleted it but, i understood this line:
that if i don't want to keep my vm, then i can leave it there
Hello!
I have a vm that i cannot delete. In my cluster i had 4 nodes, but i had to remove one from it, i had a vm inside it. I didn't need the vm inside it, so i just deleted the node.
Now i can't remove both the node and the vm from web gui.
the remove button is greyed out
If i try to migrate...
Can someone confirm to me, if i change my subscription from community to basic, someone from "Proxmox Server Solutions GmbH" will answer for my questions?
And what happens if they can't solve my ticket? Refund the price of my licence?
yes, i can confirm that, the problem is with a pure installation. i made it again on an another machine, and i cant snapshot my debian vm
should i reinstall my nodes with the 3.3 iso? or what should i do?
installed a fresh proxmox server (Proxmox VE 3.4 ISO Installer) on a test machine, with "default" settings, local storage
made a test VM and stuck at snapshotting with this computer too
Formatting '/var/lib/vz/images/100/vm-100-state-teszt.raw', fmt=raw size=1598029824
snapshot create...
now spanpshotting finished with this:
Formatting '/mnt/pve/prox2/images/119/vm-119-state-pregui.raw', fmt=raw size=6815744000
snapshot create failed: starting cleanup
TASK ERROR: query-savevm returned status 'failed'
Hello!
I have some problem yesterday i have installed, 3.4.
Now i can't snapshot my VM-s, it's start "formating" but never ends.
syslog:
Feb 25 12:24:01 p2 pvedaemon[390575]: <root@pam> starting task UPID:p2:000611BD:008A5E77:54EDB0D1:qmsnapshot:119:root@pam:
Feb 25 12:24:01 p2...
I know its different but until now (licence+upgrade) everything (HA, offline, online migration) worked.
I don't really understand this, if i have a physical machine with X CPU and an another with Y CPU and the virtual machine's CPU type is kvm64 how the vm knows what is the physical machines CPU...
Hello!
/mnt/pve/prox1/images/111/vm-111-disk-1.qcow2 is on a shared NFS storage all of the proxmox nodes can reach it, and its working with all other virtual machines.
No, sadly we dont have same computers.
P1 (Fujitsu RX300) have E5645 CPU
P2 (Fujitsu TX200) have E5504 CPU
But as like as i...
Hello!
After my company finally bought 3 community subscriptions i started to upgrade proxmox servers one-by-one.
First i migrated vms from my second node (P2) to first node (P1) added licence and upgraded.
After that i started to migrate vms back to upgrade P1.
I succesfully migrated:
-2...
Is there any chance, to attach storage as lvm and share it as nfs from proxmox server.
i mean i install nfs server on all the proxmox nodes and use something like "Setting Up A Highly Available NFS Server" guide to make them communicate, and use the nfs share on vm-s?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.