similar to: Open High Availability Cluster with xVM

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

See the PSARC case for rationale: http://www.opensolaris.org/jive/thread.jspa?threadID=58816&tstart=30 Review notes: If you haven''t reviewed xVM changes before it''s a bit confusing. Basically the dirs ending in .hg/ are normal webrevs. The ones with other names are webrevs of a particular MQ patch added on top (for virt-install and xen repos).

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:

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

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 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 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

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''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 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

hi folks, is there a straightforward or well-documented way to migrate my physical sxce snv_115 (x64) system into an xvm ? searching for "p2v" in an opensolaris context seems to pick up a few hits on zones, but nothing obvious relating to xvm on opensolaris for what it''s worth the host system is opensolaris (2010.02 snv_126), but i''m hoping that''s not very

Good afternoon, I was wondering if anyone has any in site as to how to import a VMware vmdk into xVM on OpenSolaris 2009.06 (xVM 3.1). I have a VMware VM created on VMware Server 2.0 and would like to move it over to this xVM server. I appreciate any advice anyone may have. Cheers, -Chris -- This message posted from opensolaris.org

6727404: intermittent fdisk errors while installing xVM Server guests http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6727404 Is that (at least case #1) the same as OpenSolaris 2008.05 bug 2133 (comment #22)? http://defect.opensolaris.org/bz/show_bug.cgi?id=2133 In some cases the Solaris ata driver is returning a slightly truncated capacity with the DIOCTL_GETGEOM /

It looks like xvm does not come built-in to Indiana 2008.05. Which leads to the obvious questions: 1. is xvm compatible with 2008.05 (looking to evaluate Indiana as Dom0)? 2. which packages need to be installed (still getting used to the IPS package naming structure) Thanks! This message posted from opensolaris.org

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

Hi, osol-0906 (b111b), ISC DHCP 4.0.0 I''m trying to install a client over PXE as: root@mk-xvm-1:~# virt-install --hvm --name node-6 --ram 1024 --os-type=solaris --network bridge=vmswitch0 -f /xvm/guests/node-6/root -s 5 --pxe In the VNC console I can see: [...] [rtl8139] - ioaddr 0XC200, irq 5, addr 00:16:3E:22:D8:C2 100Mbps half-duplex Searching for server (DHCP)....No IP address .No

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 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

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