Search results

@frankmanzhu not wrong per se, so don't confuse my point of view with his, I maintain multiple VM's per host (60-100) and cannot afford to have vGPU tripping my host out. but if @simon11118 has only the one or very few other VM's on that host it could be worth a shot, my environment just can't...

Sorry @simon11118 if not helpful, by steering you away from passing through non-vGPU's as if they were vGPU's, but @alexskysilk is right, it would be better on physical box for sure.

Its generally considered not advisable to use a "gamer" GPU card for a passthrough-to-vm AI card. Even it it connects to the VM, its still just a 5090, your AI will be the slowest thing you ever saw. We have done this trying to use various cards, some Nvidia (gamer) style and some Tesla cards...

might be better off with one of these since you need the other peripherals to work also, but you would need type C port on the host

Although I have done this with a USB sound adapter, never video. Why do you need to see the VM's screen on a physical monitor anyways?

Any idea what the ETA when that gets implemented?

Well, it's "ALPHA" for a reason. Let's hope they see these comments and implement.

How did you change the text in that Allocation box?

I see its not really "total configured" as it says, it should say something like: "not running but configured" maybe?

Good question, I see that on mine now too. I guess we need someone to explain what exactly does "Configured" mean? Probably not what we think it is. Look what one of my Remote clusters shows: CPU Cores assigned 509 running / 524 physical (0 total configured) Memory assigned 742 GiB running /...

Perfect, I didn't even think to look on the DataCenter side.

api error (status = 400 Bad Request): error creating token: api error (status = 400 Bad Request): Parameter verification failed.tokenid: Token already exists How do I use existing token or delete the one that's already there?

We updated to 0.7.0 of the esxi import tool to fix the transfer issue. So clearly there is more bug fixes that are being fixed we will wait for a stable version of the tool. its not even version1.0.0 yet.

We updated to 0.7.0 of the esxi import tool to fix the transfer issue. But your solution makes sense also.

Hypervisor: VMware ESXi, 7.0.3, 19193900

pve-esxi-import-tools: Installed: 0.6.1 Candidate: 0.6.1 Version table: *** 0.6.1 500 500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages 100 /var/lib/dpkg/status 0.6.0 500 500 http://download.proxmox.com/debian/pve...

root@proxmoxVDI1:~# pveversion -v proxmox-ve: 8.1.0 (running kernel: 6.5.11-5-pve) pve-manager: 8.1.10 (running version: 8.1.10/4b06efb5db453f29) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-8 proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3 proxmox-kernel-6.5: 6.5.13-3...

**Update**, after waiting 15 minutes I can rejoin the server now. What is going on here?

Well, I tried it on one of the other VMWARE boxes and it did the exact same thing. I now only have one VMWARE box I can connect to, although I can't migrate any VM from any box.

I connected to 3 vmware vsphere boxes. 1 dropped during a VM migration. I deleted the storage and now cannot re-add it. I get the below error: create storage failed: (vim.fault.HostConnectFault) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = '503 Service...