12:51 p.m.
Hi all,
I'm the maintainer for open-vm-tools package in Fedora.
For the benefit of Fedora Atomic users on VMware platform, I would like to add
open-vm-tools package to Fedora Atomic.
Could somebody please advise/help me with the process involved to get open-vm-tools
package in Fedora Atomic?
Thanks in advance,
Ravindra
1:33 p.m.
Great - is there a *technical* (meaning non-policy) reason why Fedora's
version of open-vm-tools doesn't support mounting host files in the guest?
VMware does such a terrible job at tracking changes in the kernel source
that I've given up on using it. And why is open-vm-tools installed by
default on Fedora Workstation on bare metal or VirtualBox or qemu-kvm
guests?
Sorry if I'm "shooting the messenger" here but I've just wasted a couple
of
days trying to make VMware Workstation work on a Fedora 21 host and Fedora
21 guests work with VMware hosts. There are two open source alternatives,
one of which is just a "yum install" away on a Fedora 21 host and which
works flawlessly with all modern kernels.
On Fri, Nov 21, 2014 at 10:51 AM, Ravindra Kumar <ravindrakumar(a)vmware.com>
wrote:
Hi all,
I'm the maintainer for open-vm-tools package in Fedora.
For the benefit of Fedora Atomic users on VMware platform, I would like to
add open-vm-tools package to Fedora Atomic.
Could somebody please advise/help me with the process involved to get
open-vm-tools package in Fedora Atomic?
Thanks in advance,
Ravindra
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
1:07 p.m.
Thanks for the feedback Ed.
Fedora's version does not have vmhgfs driver and therefore it does not work out of
box. We are aware of this and hopefully have a solution in future.
Now that Anaconda has platform detection logic, default installation will be fixed soon.
Please send across any more feedback you may have about open-vm-tools on our mailing
lists: http://sourceforge.net/p/open-vm-tools/mailman/.
Thanks,
Ravindra
From: cloud-bounces(a)lists.fedoraproject.org [mailto:cloud-bounces@lists.fedoraproject.org]
On Behalf Of M. Edward (Ed) Borasky
Sent: Friday, November 21, 2014 11:34 AM
To: Fedora Cloud SIG
Subject: Re: Adding open-vm-tools package to Fedora Atomic
Great - is there a *technical* (meaning non-policy) reason why Fedora's version of
open-vm-tools doesn't support mounting host files in the guest? VMware does such a
terrible job at tracking changes in the kernel source that I've given up on using it.
And why is open-vm-tools installed by default on Fedora Workstation on bare metal or
VirtualBox or qemu-kvm guests?
Sorry if I'm "shooting the messenger" here but I've just wasted a couple
of days trying to make VMware Workstation work on a Fedora 21 host and Fedora 21 guests
work with VMware hosts. There are two open source alternatives, one of which is just a
"yum install" away on a Fedora 21 host and which works flawlessly with all
modern kernels.
On Fri, Nov 21, 2014 at 10:51 AM, Ravindra Kumar
<ravindrakumar@vmware.com<mailto:ravindrakumar@vmware.com>> wrote:
Hi all,
I'm the maintainer for open-vm-tools package in Fedora.
For the benefit of Fedora Atomic users on VMware platform, I would like to add
open-vm-tools package to Fedora Atomic.
Could somebody please advise/help me with the process involved to get open-vm-tools
package in Fedora Atomic?
Thanks in advance,
Ravindra
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org<mailto:cloud@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/cloud<https://urldefe...
Fedora Code of Conduct:
http://fedoraproject.org/code-of-conduct<https://urldefense.proofpoint...
--
Twitter:
http://twitter.com/znmeb<https://urldefense.proofpoint.com/v2/url?u=ht...;
Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview<https://urldefense.proofpoint.com/...
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
4:27 p.m.
On 11/21/2014 01:51 PM, Ravindra Kumar wrote:
Could somebody please advise/help me with the process involved to
get
open-vm-tools package in Fedora Atomic?
Silly question - do the qcow/etc images we're producing now run on
VMware? I haven't tried importing them to anything VMware...
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
6:26 p.m.
You'd need to reformat them to vmdk with 'qemu-img convert' first, I think.
I got the Koji image to work on Windows 8.1 Client Hyper-V by using
'qemu-img convert' to convert it from qcow2 to vhdx.
On a related note, is there a plan to build "boot2atomic"? Like
Boot2Docker, only Atomic instead of coreos.
On Fri, Nov 21, 2014 at 2:27 PM, Joe Brockmeier <jzb(a)redhat.com> wrote:
On 11/21/2014 01:51 PM, Ravindra Kumar wrote:
> Could somebody please advise/help me with the process involved to get
> open-vm-tools package in Fedora Atomic?
Silly question - do the qcow/etc images we're producing now run on
VMware? I haven't tried importing them to anything VMware...
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
6:20 a.m.
2014-11-22 1:26 GMT+01:00 M. Edward (Ed) Borasky <znmeb(a)znmeb.net>:
You'd need to reformat them to vmdk with 'qemu-img
convert' first, I think.
I got the Koji image to work on Windows 8.1 Client Hyper-V by using
'qemu-img convert' to convert it from qcow2 to vhdx.
On a related note, is there a plan to build "boot2atomic"? Like Boot2Docker,
only Atomic instead of coreos.
I think you're mistaken. First, boot2docker is not based on CoreOS,
it's a lightweight linux distro (a derivative of Tiny Core Linux).
Second, Atomic Host/Core OS/Boot2docker albeit optimized for different
use cases (production vs test) are minimal distro
for hosting containers.
You may use Fedora Atomic as an alternative to boot2docker, though it
won't be as small as boot2docker.
Regards,
H.
9:24 a.m.
On 11/22/2014 06:20 AM, Haïkel wrote:
You may use Fedora Atomic as an alternative to boot2docker, though it
won't be as small as boot2docker.
I think there's some additional tooling around boot2docker, but I have
to admit I haven't used it + don't know enough about it. Maybe something
to test around the holidays.
So the question may well be "is Fedora / Project Atomic" going to do
something that fills *all* the requirements of boot2docker.
The answer right now is "TBD" -- but if we have folks who want to work
on the additional requirements above/beyond what's already in Atomic,
I'd be happy to try to help make that happen.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
12:58 p.m.
I've used Boot2Docker - it's "point, click and ship Docker hosting" for
Windows or MacOS X and it bundles the open-source piece of VirtualBox to
get that done. I haven't used it on a Mac but on Windows you download an
installer and run it. It installs VirtualBox, Windows MSYS Git and the
Boot2Docker Linux infrastructure.
You double-click on a desktop icon and it creates a VM for the Linux Docker
host, fires it up connected to a VirtualBox host-only network and gives you
a command line window in the VM where you can do "docker run" on anything
from Docker Hub, or build your own images and containers.
My own personal testing is down a different path - I'm testing Atomic as a
guest in the "native" Windows 8.1+ (Client) Hyper-V. I've hit a few bugs
with Fedora, most notably
https://bugzilla.redhat.com/show_bug.cgi?id=1097772, but I have gotten
Atomic to boot and talk to the command line - next step is to hook up
networking and verify that containers can talk to, for example, a browser.
On Tue, Nov 25, 2014 at 7:24 AM, Joe Brockmeier <jzb(a)redhat.com> wrote:
On 11/22/2014 06:20 AM, Haïkel wrote:
>
> You may use Fedora Atomic as an alternative to boot2docker, though it
> won't be as small as boot2docker.
I think there's some additional tooling around boot2docker, but I have
to admit I haven't used it + don't know enough about it. Maybe something
to test around the holidays.
So the question may well be "is Fedora / Project Atomic" going to do
something that fills *all* the requirements of boot2docker.
The answer right now is "TBD" -- but if we have folks who want to work
on the additional requirements above/beyond what's already in Atomic,
I'd be happy to try to help make that happen.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
9:38 a.m.
Hi Ravindra,
At the moment, we do not have a formal process for this. The problem is
further compounded by the fact that there is only one tree. Meaning that
open-vm-tools would end up even on other deployment targets such as bare
metal, AWS/GCE, etc.
At a high level, we are trying to coalesce around cloud-init as much as
possible as the core agent. It looks to me like a lot of open-vm-tools
is desktop focused. The main bits here would be folder sharing, memory
ballooning?
Have you looked at running open-vm-tools as a (likely privileged)
container?
On Fri, Nov 21, 2014, at 01:51 PM, Ravindra Kumar wrote:
Hi all,
I'm the maintainer for open-vm-tools package in Fedora.
For the benefit of Fedora Atomic users on VMware platform, I would
like to add open-vm-tools package to Fedora Atomic.
Could somebody please advise/help me with the process involved to
get
open-vm-tools package in Fedora Atomic?
Thanks in advance,
Ravindra
_________________________________________________
cloud mailing list cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of
Conduct: http://fedoraproject.org/code-of-conduct
10:09 a.m.
On Mon, Nov 24, 2014 at 3:38 PM, Colin Walters <walters(a)verbum.org> wrote:
Hi Ravindra,
At the moment, we do not have a formal process for this. The problem is
further compounded by the fact that there is only one tree. Meaning that
open-vm-tools would end up even on other deployment targets such as bare
metal, AWS/GCE, etc.
At a high level, we are trying to coalesce around cloud-init as much as
possible as the core agent. It looks to me like a lot of open-vm-tools is
desktop focused. The main bits here would be folder sharing, memory
ballooning?
They don't really do the same thing. My understanding is that
cloud-init is for the initial runtime configuration like user
creation, injection of ssh keys and kicking off an orchestration tool
where as open-vm-tools is for run time management of VMware VMs such
as safe shutdown and general health reporting of the guest to vCenter.
On the oVirt/OpenStack/KVM side there's the similar qemu-guest-agent
and no doubt hyper-V will have similar.
Have you looked at running open-vm-tools as a (likely privileged)
container?
It needs some fairly low level "HW" access, not sure how that would
work containerised.
Peter
10:46 a.m.
On Mon, Nov 24, 2014, at 11:09 AM, Peter Robinson wrote:
It needs some fairly low level "HW" access, not sure how
that would
work containerised.
If you "docker run --privileged", the container has total access to the host,
it's no different from any other process running as root. Try it:
# docker run -ti --privileged -v /:/sysroot centos ls /dev
1:12 p.m.
Collin,
Like Peter mentioned, open-vm-tools are not limited to desktop operations. In fact, we
have split the package into two: open-vm-tools and open-vm-tools-desktop.
open-vm-tools is the non-desktop piece. The main service it contains vmtoolsd exits
immediately if not running on VMware platform.
I need to explore the privileged container approach, but I would also like to learn about
the technical downsides of including the package in the image itself.
Thanks,
Ravindra
-----Original Message-----
From: cloud-bounces(a)lists.fedoraproject.org [mailto:cloud-bounces@lists.fedoraproject.org]
On Behalf Of Colin Walters
Sent: Monday, November 24, 2014 8:46 AM
To: cloud(a)lists.fedoraproject.org
Subject: Re: Adding open-vm-tools package to Fedora Atomic
On Mon, Nov 24, 2014, at 11:09 AM, Peter Robinson wrote:
It needs some fairly low level "HW" access, not sure how
that would
work containerised.
If you "docker run --privileged", the container has total access to the host,
it's no different from any other process running as root. Try it:
# docker run -ti --privileged -v /:/sysroot centos ls /dev
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__admin.fedoraproject....
Fedora Code of Conduct:
https://urldefense.proofpoint.com/v2/url?u=http-3A__fedoraproject.org_cod...
3438
days inactive
3442
days old
11 comments
6 participants
participants (6)
-
Colin Walters -
Haïkel -
Joe Brockmeier -
M. Edward (Ed) Borasky -
Peter Robinson -
Ravindra Kumar