Search results

Ampere? https://amperecomputing.com/reference-platforms/ https://store.avantek.co.uk/ampere-altra-mt-jade.html But I agree otherwise - the AMD64 *server* portion isn't viable, but the ARM *client* I'll be looking at deploying

So I just pick a random Job ID? is there a specific format to adhere to?

On this "stable" ID for jobs.cfg: what is the (for 7.1 mainly, but also 6.4 till I upgrade that cluster) recommended way to script or automate (via bash/Ansible/Terraform) the backups for VMs and LXCs?

Check SSH logs too.....

same status in 7.1 - /me awaits the feature request

https://bugzilla.proxmox.com/show_bug.cgi?id=1532 for the feature request Have the same "issue" today ;(

depends whether you are able to remove the module, ie. it's not in use but for things networking, you do want to reboot

Yeah, that is a risk I'm willing to take in my environment given I'm the sysadmin for all of them, so if somebody/code other than what I need/want to execute in the VMs, then I have other/bigger security problems :(=) Great idea, was thinking about that, but currently the cost/expense not worth...

Well, I have the same "problem", as using hosting providers I am limited in my choices and thus the mixing of AMD and Intel is becoming a reality for various configurations and price points :( Thus the question for me is also which is the beterer performance wise: QEMU64 or KVM64 ? (Yes yes, I...

Yes and no. The assumption here: BBI -IPv6/64 - Node1{FireWall/NatDevice} -(vRack NAT6 or >/64 [note1])- Node2{VM} The {VM} can be moved from Node1 to Node2 and back, as long as its on the same vRack-dot11q vlan. The "secret sauce" is that {FireWall/NatDevice} that is listening and answering...

I was wondering about that on macOS and then I found this, so yeah, it's FireFox - MS-Edge (Chromium) displays correctly

Thank you! I was however hoping for a DKMS version to NOT have the above problem :(=)

could you be so kind and point us at the instructions/package/etc. for the recompile and the nvm firmware?

At present (as on 9 Nov 2021) OVH does NOT provide ROUTABLE (ie. public accessible) IPv6 on the vRack as they do with the /30+ IPv4s attached to the vRack The only way I am aware of to get IPv6 on the vRack, is to use the public interface of a server, and have that NAT/route to the other...

just got this https://bugzilla.proxmox.com/show_bug.cgi?id=1007#c15 that is peppered with spam URLs Where is the best place to log/report them?

I'm 100% with you @fabian and I did read the documentation. I'll refer you to the definition and use of brackets in writing: the sentence should stand on it's OWN... the brackets are OPTIONAL details, and that's why the simple explanation and the results I experienced "surprising". Now I know...

ZFS is one of the great features/etc. to use with PVE I.M.O. Containers isn't great 'cause off Linux's NIHS - yes I'm using them, gone a while, but you want to use KVM/qemu/VMs to compare to ESXi Sounds like you need no reason so just go back to ESXi ;(

You missed the points: 1. It's counter intuitive 2. The Documentation is NOT clearly EXPLICIT about it... only in parathesis which in the English language is "optional" https://www.google.com/search?q=parentheses+meaning&oq=paranthesis

but the problem here is that the "expected" is that it'll parse the rootfs/mpX/etc. and use that exact storage in that config. I'd rather say that the manuals then need to be specific: "Simple mode will ALWAYS ONLY use local storage, no parsing the config, only the layout/sizes of the storages...

Good day, Trying pct restore on the CLI today for the time, on PVE 7.0, it seems to only use the "local", not the rootfs config inside the backup, and I seem to need to provide the storage parameter to use the rootfs on the correct storage...