How do I paste into a VM console that has no clipboard?

Why Ctrl+V does nothing in a VM console

A hypervisor's graphical console is a picture of the VM's screen plus a pipe for input. In the protocol behind VNC, key presses travel as key events identified by keysym values, and pointer moves travel as pointer events.

So when you press Ctrl+V, the console does exactly what it is built to do: it delivers Ctrl and V to the guest as a key combination. The guest then pastes from its own clipboard, which has never seen the text you copied on the host.

To be precise, the VNC protocol does define a "cut text" message, but a hypervisor's built-in VNC server has nowhere to put that text unless an agent is running inside the guest. A browser console has a second problem: the Apache Guacamole project's FAQ calls browser copy and paste events "extremely problematic" to rely on, which is why web consoles give you a clipboard panel rather than honoring Ctrl+V.

This is not the same as the corporate VDI case. In Citrix and VMware Horizon a clipboard channel exists and an administrator's policy switches it off. Here nobody blocked anything. The channel is simply not there. (For web forms that reject paste, see why paste does not work.)

Fix 1: do not use the graphical console

The best fix is to stop needing the console. In a terminal session your own terminal emulator does the pasting and sends the result as text.

• SSH - once the guest has a network address and an SSH server, paste works like any other terminal.
• Serial console - for a VM with no working network. On Proxmox, add a serial port (qm set <VMID> -serial0 socket), add console=tty0 console=ttyS0 to the guest's kernel command line, and connect with qm terminal <VMID> or the web UI's xterm.js console.
• RDP or WinRM - for Windows guests once networking is up. RDP carries a clipboard of its own.

The graphical console is for the minutes before any of that works: installers, boot loaders, disk-encryption prompts, a broken network config.

Fix 2: the console's own clipboard feature

• Proxmox noVNC - has an optional VNC clipboard with a side-panel button. Details in the worked example below.
• Proxmox SPICE - switch the VM's display to SPICE and connect with virt-viewer instead of the browser. Proxmox's documentation refers to the "default SPICE clipboard", which needs the SPICE agent in the guest.
• VMware (VMRC) - Broadcom's KB says copy and paste needs VMware Tools in the guest plus three per-VM advanced settings: isolation.tools.copy.disable = FALSE, isolation.tools.paste.disable = FALSE and isolation.tools.setGUIOptions.enable = TRUE. It is text only, and the same KB says it stays disabled at the logon screen for security reasons.
• VirtualBox - the manual says the guest clipboard "can optionally be shared" with the host once Guest Additions are installed.
• Apache Guacamole - open the Guacamole menu with Ctrl+Alt+Shift and put your text in the clipboard field at the top.

The catch most of them share: they need tools or an agent inside the guest, which a fresh install does not have. For first-boot secrets, avoid the problem instead. Proxmox's cloud-init support can inject an SSH public key (qm set <VMID> --sshkey ~/.ssh/id_rsa.pub), and its documentation recommends key-based login over setting a password.

Fix 3: the hypervisor's own "type this text" feature

Some hypervisor clients ship the keystroke approach natively.

• Hyper-V - the VMConnect window has a Clipboard menu whose first item is Type Clipboard Text. As a Microsoft blog post puts it, "the feature types the contents of the clipboard text." Microsoft's current documentation says Type clipboard text is available only for VMs running recent Windows versions, so do not count on it for a Linux guest.
• VMware Hands-on Labs - Broadcom documents a Send Text icon in its own lab console: enter the text, click Send.
• VMware Remote Console and Workstation - Broadcom's copy and paste KB names both: at the Windows logon screen, where clipboard paste is not allowed, "For Workstation the method is a 'Type Text' feature" and "For VMRC the method is 'Send clipboard as typed text'". We found no paste path documented for the vSphere browser console, so treat that one as unknown.

Paste into the Proxmox noVNC console

Proxmox is the worked example because older answers are stale. There are now two routes.

Route A: the VNC clipboard. The Proxmox VE documentation gives the command:

qm set <vmid> -vga <displaytype>,clipboard=vnc

The guest needs the SPICE guest tools (on Debian-based systems, spice-vdagent). Then, in the words of a Proxmox staff member on the support forum: "click the clipboard button in the noVNC panel and paste the text you want to send to the VM into the text box that opens." It is a side panel, not Ctrl+V. The documentation lists two costs: the VNC clipboard replaces the default SPICE clipboard on that VM, and VMs on a QEMU or machine version below 10.1 with the VNC clipboard enabled cannot be live-migrated.

Route B: the serial terminal. In a forum thread marked solved, a long-standing community member's fix for an Ubuntu VM was: add a serial port, set GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,115200" in /etc/default/grub, run update-grub and reboot. The xterm.js console then pastes like a terminal.

Both routes need a guest you can already log in to and change. Shift+Insert, which older posts suggest, is for containers: one write-up that tested it found it works in an LXC console and not in a Linux or Windows VM. For the installer, the boot loader or a guest you cannot modify, you are down to fix 4.

Fix 4: a tool on the host that types the clipboard

The one channel every console has is the keyboard. A host-side typer reads your clipboard and presses the keys for you. Nothing is installed in the guest.

• ClickPaste - free, open source (BSD-3-Clause), Windows 10/11. A notification-area app that types the clipboard wherever you click, with a configurable delay between keystrokes.
• AutoHotkey - free, Windows. A starting point for v2 is below. Two details matter: SetKeyDelay is ignored in the default SendInput mode, so use SendEvent, and {Raw} stops characters like ^ and + being read as modifiers.

^+v::{
	SetKeyDelay 30, 10
	SendEvent "{Raw}" A_Clipboard
}

There are more, including macOS options, on our clipboard typing tools page.

copypaster is one option in the same category, for Windows and macOS: copy, focus the console, press play, and it types the clipboard after a short countdown. The part that matters here is adjustable speed. A laggy remote console can drop or reorder characters that arrive too fast, so being able to slow the typing down matters. It does what Hyper-V's Type clipboard text does, in consoles that lack it, and it changes how text enters the console and nothing else.

Caveats, whichever typer you use

• Keyboard layout mismatch mangles symbols. A VNC console carries key symbols, the hypervisor has to turn them back into physical key presses using a keymap, and the guest reads those presses with its own layout. QEMU's documentation says its -k keymap option exists for displays such as VNC where raw keycodes are hard to get, and defaults to en-us. Proxmox exposes it as the VM's keyboard option, while noting it is "often better handled from within the guest OS." If the layers disagree, letters usually survive and @ # " | \ ~ move. Broadcom documents the same class of fault for special characters in the vSphere web console under several European keyboard locales. Type a test string of symbols before you trust a password.
• Long text and lag. Dropped or reordered characters are a speed problem. Slow the typer down, send long content in chunks, and for anything longer than a screen, get SSH working and paste there instead.
• Passwords stay on the host clipboard. The console never touched your clipboard, so the secret is still there when you finish, and clipboard history or cloud sync may have kept a copy. Clear it afterwards.

Some hosted lab viewers behave the same way, but we have not verified any specific one, so check your provider's documentation. If a lab disables the clipboard as an assessment control, that is a rule to follow, not a bug to work around.