similar to: ZFS LDOMs Jumpstart virtual disk issue

I''ve tried using S10 U6 to reinstall the boot file (instead of U5) over jumpstart as its a ldom, noticed a another error. Boot device: /virtual-devices at 100/channel-devices at 200/network at 0 File and args: -s Requesting Internet Address for 0:14:4f:f9:84:f3 boot: cannot open kernel/sparcv9/unix Enter filename [kernel/sparcv9/unix]: Has anyone seen this error on U6 jumpstart or is

Anyone have idea how to create ZFS pool and volumes during jumstart instalation ? (I''m using JumpStart Enterprise Toolkit) kloczek

I understand that currently, at least under Solaris 10u6, it is not possible to jumpstart a new system with a zfs root using a flash archive as a source. Can anyone comment as to whether this restriction will pass in the near term, or if this is a while out (6+ months) before this will be possible? Thanks, Jerry

[Cross-posting to ldoms-discuss] We are occasionally seeing massive time-to-completions for I/O requests on ZFS file systems on a Sun T5220 attached to a Sun StorageTek 2540 and a Sun J4200, and using a SSD drive as a ZIL device. Primary access to this system is via NFS, and with NFS COMMITs blocking until the request has been sent to disk, performance has been deplorable. The NFS server is a

Hello, I don't know how off the wall this question will be, but first let me say that I've found your buildpkg.sh script very useful in creating an OpenSSH package for use on my Solaris systems. Currently I'm trying to set up a fully automated JumpStart system at my workplace, and I'm realizing that the 'postinstall' script (and possibly some of the other install scripts)

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

Hi everybody, Today I tried the latest Solaris on Xen build. I downlaoded all files and created the iso. Then I wanted to run setup_install_server , but this failed: bash-3.00# ./setup_install_server /export/sol_xen/ -bash: ./setup_install_server: cannot execute binary file -bash-3.00# So I create a tar file to copy over all files to export/sol_xen/ Then I tried to start and install via

Hi all, I'm trying to use mboot.c32 to build our Solaris machines but the problem we are getting is the network interface doesn't get configured. It would boot in to the miniroot and then drops in to a shell. At the shell, if I configure the interface via dhcp it would continue on with the jumpstart. This is the first time we are using syslinux (version 4.04) and looking at the

I have just upgraded my jumpstart server to S10 u2 b9a. It is an Ultra 10 with two 120GB EIDE drives. The second drive (disk1) is new, and has u2b9a installed on a slice, with most of the space in slice 7 for the ZFS pool I created pool1 on disk1, and created the filesystem pool1/ro (for legacy reasons). I them moved my data from the original disk0 UFS file system to pool1/ro. Initially I

I accidentally created a zpool on a boot disk, it paniced the system and now I can jumpstart and install the OS on it. This is what it looks like. partition> p Current partition table (original): Total disk sectors available: 17786879 + 16384 (reserved sectors) Part Tag Flag First Sector Size Last Sector 0 usr wm 34 8.48GB

Warning: WINE Newbie Alert. Proceed with caution.... Background: I don't want to fork up $$$ for a separate Windows machine for my kid so I've decided to see if I can run any of the popular brain-rot software under WINE (Is it "WINE" or "Wine" or "wine"?) on a Linux 2.4.18 kernel. My first project is a vintage 1995 version of JumpStart Kindergarten. Seeing

Hello, I''m a grad student working at University of Michigan in computer architecture. I''m writing to open up the idea that instrumentation of the xvm would be extremely useful tool for the research community. Those of us interested in virtualization are very interested in monitoring the behavior of these systems and with low engineering effort! I was hoping to get feedback on

Suppose I have a storage server that runs ZFS, presumably providing file (NFS) and/or block (iSCSI, FC) services to other machines that are running Solaris. Some of the use will be for LDoms and zones[1], which would create zpools on top of zfs (fs or zvol). I have concerns about variable block sizes and the implications for performance. 1.

I'm trying to get Knowledge Adventure's Jumpstart Preschool to run under wine 0.9 on debian stable. According to <http://appdb.winehq.org/appview.php?appId=801> this program works flawlessly. But when I try it, it runs until I get just past the introduction and then a sudden crash. Fortunatly it keeps a log and the log says: MIDI driver error processing MENU\MID\MM000_.WSB So my

We have a virtualized environment of T-Series where each host has either zones or LDoms. All of the virtual systems will have their own dedicated storage on ZFS (and some may also get raw LUNs). All the SAN storage is delivered in fixed sized 33GB LUNs. The question I have to the community is whether it would be better to have a pool per virtual system, or create a large pool and carve out ZFS

Hi All, Now that we have multiboot capable pxelinux, thanks to mboot.c32, I decided to try and remove pxegrub from my x86 jumpstart infrastructure since, in theory, pxelinux can now do it all. The problem I'm having is I'm not very sure I'm following Tim's documentation correctly... I'm not 100% what comes after the --- and whether the Sun kernel needs it's arguments

Folks; During a jumpstart (2nd boot) of a Sun Fire 240 with Solaris 10 Update 3 (11/06), I noticed the following message; Jun 27 11:43:33 first fbt: NOTICE: cannot instrument return of fd_intr at 7b7d6278: non-canonical return instruction Kernel level was Generic_118833-33. Jumpstart was conducted using the standard JET modules. What gives? The jumpstart worked though. Solaris 10 installed

Hi, since hostid is stored in the label, "zpool import" failed if the hostid dind''t match. Under certain circonstances (ldom failover) it means you have to manually force the zpool import while booting. With more than 80 LDOMs on a single host it will be great if we could configure the machine back to the old behavior where it didn''t failed, maybe with a /etc/sytem

I'm having some difficulties pxe booting Solaris. So far I have tried the mboot.c32, and the pxegrub shipped with Solaris. At first I had some problems with blksize, but this disapeared when I changed from atftpd to tftpd-hpa. The point at which I'm stuck now is, the kernel and x86.microroot/x86.miniroot is loaded but then VMWare crashes. I might try with real hardware, but I thought

That is...is there a mechanism provided to do this? As an afterthought, this also applies to non-global zones, although one can stick something in the oem-banner eeprom variable that is identically visible on all the zones, which is not the case on LDOMs. However, that''s not a supported mechanism. Having something that was would be better. Ideal if the same mechanism (on what might or