similar to: Install RedHat/CentOS domU on OpenSolaris with ISO image

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:

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

# lofiadm -a /export/home/isos/f8.iso /dev/lofi/1 # mount -o ro -F hsfs /dev/lofi/1 /mnt # share -F nfs /mnt Start virt-install :- # virt-install -n F8PVM --ram 1024 --nographics -p \ -f /dev/zvol/dsk/xvmpool/f8-disk -l nfs:192.168.1.42:/mnt -d Starting install... libvir: Xen Daemon error : GET operation failed: Tue, 15 Apr 2008 09:12:44 DEBUG Preparing mount at

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#

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

Hi Sorry for the cross-posting, I''d sent this to zfs-code originally. Wrong forum. 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

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

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

I am running OpenSolaris build 134 on a T1000 (Sparc). It has been an uphill battle getting this far. Many of the commands I find in the various documentation won''t work for me. ------------------------------------------------------------ steve@t1000:~# pfexec pkg install xvm-gui Creating Plan pkg: ''xvm-gui'' matches multiple packages

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-

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

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

Hello, I am desperate. Today I realized that my OS 108 doesn''t want to boot. I have no idea what I screwed up. I upgraded on 108 last week without any problems. Here is where I''m stuck: Reading ZFS config: done. Mounting ZFS filesystems: (1/17) cannot mount ''/export'': directory is not empty (17/17) $ svcs -x svc:/system/filesystem/local:default (local file

Hello, 1) On OpenIndiana 151, I configured nut 2.6.1 as configure --prefix=/opt/nut/2.6.1 --with-cgi --with-hal --with-user=ups --with-group=nut CC=cc The result is -e Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes build Powerman PDU client driver: no enable SSL development code: yes

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

I''m running a ubuntu 9.04 64 bit dom0 with kernel 2.6.29.6 and xen 3.4.0. My eth0 is bridged to br0 and to my guest VMs. The dom0 is running a dhcp server on br0 which is able to provide leases to physical machines on eth0, and also to a windows xp domU which is bridged to br0. However my open solaris 2009.6 domU is unable to obtain a dhcp lease. On the opensolaris side I can see this:

Begin forwarded message: > From: Kostas Oikonomou <ko at research.att.com> > Date: August 25, 2011 9:51:27 AM EDT > To: Charles Lepple <clepple at gmail.com> > Subject: Re: [Nut-upsuser] nut 2.6.1 on OpenSolaris/OpenIndiana > doesn't find Tripp-Lite ECO550 UPS > > Hi Charles, > > The log hasn't been trimmed. The man page says: > > The

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

# xm create -c vm01.cfg Error: Cannot open config file "vm01.cfg" www:/var/log/xen# xm create -c /etc/xen/auto/vm01.cfg Using config file "/etc/xen/auto/vm01.cfg". Error: (22, 'Invalid argument') # xm log [2006-10-24 16:16:30 xend.util.security 29229] INFO (__init__:1072) Resource label file not found. [2006-10-24 16:16:30 xend.util.security 29229] INFO

How does one install a new vm behind a proxy? When I start the virt-install routine Xen seems to be unable to load information from the ftp/http sources. As a consequence, I tried to install from the DVD-iso as well as the file system. Xen then prompts "What type of media contains the packages to be installed?". After choosing ''hard drive'' it prompts that I do not seem