similar to: Attempt to create F8 FomU at SNV85 Dom0

I believe ZFS is causing a panic whenever I attempt to mount an iso image (SXCR build 39) that happens to reside on a ZFS file system. The problem is 100% reproducible. I''m quite new to OpenSolaris, so I may be incorrect in saying it''s ZFS'' fault. Also, let me know if you need any additional information or debug output to help diagnose things. Config: [b]bash-3.00#

I am pretty new to using solaris''s xvm. I booted my sol dom0 and attempted to create a one of the linux pre-built domU''s. Every time I try to run the xm create command I get an error saying something about it not being able to find the kernel file. Any ideas. This message posted from opensolaris.org

I have the box dual booting SNV85 Dom0 and F8 Dom0. Both Dom0s utilize same ethernet interface for connection to ADSL Modem acting as DHCP Bridge (ZyXEL P660RT2). Both Dom0s obtain IP adress from ISP at boot up with no problems. 1. When i install SNV85 DomU at F8 Dom0 ( vif=['' '']) with DHCP option it gets IP adress from ISP in 1-2 min 2. When i virt-install SNV85 DomU at

Apparently with zfs boot, if the zpool is a version grub doesn''t recognize, it merely ignores any zfs entries in menu.lst, and apparently instead boots the first entry it thinks it can boot. I ran into this myself due to some boneheaded mistakes while doing a very manual zfs / install at the summit. Shouldn''t it at least spit out a warning? If so, I have no issues filing a

Hey, guys I just do the test for use loop device as vdev for zpool Procedures as followings: 1) mkfile -v 100m disk1 mkfile -v 100m disk2 2) lofiadm -a disk1 /dev/lofi lofiadm -a disk2 /dev/lofi 3) zpool create pool_1and2 /dev/lofi/1 and /dev/lofi/2 4) zpool export pool_1and2 5) zpool import pool_1and2 error info here: bash-3.00# zpool import pool1_1and2 cannot import

We are running Solaris 10 11/06 on a Sun V240 with 2 CPUS and 8 GB of memory. This V240 is attached to a 3510 FC that has 12 x 300 GB disks. The 3510 is configured as HW RAID 5 with 10 disks and 2 spares and it''s exported to the V240 as a single LUN. We create iso images of our product in the following way (high-level): # mkfile 3g /isoimages/myiso # lofiadm -a /isoimages/myiso

The `lofiadm'' man page describes how to export a file as a block device and then use `mkfs -F pcfs'' to create a FAT filesystem on it. Can''t I do the same thing by first creating a zvol and then creating a FAT filesystem on it? Nothing I''ve tried seems to work. Isn''t the zvol just another block device? -- -Gary Mills- -Unix Group-

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

Hi all, I have a 5 drive RAIDZ volume with data that I''d like to recover. The long story runs roughly: 1) The volume was running fine under FreeBSD on motherboard SATA controllers. 2) Two drives were moved to a HP P411 SAS/SATA controller 3) I *think* the HP controllers wrote some volume information to the end of each disk (hence no more ZFS labels 2,3) 4) In its "auto

Hi I''m looking into forensic aspects of ZFS, in particular ways to use ZFS tools to investigate ZFS file systems without writing to the pools. I''m working on a test suite of file system images within VTOC partitions. At the moment, these only have 1 file system per pool per VTOC partition for simplicity''s sake, and I''m using Solaris 10 6/06, which may not

On Tue, Nov 06, 2007 at 03:24:08PM -0800, Tony Feldmann wrote: >>You also need to find the relevant kernel/ramdisk for the domU - the jailtime >>images don''t seem to include them, infuriatingly. Johnlev''s respond:- It''s way simpler to export an unpacked ISO over NFS and install via virt-install. regards john I am not sure how to manage on Solaris to get

Dear all, The below is my steps to setup RedHat/CentOS domU on OpenSolaris with ISO image.Although there are some guides to describe how to install Linux on domU,but their install media are from http or OpenSuSe image. I find there is some different from RedHat ISO image. 1) $pfexec svcadm enable svc:/network/nfs/client:default # I find the nfs client is disabled by default, this issue spent

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

System config:- bash-3.2# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 rge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2 inet 192.168.1.53 netmask ffffff00 broadcast 192.168.1.255 ether 0:1e:8c:25:cc:a5 lo0:

************************ Installation profile ************************ [root@ServerRHL51 vm]# cat snv85.install name = "Solaris85pvm" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-85" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk =

Hi I have installed nevada77 in x4200. But i can''t use ''virt-install'' ro create guest domain. Do I need add more pkg? what''s wrong? #virt-install --name xmv-test-1 ram 1024 --nographics --file /export/home/xmv-test-1 --location /export/home/software/snv-solarisdvd-x86-77.iso Traceback (most recent call last): File "/usr/bin/virt-install", line 657,

Is there an existing RFE for, what I''ll wrongly call, "recursively visable snapshots"? That is, .zfs in directories other than the dataset root. Frankly, I don''t need it available in all directories, although it''d be nice, but I do have a need for making it visiable 1 dir down from the dataset root. The problem is that while ZFS and Zones work smoothly

It was rumored that Nevada build 105 would have ZFS encrypted file systems integrated into the main source. In reviewing the Change logs (URL''s below) I did not see anything mentioned that this had come to pass. Its going to be another week before I have a chance to play with b105. Does anyone know specifically if b105 has ZFS encryption? Thanks, Jerry -------- Original Message

Hi and hello, The error: libvirtError: virtDomainCreate() failed POST operation failed: (xend.err "(2,''Invalid Kernel'', ''xc_dom_find_loader : no loader found \\n'')") My Machine: SunOS katecholamin 5.11 snv_111b i86pc i386 i86xpv Solaris I created a disk: pfexec zfs create -V 10G rpool/vms/centos/centos-dsk Mounted my .iso and shared it via nfs:

Hi, does anybody have a list of working Linux Live CDs with Xen Support which I can use in a Xen Domain? What I''m looking for is more or less something like Knoppix with Xen Support so that I can use the yet-not-supported hardware of my Ferrari 4005 in the Linux Domain regards Bernd This message posted from opensolaris.org