similar to: xVM least privilege: please review

http://cr.opensolaris.org/~johnlev/xvm-vnc-chown/ Now Xvnc runs as the ''jack'' user on the live CD, the password file must be owned by jack for it to work. Note that a full fix for this would make this VNC service only exist on the live CD[1]. As a temporary measure, we just disable ourselves post-install. Process question: after putting back to pkg-gate, does this need

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 updated to b129 and now I get this error in dmesg on boot. Dec 15 06:26:05 nas svc.startd[9]: [ID 652011 daemon.warning] svc:/system/xvm/domains:default: Method "/lib/svc/method/xvm-domains start" failed with exit status 1. Dec 15 06:26:07 nas last message repeated 2 times Dec 15 06:26:07 nas svc.startd[9]: [ID 748625 daemon.error] system/xvm/domains:default failed: transitioned to

Hello All, One of our user is facing java.lang.OutOfMemoryError: PermGen space issue on a Windows 2003 32 bit xVM domU with 4GB RAM. He is able to successfully do these tests on equivalent physical system with Windows 2003 OS and 4GB RAM. Another user is facing issues with Tomcat running out of heap space on a Win2008 64bit xvM domU Our xVM hypervisor server is X4150 server with 64GB RAM

Hi Everyone, Just a quick fyi, as within the HA Clusters community we have recently endorsed a project to develop an Open High Availability Cluster (OHAC) failover agent for xVM guest domains. The HA Clusters community is located at http://opensolaris.org/os/community/ha-clusters/ The project, Cluster Agent: OpenSolaris xVM, is located at http://opensolaris.org/os/project/ha-xvm/ As we

Hi Dave, I built successfully an xvm 3.3 system. However, I found virt-manager and virt-install don''t work. I attached the error messages of both as below. xm tool seems to work. I can run OpenSolaris200811 LiveCD and install it onto file based disk. The error messages of virt-manager: ====start of error message==== Unable to open connection to hypervisor URI ''xen'':

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

http://cr.opensolaris.org/~johnlev/xvm-daemon-chdir/ thanks, john

Hi, I double checked the configuration with xm and the "w!" option seems to be configured :-( I also upgraded to build 123, but also no change in behaviour. Thus is this a RAC 11.2 problem or is there a general problem using zvols as as shared disks for xVM domains ? (device (vbd (protocol x86_64-abi) (uuid 048d282d-da4c-2e0b-b9f4-f3f4cc0811c7)

Hi all, I''m in the process of building a home server with OpenSolaris 2009.06. It''s main function is to serve files (hence using OpenSolaris for some ZFS goodness), but I want to host some Windows x64 VMs on it as well. Given that there are currently no x64 Windows drivers for xVM, I was thinking of starting with VirtualBox (which does have x64 Windows drivers), and then

Hi all, I installed 2009.06, xVM and happily installed a domU with no issues. I just did this through the virt-manager GUI, and kept it as simple as possible. Later I installed and booted a zone with very simple and standard configuration. My existing xVM virtual machine did not immediately stop working, or have any interruption at all. But, I can no longer create new virtual machines, or even

Hi, Gurus, which build is stable for xVM? I chose Nevada 111 as xVM server, because it''s build base for OpenSolaris 200906. I think it should be stable. But I met error when I creating second vm on it. I tried virt-install and virt-manager, and I got same error. Here is error info libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed:

i''m crossposting from the opensolaris help forum: i''ve just migrated some zones to newer hardware running b94, and find that after a while working with an hvm in xvm, the machine hangs/panics. if i leave xvm stuff alone, the machine is perfectly reliable. it''s x64, intel chipset/procs anybody else having these troubles - zones and xvm together causing hangs/panics?

Hi, I''ve started to play with CPU power management today, and that didn''t work at first. By default, my OpenSolaris host boots with a xVM enabled kernel. I reboot it with a standard kernel to see, and then CPU power management works perfectly. I searched a long time, but I didn''t find anywhere a word about CPU power management disabled when using an xVM kernel.

I just filed bug 7215. Here is the workaround: Symptom: http://src.opensolaris.org/source/xref/xen-gate/xvm-3.3%2Bsunos.hg/ or http://src.opensolaris.org/source/xref/xen-gate/xvm-3.3+sunos.hg/ Error 404: File not found! The requested resource is not available. Workaround: Escaping the % character with %25 will do the trick, because the last parse step will get an %2B escape sequence as

Hello, sorry if these questions have been answered before but please excuse me, I''m new to xVM :) Anyway I have been using Linux/Xen for quite a while and am very familiar with it. I am very interesting in changing to OpenSolaris/xVM for the primary reason of being able to easily leverage the ZFS filesystem and thin provisioning for better storage efficiency. 1) Is this ZFS thin

Hello All, I''m investigating the possibility of running an EAL-certified Solaris as a dom0 and domU on Xen or xVM. The rationale of running Solaris in dom0 is for security features, such as the features provided by the Controlled Access Protection Profile. So far it seems like a Solaris HVM is ideal for each domU in my current scenario, due to the ability for labeling via trusted

I have a Sony lib-162 tape library hooked up to an adaptec 39160 scsi controller. I''m running OpenSolaris / Indiana snv_98 with the CADP160 driver installed from a SXCE dvd (snv_99). When I boot without xvm, I can run "mt config" and see the configuration information for the first drive in the library. Under xvm, some scsi operations still work - I can access the changer, move

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

Trying to boot my Thinkpad T30 with Solaris snv_81 xVM it get the error message This version of Solaris xVM does not support this hardware The output of "echo ::interrupts | mdb -k" while booted without xVM is bash-3.2# echo ::interrupts | mdb -k IRQ Vector IPL(lo/hi) Bus Share ISR(s) 0 0x20 14/14 - 1 cbe_fire 1 0x21 5/5 ISA 1 i8042_intr 3 0x23