But for sure the error 'storage 'vmbox_lvm-local' is not available on node 'c1-krrblade1'' confusing. Because VM does not use that storage directly.
I understand that it is more related to my specific setup.
As I have to use somehow local storage of VMbox on other nodes. So that is why it is...
LVM layout is not an issue here.
I've installed multipath-tools so user space tools wil not be confused by double PV
That is why I've renamed VG on each node to own name instead just pve. So nodes will not confused by multiple pve VG.
But thing is that VM is running thru iscsi storage.
And...
Sure it say not available on blade1/2.
And on vmbox it shows list of vms on it.
But thing is that that same LVM storage is shared thru ISCSI to other nodes.
And VM 10085 is actually configured not with vmbox_lvm-local but with vmbox-lvm-on-scsi.
So during migration it looks like logic of...
Yes those were deleted.
I did moved disks with deletion enabled.
No any reference to old disk in config,
As you see I've posted grep result from config.
I am suing raw LVM as you can see. So no snapshots.
For sure it is some node spesific cache or something.
As I tested following.
Moved config manually to c1-krrblade1 node.
Started there with no issues.
Migrated back to vmbox node on UI with no issues.
But when tried migrate again to c1-krrblade1 it failed with same error.
Bug??
Hello All,
I am having issues with migration after I move drives to shared disk. That issue appears only with new proxmox clusters.
Here issue is:
Before VM disks were on vmbox_lvm-local.
Moved them to shared iscsi drive.
root@vmbox:~# grep disk /etc/pve/nodes/vmbox/qemu-server/10085.conf...
Hello All,
How to get into NoVNC Clipboard/Settings pannels?
I see they are present in source code of page and some time I even see those blinking during load console.
Thanks
Guys
Are there any way to see memory ballooning in action?
I have multiple guests which are not using memory fully and for sure host can steel certain amount of memory from them instead of using swap.
Memory Balloon is not much documented in Wiki.
Requirements are not clear. For linux...
Mine is the same.
I have two fresh nodes.
Non of vms working with SPICE. What I am missing?
root@kvm1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm...
I am using SPICE from Proxmox UI.
Debug I've made to have some additional info.
In general when I click the SPICE button I am getting error that viwer can not connect to graphical server.
I know that :) You have 30 sec.
If file is expired you will get an error about ticket.
So I was doing download file and connecting immediately.
Thank you for your answer.
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.