os: VMware disk won't properly come online in the OS

BurmillaOS Version: (ros os version)

v1.9.6

Where are you running BurmillaOS? (docker-machine, AWS, GCE, baremetal, etc.)

VMware vSphere datacenter

Which processor architecture you are using?

Intel Xeon

Do you use some extra hardware? (GPU, etc)?

Which console you use (default, ubuntu, centos, etc…)

Default

Do you use some service(s) which are not enabled by default?

Have you installed some extra tools to console?

VMware Tools

Do you use some other customizations?

Network config DHCP on boot

I am using the VMware ISO and cannot get the disk drive to properly come up. The VM in vSphere shows that the data disk is attached to the VM, but when I go to the console for BurmillaOS and do a df -h, I don’t see the 20GB disk. I am using a node template to boot-strap the node into VMware. The networking, CPU and memory config options are properly being set for the VM.

About this issue

Original URL
State: closed
Created a year ago
Comments: 31 (13 by maintainers)

Most upvoted comments

RancherOS did contain huge number of ready made installation medias. Sounds that you have been using their rancheros-vmware-autoformat.iso version.

He we purposely limit number of medias to minimum based on feedback which was got from #6 and those auto format medias are one of those which got dropped out from options. You can of course still fill your use case to there and in case we found others who have need for that we can consider re-adding it.

How it works now is that if you want automate installation on VMware you can use guestinfo field cloud-init.config.data for that. More about those in https://burmillaos.org/docs/installation/cloud/vmware-esxi/

and here is real world example how configure it with Terraform:

guestinfo.cloud-init.config.data = <<EOD
#!/bin/bash
(cat << EOF
#cloud-init
runcmd:
- ["mount", "-t", "ext4", "/dev/sdb", "/var/lib/docker"]
rancher:
  sysctl:
    vm.max_map_count: 262144
ssh_authorized_keys:
  - ${var.rancher_public_key}
EOF
)> cloud-init.yml
if ! blkid | grep -q "RANCHER_STATE"; then
 sudo ros install -d /dev/sda --no-reboot -c cloud-init.yml
 if ! blkid | grep -q "USER_DOCKER"; then
  sudo mkfs.ext4 /dev/sdb -L USER_DOCKER
 fi
 sudo reboot
else
 echo "already installed"
fi
EOD

Alternative you can create VMware template by doing installation like this:

#!/bin/bash
echo "Intalling to disk" > /dev/tty1
ros install -f -d /dev/sda --no-reboot --debug --append "console=tty1 console=ttyS0,115200n8 printk.devkmsg=on rancher.autologin=ttyS0"
halt -P

and marking that first VM as template and then just create other VMs based on it.

olljanat on Jan 14, 2023