Ask Your Question
0

Fail to build bootstrap image in the first booting

asked 2017-03-26 11:33:17 -0700

ttcong gravatar image

updated 2017-03-26 11:34:47 -0700

Hello everyone,

Followed the instruction in this link , I have successfully installed the Jump host on a VM (VMWare Workstation). Bootstrap image has automatically been built and activated. (default setup)

But when I repeat the same step in bare metal (default setup), I get the bootstrap image building failed error. This is my fuel-bootstrap-image-build.log

http://pastebin.com/tJ7XgndM.

I can make sure that my Internet connection is not broken. Even when I try to set up a local repository and manually build it again, it's still failed.

So I try to replace all the localhost links in "/etc/fuel-bootstrap-cli/fuelbootstrapcli.yaml" by the links suggested by "/usr/share/fuelbootstrapcli/fuelbootstrapcli.yaml.sample", it works !!! Bootstrap image can be built and activated.

So anyone can tell me why please ???

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-07-02 02:51:13 -0700

akm17 gravatar image

My friend had exactly the same problem with the installation, he turned to StudyDaddy and there he was told a number of reasons for which there could be a problem, that's part of the answer that he was given, maybe this will help you. If not, turn to them yourself!

Process Scheduling Note: The information in this section was created to address scheduling problems with Windows NT. Although Windows NT is no longer supported as a host OS, VMware currently has no corresponding information for Windows 2000, Windows XP or Windows Server 2003 hosts. The process scheduler on Windows NT does not necessarily schedule processes in a way that allows you to get the best performance from your particular combination of virtual machines and applications running on the host. VMware Workstation on a Windows host provides configuration options that let you adjust scheduling priorities to meet your needs. These configuration options are available from the Edit > Preferences > Priority and VM > Settings > Options > Advanced menu options. These menu items allow you to specify either high or normal priority when the mouse and keyboard are grabbed by the virtual machine and either normal or low priority when they are not grabbed. Global priority is taken as the default across all virtual machines. Local priority overrides the global settings for just the specific virtual machine where you make the changes. Pay particular attention to the grabbed: HIGH - ungrabbed: NORMAL and grabbed: NORMAL - ungrabbed: LOW settings. The grabbed: HIGH - ungrabbed: NORMAL setting is useful if you have many background processes or applications and you do not care if they run with fairly low relative priority while VMware Workstation is in the foreground. In return, you get a very noticeable performance boost using a VMware Workstation virtual machine while another virtual machine is running or while some other processor-intensive task (a compile, for example) is running in the background. The reverse is true of the grabbed: NORMAL - ungrabbed: LOW setting. If your host machine feels too sluggish when a virtual machine is running in the background, you can direct the virtual machine to drop its priority when it does not have control of the mouse and keyboard. As with the high setting, this is a heavy-handed change of priority, so the virtual machine and any background applications run much more slowly.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
1 follower

Stats

Asked: 2017-03-26 11:33:17 -0700

Seen: 43 times

Last updated: Jul 02