Hey, everyone, I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU to run correctly. I''ve followed a couple of the instruction sets out on the Xen wiki and other folks blogs, but I''m running into an issue with the domU crashing. The OpenSolaris version is the latest development release - 5.11-0.128. The config looks like this: name="ImageServer" uuid="e1ba32be-9789-d187-dc94-6cf25ea17d9e" memory=1024 vcpus=4 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 kernel="/etc/xen/vm/osol-5.11-0.128a" ramdisk="/etc/xen/vm/osol-5.11-0.128a.boot" extra="/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk=[ ''file:/xenstore/nfs/ImageServer/disk0,0,w'', ''file:/xenstore/iso/Solaris/osol-dev-128a-ai-x86.iso,6:cdrom,r'', ] vif=[ ''mac=00:16:3e:11:be:de,bridge=xenbr30'', ] serial="pty" The domU appears to try to start, but immediately crashes. When I look at xm dmesg, I get the following output: (XEN) Unhandled page fault in domain 119 on VCPU 0 (ec=0002) (XEN) Pagetable walk from 0000000000000000: (XEN) L4[0x000] = 00000001e7127067 0000000000007a0c (XEN) L3[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S (XEN) Domain 119 (vcpu#0) crashed on cpu#1: (XEN) ----[ Xen-3.2.3_17040_17-0.5_24_xtp x86_64 debug=n Not tainted ]---- (XEN) CPU: 1 (XEN) RIP: e033:[<fffffffffb891e08>] (XEN) RFLAGS: 0000000000000206 CONTEXT: guest (XEN) rax: 000000000000002f rbx: 0000000000000006 rcx: 0000000000000034 (XEN) rdx: 0000000000000017 rsi: 000000004080ebd0 rdi: 0000000000000000 (XEN) rbp: 000000004080eb30 rsp: 000000004080ead0 r8: 000000004080ebed (XEN) r9: 0000000047fff000 r10: 0000000000007ff0 r11: 0000000000000246 (XEN) r12: 000000004080ebe7 r13: 0000000000000017 r14: 0000000000000000 (XEN) r15: 000000004080ebd0 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 000000015f45f000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=000000004080ead0: (XEN) 0000000000000034 0000000000000246 0000000000000002 fffffffffb891e08 (XEN) 000000010000e030 0000000000010006 000000004080eb18 000000000000e02b (XEN) 000000004080f010 0000000000000017 000000004080ebd0 0000000000000000 (XEN) 000000004080eb90 fffffffffb831f6d 000000004080eb60 ff003436646d612f (XEN) 0000000000000000 0000000000000000 0000000000000000 000000004080ebd0 (XEN) 0000000000000000 0000000000000000 000000004080ebd0 0000000000000000 (XEN) 000000004080ebc0 fffffffffb8b5df3 000000004080f010 0000000000000000 (XEN) 000000004080f010 000000004080ebd0 000000004080f000 fffffffffb8b4e0b (XEN) 726f6674616c702f 7670783638692f6d 2f6c656e72656b2f 6e752f3436646d61 (XEN) 0000000000007869 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 xm log indicates that memory is assigned correctly, and that all of the hotplug scripts to assign network and block devices run just fine. Then I get the following entry: [2009-12-07 08:46:00 12618] WARNING (XendDomainInfo:1269) Domain has crashed: name=ImageServer id=119. Can anyone offer any advice as to what may be going on, what I need to do to debug it further, or what to do to solve this issue? Thanks! -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, 2009-12-07 at 08:48 -0700, Nick Couchman wrote:> Hey, everyone, > I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU to run correctly. I''ve followed a couple of the instruction sets out on the Xen wiki and other folks blogs, but I''m running into an issue with the domU crashing. The OpenSolaris version is the latest development release - 5.11-0.128. The config looks like this: > > name="ImageServer" > uuid="e1ba32be-9789-d187-dc94-6cf25ea17d9e" > memory=1024 > vcpus=4 > on_poweroff="destroy" > on_reboot="restart" > on_crash="destroy" > localtime=0 > kernel="/etc/xen/vm/osol-5.11-0.128a" > ramdisk="/etc/xen/vm/osol-5.11-0.128a.boot" > extra="/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" > disk=[ ''file:/xenstore/nfs/ImageServer/disk0,0,w'', ''file:/xenstore/iso/Solaris/osol-dev-128a-ai-x86.iso,6:cdrom,r'', ] > vif=[ ''mac=00:16:3e:11:be:de,bridge=xenbr30'', ] > serial="pty"<snip>> Can anyone offer any advice as to what may be going on, what I need to do to debug it further, or what to do to solve this issue? > > Thanks! > -Nick > > > -------- > This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.Hi Nick, Not sure what is going on here, but I had successfully installed a PV Opensolaris guest a while back. My extra line was: extra="/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" Then I attached the console when I created the VM, selected the keyboard/lang and did a vnc setup so I could see the graphical installer. I put it in my blog (not trying to advertise) here: http://www.taiter.com/blog/2009/02/opensolaris-200811-paravirtual.html This has the VNC setup and the running config that is slightly different than the install config. Mind you, this was for Opensolaris 2008.11 and not SNV-128 so I am not sure if it will work for you. Good luck, Tait _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi Nick, > > Not sure what is going on here, but I had successfully installed a PV > Opensolaris guest a while back. > > My extra line was: > > extra="/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text"Tried changing my config with this line and still no good - same error in xm dmesg.> > Then I attached the console when I created the VM, selected the > keyboard/lang and did a vnc setup so I could see the graphical > installer. > > I put it in my blog (not trying to advertise) here: > http://www.taiter.com/blog/2009/02/opensolaris-200811-paravirtual.html >Thanks - I''ll take a look.> This has the VNC setup and the running config that is slightly different > than the install config. > > Mind you, this was for Opensolaris 2008.11 and not SNV-128 so I am not > sure if it will work for you.Mine is actually Opensolaris 200906 with the update to the 0.5.11-0.128 dev packages. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am not sure regarding libvirt implementation oh SLES10, however
on Fedoras => 8 John Levon''s suggestion does work:-
http://blogs.sun.com/levon/entry/opensolaris_2008_11_guest_domain
The problem is Xen 3.2 . ZFS 16 support +pygrub''s patch went in Xen
3.4.1
I back ported two required CS''s to 3.3.1.
http://bderzhavets.wordpress.com/2009/05/07/backport-zfs-support-to-xen-331-f10-dom0-kernel-2630-rc3-tip/
Boris.
________________________________
From: Nick Couchman <Nick.Couchman@seakr.com>
To: XEN Mailing List <xen-users@lists.xensource.com>
Sent: Mon, December 7, 2009 6:48:00 PM
Subject: [Xen-users] Trying to Run OpenSolaris PV
Hey, everyone,
I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU
to run correctly. I''ve followed a couple of the instruction sets out
on the Xen wiki and other folks blogs, but I''m running into an issue
with the domU crashing. The OpenSolaris version is the latest development
release - 5.11-0.128. The config looks like this:
name="ImageServer"
uuid="e1ba32be-9789-d187-dc94-6cf25ea17d9e"
memory=1024
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
kernel="/etc/xen/vm/osol-5.11-0.128a"
ramdisk="/etc/xen/vm/osol-5.11-0.128a.boot"
extra="/platform/i86xpv/kernel/amd64/unix - nowin -B
install_media=cdrom"
disk=[ ''file:/xenstore/nfs/ImageServer/disk0,0,w'',
''file:/xenstore/iso/Solaris/osol-dev-128a-ai-x86.iso,6:cdrom,r'',
]
vif=[ ''mac=00:16:3e:11:be:de,bridge=xenbr30'', ]
serial="pty"
The domU appears to try to start, but immediately crashes. When I look at xm
dmesg, I get the following output:
(XEN) Unhandled page fault in domain 119 on VCPU 0 (ec=0002)
(XEN) Pagetable walk from 0000000000000000:
(XEN) L4[0x000] = 00000001e7127067 0000000000007a0c
(XEN) L3[0x000] = 0000000000000000 ffffffffffffffff
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 119 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.2.3_17040_17-0.5_24_xtp x86_64 debug=n Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: e033:[<fffffffffb891e08>]
(XEN) RFLAGS: 0000000000000206 CONTEXT: guest
(XEN) rax: 000000000000002f rbx: 0000000000000006 rcx: 0000000000000034
(XEN) rdx: 0000000000000017 rsi: 000000004080ebd0 rdi: 0000000000000000
(XEN) rbp: 000000004080eb30 rsp: 000000004080ead0 r8: 000000004080ebed
(XEN) r9: 0000000047fff000 r10: 0000000000007ff0 r11: 0000000000000246
(XEN) r12: 000000004080ebe7 r13: 0000000000000017 r14: 0000000000000000
(XEN) r15: 000000004080ebd0 cr0: 000000008005003b cr4: 00000000000026b0
(XEN) cr3: 000000015f45f000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=000000004080ead0:
(XEN) 0000000000000034 0000000000000246 0000000000000002 fffffffffb891e08
(XEN) 000000010000e030 0000000000010006 000000004080eb18 000000000000e02b
(XEN) 000000004080f010 0000000000000017 000000004080ebd0 0000000000000000
(XEN) 000000004080eb90 fffffffffb831f6d 000000004080eb60 ff003436646d612f
(XEN) 0000000000000000 0000000000000000 0000000000000000 000000004080ebd0
(XEN) 0000000000000000 0000000000000000 000000004080ebd0 0000000000000000
(XEN) 000000004080ebc0 fffffffffb8b5df3 000000004080f010 0000000000000000
(XEN) 000000004080f010 000000004080ebd0 000000004080f000 fffffffffb8b4e0b
(XEN) 726f6674616c702f 7670783638692f6d 2f6c656e72656b2f 6e752f3436646d61
(XEN) 0000000000007869 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
xm log indicates that memory is assigned correctly, and that all of the hotplug
scripts to assign network and block devices run just fine. Then I get the
following entry:
[2009-12-07 08:46:00 12618] WARNING (XendDomainInfo:1269) Domain has crashed:
name=ImageServer id=119.
Can anyone offer any advice as to what may be going on, what I need to do to
debug it further, or what to do to solve this issue?
Thanks!
-Nick
--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
>>> On 2009/12/07 at 11:03, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > I am not sure regarding libvirt implementation oh SLES10, however > on Fedoras => 8 John Levon''s suggestion does work:- > > http://blogs.sun.com/levon/entry/opensolaris_2008_11_guest_domainI''m not using virt-install at all - I''m creating a config file for the domain (see the original post) and trying to start it when I receive the error message. The kernel and initrd are on my dom0, so ZFS support is irrelevant - I''m not trying to boot using pygrub, virt-install, or anything like that from ZFS. The issue seems to be the newer 64-bit Opensolaris kernels. I switched to the 32-bit kernel and it boots just fine - the 64-bit one crashes with the Unhandled page fault. Not sure why, but this isn''t too critical for me right now, as I don''t really need anything more than about 1 GB of RAM. Still, something is wrong, there - perhaps it''s fixed in a later version of Xen. Now I''m running into an issue where the osol disc that I''m trying to boot from won''t recognize the install media. I''ve tried booting with the following extra= lines in my config file: extra="/platform/i86xpv/kernel/unix -B console=ttya,livemode=text" extra="/platform/i86xpv/kernel/unix -B console=ttya,install_media=cdrom" with no success - the system always fails to find the install media. In the case of adding install_media=cdrom to list of argument, the Opensolaris media tries to resolve "cdrom" to an http server, which, of course, fails. I''ve tried various combinations of disk configurations for the ISO, and none of them seem to work. I''m using the osol ai ISOs right now, so I''m wondering if there''s something in here that doesn''t work properly - I''ll try switching to the regular ones here as soon as they finish downloading. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
This one i believe would be good for SLES10 :-
http://www.neuhalfen.name/2008/12/04/Installing_OpenSolaris_2008_11_in_a_Linux_dom0/
No virsh involvement + explanation what is ZFS Boot environment.
Boris.
________________________________
From: Nick Couchman <Nick.Couchman@seakr.com>
To: XEN Mailing List <xen-users@lists.xensource.com>
Sent: Mon, December 7, 2009 6:48:00 PM
Subject: [Xen-users] Trying to Run OpenSolaris PV
Hey, everyone,
I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU
to run correctly. I''ve followed a couple of the instruction sets out
on the Xen wiki and other folks blogs, but I''m running into an issue
with the domU crashing. The OpenSolaris version is the latest development
release - 5.11-0.128. The config looks like this:
name="ImageServer"
uuid="e1ba32be-9789-d187-dc94-6cf25ea17d9e"
memory=1024
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
kernel="/etc/xen/vm/osol-5.11-0.128a"
ramdisk="/etc/xen/vm/osol-5.11-0.128a.boot"
extra="/platform/i86xpv/kernel/amd64/unix - nowin -B
install_media=cdrom"
disk=[ ''file:/xenstore/nfs/ImageServer/disk0,0,w'',
''file:/xenstore/iso/Solaris/osol-dev-128a-ai-x86.iso,6:cdrom,r'',
]
vif=[ ''mac=00:16:3e:11:be:de,bridge=xenbr30'', ]
serial="pty"
The domU appears to try to start, but immediately crashes. When I look at xm
dmesg, I get the following output:
(XEN) Unhandled page fault in domain 119 on VCPU 0 (ec=0002)
(XEN) Pagetable walk from 0000000000000000:
(XEN) L4[0x000] = 00000001e7127067 0000000000007a0c
(XEN) L3[0x000] = 0000000000000000 ffffffffffffffff
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 119 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.2.3_17040_17-0.5_24_xtp x86_64 debug=n Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: e033:[<fffffffffb891e08>]
(XEN) RFLAGS: 0000000000000206 CONTEXT: guest
(XEN) rax: 000000000000002f rbx: 0000000000000006 rcx: 0000000000000034
(XEN) rdx: 0000000000000017 rsi: 000000004080ebd0 rdi: 0000000000000000
(XEN) rbp: 000000004080eb30 rsp: 000000004080ead0 r8: 000000004080ebed
(XEN) r9: 0000000047fff000 r10: 0000000000007ff0 r11: 0000000000000246
(XEN) r12: 000000004080ebe7 r13: 0000000000000017 r14: 0000000000000000
(XEN) r15: 000000004080ebd0 cr0: 000000008005003b cr4: 00000000000026b0
(XEN) cr3: 000000015f45f000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=000000004080ead0:
(XEN) 0000000000000034 0000000000000246 0000000000000002 fffffffffb891e08
(XEN) 000000010000e030 0000000000010006 000000004080eb18 000000000000e02b
(XEN) 000000004080f010 0000000000000017 000000004080ebd0 0000000000000000
(XEN) 000000004080eb90 fffffffffb831f6d 000000004080eb60 ff003436646d612f
(XEN) 0000000000000000 0000000000000000 0000000000000000 000000004080ebd0
(XEN) 0000000000000000 0000000000000000 000000004080ebd0 0000000000000000
(XEN) 000000004080ebc0 fffffffffb8b5df3 000000004080f010 0000000000000000
(XEN) 000000004080f010 000000004080ebd0 000000004080f000 fffffffffb8b4e0b
(XEN) 726f6674616c702f 7670783638692f6d 2f6c656e72656b2f 6e752f3436646d61
(XEN) 0000000000007869 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
xm log indicates that memory is assigned correctly, and that all of the hotplug
scripts to assign network and block devices run just fine. Then I get the
following entry:
[2009-12-07 08:46:00 12618] WARNING (XendDomainInfo:1269) Domain has crashed:
name=ImageServer id=119.
Can anyone offer any advice as to what may be going on, what I need to do to
debug it further, or what to do to solve this issue?
Thanks!
-Nick
--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> Still, something is wrong, there - perhaps it''s fixed in a later version of XenYes, it is:- http://bderzhavets.wordpress.com/2009/12/02/setup-opensolaris-1002-127-pv-domu-at-xen-3-4-2-libvirt-0-7-1-15-2-6-31-6-pvops-on-top-of-f12-per-john-levon/ I understood issue. What means "osol ai ISO" ? B. --------------------------------------------------------------------------------------------------------------- From: Nick Couchman <Nick.Couchman@seakr.com> To: XEN Mailing List <xen-users@lists.xensource.com>; Boris Derzhavets <bderzhavets@yahoo.com> Sent: Mon, December 7, 2009 9:11:59 PM Subject: Re: [Xen-users] Trying to Run OpenSolaris PV>>> On 2009/12/07 at 11:03, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > I am not sure regarding libvirt implementation oh SLES10, however > on Fedoras => 8 John Levon''s suggestion does work:- > > http://blogs.sun.com/levon/entry/opensolaris_2008_11_guest_domainI''m not using virt-install at all - I''m creating a config file for the domain (see the original post) and trying to start it when I receive the error message. The kernel and initrd are on my dom0, so ZFS support is irrelevant - I''m not trying to boot using pygrub, virt-install, or anything like that from ZFS. The issue seems to be the newer 64-bit Opensolaris kernels. I switched to the 32-bit kernel and it boots just fine - the 64-bit one crashes with the Unhandled page fault. Not sure why, but this isn''t too critical for me right now, as I don''t really need anything more than about 1 GB of RAM. Still, something is wrong, there - perhaps it''s fixed in a later version of Xen. Now I''m running into an issue where the osol disc that I''m trying to boot from won''t recognize the install media. I''ve tried booting with the following extra= lines in my config file: extra="/platform/i86xpv/kernel/unix -B console=ttya,livemode=text" extra="/platform/i86xpv/kernel/unix -B console=ttya,install_media=cdrom" with no success - the system always fails to find the install media. In the case of adding install_media=cdrom to list of argument, the Opensolaris media tries to resolve "cdrom" to an http server, which, of course, fails. I''ve tried various combinations of disk configurations for the ISO, and none of them seem to work. I''m using the osol ai ISOs right now, so I''m wondering if there''s something in here that doesn''t work properly - I''ll try switching to the regular ones here as soon as they finish downloading. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I understood issue. What means "osol ai ISO" ? >Opensolaris (osol) Autoinstaller (ai) ISO. -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
x86/x64 Automated Installer image, 229MB http://dlc.sun.com/torrents/info/osol-dev-128a-ai-x86.iso.torrent I believe the size of ISO will cause some communications via Internet , not required by regular installer (ISO size about 800 GB) This image cannot be a fair for installer failure. Boris. ________________________________ From: Nick Couchman <Nick.Couchman@seakr.com> To: XEN Mailing List <xen-users@lists.xensource.com>; Boris Derzhavets <bderzhavets@yahoo.com> Sent: Mon, December 7, 2009 10:05:03 PM Subject: Re: [Xen-users] Trying to Run OpenSolaris PV> I understood issue. What means "osol ai ISO" ? >Opensolaris (osol) Autoinstaller (ai) ISO. -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yeah, I finally figured out what that was about...the Autoinstaller doesn''t have the full install source, so it needs to contact the Internet. I had switched ISO images over to the full ISO, but had failed to switch the ramdisk image that I was using, so it was still trying to load the auto installer stuff. Silly me...got Opensolaris installed and working, though the 64-bit kernel still does not work on the version of Xen that I''m running. Seems like the number of reasons to upgrade my current version of Xen just keeps increasing... -Nick>>> On 2009/12/08 at 01:58, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > x86/x64 Automated Installer image, 229MB > http://dlc.sun.com/torrents/info/osol-dev-128a-ai-x86.iso.torrent > > I believe the size of ISO will cause some communications via Internet , not > required by regular installer (ISO size > about 800 GB) > This image cannot be a fair for installer failure. > > > Boris. > > > ________________________________ > From: Nick Couchman <Nick.Couchman@seakr.com> > To: XEN Mailing List <xen-users@lists.xensource.com>; Boris Derzhavets > <bderzhavets@yahoo.com> > Sent: Mon, December 7, 2009 10:05:03 PM > Subject: Re: [Xen-users] Trying to Run OpenSolaris PV > >> I understood issue. What means "osol ai ISO" ? >> > > Opensolaris (osol) Autoinstaller (ai) ISO. > > > > -------- > This e-mail may contain confidential and privileged material for the sole use > of the intended recipient. If this email is not intended for you, or you are > not responsible for the delivery of this message to the intended recipient, > please note that this message may contain SEAKR Engineering (SEAKR) > Privileged/Proprietary Information. In such a case, you are strictly > prohibited from downloading, photocopying, distributing or otherwise using > this message, its contents or attachments in any way. If you have received > this message in error, please notify us immediately by replying to this e-mail > and delete the message from your mailbox. Information contained in this > message that does not relate to the business of SEAKR is neither endorsed by > nor attributable to SEAKR. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >-------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users