similar to: which build is stable for xVM?

Hi All, Im getting the following error when I run virt-install: bash-3.2# virt-install -n winxp-01 --hvm -r 384 --vnc -f /etc/opt/vms/winxp-01.img -s 16 -c /etc/opt/images/windowsXP_SP2.iso Starting install... libvir: Xen Daemon error : POST operation failed: (xend.err ''Error creating domain: vncpasswd is not set up in VMconfig and xend-config.'') Traceback (most recent call

Folks: I am unable to get my opensolaris sn-b85 domU to start up in an opensolaris sn-b85 dom0. I am booted to xvm. Other systems, such as Fedora 8, WinXP Pro, W2k3 server, W2k8 server and Windows Vista startup normally. I have used the following to build the domU: # mkfile -n 25g /solhvm/solhvm.img # ls -l /solhvm total 269 -rw------T 1 root root 26843545600 Jul 7 10:37 solhvm.img

I am trying to create a DomU guest domain to run snv77 over an a snv77 host, following the instructions and example in http://opensolaris.org/os/community/xen/docs/virt-install.html. I booted the xVM partition (selected xVM from the grub menu). virt-install spends 2 or 3 minutes after "Starting install ..." then fails. here''s what I get: bash-3.2# virt-install --name

Hi all, just wanted to ask if it''s possible to mount a dvd image under a domU win as a "cd-rom"? The "usual" notation (''file:/export/winxp/winxp.iso,hda:cdrom,r'' becomes ''file:/other/path/whateverDVD.iso,hdf:cdrom,r'') does not seem to work (in the .py file); when I start the xp domU, it simply ignores it, no drive is shown. I tried

# 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

Hi, all I test virsh comand "domjobinfo" on x86-i386 and PPC64 host. But Both get nothing. # virsh version Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 Running hypervisor: QEMU 1.1.50 # virsh list Id Name State ---------------------------------------------------- 21 f16-ppc-qcow2

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

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 all, I am trying to install OpenSUSE 11.1 as a para-virtualized DomU on an opensolaris2009.06 guest using the xvm packages provided via IPS. I followed the instructions available here: http://www.opensolaris.org/os/community/xen/docs/virtinstall/ but I get the following error when trying to install from a NFS share where I mounted the iso (as far as I understand the only way to get a Linux

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

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

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