[Users] oVirt 3.2 and Solaris 10 guests

[René Koch]

Thanks a lot for your feedback.

I'll try to play around with qemu options next week and try to find out which setting causes this issue.
What's the best way for changing this options - using hook scripts I guess...


Regards,
René

 
 
-----Original message-----
> From:Dan Kenigsberg <danken at redhat.com>
> Sent: Wednesday 20th February 2013 11:52
> To: René Koch <r.koch at ovido.at>
> Cc: Jean-Francois Saucier <jsaucier at gmail.com>; ovirt-users <users at ovirt.org>
> Subject: Re: [Users] oVirt 3.2 and Solaris 10 guests
> 
> On Thu, Feb 14, 2013 at 05:25:47PM +0100, René Koch (ovido) wrote:
> > 
> > On Thu, 2013-02-14 at 11:22 -0500, Jean-Francois Saucier wrote:
> > > On Thu, Feb 14, 2013 at 11:21 AM, Jiri Belka <jbelka at redhat.com>
> > > wrote:
> > >         On Thu, 14 Feb 2013 10:49:13 -0500
> > >         Jean-Francois Saucier <jsaucier at gmail.com> wrote:
> > >         
> > >         > > oVirt 3.2:
> > >         > > -netdev tap,fd=25,id=hostnet0 -device
> > >         > >
> > >         > >
> > >         rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
> > >         
> > >             ^^^^^^^ - realtek, really? Try e1000 which is usually much
> > >         more reliable or virtio iface. I personally always had
> > >         terrible
> > >         experience with emulated rtl8139 by qemu-kvm, e1000 was OK.
> > > 
> > > For me, it's the same if I choose the e1000 (which I choose the first
> > > time and then try the rtl8139).
> > > 
> > Same for me - e1000 aren't working with oVirt 3.2 and Solaris 10, too.
> 
> I've heard rumours that it might be related to the fact that oVirt
> starts VMs with ACPI enabled by default (there's a way in Engine to turn
> this off).
> 
> If this is not the case, please do a more extensive bisection of the
> qemu command line. You have one "bad" cmdline; start trimming it until
> it becomes "good".
>