szernex Posted August 27, 2017 Share Posted August 27, 2017 I tried setting up a Ubuntu 14.04 Server VM (need it for my work) on my unRAID 6.4.0-rc7a server. I did the usual stuff I've also done for my Windows Server and Linux Mint VMs, downloaded the images, put them in the isos share, created a new VM with everything configured accordingly. I booted up the VM, was greeted with the installer and went through the usual process of installing Ubuntu, which seems to have been successful. So the VM reboots and I get greeted with the install screen again, so I force stop the VM and try to unmount the installation disk via the unRAID gui, to no avail. Hitting the icon next to "detach" for the server ISOshows me a confirmation dialogue if I really want to detach it, I click ok and nothing happens. So I edited the VM XML directly and removed the <disk> entry for the ISO. When I do that and boot up the VM I get to this screen Hitting ESC or any key doesn't do anything, it always goes right to the shell. Typing "exit" brings me to the boot menu, in the boot manager this is all I see Here's the original unmodified XML: <domain type='kvm'> <name>KMDS Ephesoft</name> <uuid>3f8920cc-681f-937d-c2fd-39c1898547d1</uuid> <description>KMDS Ephesoft VM</description> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='6'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.9'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3f8920cc-681f-937d-c2fd-39c1898547d1_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vdisks/KMDS Ephesoft/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/ubuntu-14.04.5-server-amd64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/library/work/'/> <target dir='work'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:96:24:ad'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='de'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> </devices> </domain> I'm at a loss as to what's wrong, so any help would be much appreciated since I really need that VM to be up and running soon. Quote Link to comment
1812 Posted August 27, 2017 Share Posted August 27, 2017 Reinstall with seabios instead of ovmf, 1 Quote Link to comment
szernex Posted August 27, 2017 Author Share Posted August 27, 2017 16 minutes ago, 1812 said: Reinstall with seabios instead of ovmf, You're a life saver! Thank you! 2 Quote Link to comment
vin Posted August 29, 2017 Share Posted August 29, 2017 Hi I'm new the unRAID and I have this very same issue with looping through the installation, again and again Can you tell me where I could change to seabios instead of ovmf This is the setup options I see Quote Link to comment
JonathanM Posted August 30, 2017 Share Posted August 30, 2017 19 minutes ago, vin said: Hi I'm new the unRAID and I have this very same issue with looping through the installation, again and again Can you tell me where I could change to seabios instead of ovmf You can't on the update screen, you have to change it on initial creation. Make sure you toggle advanced view. Quote Link to comment
vin Posted August 30, 2017 Share Posted August 30, 2017 Thanks @jonathanm yes just realized that, and I'm creating new one, Thanks again Quote Link to comment
daze Posted September 1, 2017 Share Posted September 1, 2017 On 8/27/2017 at 3:58 AM, szernex said: You're a life saver! Thank you! Why does changing the BIOS matter? Shouldn't sane defaults be set them for templates for various supported OSes? Quote Link to comment
JonathanM Posted September 1, 2017 Share Posted September 1, 2017 6 hours ago, daze said: Shouldn't sane defaults be set them for templates for various supported OSes? Yes, but mistakes happen, and this isn't the end of the world, just irritating. The developers do the best they can, but with literally thousands of possible OS and VM configuration options, it's not easy to get them all right every time, especially when they are chasing moving targets with both the virtualization platform and the randomly updated OS's. Quote Link to comment
billington.mark Posted September 2, 2017 Share Posted September 2, 2017 You could also try and use an newer version of the ovmf bios: Download from here https://www.kraxel.org/repos/jenkins/edk2/ - edk2.git-ovmf-x64-xxxxxx.noarch.rpm extract with 7zip and pull out the OVMF_CODE-pure-efi.fd and OVMF_VARS-pure-efi.fd files, put them in a share somewhere like /mnt/user/VMData/KMDS_Ephesoft/ assign them in the XML manually (replacing the existing values): <os> <type arch='x86_64' machine='pc-q35-2.9'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/VMData/KMDS_Ephesoft/OVMF_CODE-pure-efi.fd</loader> <nvram>/mnt/user/VMData/KMDS_Ephesoft/OVMF_VARS-pure-efi.fd</nvram> </os> 1 Quote Link to comment
daze Posted September 3, 2017 Share Posted September 3, 2017 (edited) 12 hours ago, billington.mark said: You could also try and use an newer version of the ovmf bios: Download from here https://www.kraxel.org/repos/jenkins/edk2/ - edk2.git-ovmf-x64-xxxxxx.noarch.rpm extract with 7zip and pull out the OVMF_CODE-pure-efi.fd and OVMF_VARS-pure-efi.fd files, put them in a share somewhere like /mnt/user/VMData/KMDS_Ephesoft/ assign them in the XML manually (replacing the existing values): <os> <type arch='x86_64' machine='pc-q35-2.9'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/VMData/KMDS_Ephesoft/OVMF_CODE-pure-efi.fd</loader> <nvram>/mnt/user/VMData/KMDS_Ephesoft/OVMF_VARS-pure-efi.fd</nvram> </os> I just get the EFI shell which goes nowhere. Any ideas? Files: 7693854 Sep 2 23:57 edk2.git-ovmf-x64-0-20170827.b2931.gdb52890926.noarch.rpm 1966080 Sep 1 06:07 ./usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd 131072 Sep 1 06:07 ./usr/share/edk2.git/ovmf-x64/OVMF_VARS-pure-efi.fd XML: https://pastebin.com/PGbf3s38 Edited September 3, 2017 by daze Quote Link to comment
Ainsley Posted May 11, 2021 Share Posted May 11, 2021 Hi there, I’m having the exact same problem but using a dedicated NVME tried to change bios to seabios but getting the same issues Anyone have any ideas? Many thanks. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.