This pull request fixes the arm64 builds for debian 11 (bullseye).
Description
The main problem was, that the packages open-vm-tools is not available for arm64 in the bullseye nor the bullseye-updates suite. The arm64 build is only available in the bullseye-backports suite. By adding the bullseye-backports suite the build succeeds.
When starting the VM a lot of Unknown ioctl 1976 messages are logged into kernel message log and the console. According to https://github.com/vmware/open-vm-tools/issues/495 this is because the kernel module _vmw_vsock_vmcitransport is missing. The kernel module is neither available in the debian-security kernel (5.10.218) nor in the bullseye-backports kernel (6.1.90).
The easiest fix at the moment it to blacklist the modules _vmw_vsock_virtio_transportcommon and _vsockloopback. As soon as _vsockloopback is loaded, the error messages appear.
Related Issue
1371
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)
Checklist:
[X] I have read the CONTRIBUTING document.
[X] I have run the pre-merge tests locally and they pass.
[X] I have updated the documentation accordingly.
[X] I have added tests to cover my changes.
[X] If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
This pull request fixes the arm64 builds for debian 11 (bullseye).
Description
The main problem was, that the packages
open-vm-tools
is not available for arm64 in the bullseye nor the bullseye-updates suite. The arm64 build is only available in the bullseye-backports suite. By adding the bullseye-backports suite the build succeeds.When starting the VM a lot of Unknown ioctl 1976 messages are logged into kernel message log and the console. According to https://github.com/vmware/open-vm-tools/issues/495 this is because the kernel module _vmw_vsock_vmcitransport is missing. The kernel module is neither available in the debian-security kernel (5.10.218) nor in the bullseye-backports kernel (6.1.90).
The easiest fix at the moment it to blacklist the modules _vmw_vsock_virtio_transportcommon and _vsockloopback. As soon as _vsockloopback is loaded, the error messages appear.
Related Issue
1371
Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.