great to see progress.
The command and output indicate that you've been able to pass beyond the fingerprint verification and on to the next error.
I presume you meant to ask why you are getting this error now? If so, the simplest explanation is that the token ID does not, indeed, exist.
You...
Hi @cshill
a) use <> CODE tags from the menu of the edit box. This will prevent smiley faces replacement and present readable information
b) replacing a suffix of an IP, which is located within a reserved private network space, hardly helps you with any security posture
c) you have spaces " " in...
Hi @TMKC, have you tried pools and/or tags as described here:
https://forum.proxmox.com/threads/feature-request-folders.26668/
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @bemo47 , the procedure below has always worked for us:
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @Adamced, yes, its possible.
Changing networks is somewhat involved. I'd recommended reading on forum about pitfalls, making a good backup, or even building a virtual cluster and ironing out the procedure there first.
good luck
Blockbridge : Ultra low latency all-NVME shared storage for...
Hi @Ryan Anderson ,
One explanation - the values you are looking for were not specified. For example:
root@pve-1:~# qm create 998
root@pve-1:~# pvesh get /nodes/pve-1/qemu/998/config --output-format json-pretty
{
"boot" : " ",
"digest" : "a0097e911e7c535d4b392072fedc19c917a41422"...
Next time consider posting actual commands you are using, including output/error.
You verify token by specifying it on the command line
qm remote-migrate 999 9999 'apitoken=PVEAPIToken=root@pam!test=69398265-0806-4401-9503,host=172.16.202.202' --target-bridge vmbr0 --target-storage local-lvm...
A quick search brings up this recent conversation that may be helpful :
https://forum.proxmox.com/threads/qm-remote-migrate-from-a-single-node-to-cluster.156014/
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
The [] and <> are part of Linux documentation convention.
The [] mean that the parameter is optional.
The [<>] means that if you do replace, it must be particular information.
The <> means its required and there is no particular format.
[<target-vmid>] means that you can provide target VM ID...
I would recommend using API/pvesh:
pvesh get /nodes/pve-1/tasks -typefilter qmclone
further filtering can be done via "jq" for particular time and status
https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/tasks
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi @proxdrop ,
"qm" command interface can only manipulate the VMs local to where "qm" is running. Lets just say for historical reasons.
If you want to "pull" migrate (or do anything else), you need to use pvesh interface. There you can and must specify the Node you are addressing.
You can also...
Great news Pavel.
We are looking forward to the fixed release.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @milocheri ,
The QEMU guest agent is not developed or supported by PVE. You'd need to find community specific to Oracle Linux, they may have a more direct knowledge.
Keep in mind that QEMU agent source code is freely available. If push comes to shove, you can compile the binary on your own...
This sounds like an error at an early boot process (bios), before OS is engaged. Have you set the boot order properly in VM options?
What is your VM configuration? "qm config [vmid]"
Does the serial console work on your VM? "qm start [vmid] && qm terminal [vmid]"
If it does not, post a...
Hi @husskii ,
There are two types of clones in PVE: full and thin. Both are an identical copy bit-by-bit of the original VM.
MAC and VMID changes are controlled by PVE. The IP/Hostname could also be controlled externally, ie via PVE or DHCP.
The boot-id change is expected on every boot, whether...
Thank you for the update @t.lamprecht . We've been running PVE/QEMU9 in parallel with PVE/QEMU8 in our CI/CD since the original announcement, and it is rock solid.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @Amnesty1850 , welcome to the forum.
You can extract creation time of the VM/CT via API or CLI. However, I don't think anything internally in PVE is tracking the last run time. You'd need to build your own tracking/reporting for that.
Blockbridge : Ultra low latency all-NVME shared storage...
Hi @Guillaume Soucy ,
This is more of a generic Linux question rather than something specific to PVE.
I'd start my research here: https://unix.stackexchange.com/questions/106765/mounting-an-old-floppy-image-file-ima-format-how-hard-can-it-be
Blockbridge : Ultra low latency all-NVME shared...
none. Orderly shutdown your VMs, downgrade the kernel and reboot.
I don't now anyone who is looking forward to data loss
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
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.