On Tue, 2013-09-17 at 14:38 +0300, Itamar Heim wrote: > On 09/17/2013 02:23 PM, Ren Koch (ovido) wrote: > > > > On Mon, 2013-09-16 at 19:16 +0200, Gianluca Cecchi wrote: > >> On Mon, Sep 16, 2013 at 6:39 PM, René Koch (ovido) wrote: > >> > >>> > >>> and what about the qemu command line produced by virt-manager ? > >>> > >>> > >>> > >>> Good point - here's the command line of Sol11 with virt-manager on this > >>> oVirt host: > >>> > >> > >> > >> Could it be that the > >> -cpu Nehalem > >> > >> in some way can influence the problem? It only appears in oVirt > >> generated command line > > > > Yes, indeed it does (even I have no clue how this can influence > > networking). > > When adding cpu model to my plain kvm machines libvirt xml network isn't > > working anymore. > > I'll test with some hook scripts if removing the cpu model will solve > > the network issue for my oVirt Solaris guest. > > Thanks for the hint. > > if you can pinpoint and reproduce, probably worth adding the qemu-kvm > mailing list >
I managed to get Solaris networking running when removing cpu model and cpu match attributes, which are added by oVirt but not by virt-manager. I created a hook script (99_fix_solaris) which removes these information. Afterwards networking is fine in Solaris guests: https://github.com/ovido/ovirt-stuff/tree/master/hooks Just one question renaming: Is there any downside from oVirt side when removing these cpu information like e.g. features aren't working as expected? Thanks all for the hints. Regards, René _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
