<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><span></span><br><span></span><br><blockquote type="cite"><blockquote type="cite"><span>On 09 Dec 2013, at 20:56, Itamar Heim <<a href="mailto:iheim@redhat.com">iheim@redhat.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 12/09/2013 04:42 PM, Blaster wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Dec 6, 2013, at 5:25 AM, Vinzenz Feenstra <<a href="mailto:vfeenstr@redhat.com">vfeenstr@redhat.com</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><<a href="mailto:vfeenstr@redhat.com">mailto:vfeenstr@redhat.com</a>>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>I understand that you're disappointed and we're trying to make our</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>best to make the user experience better. You should be considering the</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>age of the project and what we're actually already providing. Yes not</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>everything is perfect, but we're working hard on improving it.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>We're working in a collaborative way together with the community, if</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>you're missing something, there's always the possibility to help out.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Even if you're not a programmer you can help improving the experience.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Bob pretty much said it all for me already…I’m not so much as</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>disappointed in ovirt development as I am the marketing of it. ovirt is</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>being marketed as an ESXi replacement when it surely isn’t. Probably</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>90%+ of what ESXi is used for is virtualizing Windows. Give ovirt in</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>it’s current form to a typical Windows user and they’ll self destruct.</span></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>The first issue with the agents as I can’t even find any documentation</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>on what agents really need installing, and what features I’m getting</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>with that agent!</span><br></blockquote></blockquote><span></span><br><span>Check out the new page by Nicholas Kesick [1]</span></div><div><br><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Another thing is, I would think that Fedora would be integrated enough</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>with ovirt that it would be able to automatically detect it’s running on</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>ovirt and install all the required agents automatically.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I forgot my number 5) BIOS needs to work like a standard PC BIOS (as</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>does ESXi) in allowing you to press F8 to get a boot menu or F12 for</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>network boot. </span></blockquote></blockquote><div><br></div>Seabios has boot menu support on F12. I don't recall if we specifically disable it, I think not</div><div><br><blockquote type="cite"><blockquote type="cite"><span>This run once stuff is silly. It works fine the first</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>time I create a VM as there’s no bootable OS on the datastore, but if I</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>need to re-PXE boot a VM, then I have to Run Once..OK, fine, but when</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>the PXE completes it reboots, back into network boot, then I have to</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>kill the VM and restart it normally. Under a PC (or ESXi) BIOS, I just</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>hit F12, network boot, OS re-installs, then reboots normally. Much</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>better user experience. I gave our Red Hat sales people feedback on</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>this issue and was told it’s not going to change.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>if you open a support ticket for this request, it will be associated with an RFE, helping its priority (which is via support, not sales, but we can take that offline i guess).</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>iirc, the problem on this one is not supported by qemu or libvirt, so we'd need vdsm manage the restart as a shutdown (which libvirt supports), then start the VM again without the ISO.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I'm trying to remember if this was supposed to be resolved by qemu supporting this or the vdsm logic.</span><br></blockquote><blockquote type="cite"><span>michal?</span><br></blockquote><div><br></div>By engine+vdsm logic. Patches by Martin Betak are still stuck on vdsm. It won't help with the above if the reboot is triggered from within the guest we don't plan to recreate the VM on engine. The UI reboot button would, but IIUC that's not the same case<br><br></div><div>[1] <a href="http://www.ovirt.org/Understanding_Guest_Agents_and_Other_Tools">http://www.ovirt.org/Understanding_Guest_Agents_and_Other_Tools</a></div></body></html>