Re: [ovirt-users] Run Once install -> reboot loop
On Friday, February 19, 2016 10:23:02 AM Jamie Lawrence wrote: > > On Feb 18, 2016, at 11:45 PM, René Koch wrote: > > > > Hi Jamie, > > > > That reason for this is, that the iso will be mounted as long as you're in > > run once mode. > > > > You can fix this by powering off your vm after the installation and run it > > again in "normal" mode. As you don't want to run the vm in run once mode > > forever, you have to shut it down anyway. > But it seems that this has worked for me in the past, when I was creating > these through the GUI. In other words, after the OS installer reboots, it > would correctly reboot in “normal” mode. Am I hallucinating that? > It works in the UI because the HD is the first boot device and the CDROM is lower in the order. When you boot, it sees the HD doesn't have a boot record and continues to the next one. Once installed the reboot will have given the HD a boot record and it will start from there. Make sure that in your case the CDROM is NOT the first device and I think you should be alright. > In any case, I’m sure there’s a power-off API method, but I’m not sure how > to reliably detect when to call it. I could do something hacky like call my > own API endpoint as the last action of the installer somehow (I know how to > with Debian, and I’m sure the RH family can do it as well), but that seems > fragile. > > Maybe hack the installer to power power off instead of reboot, and detect > that? I hate the idea of having to fork/maintain my own installer > patches... > > What do other people do for automating this situation? > > -j > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Run Once install -> reboot loop
> On Feb 18, 2016, at 11:45 PM, René Koch wrote: > > Hi Jamie, > > That reason for this is, that the iso will be mounted as long as you're in > run once mode. > > You can fix this by powering off your vm after the installation and run it > again in "normal" mode. As you don't want to run the vm in run once mode > forever, you have to shut it down anyway. But it seems that this has worked for me in the past, when I was creating these through the GUI. In other words, after the OS installer reboots, it would correctly reboot in “normal” mode. Am I hallucinating that? In any case, I’m sure there’s a power-off API method, but I’m not sure how to reliably detect when to call it. I could do something hacky like call my own API endpoint as the last action of the installer somehow (I know how to with Debian, and I’m sure the RH family can do it as well), but that seems fragile. Maybe hack the installer to power power off instead of reboot, and detect that? I hate the idea of having to fork/maintain my own installer patches... What do other people do for automating this situation? -j ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Run Once install -> reboot loop
Hi Jamie, That reason for this is, that the iso will be mounted as long as you're in run once mode. You can fix this by powering off your vm after the installation and run it again in "normal" mode. As you don't want to run the vm in run once mode forever, you have to shut it down anyway. Regards, René On 02/19/2016 01:19 AM, Jamie Lawrence wrote: Hello all, I’m running overt 3.6.0 on Centos 7.[1] I’ve been working on getting Ovirt to slot in to our environment, and almost have a setup that works. I can now build isos on demand for automated installs (I’m working around some local networking choices without modifying them for now, which is why this isn’t a PXE boot) and create my guests, pointing them to the iso form which to install via Run Once. This all works. The problem is that after the install, the guest reboots, but (best I can tell) Ovirt doesn’t detect it, the iso is still mounted, and the install happens all over again. Rinse, repeat. Has anyone seen this? Or better, does anyone know how to fix this? Thanks, -j [1] # yum list installed |grep ovirt ebay-cors-filter.noarch1.0.1-0.1.ovirt.el7@ovirt-3.6 gperftools-libs.x86_64 2.4-7.el7 @ovirt-3.6 ipxe-bootimgs.noarch 20130517-7.gitc4bce43.el7 @ovirt-3.6 ipxe-roms.noarch 20130517-7.gitc4bce43.el7 @ovirt-3.6 ipxe-roms-qemu.noarch 20130517-7.gitc4bce43.el7 @ovirt-3.6 jasperreports-server.noarch6.0.1-1.el7@ovirt-3.6 libcacard-ev.x86_6410:2.3.0-29.1.el7 @ovirt-3.6 libgovirt.x86_64 0.3.1-3.el7@base otopi.noarch 1.4.0-1.el7.centos @ovirt-3.6 otopi-java.noarch 1.4.0-1.el7.centos @ovirt-3.6 ovirt-engine.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-backend.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-cli.noarch3.6.0.1-1.el7.centos @ovirt-3.6 ovirt-engine-dbscripts.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-extension-aaa-jdbc.noarch 1.0.1-1.el7@ovirt-3.6 ovirt-engine-extension-aaa-ldap.noarch 1.1.2-1.el7.centos @ovirt-3.6 ovirt-engine-extension-aaa-ldap-setup.noarch 1.1.2-1.el7.centos @ovirt-3.6 ovirt-engine-extensions-api-impl.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-jboss-as.x86_64 7.1.1-1.el7.centos @ovirt-3.6 ovirt-engine-lib.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-restapi.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-sdk-python.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-base.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-ovirt-engine.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-ovirt-engine-common.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-websocket-proxy.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-tools.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-userportal.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-vmconsole-proxy-helper.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-webadmin-portal.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-websocket-proxy.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-wildfly.x86_648.2.0-1.el7@ovirt-3.6 ovirt-engine-wildfly-overlay.noarch001-2.el7 @ovirt-3.6 ovirt-host-deploy.noarch 1.4.0-1.el7.centos @ovirt-3.6 ovirt-host-deploy-java.noarch 1.4.0-1.el7.centos @ovirt-3.6 ovirt-host-deploy-offline.x86_64 1.4.0-1.el7.centos @ovirt-3.6 ovirt-hosted-engine-ha.noarch 1.3.2.1-1.el7.centos @ovirt-3.6 ovirt-hosted-engine-setup.noarch 1.3.0-1.el7.centos @ovirt-3.6 ovirt-image-uploader.noarch3.6.0-1.el7.centos @ovirt-3.6 ovirt-iso-uploader.noarch 3.6.0-1.el7.centos @ovirt-3.6 ovirt-setup-lib.noarch 1.0.0-1.el7.centos @ovirt-3.6 ovirt-vmconsole.noarch 1.0.0-1.el7.centos @ov
[ovirt-users] Run Once install -> reboot loop
Hello all, I’m running overt 3.6.0 on Centos 7.[1] I’ve been working on getting Ovirt to slot in to our environment, and almost have a setup that works. I can now build isos on demand for automated installs (I’m working around some local networking choices without modifying them for now, which is why this isn’t a PXE boot) and create my guests, pointing them to the iso form which to install via Run Once. This all works. The problem is that after the install, the guest reboots, but (best I can tell) Ovirt doesn’t detect it, the iso is still mounted, and the install happens all over again. Rinse, repeat. Has anyone seen this? Or better, does anyone know how to fix this? Thanks, -j [1] # yum list installed |grep ovirt ebay-cors-filter.noarch1.0.1-0.1.ovirt.el7@ovirt-3.6 gperftools-libs.x86_64 2.4-7.el7 @ovirt-3.6 ipxe-bootimgs.noarch 20130517-7.gitc4bce43.el7 @ovirt-3.6 ipxe-roms.noarch 20130517-7.gitc4bce43.el7 @ovirt-3.6 ipxe-roms-qemu.noarch 20130517-7.gitc4bce43.el7 @ovirt-3.6 jasperreports-server.noarch6.0.1-1.el7@ovirt-3.6 libcacard-ev.x86_6410:2.3.0-29.1.el7 @ovirt-3.6 libgovirt.x86_64 0.3.1-3.el7@base otopi.noarch 1.4.0-1.el7.centos @ovirt-3.6 otopi-java.noarch 1.4.0-1.el7.centos @ovirt-3.6 ovirt-engine.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-backend.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-cli.noarch3.6.0.1-1.el7.centos @ovirt-3.6 ovirt-engine-dbscripts.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-extension-aaa-jdbc.noarch 1.0.1-1.el7@ovirt-3.6 ovirt-engine-extension-aaa-ldap.noarch 1.1.2-1.el7.centos @ovirt-3.6 ovirt-engine-extension-aaa-ldap-setup.noarch 1.1.2-1.el7.centos @ovirt-3.6 ovirt-engine-extensions-api-impl.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-jboss-as.x86_64 7.1.1-1.el7.centos @ovirt-3.6 ovirt-engine-lib.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-restapi.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-sdk-python.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-base.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-ovirt-engine.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-ovirt-engine-common.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-setup-plugin-websocket-proxy.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-tools.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-userportal.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-vmconsole-proxy-helper.noarch 3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-webadmin-portal.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-websocket-proxy.noarch3.6.0.3-1.el7.centos @ovirt-3.6 ovirt-engine-wildfly.x86_648.2.0-1.el7@ovirt-3.6 ovirt-engine-wildfly-overlay.noarch001-2.el7 @ovirt-3.6 ovirt-host-deploy.noarch 1.4.0-1.el7.centos @ovirt-3.6 ovirt-host-deploy-java.noarch 1.4.0-1.el7.centos @ovirt-3.6 ovirt-host-deploy-offline.x86_64 1.4.0-1.el7.centos @ovirt-3.6 ovirt-hosted-engine-ha.noarch 1.3.2.1-1.el7.centos @ovirt-3.6 ovirt-hosted-engine-setup.noarch 1.3.0-1.el7.centos @ovirt-3.6 ovirt-image-uploader.noarch3.6.0-1.el7.centos @ovirt-3.6 ovirt-iso-uploader.noarch 3.6.0-1.el7.centos @ovirt-3.6 ovirt-setup-lib.noarch 1.0.0-1.el7.centos @ovirt-3.6 ovirt-vmconsole.noarch 1.0.0-1.el7.centos @ovirt-3.6 ovirt-vmconsole-host.noarch1.0.0-1.el7.centos @ovirt-3.6 ovirt-vmconsole-proxy.noarch 1.0.0-1.el7.centos @ovirt-3.6 patternfly1.noarch 1.3.0-1.el7.centos @ovirt-3.6-patternfly1-noarch-epel python-gluster.noarch 3.7.6-1.el7 @ovirt-3.6-glusterfs-noarch-e
