On 12/16/2013 05:47 AM, René Koch wrote:
> Hi,
>
> -----Original message-----
>> From:Sander Grendelman <sander(a)grendelman.com>
>> Sent: Monday 16th December 2013 11:00
>> To: Joop <jvdwege(a)xs4all.nl>
>> Cc: users(a)ovirt.org
>> Subject: Re: [Users] Solaris 11.1 ISO panic on boot
>>
>> There's also a thread about Solaris 11 here:
>>
http://lists.ovirt.org/pipermail/users/2013-September/016168.html
>>
>> On Mon, Dec 16, 2013 at 10:35 AM, Joop <jvdwege(a)xs4all.nl> wrote:
>>> Blaster wrote:
>>>>
>>>> I have a Solaris 11.1 system running on a nice piece of hardware
>>>> that I’d
>>>> like to make better use of. I would like to virtualize it under
>>>> ovirt.
>>>>
>>>> I created an ovirt guest using the RHEL 64 bit template. I
>>>> attached the
>>>> Solaris 11.1 ISO and booted. As soon as the Solaris banner is
>>>> displayed,
>>>> poof, kernel panic.
>
> I suggest to use the following settings for your Solaris guest:
> * Operating System: Other
> * nic1: rtl8139
> * Disk1: IDE
>
> Booting from the DVD ISO works fine for Sol 10 and 11 with these
> settings.
>
>>>>
>>>> Of course every whizzes by so fast I have no chance of getting a
>>>> screen
>>>> shot.
>>>>
>>>> Has anyone been successful in boot Solaris 11.1 under ovirt?
>>>> Should I
>>>> have picked a different template?
>
> In my oVirt setup (3.3 now, but worked on 3.2, too) there are Solaris
> 10 and 11 vms running.
> See the specs above.
>
> I had some issues with network traffic, which can be solved with a
> host hook (99_fix_solaris):
>
https://github.com/ovido/ovirt-stuff/tree/master/hooks
>
> Please let me know if this fixes your issues...
>
>
> Regards,
> René
René - maybe a patch to add solaris to osinfo config file with these
limitations (hmm, it would still need the hook, which is a shame[1])
Joop - just a btw - not sure why you start from a rhel64 template,
rather than start from blank + add disk, then boot from iso.
(since there is no benefit to either doing COW of solaris over the
rhel64 template, nor to cloning it)
[1] michal/roy - thoughts about allowing to specify at osinfo level
extra flags or override the cpu model altogether (iirc, windows guest
would need this as well for new windows specific flags going forward).
extra flags
at osinfo sounds right but overriding the whole model I
think is more appropriate at the VM level configuration
so we can actually validate it with the cluster capabilities.
os.${id}.devices.cpu.extraFlags
Itamar - I didn't get if windows would have to have its cpu overridden
or just the extra hyperV flag? (btw what's this flag name?)
>
>
>
>>>>
>>>>
>>>
>>> I did a search through my message folder and found the thread. It
>>> was about
>>> solaris10 and networking didn't work. So maybe this is different or
>>> not.
>>> Could you test if the same iso can be booted using virt-manager or
>>> kvm/qemu
>>> directly?
>>>
>>> Joop
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/users
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>