Hello, I'm going to manage two kinds of environments. 1) All-in-one installed as an F18 guest (f18aio) on a laptop 2) Engine as an F18 guest of a dedicated server + node as a separate physical server with F18 installed on it
In particular for 1) I have to start/stop almost daily the oVirt infrastructure that is collapsed on a unique environment engine+node on f18aio. The laptop is an Asus U36SD with an SSD disk and 8Gb of ram and F17 OS. I'm verifying that in respect of some months ago nested virtualization works well on this intel cpu: (2cores + HT Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz) In fact I was able to install this f18aio F18 guest with all-in-one oVirt 3.2 nightly and create and run a windows XP vm inside it. After solving other problems I have what seems a stable environment My first approach for stop/start seems working from a functional point of view, but I would like confirmation of possible missing steps: starting point is oVirt infra running with all its defined vm running on it (only one atm) a) shutdown all vms in oVirt (only one atm) b) logout from webadmin portal c) simply shutdown the OS of the F18 guest f18aio) (without putting node in maintenance or other things) d) shutdown the laptop Then e) power on the laptop f) start the f18vm g) wait about 4 minutes when from "contending" state the local_datacenter passes to "Up" h) start the desired oVirt vms (one atm) I would also like to have clear correct procedures for case 2) that should respect production-like environments and so be aware of how to behave in case of panned maintenance / outages. Is it perhaps better in any case in 1) and 2) to first put the host in maintenance mode? Thanks to all for your continuous help, and Happy New year to you and to the Maya people ;-) Gianluca
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
