Skip to content
This repository was archived by the owner on Jan 1, 2021. It is now read-only.

Conversation

norio-nomura
Copy link
Contributor

fixes #1369

@tianon
Copy link
Contributor

tianon commented Dec 10, 2018

Is this the minimal set necessary, or is this simply enabling more flags and one of them happens to do the trick? (How much testing has this had?)

@norio-nomura
Copy link
Contributor Author

The minimal set is CONFIG_VMWARE_PVSCSI for #1369 (maybe #1368 too).
But I think all adding configs are needs for running on VMware.

This is VMware physical memory management driver which acts like a "balloon" that can be inflated to reclaim physical pages by reserving them in the guest and invalidating them in the monitor, freeing up the underlying machine pages so they can be allocated to other guests. The balloon can also be deflated to allow the guest to use more physical memory.

This driver supports VMware's para virtualized SCSI HBA

This module implements a VMCI transport for Virtual Sockets.
Enable this transport if your Virtual Machine runs on a VMware hypervisor.

How much testing has this had?

I confirmed that .iso including this change works like v18.06.1-ce do.

@norio-nomura
Copy link
Contributor Author

Information about Linux driver for VMware: https://kb.vmware.com/s/article/2073804

@unsignedint
Copy link

Sorry, I am new to this project.. can someone explain how to actually build this PR (or boot2docker in general)? Thanks :)

@frol
Copy link

frol commented Dec 21, 2018

FYI there is also PR #1372, which partially overlaps with the listed modules.

@frol
Copy link

frol commented Dec 22, 2018

How much testing has this had?

I have combined the kernel options from this and #1372 PRs and built an image which successfully run on my VMware ESXi server and detected the persistent hard drive (thus, my issue #1368 will be resolved with this PR) and also successfully passed my automatic stress-testing suite (it uses quite a few of Docker features and some extra Cgroup capabilities).

@unsignedint To build boot2docker.iso, run these two commands:

docker built -t boot2docker .
docker run --rm boot2docker > boot2docker.iso

Here is the image I have built: https://drive.google.com/file/d/1uIeMp5UE6xswZdoU4Xn7nOAvsJ-cefix/view?usp=sharing

@stefangweichinger
Copy link

stefangweichinger commented Dec 26, 2018

How much testing has this had?

I have combined the kernel options from this and #1372 PRs and built an image which successfully run on my VMware ESXi server and detected the persistent hard drive (thus, my issue #1368 will be resolved with this PR) and also successfully passed my automatic stress-testing suite (it uses quite a few of Docker features and some extra Cgroup capabilities).

@unsignedint To build boot2docker.iso, run these two commands:

docker built -t boot2docker .
docker run --rm boot2docker > boot2docker.iso

Here is the image I have built: https://drive.google.com/file/d/1uIeMp5UE6xswZdoU4Xn7nOAvsJ-cefix/view?usp=sharing

built the image as well, thanks for documenting ... but how do I tell docker-machine to use my image instead of downloading as usual? Do I have to provide my own image via http really? pls advise, thanks.

EDIT: solved by providing local image ... thanks

@tianon tianon merged commit c33ce3a into boot2docker:master Dec 28, 2018
@norio-nomura norio-nomura deleted the add-missing-configurations-for-vmware branch December 28, 2018 00:39
@norio-nomura
Copy link
Contributor Author

Thanks! 🙏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Persistent partition does not exist on VMware Fusion with v18.09.1-rc1
5 participants