4 ms·
Worth stating that this update does not currently work with the virtualbox gem, and thus is incompatible with vagrant.
by scorchin 16y ago
Worth stating that this update does not currently work with the virtualbox gem, and thus is incompatible with vagrant.
- deleted 16y ago[deleted]
- deleted 16y ago[deleted]
- wnoise 16y agomitchellh: For some unknown reason your reply is marked "dead". Most won't see it, and there is no way to directly reply to it.
- mitchellh 16y agoI reposted it. Hopefully it'll work this time. I think I confused HN by deleting a few too many things too fast.
- mitchellh 16y agovirtualbox gem and Vagrant dev here. I took a quick look at the updated header files this morning and there is a _ton_ of API changes in VirtualBox 4.0. That coupled with the release just before the holidays start for me and a weeklong trip to Maui means that I can't give a reliable timeframe for pushing in support for 4.0 and testing it thoroughly. The work is starting now, but I fear this is something which won't be available to Vagrant users until early 2011.
- JshWright 16y agoAs someone who just finished updating a number of applications for the new API... I feel your pain... All in all though, I think these changes are for the better (especially the session related stuff).
- mdaniel 16y agoI hope this comes across in the genuinely inquizitive manner that I intend it: isn't that what the four beta releases were designed to do: give integrators and users the time to prepare for the impending release?
- mitchellh 16y agoYes they are, and its my fault for not paying more attention to them. I was pushing really hard to get libvirt support into Vagrant before 4.0 was out, and didn't expect 4.0 to be out this soon. :-\