search for: boot_arch

...grub menu anymore but only the grub prompt. I managed to boot it manually using another BE. I was unable to use the original BE getting this error message during the manual boot: bootfs rpool/ROOT/rp01 OK kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS OK module$ /platform/i86pc/$ISADIR/boot_archive after this command I got the error: Error 16: Inconsistent filesystem structure. I had to use a different BE to boot up the system. I''ve tried to repair boot_archive from the rp01 BE but unsuccessfully every time ending up in the grub menu forced to manually boot the system using a diff...

Hi, in preparation to try zfs boot on sparc I installed all recent patches incl. feature patches comming from s10s_u3wos_10 and after reboot finally 137137-09 (still having everything on UFS). Now it doesn''t boot at anymore: ############################### Sun Fire V240, No Keyboard Copyright 2006 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.22.23, 2048 MB memory installed,

I can enabling 32bit solaris guest on top of solaris dom0, but I don''t know how to enable 64bit solaris guest on top of solaris dom0. what configuration I need to modify?

...ce: ffmod0 Sep 11 11:20:59 l6-z-2-z1 genunix: ffmod0 is /pseudo/ffmod@0 # #reboot Sep 11 11:22:25 l6-z-2-z1 reboot: initiated by root on /dev/console Sep 11 11:22:25 l6-z-2-z1 pseudo: pseudo-device: devinfo0 Sep 11 11:22:25 l6-z-2-z1 genunix: devinfo0 is /pseudo/devinfo@0 updating /platform/i86pc/boot_archive...this may take a minute Sep 11 11:22:45 l6-z-2-z1 pseudo: pseudo-device: lofi0 Sep 11 11:22:45 l6-z-2-z1 genunix: lofi0 is /pseudo/lofi@0 mount: No such file or directory bootadm: mount of /dev/dsk/c1d0p0:boot (fstype pcfs) failed bootadm: cannot restore GRUB slice The .py file is: name = &quo...

...Copying. Creating shared file system mount points. Creating compare databases for boot environment <sol11>. Creating compare database for file system </>. Updating compare databases on boot environment <sol11>. Making boot environment <sol11> bootable. Creating boot_archive for /.alt.tmp.b-b2.mnt updating /.alt.tmp.b-b2.mnt/platform/sun4u/boot_archive Population of boot environment <sol11> successful. Creation of boot environment <sol11> successful. 4) luactivate sol11 5) lustatus Result: Boot Environment Is Active Active...

...------------------------------------------------------- title Solaris Nevada snv_66 X86 (xen dom0) root (,0,g) bootfs files/s11-root-xen kernel$ /boot/$ISADIR/xen.gz module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/uni x -B $ZFS-BOOTFS -vk module$ /platform/i86pc/$ISADIR/boot_archive # ------------------------------------------------------------ grub boot for xen crashes with the error message: Error 16: Inconsistent filesystem structure GRUB uses fixed memory locations for MOS, DNODE, ZFS_SCRATCH... MOS is at memory location 0x100000. DNODE is at memory location 0...

Hello! I installed NexentaOS (Opensolaris kernel b104+). First booting system is true. Before first rebooting system updates boot_archive. It''s false. Computer is freeze and CapsLock and ScrollLock is blinking. Helps only RESET button. My system is Ubuntu 8.10, kernel-2.6.30-rc3-tip, Xen-3.4-Stable with debug options enabled. My hardware: AMD Athlon64X2 5400+, RAM 4GB. For DomU: mem=1024, LVM disk DomU loaded with the hel...

...is my pool that I can import, so I import it and it works. But I wonder why it isn''t imported automatically. How is managed the pool import during bootup ? Does solaris try to import every single pool that''s available, or does it read some list from a file somewhere (possibly the boot_archive) ? -- This message posted from opensolaris.org

...iff_solaris(fs, cfg): longmode = True if not cfg["kernel"]: - cfg["kernel"] = "/platform/i86xen/kernel/unix" + cfg["kernel"] = "/platform/i86xpv/kernel/unix" cfg["ramdisk"] = "/platform/i86pc/boot_archive" if longmode: - cfg["kernel"] = "/platform/i86xen/kernel/amd64/unix" + cfg["kernel"] = "/platform/i86xpv/kernel/amd64/unix" cfg["ramdisk"] = "/platform/i86pc/amd64/boot_archive" #...

...No such file or directory: ''/dev/0'' my config file looks like this: name = "solaris" memory = "400" kernel = "/solaris/platform/i86xen/kernel/amd64/unix" extra = "/platform/i86xen/kernel/amd64/unix" ramdisk = "/solaris/platform/i86pc/boot_archive" on_shutdown = "destroy" on_reboot = "restart" on_crash = "destroy" root = "/dev/dsk/c0d0s0" disk = [''file:/solaris/root.file,0,w''] vif = [''ip=10.12.1.90'']

Thanks to everyone who works on the opensolaris project. I think it would be helpful to update the documentation on this page: http://opensolaris.org/os/community/xen/docs/linux-dom0/ The crucial steps of mounting the boot environment, updating the boot_archive, copying the boot_archive back to dom0, finding the ZFS-ID of the boot environment, and finally adding that ZFS-ID to the kernel parameters in the xen config file are not mentioned. Thanks, -- Ben Gladwell www.worthpoint.com www.goantiques.com

Let me thank everyone in advance. I''ve read a number of posts here and it helped tremendously in getting the install done. I have a couple of remaining issues which I can''t seem to overcome. Here are the basics: dom0 - CentOS 5.2 32-bit Xen 3.2.1 compiles from source domU - os200805.iso The install config: [root@internetpowagroup oshman]# cat opensolaris.install name =

...eate the xem domain using the following configuration file: memory = 256 name = "t1-30-zone1" kernel = "/export/root/t1-30-zone1/platform/i86xen/kernel/unix" extra = "/platform/i86xen/kernel/unix -B console=xen" ramdisk = "/export/root/t1-30-zone1/platform/i86pc/boot_archive" nics = 1 ip = "10.17.1.53" vif = [ ''bridge=xenbr0'' ] nfs_root = "l6-g-8:/export/root/t1-30-zone1" nfs_server = "10.17.1.97" restart = ''none'' I''ve launched the following command: xm create -c ./t1-30-zone1.py Usin...

...i -- 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 = 2...

...n booting into Xen: grub> #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- grub> title Solaris on Xen grub> kernel$ /boot/$ISADIR/xen.gz grub> module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B console=ttyb grub> module$ /platform/i86pc/$ISADIR/boot_archive grub> #---------------------END BOOTADM-------------------- > SunOS Release 5.11 Version onnv-gate 64-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: Found xen v3.0.4-1-sun but need xen v3.0.4-1-xvm > WARNING...

Hi, I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux dom0. I''m using a file backed VBD. I used the iso image to first launch and install OpenSolaris into the file VBD. Once that process is complete, I''m trying to run it using the config file below: name = ''opensolaris'' vcpus = 1 memory = "512" vif =

...procedure documented in > > http://blogs.sun.com/tabriz/entry/are_you_ready_to_rumble > > a raidz pool can be used for booting. > > The zfs booter, in the current implementation, expects > to find these critical files: > > /boot/grub/menu.lst > /platform/i86pc/boot_archive > /platform/i86pc/kernel/unix > > in a dataset in a zfs pool and it can only access one > disk, so all of those files (and all blocks in those > files) need to be accessible on that disk. If the pool > is constructed of mirrored disks, that''s OK, because > every...

Anyone knows if this is something that will be looked at before b134 is released? Bug 13743 - virsh and xm is unable to start domain first time after boot http://defect.opensolaris.org/bz/show_bug.cgi?id=13743 Regards Henrik http://sparcv9.blogspot.com

Hi, I have installed b_78 on a Dell 2950 and booting to bare metal works fine but when I try to boot using the grub entry Solaris xVM it will boot to the point where it displays the uname info and then just stays there. It will not boot past that point. I have enabled VT technology in the BIOS (but only after the installation). Where/what can I look at to trouble shoot this? I am new to xen and

...n both disk mbr # also disable splash since it will not work well with mirror setup cat >/rootpool/boot/grub/menu.lst default 0 fallback 1 title Solaris ZFS mirror 1 root (hd0,0,a) bootfs rootpool/rootfs kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS module$ /platform/i86pc/$ISADIR/boot_archive title Solaris ZFS mirror 2 root (hd1,0,a) bootfs rootpool/rootfs kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS module$ /platform/i86pc/$ISADIR/boot_archive title Solaris Failsafe kernel /boot/platform/i86pc/kernel/unix -B console=ttya module /boot/x86.miniroot # install grub on b...