Description of problem: Once the installation of the guest has started it would be useful to allow the user to reboot the guest into the selected run once mode (pxe,cdrom etc) again. This allows the user to workaround any issues that arise from a small pxe timeout, selecting incorrect options during the OS install etc. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.0.0-0.9.beta4.el6ev.noarch How reproducible: Always. Steps to Reproduce: 1. Start the OS installation of the guest via PXE. 2. Allow the guest to hit the timeout value for PXE in the environment. 3. The guest will then fail to boot from the local disk and thus the installation will fail. Actual results: No options present to reboot the guest during the OS installation step. Expected results: A user can reboot the guest, select a new run once mode etc during the OS installation step. Only continuing once the OS installation is complete. Additional info:
You can workaround this by using another open terminal on the host with the following commands : # hosted-engine --vm-poweroff Machine destroyed # hosted-engine --vm-start 98374dcc-422f-41b4-9db5-ed8571ed7875 Status = WaitForLaunch nicModel = rtl8139,pv emulatedMachine = rhel6.5.0 pid = 0 displayIp = 0 devices = [{'index': '2', 'iface': 'ide', 'specParams': {}, 'readonly': 'true', 'deviceId': '112bd6bf-6cf8-4f31-848a-19dcc1b062dc', 'address': {'bus': '1', 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '0'}, 'device': 'cdrom', 'shared': 'false', 'path': '', 'type': 'disk'}, {'index': '0', 'iface': 'virtio', 'format': 'raw', 'type': 'disk', 'address': {'slot': '0x06', 'bus': '0x00', 'domain': '0x0000', 'type': 'pci', 'function': '0x0'}, 'volumeID': '0e08b8ca-4983-4024-92a0-33cea861eae0', 'imageID': 'a3a99635-9434-4e40-83d3-1c9601b4f302', 'specParams': {}, 'readonly': 'false', 'domainID': '21a961dc-cd3b-42e9-b44e-47809837cfed', 'deviceId': 'a3a99635-9434-4e40-83d3-1c9601b4f302', 'poolID': '00000000-0000-0000-0000-000000000000', 'device': 'disk', 'shared': 'exclusive', 'propagateErrors': 'off', 'optional': 'false'}, {'device': 'scsi', 'model': 'virtio-scsi', 'type': 'controller'}, {'nicModel': 'pv', 'macAddr': '00:16:3e:62:3e:ae', 'linkActive': 'true', 'network': 'rhevm', 'bootOrder': '1', 'filter': 'vdsm-no-mac-spoofing', 'specParams': {}, 'deviceId': '984efe85-1afe-48d0-aafc-39148bd8e955', 'address': {'slot': '0x03', 'bus': '0x00', 'domain': '0x0000', 'type': 'pci', 'function': '0x0'}, 'device': 'bridge', 'type': 'interface'}, {'device': 'console', 'specParams': {}, 'type': 'console', 'deviceId': 'cc902d26-cd32-4a0b-ae4f-4b791888879c', 'alias': 'console0'}] smp = 2 vmType = kvm display = vnc displaySecurePort = -1 memSize = 4096 displayPort = -1 cpuType = Nehalem spiceSecureChannels = smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir vmName = HostedEngine clientIp = # hosted-engine --add-console-password=redhat code = 0 message = 'Done' However I would still like to see this integrated into the main installation flow.
Sandro, as discussed on IRC it would be nice to have > When the installation is completed reboot or shutdown the VM: > the system will wait until then Changed to something like : > When the installation is completed please shutdown the VM. > To reboot the VM please press R and <enter> > To select a new boot device please press E and <enter> Thanks again!
merged on upstream master only, for 3.4.0 rebase.
Reopened, failed QA: https://bugzilla.redhat.com/show_bug.cgi?id=1055497#c3
re-assigning and re-targeting. Not a blocker for 3.4.0.
Following an internal discussion, we decided to close this bug, as it's not critical, and solving it well will require more work than seems worth it. Instead we'll solve bug 1106556 now (re-target from 3.6 to 3.5). (This obviously refers only to the last part of the bug, allowing changing the run-once boot device. The first part was already solved for 3.3).