Start a Conversation

Unsolved

T

10 Posts

2394

January 14th, 2019 07:00

Better VMware Hardware for OME Appliance

Please update the next version of the OME Vmware appliance to:

  1. pvscsi
  2. vmxnet3
  3. auto-detect video

 

And generally, regardless of platform:

  1. 4.x Linux kernel (if not already. I wouldn't know, but it looks like CentOS 7.5, but unsure, and it doesn't support SNMP or SSH. If it does, where can I find documentation?)

May 6th, 2019 12:00

And also include open-vm-tools

8 Posts

June 20th, 2019 09:00

Here is the details I found for OME 3.1.

[root@dev etc]# cat os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

 

[root@dev etc]# cat /etc/centos-release
CentOS Linux release 7.5.1804 (Core)

 

Kernel version looks like 3.10:

willid34@dev:~$ sudo ls mount/boot
boot  lost+found
config-3.10.0-862.11.6.el7.x86_64  mbrid
efi  memtest86+-5.01
elf-memtest86+-5.01  symvers-3.10.0-862.11.6.el7.x86_64.gz
grub  System.map-3.10.0-862.11.6.el7.x86_64
grub2  unicode.pf2
initramfs-3.10.0-862.11.6.el7.x86_64.img  vmlinuz-3.10.0-862.11.6.el7.x86_64
 
I know it's kind of an older thread but posting here in case anyone is curious.

2 Posts

June 22nd, 2019 09:00

Hi, Out of curiosity: How did you root access to the OS? BR Soerenv

8 Posts

September 12th, 2019 09:00

I mounted the KVM hard drive image files and then used chroot to change to the root of that drive.  The following commands will allow you to "peek" inside the image, useful for log gathering or whatever else you may need:

  1. sudo guestmount -a openmanage_enterprise.qcow2 -m /dev/OMCAppVG/LVRoot YOUR_FOLDER
  2. sudo chroot YOUR_FOLDER

124 Posts

September 15th, 2019 13:00

Of course you get full access to such an appliance's OS if you really want to.

They lock it down since they probably don't want any script kiddies messing around with it and then call support "it's not working" (and now it's totally unfixable). So for anyone asking "how did you do this" I'd prefer you keep it for yourself (too late already). If someone doesn't know how to do it they probably shouldn't be messing with it in the first place.

Maybe there's also a slight chance of internals being in there they don't want anyone to see. But that would be really stupid.

As for the original topic (including vm tools etc.): +1

No Events found!

Top