Gazman
December 4, 2019, 8:39pm
1
After updating from 5.6.1 to 5.10 RHEL 7.6 and 7.5 installers do not detect a drive (sda) to install to. Fedora server 29 and Ubuntu server 18.04 install with no issues, the problem seems to be specific to Red Hat. I’ve exhaustively searched for a resolution to no avail so I’m hoping someone here can help.
I’ve tried simple and complex changes to the template but nothing changes the behavior. Current template for 7.5:
CONTEXT = [
NETWORK = “YES”,
SSH_PUBLIC_KEY = “$USER[SSH_PUBLIC_KEY]” ]
DISK = [
FORMAT = “raw”,
TYPE = “fs” ]
DISK = [
IMAGE = “RHEL 7.5 Installer”,
IMAGE_UNAME = “oneadmin” ]
GRAPHICS = [
LISTEN = “0.0.0.0”,
TYPE = “VNC” ]
HYPERVISOR = “kvm”
LOGO = “images/logos/redhat.png”
MEMORY_UNIT_COST = “MB”
OS = [
BOOT = “disk0,disk1” ]
7.6:
AS_GID = “0”
AS_UID = “0”
CONTEXT = [
NETWORK = “YES”,
SSH_PUBLIC_KEY = “$USER[SSH_PUBLIC_KEY]” ]
CPU = “1”
DISK = [
DRIVER = “bochs”,
FORMAT = “raw”,
TYPE = “fs” ]
DISK = [
IMAGE = “RHEL 7.6 installer”,
IMAGE_UNAME = “oneadmin” ]
GRAPHICS = [
LISTEN = “0.0.0.0”,
RANDOM_PASSWD = “YES”,
TYPE = “VNC” ]
HYPERVISOR = “kvm”
INPUTS_ORDER = “”
LOGO = “images/logos/redhat.png”
MEMORY = “8192”
MEMORY_UNIT_COST = “MB”
NIC = [
NETWORK = “DHCP”,
NETWORK_UNAME = “oneadmin” ]
OS = [
ARCH = “x86_64”,
BOOT = “disk0,disk1” ]
SUNSTONE = [
NETWORK_SELECT = “NO” ]
Running OpenNebula 5.10.0, upgraded from 5.6.1 and as fresh install (fully purged old install and any old configs, both result in same failure) on Ubuntu 18.04 front end and nodes.
Steps to reproduce
Upload RHEL 7.5 or 7.6 installer
Create template
Spin new VM with 8GB memory, 1 CPU and 50GB volatile drive (for sda)
Run VM and attempt install
Current results:
No disk detected by installer
Expected results:
Installer detects drive space and allows partitioning and install
Could you provide the domain XML? Just the output of
virsh dumpxml one-${VM_ID}
Best Regards,
Anton Todorov
Gazman
December 5, 2019, 5:41pm
3
On the VM with the RH installer running I get the following error:
admin@:~$ virsh dumpxml one-33
error: failed to get domain ‘one-33’
error: Domain not found: no domain with matching name ‘one-33’
On a new Ubuntu VM I spun I get this:
admin@:~$ virsh dumpxml one-16
one-16
7ef5dfdf-5bdc-4f63-a782-22510045603b
0
0
5.10.0
1575409916
1575419539
8388608
8388608
1
1024
/machine
hvm
destroy
restart
destroy
/usr/bin/qemu-system-x86_64
libvirt-7ef5dfdf-5bdc-4f63-a782-22510045603b
libvirt-7ef5dfdf-5bdc-4f63-a782-22510045603b
+9869:+9869
+9869:+9869
Gazman
December 5, 2019, 9:23pm
8
Sorry for all the spam, I think I’ve got it this time:
admin@vm-node:~$ virsh dumpxml one-16
<domain type=‘kvm’ id=‘49’>
<name>one-16</name>
<uuid>7ef5dfdf-5bdc-4f63-a782-22510045603b</uuid>
<title>vm</title>
<metadata>
<one:vm xmlns:one=“http://opennebula.org/xmlns/libvirt/1.0 ”>
<one:system_datastore><![CDATA[/var/lib/one//datastores/0/16]]></one:system_datastore>
<one:name><![CDATA[psera2-ub04vm]]></one:name>
<one:uname><![CDATA[oneadmin]]></one:uname>
<one:uid>0</one:uid>
<one:gname><![CDATA[oneadmin]]></one:gname>
<one:gid>0</one:gid>
<one:opennebula_version>5.10.0</one:opennebula_version>
<one:stime>1575409916</one:stime>
<one:deployment_time>1575419539</one:deployment_time>
</one:vm>
</metadata>
<memory unit=‘KiB’>8388608</memory>
<currentMemory unit=‘KiB’>8388608</currentMemory>
<vcpu placement=‘static’>1</vcpu>
<cputune>
<shares>1024</shares>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch=‘x86_64’ machine=‘pc-i440fx-bionic’>hvm</type>
</os>
<features>
<acpi/>
</features>
<clock offset=‘utc’/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type=‘file’ device=‘disk’>
<driver name=‘qemu’ type=‘raw’ cache=‘none’/>
<source file=’/var/lib/one//datastores/0/16/disk.0’/>
<backingStore/>
<target dev=‘sda’ bus=‘scsi’/>
<boot order=‘1’/>
<alias name=‘scsi0-0-0’/>
<address type=‘drive’ controller=‘0’ bus=‘0’ target=‘0’ unit=‘0’/>
</disk>
<disk type=‘file’ device=‘cdrom’>
<driver name=‘qemu’ type=‘raw’ cache=‘none’/>
<source file=’/var/lib/one//datastores/0/16/disk.1’/>
<backingStore/>
<target dev=‘hda’ bus=‘ide’/>
<readonly/>
<boot order=‘2’/>
<alias name=‘ide0-0-0’/>
<address type=‘drive’ controller=‘0’ bus=‘0’ target=‘0’ unit=‘0’/>
</disk>
<disk type=‘file’ device=‘cdrom’>
<driver name=‘qemu’ type=‘raw’/>
<source file=’/var/lib/one//datastores/0/16/disk.2’/>
<backingStore/>
<target dev=‘hdb’ bus=‘ide’/>
<readonly/>
<alias name=‘ide0-0-1’/>
<address type=‘drive’ controller=‘0’ bus=‘0’ target=‘0’ unit=‘1’/>
</disk>
<controller type=‘usb’ index=‘0’ model=‘piix3-uhci’>
<alias name=‘usb’/>
<address type=‘pci’ domain=‘0x0000’ bus=‘0x00’ slot=‘0x01’ function=‘0x2’/>
</controller>
<controller type=‘pci’ index=‘0’ model=‘pci-root’>
<alias name=‘pci.0’/>
</controller>
<controller type=‘scsi’ index=‘0’>
<alias name=‘scsi0’/>
<address type=‘pci’ domain=‘0x0000’ bus=‘0x00’ slot=‘0x04’ function=‘0x0’/>
</controller>
<controller type=‘ide’ index=‘0’>
<alias name=‘ide’/>
<address type=‘pci’ domain=‘0x0000’ bus=‘0x00’ slot=‘0x01’ function=‘0x1’/>
</controller>
<interface type=‘bridge’>
<mac address=‘02:00:cc:af:9a:37’/>
<source bridge=‘br0’/>
<target dev=‘one-16-0’/>
<model type=‘rtl8139’/>
<alias name=‘net0’/>
<address type=‘pci’ domain=‘0x0000’ bus=‘0x00’ slot=‘0x03’ function=‘0x0’/>
</interface>
<input type=‘mouse’ bus=‘ps2’>
<alias name=‘input0’/>
</input>
<input type=‘keyboard’ bus=‘ps2’>
<alias name=‘input1’/>
</input>
<graphics type=‘vnc’ port=‘5916’ autoport=‘no’ listen=‘0.0.0.0’>
<listen type=‘address’ address=‘0.0.0.0’/>
</graphics>
<video>
<model type=‘cirrus’ vram=‘16384’ heads=‘1’ primary=‘yes’/>
<alias name=‘video0’/>
<address type=‘pci’ domain=‘0x0000’ bus=‘0x00’ slot=‘0x02’ function=‘0x0’/>
</video>
<memballoon model=‘virtio’>
<alias name=‘balloon0’/>
<address type=‘pci’ domain=‘0x0000’ bus=‘0x00’ slot=‘0x05’ function=‘0x0’/>
</memballoon>
</devices>
<seclabel type=‘dynamic’ model=‘apparmor’ relabel=‘yes’>
<label>libvirt-7ef5dfdf-5bdc-4f63-a782-22510045603b</label>
<imagelabel>libvirt-7ef5dfdf-5bdc-4f63-a782-22510045603b</imagelabel>
</seclabel>
<seclabel type=‘dynamic’ model=‘dac’ relabel=‘yes’>
<label>+9869:+9869</label>
<imagelabel>+9869:+9869</imagelabel>
</seclabel>
</domain>
Gazman
December 9, 2019, 7:49pm
9
I was able to resolve this. It appears the RHEL installs no longer support SCSI/SATA bus formats. I was able to resolve by going into the VM template for my RHEL 7.5/6 installer, in the storage tab -> advanced options and change the dropdown for BUS from blank to Parallel ADA (IDE). The next VM I spun and used the RHEL installer disk successfully detected the 50GB drive I had allocated to the VM.