similar to: 6295108 When installing to second disk, grub defaults to hd0 instead of hd1

Author: szhou Repository: /hg/zfs-crypto/gate Revision: 56b02c555bfb41a423c9856c46c8918128e9d3c1 Log message: PSARC 2005/373 Contract for the Miniroot Repository 6263254 console output gets graphically corrupted after the newboot 6270368 grub does not honor vendor option 150 to specify menu.lst file 6271324 boot-archive.xml is delivered into the wrong directory 6271395 grub should show progress

Author: szhou Repository: /hg/zfs-crypto/gate Revision: 47e5c553760ca02d7f7f83b1d8a08e7a5d531e54 Log message: 6275104 Can''t use pxegrub to boot off e1000g on v65x 6277640 "available" devinfo property for PCI-PCI bus node is incorrect on intlhotp-1.west system 6286065 "No ethernet found "message under Grub on Dell Precision MT system 6301048 Solaris banner missing when

Please apply that patch to squeeze, otherwise you will not be able to boot even a standard squeeze installation! Since there is no pv-grub in squeeze I think it's quite important to fix it. Cheers, Darkbasic

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Tags: patch pygrub could not boot a newly-updated Debian/testing domU with a non-chained grub2. The traceback was: Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub/grub.cfg WARNING:root:Unknown directive load_video WARNING:root:Unknown directive terminal_output Traceback (most recent call last): File

On Fri, Jun 10, 2016 at 2:06 AM, Adam Goldman via Syslinux <syslinux at zytor.com> wrote: > PXELINUX has stopped recognizing the keeppxe option on the kernel > command line. Here is a patch to make it work again. > > With COM32, it is no longer possible to use preprocessor directives to > determine the SYSLINUX variant. The code inside the #if will never be > compiled. So,

Hello, I've been having a problem trying to boot from first hard drive via pxelinux 5.01 on a HP Proliant server having a SmartArray P220i RAID controller. On other hardware and VMs that i've tried it works. My config file looks like this: label localboot kernel chain.c32 append hd0 Is this a known issue or has anyone experienced this? Thanks, Andrei

Author: vikram Repository: /hg/zfs-crypto/gate Revision: 713996eb2dc91bcfcc9abdc42346acdc09d25708 Log message: 6267174 "bootadm set-menu" should give more boundary check for the "default" option 6294234 bootadm silently fails to update archive 6294785 bootadm hangs during reboot with args 6299969 bootadm can''t update archive on alternate path 6300723 bootadm misbehaves

Hi folks, I''ve been asked to post my experiences here, so... well, here goes :) (in no particular order). We can view bugs in kernel/xen via bugs.opensolaris.org, but not file them against kernel/xen. Could that be added to the list of categories for submission? There''s kind of a composite set of problems with bootadm(1M). While the modified bootadm will update

PXELINUX has stopped recognizing the keeppxe option on the kernel command line. Here is a patch to make it work again. With COM32, it is no longer possible to use preprocessor directives to determine the SYSLINUX variant. The code inside the #if will never be compiled. So, I changed it to use syslinux_filesystem() to determine the variant. Also, I moved the relevant code from

Author: setje Repository: /hg/zfs-crypto/gate Revision: cc6c7f4cdc6315564dc66bc978503b27d8a4499f Log message: 6341178 bootadm refuses to check read-only alternate root Files: update: usr/src/cmd/boot/bootadm/bootadm.c

Hello the list, I thought that it should be easy to do a clone (not in the term of zfs) of a disk with zpool. This manipulation is strongly inspired by http://www.opensolaris.org/jive/thread.jspa?messageID=135038 and http://www.opensolaris.org/os/community/zfs/boot/ But unfortunately this doesn''t work, and we do have no clue what could be wrong on c1d0 you have a zfs root create a

I''ve hit this bug on my home machine couple of times and finally decided to log it since I''ve spend 2 days configuring my "OpenSolaris 2008.11 snv_101b_rc2 X86" and after installing the SUNWsmbfskr package I ended up in the grub> menu. The package contains a necessary module for CIFS. After pkg install SUNWsmbfskr, I rebooted the box. There was no grub menu anymore

After BFU-ing my system to b75 I ended up with a panicing system when 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>

This is opensolaris on a Tecra M5 using an 128GB SSD as the boot device. This device is partitioned into two roughly 60GB partitions. I installed opensolaris 2009.06 into the first partition then did an image update to build 124 from the dev repository. All went well so then I created a zpool from the second partition , which created fine and I could add filesystems to that pool. however

Author: vikram Repository: /hg/zfs-crypto/gate Revision: d549354bd629eeb05494b7ad6228b8fc8c650915 Log message: 6315667 bootadm complains when running init under pfexec Files: update: usr/src/lib/libsecdb/exec_attr.txt

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

Hello all, I am a long-time user of NUT (since last millennium, or so it seems) and beside Linux where I've started, I also integrated it with our Solaris 8 and 9 servers' shutdown procedures - avoiding the possible "hole" when the line power returns right at the bad moment when UPSes and systems are already told to power off. In this case, they see no event like "I am

I''m trying to figure out what the CURRENT requirements are for configuring the xVM domains to start at boot-time and stop on shutdown. The closest to current I''ve seen is http://opensolaris.org/os/community/xen/docs/xVM_lowres.pdf which does not address the problem, and http://opensolaris.org/os/community/xen/docs/xvm-ktde-20070917.pdf which states: *

Using build 70, I followed the zfsboot instructions at http:// www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/ to the letter. I tried first with a mirror zfsroot, when I try to boot to zfsboot the screen is flooded with "init(1M) exited on fatal signal 9" Than I tried with a simple zfs pool (not mirrored) and it just reboots right away. If I try to setup grub