Thanks. Done. I haven't filled out one of those in a while. The bz# is 922274. I'm kind of hoping that ovirt-node gets more stable in terms of installation and configuration over time. With my hack I finally got ovirt-node to boot automatically on the box I was testing with, but then got completely stuck in network configuration when trying to configure bonded interfaces. WebUI doesn't work. ovirt-node console network settings don't stick. I gave up for now, threw the hard disk back in the box and booted it back up as a full hypervisor. The good news is that I still have the SD card that I can throw in any time to restart the test and no running VMs were harmed during the duration of my testing. ;) In the meantime, I'll watch the bug to see if there's any movement over time and test if needed...
-I On Fri, Mar 15, 2013 at 1:32 AM, Fabian Deutsch <[email protected]> wrote: > Am Donnerstag, den 14.03.2013, 15:13 -0700 schrieb Ian Forde: > > That got me a 2nd bootable entry in my BIOS, which I was able to set > > to default and boot from successfully (despite a subsequent warning > > about secure boot not being available). > > > > > > So here's my question: Is there a way that I can submit info back > > about the ovirt-node install that can help debug the stock install of > > ovirt-node getting media to boot on a box that won't let me disable > > EFI? > > Hey Ian, > > nice research and even better that you got a solution! > The best way to get your findings into ovirt-node is to file a bug > against that component in bugzilla [1] and attach your solution there. > That will definetly help to solve this bug quicker. > > Greetings > fabian > > -- > [1] > > https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt&component=ovirt-node > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
