Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
Jason King wrote: I tried it and it worked great. Even cloned my boot environment, and BFU'd the clone and it seemed to work (minus a few unrelated annoyances I haven't tracked down yet). I'm quite excited about the possibilities :) I am wondering though, is it possible to skip the creation of the pool and have it install to an empty filesystem(s) in an existing pool (assume the pool is already setup w/ grub and the like)? I'm thinking installing new builds (no upgrades), etc, as time goes on until the new installer is here. Yes, eventually, we should be able to do that. But the version of pfinstall you have right now doesn't support it. Lori ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
Mike makes a good point. We have some severe problems with build 63. I've been hoping to get an answer for what's going on with it, but so far, I don't have one. So, note to everyone: for zfs boot purposes, build 63 appears to be DOA. We'll get out information on that as soon as possible, and try it get it fixed for build 64, but until then, stick with build 62. Lori Mike Dotson wrote: Lori, Couldn't tell but is he running build 63? On Tue, 2007-05-01 at 08:16 -0600, Lori Alt wrote: It looks to me like what you did should have worked. The cluster line is fine. I almost always include one in my profiles. So here's a couple things to try: 1. After the install completes, but before you reboot, look at the GRUB menu file: # mount -F zfs mypool /mnt # cat /mnt/boot/grub/menu.lst The tail of the file should look like this: #-- ADDED BY BOOTADM - DO NOT EDIT -- title Solaris Nevada snv_62 X86 kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS module$ /platform/i86pc/$ISADIR/boot_archive #-END BOOTADM #-- ADDED BY BOOTADM - DO NOT EDIT -- title Solaris failsafe kernel /boot/platform/i86pc/kernel/unix -s module /boot/x86.miniroot-safe #-END BOOTADM If it doesn't, something has gone wrong. Although, as long as you have the first of those two entries, it should still boot. 2. You can edit the first kernel$ line above to add -kd to it. That will cause the system to boot into kmdb (assuming it boots at all). If it gets that far, you can either poke around in kmdb if you know it, or just type :c to complete rebooting, at which point maybe you'll get some useful error messages. 3. When you did the install, were there any error messages? Offhand, I don't have any ideas as to what the problem is. But these are some of the things I'd do to debug it. Let me know how it goes. Lori Mike Walker wrote: I also downloaded the .iso file, burned it, and started the install process. I followed these instructions for creating the profile. [i]Here's a quick-and-dirty way to do a profile-driven install: 1. Boot your system off the net or from the DVD in the usual manner. 2. Select Interactive Install. Then, at the first opportunity to exit out of it (which will be after you've answered the system configuration questions, such as whether you want Kerberos and what the root password will be), exit out to a shell. 3. Create a profile for the install in /tmp/profile. (The contents of the profile are described below). 4. Execute the following: # pfinstall /tmp/profile When it's done, reboot. You should get a GRUB menu. Select the entry with the title Solaris release-name X86. The failsave entry should work too. Creating a profile for the install -- The system profile you use should look something like this: install_type initial_install cluster SUNWCuser filesys c0t0d0s1 auto swap pool mypool free / mirror c0t0d0s0 c0t1d0s0 dataset mypool/BE1 auto / dataset mypool/BE1/usr auto /usr dataset mypool/BE1/opt auto /opt dataset mypool/BE1/var auto /var dataset mypool/BE1/export auto /export[/i] Obviously I changed the drive's as required. Then ran the pfinstall on the profile I created. The install looked like it worked correctly, but after a reboot I'm having issues. I get to the grub menu, which only has one entry Solaris. Which when you edit the line is the following [b]kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b]. When I pick this option all it sits there for a second, then boot loops and comes back to the grub menu. Any suggestions? Any way I can see what its doing when it pauses before the reboot? I'm kinda new at this OpenSolaris stuff, so any debugging tips/tricks would be greatly appreciated. Mike This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
sits there for a second, then boot loops and comes back to the grub menu. I noticed this too when I was playing... using kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS I could see vmunix loading, but it quickly NMIed around the rootnex: [ID 349649 kern.notice] isa0 at root point... changing bootfs root/snv_62 to bootfs rootpool/snv_62 and rebuilding the pool EXACTLY the same way fixed it. try changing dataset mypool to dataset rootpool... and I bet it will work.. Rob ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
That's a good catch - I had indeed changed mine to rootpool, but didn't think the chosen name mattered. On 5/1/07, Rob Logan [EMAIL PROTECTED] wrote: sits there for a second, then boot loops and comes back to the grub menu. I noticed this too when I was playing... using kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS I could see vmunix loading, but it quickly NMIed around the rootnex: [ID 349649 kern.notice] isa0 at root point... changing bootfs root/snv_62 to bootfs rootpool/snv_62 and rebuilding the pool EXACTLY the same way fixed it. try changing dataset mypool to dataset rootpool... and I bet it will work.. Rob ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
The name of the pool should not matter. Lori Malachi de Ælfweald wrote: That's a good catch - I had indeed changed mine to rootpool, but didn't think the chosen name mattered. On 5/1/07, *Rob Logan* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: sits there for a second, then boot loops and comes back to the grub menu. I noticed this too when I was playing... using kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS I could see vmunix loading, but it quickly NMIed around the rootnex: [ID 349649 kern.notice] isa0 at root point... changing bootfs root/snv_62 to bootfs rootpool/snv_62 and rebuilding the pool EXACTLY the same way fixed it. try changing dataset mypool to dataset rootpool... and I bet it will work.. Rob ___ zfs-discuss mailing list zfs-discuss@opensolaris.org mailto:zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
The only big difference I see between what you did and what I did was I didn't have the cluster line. On reboot, mine said something like 'Solaris nv_b62' Is it possible there were any errors while it was installing? If it generates a log during install, maybe you can ftp it away before the reboot. Mal On 4/30/07, Mike Walker [EMAIL PROTECTED] wrote: I also downloaded the .iso file, burned it, and started the install process. I followed these instructions for creating the profile. [i]Here's a quick-and-dirty way to do a profile-driven install: 1. Boot your system off the net or from the DVD in the usual manner. 2. Select Interactive Install. Then, at the first opportunity to exit out of it (which will be after you've answered the system configuration questions, such as whether you want Kerberos and what the root password will be), exit out to a shell. 3. Create a profile for the install in /tmp/profile. (The contents of the profile are described below). 4. Execute the following: # pfinstall /tmp/profile When it's done, reboot. You should get a GRUB menu. Select the entry with the title Solaris release-name X86. The failsave entry should work too. Creating a profile for the install -- The system profile you use should look something like this: install_type initial_install cluster SUNWCuser filesys c0t0d0s1 auto swap pool mypool free / mirror c0t0d0s0 c0t1d0s0 dataset mypool/BE1 auto / dataset mypool/BE1/usr auto /usr dataset mypool/BE1/opt auto /opt dataset mypool/BE1/var auto /var dataset mypool/BE1/export auto /export[/i] Obviously I changed the drive's as required. Then ran the pfinstall on the profile I created. The install looked like it worked correctly, but after a reboot I'm having issues. I get to the grub menu, which only has one entry Solaris. Which when you edit the line is the following [b]kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS[/b]. When I pick this option all it sits there for a second, then boot loops and comes back to the grub menu. Any suggestions? Any way I can see what its doing when it pauses before the reboot? I'm kinda new at this OpenSolaris stuff, so any debugging tips/tricks would be greatly appreciated. Mike This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
I was hoping that someone more well-versed in virtual machines would respond to this so I wouldn't have to show my ignorance, but no such luck, so here goes: Is it even possible to build a virtual machine out of a zfs storage pool? Note that it isn't just zfs as a root file system we're trying out. It's the whole concept of booting from a dataset within a storage pool. I don't know enough about how one sets up a virtual machine to know whether it's possible or even meaningful to talk about generating a b62-on-zfs virtual machine. Lori MC wrote: If the goal is to test ZFS as a root file system, could I suggest making a virtual machine of b62-on-zfs available for download? This would reduce duplicated effort and encourage new people to try it out. This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Re: zfs boot image conversion kit is posted
I'm not sure I understand the question. Virtual machines are built by either running a virtualization technology in a host operating systems, such as running VMware Workstation in Linux, running Parallels in Mac OS X, Linux or Windows, etc. These are sometimes referred to as Type II VMMs, where the VMM (Virtual Machine Monitor - the chunk of software responsible for running the guest operating system) is hosted by a traditional operating system. In Type I VMMs, the VMM runs on the hardware. VMware ESX Server is an example of this (although some argue it is not, since technically there's an ESX kernel that runs on the hardware in support of the VMM). So Building a virtual machine on a zpool would require that the host operating system supports ZFS. An example here would be our forthcoming (no, I do not know when), Solaris/Xen integration, assuming there is support for putting Xen domU's on a ZFS. It may help to point out that when a virtual machine is created, it includes defining a virtual hard drive, which is typically just a file in the file system space of the hosting operating system. Given that, a hosting operating system that supports ZFS can allow for configuring virtual hard drives in the ZFS space. So I guess the anwer to your question is theoretically yes, but I'm not aware of an implementation that would allow for such a configuration that exists today. I think I just confused the issue...ah well... /jim PS - FWIW, I have a zpool configured in nv62 running in a Parallels virtual machine on Mac OS X. The nv62 system disk is a virtual hard disk that exists as a file in Mac OS X HFS+, thus this particular zpool is a partition on that virtual hard drive. Lori Alt wrote: I was hoping that someone more well-versed in virtual machines would respond to this so I wouldn't have to show my ignorance, but no such luck, so here goes: Is it even possible to build a virtual machine out of a zfs storage pool? Note that it isn't just zfs as a root file system we're trying out. It's the whole concept of booting from a dataset within a storage pool. I don't know enough about how one sets up a virtual machine to know whether it's possible or even meaningful to talk about generating a b62-on-zfs virtual machine. Lori MC wrote: If the goal is to test ZFS as a root file system, could I suggest making a virtual machine of b62-on-zfs available for download? This would reduce duplicated effort and encourage new people to try it out. This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
