similar to: Bfu xVM to build 92 problems

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>

I have tried to define a domain or using virt-install both failed. Could some one give me the correct command to do this? I used: virt-install --nographics --paravirt --os-type=solaris --os-variant=opensolaris --ram 1024 --name cam-host --disk path=/dev/dsk/c0t600A0B800049E902000008EB4A9CE744d0p0,driver=phy -l /export/media_images/sol-nv-b121-x86-dvd.iso thx, florian

During boot, I get the following error: Nov 16 09:16:41 sol11 svc.startd[7]: [ID 652011 daemon.warning] svc:/system xvm/store:default: Method "/lib/svc/method/xenstored start" failed with exit status 96. Nov 16 09:16:41 sol11 svc.startd[7]: [ID 748625 daemon.error] system/xvm/store:default misconfigured: transitioned to maintenance (see ''svcs -xv'' for details) It

Hi All, I have bfu''ed to net-virt_xb-21_snv_81_021308. The dladm command on my machine does not have create-etherstub option. Please let me know what could be the issue. Thanks Khushal

Hi All, I am running nevada 79 BFU''ed to 82. The machine is a Ultra 20 with 4GB memory. I have several Windows XP domU''s configured and registered. When ever I try to start the fourth domain I get an out of memory exception: Not enough memory is available, and dom0 cannot be shrunk any further Each of my domains only uses 256 so I thought there would be sufficient memory

Apparently the b89 xvm-src.tar.bz2 tar bz2 archive is corrupted / truncated on the b89 source download page: http://dlc.sun.com/osol/on/downloads/b89/ http://dlc.sun.com/osol/on/downloads/b89/xvm-src.tar.bz2 In the past, the xvm-src.tar.bz2 file had a size of ~ 100 mbytes; with b89 the size of the downloadable archive is only 72 mbytes. And bzip2 complains: % bzip2 -tv

I just went through a BFU update to snv_127 on a V880 : neptune console login: root Password: Nov 3 08:19:12 neptune login: ROOT LOGIN /dev/console Last login: Mon Nov 2 16:40:36 on console Sun Microsystems Inc. SunOS 5.11 snv_127 Nov. 02, 2009 SunOS Internal Development: root 2009-Nov-02 [onnv_127-tonic] bfu''ed from /build/archives-nightly-osol/sparc on 2009-11-03 I have [

I am trying to build Xen from on-src-b79. According to opensolaris website, all xVM sources should be in the on-src-b79 tree, and no additional sources are required. I followed the procedure for doing the nightly build, and I expected that, as a result I will build, along with the Solaris kernel, the xen.gz image. I was hoping to copy that xen.gz image to my test machine, so I can boot with my own

After building and bfu''in the lastest ON build, any time I run a dtrace script I get a Seg Fault. Is there a dtrace for dtrace :) Doug root at prae> dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0)); }'' Segmentation Fault (core dumped) root at prae> pstack core core ''core'' of 101364: dtrace -n

Hi, I''m searching for a tutorial to install correctly a xen domU on OpenSolaris domO. Please help me ... -- This message posted from opensolaris.org

Anyone knows if this is something that will be looked at before b134 is released? Bug 13743 - virsh and xm is unable to start domain first time after boot http://defect.opensolaris.org/bz/show_bug.cgi?id=13743 Regards Henrik http://sparcv9.blogspot.com

Hi, Can anyone explain the following to me? Two zpool devices points at the same data, I was installing osol 2008.11 in xVM when I saw that there already was a partition on the installation disk. An old dataset that I deleted since i gave it a slightly different name than I intended is not removed under /dev. I should not have used that name, but two device links should perhaps not

Hi. I''m all set for doing performance comparsion between Solaris/ZFS and FreeBSD/ZFS. I spend last few weeks on FreeBSD/ZFS optimizations and I think I''m ready. The machine is 1xQuad-core DELL PowerEdge 1950, 2GB RAM, 15 x 74GB-FC-10K accesses via 2x2Gbit FC links. Unfortunately the links to disks are the bottleneck, so I''m going to use not more than 4 disks, probably.

I''ve recently upgraded my x4500 to Nevada build 97, and am having problems with the iscsi target. Background: this box is used to serve NFS underlying a VMware ESX environment (zfs filesystem-type datasets) and presents iSCSI targets (zfs zvol datasets) for a Windows host and to act as zoneroots for Solaris 10 hosts. For optimal random-read performance, I''ve configured a single

This is the error HYPERVISOR_UPDATE_va_mapping() failed Press any key to reboot. Please help. Thanks a lot. -- This message posted from opensolaris.org

[ Redirecting to xen-discuss@opensolaris.org ] xiao liu wrote: > I installed Nevada b84 on my laptop then built latest onnv-gate > on it. > > After I installed it using Install and try to boot, > it panic for don''t know "/xpvd" (hvmboot_rootconf failed) > > Seems b84 don''t support xpvd/xpv, What should I do now, > should I use BFU instead?

Hi all, I have a Toshiba Tecra M9 and have not been able to boot it dom0. This is running SXDE 01/08, snv79b. After booting under kmdb and setting moddebug=80000000 before booting the Solaris kernel (with help from Dan Mick), I was able to see mac_ether as the last thing loading, right after loading the e1000g driver. I cannot drop into kmdb via F1-A after it hangs. I''ve also

http://dlc.sun.com/osol/on/downloads/b114/ This URL makes me think that if I just sit down and figure out how to compile OpenSolaris, I can try b114 now^h^h^h eventually ? I am really eager to try out the new quota support.. has someone already tried compiling it perhaps? How complicated is compiling osol compared to, say, NetBSD/FreeBSD, Linux etc ? (IRIX and its quickstarting??) --

Hi unfortunately VirtualBox does not work yet in a Solaris Dom0: I installed VirtualBox beta and it runs fine on bare metal. Unfortunately the necessary driver does not load automatically in a xVM Dom0. It can be loaded manually but it looks like it does not work in a Dom0: bash-3.2# modinfo | grep vbox # this is a one time task: bash-3.2# cp /platform/i86pc/kernel/drv/amd64/vboxdrv

Here is the error I get, Unable to complete install ''exceptions.RuntimeError Error creating vdisk /var/lib/xen/images/centos.img Traceback (most recent call last): File "/var/tmp/pkgbuild-gbuild/SUNWvirt-manager-0.6.1-build/virtManager/create.py", line 730, in do_install File "/export/builds/xvm_127///proto/install/usr/lib Please could you help? I would like to