| 2015-04-06 20:05:48 +0300 | received badge | ● Famous Question (source) |
| 2015-03-25 20:56:38 +0300 | received badge | ● Enthusiast |
| 2015-03-24 14:44:39 +0300 | commented answer | Windows VFAT support I have the log. How do I get it to you? Note that the command line used to boot the instance includes: --config-drive=true. |
| 2015-03-10 15:35:57 +0300 | commented answer | Windows VFAT support Just making sure... I noticed that the config drive works if I boot the instance and run cloudbase-init from the command line, but it doesn't when run as a service when the instance first boots? Note, I am bypassing the included unattend.xml, thus solely depending on the service to all the work. |
| 2015-03-01 22:04:41 +0300 | received badge | ● Notable Question (source) |
| 2015-02-28 03:26:47 +0300 | commented answer | Windows VFAT support Great! Any idea when the patch will be integrated in the installer? |
| 2015-02-24 11:45:53 +0300 | received badge | ● Popular Question (source) |
| 2015-02-17 17:40:33 +0300 | asked a question | Windows VFAT support The current build of cloudbase-init we're using is oct-2014 and this does not support config drive in vfat format. I found a patch here: http://bazaar.launchpad.net/~lihaosz/... I've tested this by installing cloudbase-init and then overlaying the python files, but this does not seem to work. The config drive shows up in Windows as an unrecognized disk. Not usable. Has this patch been tested? (we are on Icehouse) If so, are there plans to integrate this into the MSI installer? We are in urgent need of getting this resolved. Thanks! |
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.