Hi -- I wanted to boot s10 HVM in 64-bit mode but it always boots in 32-bit mode. Is there a special grub entry to boot s10 HVM domU in 64-bit mode? Or is it HVM loader? The grub entry is like this title Solaris 10 5/08 s10x_u5wos_01 X86 kernel /platform/i86pc/multiboot module /platform/i86pc/boot_archive s10.py file is as follows :- import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 shadow_memory = 8 name = "S10U5HVM" vcpus=1 vif = [ ''bridge=nge1, ip=10.5.63.98'' ] disk = [ ''file:/xVM/s10/mydisk.raw,hdc,w''] on_poweroff = ''destroy'' on_reboot = ''destroy'' on_crash = ''preserve'' device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot=''cd'' sdl=0 vnc=1 vnclisten="0.0.0.0" vncconsole=1 vncpasswd=''abc'' nographic=0 stdvga=0 serial=''null'' And also the performance is not great when I boot s10 with more than one VCPU. Any recent fixes which went in dom0 or hypervisor? I''m using snv_80 build for dom0. # xm info xen_major : 3 xen_minor : 0 xen_extra : .4-1-xvm Thanks, -- /Saurabh http://blogs.sun.com/saurabh_mishra
Hi Saurabh, I think Xen 3.0.4 (which is what is in Solaris now) only runs 32bit HVM guests. I think this is being worked on for the next integration Chris Saurabh Misra wrote:> Hi -- > > I wanted to boot s10 HVM in 64-bit mode but it always boots in 32-bit > mode. Is there a special grub entry to boot s10 HVM domU in 64-bit mode? > Or is it HVM loader? > > The grub entry is like this > > title Solaris 10 5/08 s10x_u5wos_01 X86 > kernel /platform/i86pc/multiboot > module /platform/i86pc/boot_archive > > s10.py file is as follows :- > > import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib'' > > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 2048 > shadow_memory = 8 > name = "S10U5HVM" > vcpus=1 > vif = [ ''bridge=nge1, ip=10.5.63.98'' ] > disk = [ ''file:/xVM/s10/mydisk.raw,hdc,w''] > on_poweroff = ''destroy'' > on_reboot = ''destroy'' > on_crash = ''preserve'' > device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' > boot=''cd'' > sdl=0 > vnc=1 > vnclisten="0.0.0.0" > vncconsole=1 > vncpasswd=''abc'' > nographic=0 > stdvga=0 > serial=''null'' > > > And also the performance is not great when I boot s10 with more than one > VCPU. Any recent fixes which went in dom0 or hypervisor? I''m using > snv_80 build for dom0. > > # xm info > xen_major : 3 > xen_minor : 0 > xen_extra : .4-1-xvm > > > Thanks, > -- > /Saurabh > http://blogs.sun.com/saurabh_mishra > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >
> I wanted to boot s10 HVM in 64-bit mode but it always boots in 32-bit > mode. Is there a special grub entry to boot s10 HVM domU in 64-bit mode?Yes, under xvm 3.0.4 the cpuid flags aren''t reported 100% the same as on metal, and the small difference is enough that the boot code decides that the HVM domU environment isn''t capable of 64-bit mode (which is wrong), and falls back to 32-bit mode. See bug 6471548, which is similar: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6471548 As a workaround try to add the 64-bit kernel path into the grub boot entry, I think the following should work kernel /platform/i86pc/multiboot kernel/amd64/unix See also: http://www.opensolaris.org/jive/thread.jspa?messageID=182632#182177 http://www.opensolaris.org/jive/thread.jspa?messageID=141307#141602 And IIRC, the hang when doing BIOS calls from 64-bit HVM has been fixed in a recent opensolaris release: http://www.opensolaris.org/jive/thread.jspa?messageID=141307#142380 This message posted from opensolaris.org
Possibly Parallel Threads
- Changes to default output from post S10 zfs list
- aggregate printing with S10
- 6251659 statvfs taking 30 second to complete performance regression s9 to s10 oracle 9ir2 starcat ufs
- 6259653 cp command fail to copy 3.2 GB flash archive from DVD in S9/S10 32 bit x86 system.
- 6217588 New Keyboards software needed for S11 and S10 U2