VirtualBox 5.2.6双向剪贴板无法使用，寻求技术支持

Hey there, let's work through this clipboard problem together. I've run into similar quirks with VirtualBox's shared clipboard before, so here are targeted steps to fix it:

1. Ensure Guest Additions are Properly Installed (Critical!) #

The bidirectional clipboard relies entirely on VirtualBox Guest Additions. For your Windows 7 32-bit guest:

• Go to your VirtualBox window's top menu, click Devices > Insert Guest Additions CD Image.
• In your Windows 7 guest, open the mounted CD drive and run VBoxWindowsAdditions.exe (make sure to run it as Administrator).
• During installation, don't skip any components—ensure the "Shared Clipboard" feature is included.
• Reboot the guest machine after installation completes.

2. Double-Check Clipboard Settings #

Sometimes settings don't stick as expected:

• Shut down the guest machine (don't just pause/save state).
• Go to Settings > General > Advanced for your VM.
• Confirm Shared Clipboard is set to Bidirectional (you can also set Drag'n'Drop to Bidirectional for extra functionality).
• Click OK to save, then start the guest again.

3. Verify Related Services on Host and Guest #

Guest Machine (Windows 7) #

• Press Win + R, type services.msc and hit Enter.
• Look for the VirtualBox Guest Service entry. Ensure it's running, and set its startup type to Automatic.
• If this service doesn't exist, your Guest Additions installation failed—repeat step 1 carefully.

Host Machine (CentOS 7) #

• Open a terminal and check if VirtualBox core services are active:

  sudo systemctl status vboxdrv
  sudo systemctl status vboxservice
  

• If either service is inactive, start them with:

  sudo systemctl start vboxdrv
  sudo systemctl start vboxservice
  

• To make them start automatically on boot:

  sudo systemctl enable vboxdrv
  sudo systemctl enable vboxservice
  

4. Check SELinux Restrictions (CentOS 7 Specific) #

CentOS 7's default SELinux configuration might block VirtualBox's clipboard functionality. Test this temporarily:

• Run this command in your host terminal:

  sudo setenforce 0
  

• Restart your guest VM and test the clipboard. If it works now, you'll need to adjust SELinux policies permanently (avoid leaving SELinux disabled long-term). You can add a policy module for VirtualBox or adjust context labels for relevant files.

5. Upgrade VirtualBox to a Newer Version #

VirtualBox 5.2.6 is quite outdated and has known bugs. Upgrading to a newer stable version often resolves such issues:

• First, remove the old version:

  sudo yum remove VirtualBox-5.2
  

• Add the official VirtualBox repository for CentOS 7, then install a newer version (e.g., 6.1, which is compatible with CentOS 7):

  sudo yum install VirtualBox-6.1
  

• Note: Back up your VM before upgrading to avoid data loss.

6. Test with a Fresh VM (As a Last Resort) #

If all above steps fail, create a new Windows 7 32-bit VM from scratch, install Guest Additions correctly, and test the clipboard. This will help rule out any corrupted configuration in your existing VM.

内容的提问来源于stack exchange，提问作者Bilesh Ganguly