Hi, I've started doing some testing on the Virtualbox Vagrant box ( http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... )
I've hit a couple of issues:
1) The disk size, at about 8 GB, is too small. Could it be bumped to 50-100 GB? Since the on-disk image will grow dynamically this won't take up that much space by default but will make it usable for those that need more storage on the root partition (and I don't want to have to custom mount additional partitions).
2) The VirtualBox Guest Additions aren't included. I'm assuming this is due to a licensing issue and not that they were simply not considered but wanted to double check.
Otherwise it's been great, and saves me having to build my own custom box, which is definitely a win.
-Jeff
On 08/07/15 18:02, Jeff Sheltren wrote:
Hi, I've started doing some testing on the Virtualbox Vagrant box (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...)
I've hit a couple of issues:
- The disk size, at about 8 GB, is too small. Could it be bumped to
50-100 GB? Since the on-disk image will grow dynamically this won't take up that much space by default but will make it usable for those that need more storage on the root partition (and I don't want to have to custom mount additional partitions).
let me poke this a bit, i dont think we get dynamic / sparse disk images with the koji setup, but will check.
- The VirtualBox Guest Additions aren't included. I'm assuming this is
due to a licensing issue and not that they were simply not considered but wanted to double check.
there are no licensing issues with the additions, just needs someone to rpm'ise them up so we can use them. thanks for offering to get this done :)
Otherwise it's been great, and saves me having to build my own custom box, which is definitely a win.
fantastic, the June '15 images are ready to fly, and should be online tomorrow.
regards,
On 07/08/2015 10:32 PM, Jeff Sheltren wrote:
Hi, I've started doing some testing on the Virtualbox Vagrant box (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...)
I've hit a couple of issues:
- The disk size, at about 8 GB, is too small. Could it be bumped to
50-100 GB? Since the on-disk image will grow dynamically this won't take up that much space by default but will make it usable for those that need more storage on the root partition (and I don't want to have to custom mount additional partitions).
Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it would be sparse disk. Also there are few tricks you can do with the Vagrantfile to increase the disk size. But I have not tried them
- The VirtualBox Guest Additions aren't included. I'm assuming this
is due to a licensing issue and not that they were simply not considered but wanted to double check.
This part I am not sure. I need to check how we can add "VirtualBox Guest Additions". yes, we want to fix this.
Otherwise it's been great, and saves me having to build my own custom box, which is definitely a win.
-Jeff
How do we track these issues? I just dont want to loose track of these.
-Lala
I would suggest keeping the root volume as minimal as possible for the box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box.
Cheers, Tim
On 8 July 2015 at 19:31, Lalatendu Mohanty lmohanty@redhat.com wrote:
On 07/08/2015 10:32 PM, Jeff Sheltren wrote:
Hi, I've started doing some testing on the Virtualbox Vagrant box (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...)
I've hit a couple of issues:
- The disk size, at about 8 GB, is too small. Could it be bumped to
50-100 GB? Since the on-disk image will grow dynamically this won't take up that much space by default but will make it usable for those that need more storage on the root partition (and I don't want to have to custom mount additional partitions).
Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it would be sparse disk. Also there are few tricks you can do with the Vagrantfile to increase the disk size. But I have not tried them
- The VirtualBox Guest Additions aren't included. I'm assuming this is
due to a licensing issue and not that they were simply not considered but wanted to double check.
This part I am not sure. I need to check how we can add "VirtualBox Guest Additions". yes, we want to fix this.
Otherwise it's been great, and saves me having to build my own custom box, which is definitely a win.
-Jeff
How do we track these issues? I just dont want to loose track of these.
-Lala
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
Hello, in addition to the other comments, I just wanted to say that it would be great to have an 'official' vmware_desktop Vagrant box available on Atlas as well.
Let me know if there's anything I can do to help enable that. I found this bugzilla issue which could maybe be used for tracking the various requirements?
https://bugs.centos.org/view.php?id=6365
Thanks,
Michael
On Thu, Jul 9, 2015 at 3:18 PM, Timothy Rees reestr.uk@gmail.com wrote:
I would suggest keeping the root volume as minimal as possible for the box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box.
Cheers, Tim
On 8 July 2015 at 19:31, Lalatendu Mohanty lmohanty@redhat.com wrote:
On 07/08/2015 10:32 PM, Jeff Sheltren wrote:
Hi, I've started doing some testing on the Virtualbox Vagrant box (
http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... )
I've hit a couple of issues:
- The disk size, at about 8 GB, is too small. Could it be bumped to
50-100 GB? Since the on-disk image will grow dynamically this won't
take up
that much space by default but will make it usable for those that need
more
storage on the root partition (and I don't want to have to custom mount additional partitions).
Yes, this can be fixed. I am fine with bumping the disk size to 50GB as
it
would be sparse disk. Also there are few tricks you can do with the Vagrantfile to increase the disk size. But I have not tried them
- The VirtualBox Guest Additions aren't included. I'm assuming this is
due to a licensing issue and not that they were simply not considered
but
wanted to double check.
This part I am not sure. I need to check how we can add "VirtualBox Guest Additions". yes, we want to fix this.
Otherwise it's been great, and saves me having to build my own custom
box,
which is definitely a win.
-Jeff
How do we track these issues? I just dont want to loose track of these.
-Lala
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 09/07/15 12:23, Michael Vermaes wrote:
Hello, in addition to the other comments, I just wanted to say that it would be great to have an 'official' vmware_desktop Vagrant box available on Atlas as well.
Let me know if there's anything I can do to help enable that. I found this bugzilla issue which could maybe be used for tracking the various requirements?
https://bugs.centos.org/view.php?id=6365
Thanks,
Michael
I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ?
- KB
On Thu, Jul 9, 2015 at 3:18 PM, Timothy Rees <reestr.uk@gmail.com mailto:reestr.uk@gmail.com> wrote:
I would suggest keeping the root volume as minimal as possible for the box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box. Cheers, Tim On 8 July 2015 at 19:31, Lalatendu Mohanty <lmohanty@redhat.com <mailto:lmohanty@redhat.com>> wrote: > On 07/08/2015 10:32 PM, Jeff Sheltren wrote: >> >> Hi, I've started doing some testing on the Virtualbox Vagrant box >> (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505-x86_64-01.box) >> >> I've hit a couple of issues: >> >> 1) The disk size, at about 8 GB, is too small. Could it be bumped to >> 50-100 GB? Since the on-disk image will grow dynamically this won't take up >> that much space by default but will make it usable for those that need more >> storage on the root partition (and I don't want to have to custom mount >> additional partitions). >> > > Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it > would be sparse disk. Also there are few tricks you can do with the > Vagrantfile to increase the disk size. But I have not tried them > >> 2) The VirtualBox Guest Additions aren't included. I'm assuming this is >> due to a licensing issue and not that they were simply not considered but >> wanted to double check. >> > > This part I am not sure. I need to check how we can add "VirtualBox Guest > Additions". yes, we want to fix this. >> >> Otherwise it's been great, and saves me having to build my own custom box, >> which is definitely a win. >> >> -Jeff > > > How do we track these issues? I just dont want to loose track of these. > > -Lala >
On Fri, Jul 10, 2015 at 5:36 AM, Karanbir Singh mail-lists@karan.org wrote:
On 09/07/15 12:23, Michael Vermaes wrote:
Hello, in addition to the other comments, I just wanted to say that it would be great to have an 'official' vmware_desktop Vagrant box available on Atlas as well.
Let me know if there's anything I can do to help enable that. I found this bugzilla issue which could maybe be used for tracking the various requirements?
https://bugs.centos.org/view.php?id=6365
Thanks,
Michael
I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ?
- KB
Thanks for the suggestion. Here's the message I received when I tried to 'vagrant up' after ' vagrant init centos/7 '
Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: Box 'centos/7' could not be found. Attempting to find and install... default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation default: Box Version: >= 0 ==> default: Loading metadata for box 'centos/7' default: URL: https://atlas.hashicorp.com/centos/7 The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it.
If you're adding a box from HashiCorp's Atlas, make sure the box is released.
Name: centos/7 Address: https://atlas.hashicorp.com/centos/7 Requested provider: ["vmware_desktop", "vmware_fusion", "vmware_workstation"]
Based on your comment, it sounds like the underlying image should be compatible with VMware, it probably just needs to be uploaded again specifying that it is also valid for the vmware_desktop provider.
Similarly to Jeff's request about Guest Additions for VirtualBox, it would be ideal to have the VMware Tools preinstalled in this box - this is a requirement for shared folders to work. If the CentOS 7 image is built from https://github.com/CentOS/sig-cloud-instance-build/blob/master/vagrant/cento..., I think it would be a matter of including open-vm-tools in the list of packages, to get access to /usr/lib64/libhgfs.so.
On Thu, Jul 9, 2015 at 3:18 PM, Timothy Rees <reestr.uk@gmail.com mailto:reestr.uk@gmail.com> wrote:
I would suggest keeping the root volume as minimal as possible forthe
box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box. Cheers, Tim On 8 July 2015 at 19:31, Lalatendu Mohanty <lmohanty@redhat.com <mailto:lmohanty@redhat.com>> wrote: > On 07/08/2015 10:32 PM, Jeff Sheltren wrote: >> >> Hi, I've started doing some testing on the Virtualbox Vagrant box >> (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... )
>> >> I've hit a couple of issues: >> >> 1) The disk size, at about 8 GB, is too small. Could it bebumped to
>> 50-100 GB? Since the on-disk image will grow dynamically this won't take up >> that much space by default but will make it usable for those that need more >> storage on the root partition (and I don't want to have to custom mount >> additional partitions). >> > > Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it > would be sparse disk. Also there are few tricks you can do with the > Vagrantfile to increase the disk size. But I have not tried them > >> 2) The VirtualBox Guest Additions aren't included. I'm assuming this is >> due to a licensing issue and not that they were simply not considered but >> wanted to double check. >> > > This part I am not sure. I need to check how we can add "VirtualBox Guest > Additions". yes, we want to fix this. >> >> Otherwise it's been great, and saves me having to build my own custom box, >> which is definitely a win. >> >> -Jeff > > > How do we track these issues? I just dont want to loose track of these. > > -Lala >-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 07/10/2015 10:27 AM, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 5:36 AM, Karanbir Singh <mail-lists@karan.org mailto:mail-lists@karan.org> wrote:
On 09/07/15 12:23, Michael Vermaes wrote: > Hello, in addition to the other comments, I just wanted to say that it > would be great to have an 'official' vmware_desktop Vagrant box > available on Atlas as well. > > Let me know if there's anything I can do to help enable that. I found > this bugzilla issue which could maybe be used for tracking the various > requirements? > > https://bugs.centos.org/view.php?id=6365 > > Thanks, > > Michael I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ? - KB Thanks for the suggestion. Here's the message I received when I tried to 'vagrant up' after ' vagrant init centos/7 '
Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: Box 'centos/7' could not be found. Attempting to find and install... default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation default: Box Version: >= 0 ==> default: Loading metadata for box 'centos/7' default: URL: https://atlas.hashicorp.com/centos/7 The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it.
If you're adding a box from HashiCorp's Atlas, make sure the box is released.
Name: centos/7 Address: https://atlas.hashicorp.com/centos/7 Requested provider: ["vmware_desktop", "vmware_fusion", "vmware_workstation"]
Based on your comment, it sounds like the underlying image should be compatible with VMware, it probably just needs to be uploaded again specifying that it is also valid for the vmware_desktop provider.
This error is expected if you are using atlas.hashicorp.com/centos/7 https://atlas.hashicorp.com/centos/7 as we don't have vmware provider released there.
Can you please try the below [1] image. You have have to manually download the image then add it to Vagrant. Lets me know if you need any help on that.
[1] http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...
Similarly to Jeff's request about Guest Additions for VirtualBox, it would be ideal to have the VMware Tools preinstalled in this box - this is a requirement for shared folders to work. If the CentOS 7 image is built from https://github.com/CentOS/sig-cloud-instance-build/blob/master/vagrant/cento..., I think it would be a matter of including open-vm-tools in the list of packages, to get access to /usr/lib64/libhgfs.so.
Yeah thats the ks file used for creating the Vagrant box.
> > On Thu, Jul 9, 2015 at 3:18 PM, Timothy Rees <reestr.uk@gmail.com <mailto:reestr.uk@gmail.com> > <mailto:reestr.uk@gmail.com <mailto:reestr.uk@gmail.com>>> wrote: > > I would suggest keeping the root volume as minimal as possible for the > box and then let the end users to grow it using methods provided by > Vagrant. Anyone then can grow the volume to their specific use case, > its a lot easier than reducing a default, large disk provided with a > box. > > Cheers, > Tim > > On 8 July 2015 at 19:31, Lalatendu Mohanty <lmohanty@redhat.com <mailto:lmohanty@redhat.com> > <mailto:lmohanty@redhat.com <mailto:lmohanty@redhat.com>>> wrote: > > On 07/08/2015 10:32 PM, Jeff Sheltren wrote: > >> > >> Hi, I've started doing some testing on the Virtualbox Vagrant box > >> > (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505-x86_64-01.box) > >> > >> I've hit a couple of issues: > >> > >> 1) The disk size, at about 8 GB, is too small. Could it be bumped to > >> 50-100 GB? Since the on-disk image will grow dynamically this > won't take up > >> that much space by default but will make it usable for those that > need more > >> storage on the root partition (and I don't want to have to custom > mount > >> additional partitions). > >> > > > > Yes, this can be fixed. I am fine with bumping the disk size to > 50GB as it > > would be sparse disk. Also there are few tricks you can do with the > > Vagrantfile to increase the disk size. But I have not tried them > > > >> 2) The VirtualBox Guest Additions aren't included. I'm assuming > this is > >> due to a licensing issue and not that they were simply not > considered but > >> wanted to double check. > >> > > > > This part I am not sure. I need to check how we can add > "VirtualBox Guest > > Additions". yes, we want to fix this. > >> > >> Otherwise it's been great, and saves me having to build my own > custom box, > >> which is definitely a win. > >> > >> -Jeff > > > > > > How do we track these issues? I just dont want to loose track of > these. > > > > -Lala > > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh <http://twitter.com/kbsingh> GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org <mailto:CentOS-devel@centos.org> http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Fri, Jul 10, 2015 at 1:06 PM, Lalatendu Mohanty lmohanty@redhat.com wrote:
On 07/10/2015 10:27 AM, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 5:36 AM, Karanbir Singh mail-lists@karan.org wrote:
On 09/07/15 12:23, Michael Vermaes wrote:
Hello, in addition to the other comments, I just wanted to say that it would be great to have an 'official' vmware_desktop Vagrant box available on Atlas as well.
Let me know if there's anything I can do to help enable that. I found this bugzilla issue which could maybe be used for tracking the various requirements?
https://bugs.centos.org/view.php?id=6365
Thanks,
Michael
I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ?
- KB
Thanks for the suggestion. Here's the message I received when I tried to 'vagrant up' after ' vagrant init centos/7 '
Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: Box 'centos/7' could not be found. Attempting to find and install... default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation default: Box Version: >= 0 ==> default: Loading metadata for box 'centos/7' default: URL: https://atlas.hashicorp.com/centos/7 The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it.
If you're adding a box from HashiCorp's Atlas, make sure the box is released.
Name: centos/7 Address: https://atlas.hashicorp.com/centos/7 Requested provider: ["vmware_desktop", "vmware_fusion", "vmware_workstation"]
Based on your comment, it sounds like the underlying image should be compatible with VMware, it probably just needs to be uploaded again specifying that it is also valid for the vmware_desktop provider.
This error is expected if you are using atlas.hashicorp.com/centos/7 as we don't have vmware provider released there.
Can you please try the below [1] image. You have have to manually download the image then add it to Vagrant. Lets me know if you need any help on that.
[1] http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...
Thanks Lala, I tried the following but no luck:
vagrant box add http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... --name c7-vagrant --provider vmware_desktop ==> box: Adding box 'c7-vagrant' (v0) for provider: vmware_desktop box: Downloading: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... The box you attempted to add doesn't match the provider you specified.
Provider expected: vmware_desktop Provider of box: virtualbox
Similarly to Jeff's request about Guest Additions for VirtualBox, it would be ideal to have the VMware Tools preinstalled in this box - this is a requirement for shared folders to work. If the CentOS 7 image is built from https://github.com/CentOS/sig-cloud-instance-build/blob/master/vagrant/cento..., I think it would be a matter of including open-vm-tools in the list of packages, to get access to /usr/lib64/libhgfs.so.
Yeah thats the ks file used for creating the Vagrant box.
On Thu, Jul 9, 2015 at 3:18 PM, Timothy Rees <reestr.uk@gmail.com mailto:reestr.uk@gmail.com> wrote:
I would suggest keeping the root volume as minimal as possible for the box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box. Cheers, Tim On 8 July 2015 at 19:31, Lalatendu Mohanty <lmohanty@redhat.com <mailto:lmohanty@redhat.com>> wrote: > On 07/08/2015 10:32 PM, Jeff Sheltren wrote: >> >> Hi, I've started doing some testing on the Virtualbox Vagrant box >> (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505-x86_64-01.box) >> >> I've hit a couple of issues: >> >> 1) The disk size, at about 8 GB, is too small. Could it be bumped to >> 50-100 GB? Since the on-disk image will grow dynamically this won't take up >> that much space by default but will make it usable for those that need more >> storage on the root partition (and I don't want to have to custom mount >> additional partitions). >> > > Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it > would be sparse disk. Also there are few tricks you can do with the > Vagrantfile to increase the disk size. But I have not tried them > >> 2) The VirtualBox Guest Additions aren't included. I'm assuming this is >> due to a licensing issue and not that they were simply not considered but >> wanted to double check. >> > > This part I am not sure. I need to check how we can add "VirtualBox Guest > Additions". yes, we want to fix this. >> >> Otherwise it's been great, and saves me having to build my own custom box, >> which is definitely a win. >> >> -Jeff > > > How do we track these issues? I just dont want to loose track of these. > > -Lala >-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 10/07/15 06:54, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 1:06 PM, Lalatendu Mohanty lmohanty@redhat.com wrote:
On 07/10/2015 10:27 AM, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 5:36 AM, Karanbir Singh mail-lists@karan.org wrote:
On 09/07/15 12:23, Michael Vermaes wrote:
Hello, in addition to the other comments, I just wanted to say that it would be great to have an 'official' vmware_desktop Vagrant box available on Atlas as well.
Let me know if there's anything I can do to help enable that. I found this bugzilla issue which could maybe be used for tracking the various requirements?
https://bugs.centos.org/view.php?id=6365
Thanks,
Michael
I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ?
- KB
Thanks for the suggestion. Here's the message I received when I tried to 'vagrant up' after ' vagrant init centos/7 '
Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: Box 'centos/7' could not be found. Attempting to find and install... default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation default: Box Version: >= 0 ==> default: Loading metadata for box 'centos/7' default: URL: https://atlas.hashicorp.com/centos/7 The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it.
If you're adding a box from HashiCorp's Atlas, make sure the box is released.
Name: centos/7 Address: https://atlas.hashicorp.com/centos/7 Requested provider: ["vmware_desktop", "vmware_fusion", "vmware_workstation"]
Based on your comment, it sounds like the underlying image should be compatible with VMware, it probably just needs to be uploaded again specifying that it is also valid for the vmware_desktop provider.
This error is expected if you are using atlas.hashicorp.com/centos/7 as we don't have vmware provider released there.
Can you please try the below [1] image. You have have to manually download the image then add it to Vagrant. Lets me know if you need any help on that.
[1] http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...
Thanks Lala, I tried the following but no luck:
vagrant box add http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... --name c7-vagrant --provider vmware_desktop ==> box: Adding box 'c7-vagrant' (v0) for provider: vmware_desktop box: Downloading: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... The box you attempted to add doesn't match the provider you specified.
Provider expected: vmware_desktop Provider of box: virtualbox
I guess we need to repack the box itself in this case, can be done - but the updates for 1506 are done already, this might be something to target into 1507.
Also, i think its fine to split kickstarts based on the provider to suite optimisations and code specifications needed for that provider itself.
- KB
On 07/10/2015 11:24 AM, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 1:06 PM, Lalatendu Mohanty lmohanty@redhat.com wrote:
On 07/10/2015 10:27 AM, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 5:36 AM, Karanbir Singh mail-lists@karan.org wrote:
On 09/07/15 12:23, Michael Vermaes wrote:
Hello, in addition to the other comments, I just wanted to say that it would be great to have an 'official' vmware_desktop Vagrant box available on Atlas as well.
Let me know if there's anything I can do to help enable that. I found this bugzilla issue which could maybe be used for tracking the various requirements?
https://bugs.centos.org/view.php?id=6365
Thanks,
Michael
I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ?
- KB
Thanks for the suggestion. Here's the message I received when I tried to 'vagrant up' after ' vagrant init centos/7 '
Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: Box 'centos/7' could not be found. Attempting to find and install... default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation default: Box Version: >= 0 ==> default: Loading metadata for box 'centos/7' default: URL: https://atlas.hashicorp.com/centos/7 The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it.
If you're adding a box from HashiCorp's Atlas, make sure the box is released.
Name: centos/7 Address: https://atlas.hashicorp.com/centos/7 Requested provider: ["vmware_desktop", "vmware_fusion", "vmware_workstation"]
Based on your comment, it sounds like the underlying image should be compatible with VMware, it probably just needs to be uploaded again specifying that it is also valid for the vmware_desktop provider.
This error is expected if you are using atlas.hashicorp.com/centos/7 as we don't have vmware provider released there.
Can you please try the below [1] image. You have have to manually download the image then add it to Vagrant. Lets me know if you need any help on that.
[1] http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...
Thanks Lala, I tried the following but no luck:
vagrant box add http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... --name c7-vagrant --provider vmware_desktop ==> box: Adding box 'c7-vagrant' (v0) for provider: vmware_desktop box: Downloading: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505... The box you attempted to add doesn't match the provider you specified.
Provider expected: vmware_desktop Provider of box: virtualbox
I am sorry, the above image was not supposed to work for VMware. Ian (cc'ed) informed me about it. Hopefully in future koji will create images for VMware too.
-Lala
On Thu, Jul 9, 2015 at 12:18 AM, Timothy Rees reestr.uk@gmail.com wrote:
I would suggest keeping the root volume as minimal as possible for the box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box.
The box file size doesn't increase by creating a larger disk partition by default; it dynamically resizes to grow as space is used within the VM.
From the Vagrant docs (https://docs.vagrantup.com/v2/boxes/base.html):
"For example, in VirtualBox, you should create a dynamically resizing drive with a large maximum size. This causes the actual footprint of the drive to be small initially, but to dynamically grow towards the max size as disk space is needed, providing the most flexibility for the end user."
I'm not aware of any method for automatically resizing the disk of a base box. See e.g. http://askubuntu.com/questions/317338/how-can-i-increase-disk-size-on-a-vagr... for a workaround -- but I'd definitely not push that onto e.g. web developers using these VMs, and if I'd have to save my own box image, I'd just create one from scratch in the first place.
Am I missing some method for resizing the image easily on the fly? If so, that seems to contradict the Vagrant docs.
-Jeff
I've been getting bitten by the "8 Gig default size" I'm finding in AWS and other CentOS environments. It's definitely time to bump it up to 20 Gig.
On Thu, Jul 9, 2015 at 3:18 AM, Timothy Rees reestr.uk@gmail.com wrote:
I would suggest keeping the root volume as minimal as possible for the box and then let the end users to grow it using methods provided by Vagrant. Anyone then can grow the volume to their specific use case, its a lot easier than reducing a default, large disk provided with a box.
Cheers, Tim
On 8 July 2015 at 19:31, Lalatendu Mohanty lmohanty@redhat.com wrote:
On 07/08/2015 10:32 PM, Jeff Sheltren wrote:
Hi, I've started doing some testing on the Virtualbox Vagrant box (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...)
I've hit a couple of issues:
- The disk size, at about 8 GB, is too small. Could it be bumped to
50-100 GB? Since the on-disk image will grow dynamically this won't take up that much space by default but will make it usable for those that need more storage on the root partition (and I don't want to have to custom mount additional partitions).
Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it would be sparse disk. Also there are few tricks you can do with the Vagrantfile to increase the disk size. But I have not tried them
- The VirtualBox Guest Additions aren't included. I'm assuming this is
due to a licensing issue and not that they were simply not considered but wanted to double check.
This part I am not sure. I need to check how we can add "VirtualBox Guest Additions". yes, we want to fix this.
Otherwise it's been great, and saves me having to build my own custom box, which is definitely a win.
-Jeff
How do we track these issues? I just dont want to loose track of these.
-Lala
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 10/07/15 14:04, Nico Kadel-Garcia wrote:
I've been getting bitten by the "8 Gig default size" I'm finding in AWS and other CentOS environments. It's definitely time to bump it up to 20 Gig.
I dont know what 'other CentOS environments' means, but in AWS did you try and add more storage and size up ?
regards
On Fri, Jul 10, 2015 at 9:56 AM, Karanbir Singh mail-lists@karan.org wrote:
On 10/07/15 14:04, Nico Kadel-Garcia wrote:
I've been getting bitten by the "8 Gig default size" I'm finding in AWS and other CentOS environments. It's definitely time to bump it up to 20 Gig.
I dont know what 'other CentOS environments' means, but in AWS did you try and add more storage and size up ?
Yes, but it's awkward. A launch done with the current CentOS 6.x base HVM image remains with an 8 Gig "/" parition, even if a larger disk image is allocated for it, until you manually use "fdisk" to delete the partition and resize it manuall, do a reboot so CentOS 6 sees the full partition, and then use "resize2fs" to rebuild it.
I keep a larger base disk image around for just this purpose, but it's a waste of time I could better spend on other tasks, and rebooting is a fairly undesirable step.
On Wed, Jul 8, 2015 at 10:31 AM, Lalatendu Mohanty lmohanty@redhat.com wrote:
- The VirtualBox Guest Additions aren't included. I'm assuming this is
due to a licensing issue and not that they were simply not considered but wanted to double check.
This part I am not sure. I need to check how we can add "VirtualBox Guest Additions". yes, we want to fix this.
I've used these scripts to create Virtualbox boxes in the past: https://github.com/jeffsheltren/vagrant-centos Specifically, it mounts the guest additions ISO file provided by Virtualbox ( https://github.com/jeffsheltren/vagrant-centos/blob/master/setup#L44-L45) and then runs the installer to build the kernel modules from within kickstart ( https://github.com/jeffsheltren/vagrant-centos/blob/master/ks.cfg#L151-L157 ).
If someone (not me, sorry KB!) could package those as an RPM, that would definitely be interesting.
-Jeff
-
Jeff Sheltren -
Karanbir Singh -
Lalatendu Mohanty -
Michael Vermaes -
Nico Kadel-Garcia -
Timothy Rees