Thanks! With the new iso I can successfully configure the network. When I try to register the node with the engine I get the same problem though. I select "oVirt Engine", enter the IP of the engine system and hit apply and get the same menu problem as with the Network option before.
Regards, Dennis On 06/14/2012 07:58 PM, Mike Burns wrote: > 2.4.0-1 is now posted in the same place as 2.4.0. It includes a fix for > the network screen not working correctly (patch was merged, but was > missing from my repo when I built). > > Mike > > On Thu, 2012-06-14 at 13:10 -0400, Mike Burns wrote: >> On Thu, 2012-06-14 at 18:50 +0200, Dennis Jacobfeuerborn wrote: >>> On 06/14/2012 03:25 PM, Mike Burns wrote: >>>> The image is posted to the beta area on ovirt.org[1]. There will likely >>>> be a 2.4.1 release in the next couple weeks as we clean up some other >>>> issues. >>> >>> I just did a test install and this is the result so far: >>> >>> When booting the iso itself and the installed node later I get the >>> following output: >>> rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" >>> the boot process continues though. >>> >>> I can't seem to configure the network. When I move to "eth0" and hit enter >>> I see a blue screen for about 20 seconds and then I get back to the grey >>> background with header and footer but nothing in the content area. Hitting >>> a cursor key the menu appears but in the top left corner instead of where >>> it's supposed to be. Selecting anything doesn't change the content are >>> though. When I hit f12 the gui apparently resets and everything looks >>> alright again. >>> >> >> Argh, we were seeing this in builds just before the official one. >> There was a patch that fixed it that was apparently missed int the >> build. I'm respinning a new 2.4.0 build now (2.4.0-1 actually). >> >> Mike >> >> >>> Looking at the logs I see >>> ovirtfunctions - unable to determine ip/netmask from: >>> ovirtfunctions - unable to determine ip/netmask from: Device "breth0" does >>> not exist. >>> >>> Is there a manual way to configure the networking so I can test the engine >>> connection? >>> >>> Regards, >>> Dennis >>> _______________________________________________ >>> node-devel mailing list >>> [email protected] >>> http://lists.ovirt.org/mailman/listinfo/node-devel >> >> >> _______________________________________________ >> node-devel mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/node-devel > > _______________________________________________ node-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/node-devel
