windows 10 image

asked 2018-09-15 14:42:40 +0300

mhallmann
1 ●1 ●3 ●3

updated 2018-09-18 10:53:51 +0300

613 ●1 ●3 ●5

How can I create an image for Windows 10 Pro? I tried installing it and using OEM-Mode to install cloudbase, but on the first boot after that no user is created and I cant access the machine.

Thanks in advance.

Hi, how can I create a working Windows 10 Pro image with cloudbase? I later want to deploy it via Proxmox VE.

I tried installing Windows in OEM-Mode and then installing cloudbase. After the cleanup I get the login promt, but no user was created (looked into C:\Users with Ubuntu)...

edit retag flag offensive close merge delete

Comments

I am getting this error when I try to boot the Image: https://cloud.horlboge.de/index.php/s/m72CYe9MQLCSgGb After a few reboots it shows a message like "The installation process could not be started"

mhallmann ( 2018-09-18 21:21:49 +0300 )edit

This looks like an older problem that should have been fixed. Can you share the cloudbase-init version or download link you used, the win10 ISO version and the cloudbase-init logs (you will find them in 'C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log\cloudbase-init-unattend.log')

avladu ( 2018-09-19 14:05:20 +0300 )edit

I'm using the example script for creating a online image. I can provide the complete configs I am using, if neccessary. -Windows 10 Pro (1803; german) -Cloudbase-Init 0.9.11 (the version downloaded by the script) -The log-file is just empty

mhallmann ( 2018-09-19 14:25:08 +0300 )edit

Now I switched to the beta. The Image is booting - but no user config or network config is applied.

mhallmann ( 2018-09-21 00:28:35 +0300 )edit

It might be the case that proxmox ve metadata format is not supported by cloudbase-init. Can you share the config-drive where the metadata resides? thanks

avladu ( 2018-09-24 12:37:15 +0300 )edit

Here is the complete content of the drive: https://cloud.horlboge.de/index.php/s/dBA2QTXEa7PqKNT/download Edit: Corrected the link

mhallmann ( 2018-09-24 15:17:13 +0300 )edit

I tried to download it and check it, but it seems corrupted. The config drive folders should be named OPENSTACK, not OPENSTAC. There are missing letters also in the filenames of the subfolders. Can you verify is the correct archive?

avladu ( 2018-09-28 10:30:19 +0300 )edit

I would prefer the actual ISO file, if possible, so that I can reproduce the behaviour as close as possible

avladu ( 2018-09-28 10:45:24 +0300 )edit

The only way I could get an ISO file would be cloning the drive from within windows. As you can see the file names are as they are on the virtual CD: https://cloud.horlboge.de/index.php/s/9BoEj7gptdEAwkf

mhallmann ( 2018-09-28 11:04:43 +0300 )edit

I see, but the filenames are completely wrong (misspelled). Is there a copy paste / visual reason or the ISO is corrupted?

avladu ( 2018-10-01 14:44:26 +0300 )edit

see more comments

3 answers

Sort by » oldest newest most voted

answered 2018-09-18 10:55:06 +0300

avladu

613 ●1 ●3 ●5

updated 2018-09-24 12:44:19 +0300

Hello,

Here are the tools to create Windows images:

https://github.com/cloudbase/windows-...

You can find relevant examples in the Readme and the examples folder: https://github.com/cloudbase/windows-...

Edit1:

According to https://pve.proxmox.com/wiki/Cloud-InitFAQ#UsageinProxmoxVE: "The configdrive v2 variant may work for windows guests using cloudbase-init, but this is not officially supported."

Edit2: Nocloud metadata support is in review: https://blueprints.launchpad.net/clou...

Thank you,
Adrian Vladu

edit flag offensive delete link

Comments

Hello Adrian, configdrive 2 and nocloud support are working so far, maybe it is the folder structure or folder/file name thanks for your help

alebeta ( 2018-10-11 22:50:08 +0300 )edit

Are there any builds of cloudbase-init which support nocloud?

mhallmann ( 2018-10-12 15:43:04 +0300 )edit

add a comment

answered 2018-09-22 19:26:15 +0300

alebeta
1 ●1 ●1

Hello friends,

I have the same problem so far. the config is not taking place. I install cloudbase-init from the binary and this is my cloudbase-init-unattendet.conf

[DEFAULT] username=Administrator groups=Administrators injectuserpassword=true cdrom=true locations=cdrom bsdtarpath=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\bin\bsdtar.exe mtoolspath=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\bin\ verbose=true debug=true logdir=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log\ logfile=cloudbase-init-unattend.log defaultloglevels=comtypes=INFO,suds=INFO,iso8601=WARN,requests=WARN loggingserialportsettings=COM1,115200,N,8 mtuusedhcpconfig=true ntpusedhcpconfig=true localscriptspath=C:\Program Files\Cloudbase Solutions\Cloudbase-Init\LocalScripts\ metadataservices=cloudbaseinit.metadata.services.configdrive.ConfigDriveService plugins=cloudbaseinit.plugins.common.userdata.UserDataPlugin allowreboot=false stopserviceonexit=false checklatestversion=false

My host is proxmox 5.2 and the guest Windows Server 2016.

The system is booting but no changes are taking place, with proxmox im trying to configure mounting a cloud-init device and I set the option citype: configdrive2

What could be happening?

Thanks

edit flag offensive delete link

Comments

Hello, can you share the config drive in order to reproduce the problem? Nocloud support is in review for cloudbase-init, let me know if you can test it out (I ve updated my post above where to find the patch). Thank you, Adrian.

avladu ( 2018-09-24 12:46:10 +0300 )edit

Hello Adrian, Thanks for your help The config drive disk has the name config-2, inside there is a folder with name OPENSTAC(similar to your comment before), inside are two folders CONTENT and LATEST in latest we have files META_DAT.JSO and USER_DAT and in CONTENT file 0000. Thanks

alebeta ( 2018-10-11 22:06:45 +0300 )edit

add a comment