In this article
AMD describes Radeon PRO V340 as a dual-GPU Vega board with 32 GB HBM2 in total.
AMD describes Radeon PRO V340 as a dual-GPU Vega board with 32 GB HBM2 in total. It is not one GPU with unified 32 GB memory or a validated route for current Cycles HIP.
Official variants and the memory boundary
AMD describes V340 as a dual-GPU board with 32 GB in total. This does not specify one device with unified memory. The checked primary material does not establish individual GPU capacity here; validate it for the actual configuration rather than substituting an assumption.
| AMD board | Total memory across two GPUs | Board power |
|---|---|---|
| 32 GB board total across two GPUs | 32 GB HBM2 | Not verified |
Establish the LLM software path
Radeon PRO V340 is absent from the checked ROCm Core SDK 10.1.0 GPU list. Support for a neighboring model cannot be transferred through a shared generation or a similar name. For a separate experiment, the llama.cpp build documentation describes a Vulkan backend. That route requires a suitable driver, detection of the actual device, and validation of the selected GGUF; Vulkan in a specification does not establish that every operation works. Save tensor-placement logs and compare output with a reference run before concluding that the GPU is actually involved. This is not a claim of current official ROCm support for this card.
A practical scenario for this model
The practical case is evaluating an old VDI server recorded only as “V340, 32 GB.” Recover physical-device count and guest-resource allocation first. Aggregate board memory does not mean one model can address it as one contiguous resource. The checked AMD material is also not used here to declare individual GPU capacity: establish that through documentation for the actual configuration and device detection. Separately identify the available API and actual placement for a model experiment rather than inferring them from SR-IOV presence or a working remote display. The outcome may describe only a limited guest profile. That is more useful than an assumed modern universal card that confuses the physical board, multiple GPUs, and virtual resources. Preserve these boundaries before attempting to select any model profile.
Validate Blender Cycles separately
Vega predates the RDNA 1 HIP hardware floor in the Blender Cycles 5.2 LTS manual. It is therefore not a current Cycles HIP target; historical compute support or a ROCm LLM experiment cannot establish renderer eligibility.
Historical visualization positioning cannot make Vega meet the current Cycles HIP floor. An archived VDI project and its previous renderer need their own version record rather than replacing current qualification.
Preserve a machine-level acceptance record
Physical board memory and guest-assigned memory are different quantities. Record the virtualization profile and resources visible to the device; owning the host board does not give every virtual machine all of its memory.
State explicitly: two GPUs, aggregate 32 GB on the board, and individual-device capacity not established by this source. Board power also remains unverified; neighboring V products cannot supply an inferred value.
The acceptance artifact should connect board identity, software versions, model revision, and the workload actually exercised. After any of those changes, the old result describes its original run rather than establishing compatibility of the new configuration.
Related reading
Multiple GPUs in a pool: one service or one large model?; GPU containers or virtual machines: what to check before deployment; NVIDIA and AMD GPU catalogue for LLM inference and server rendering.