similar to: usb access from PV domU?

After googling around and reading the material on the opensolaris.org xvm community site, I still do not understanding the configuration of networking and would appreciate some assistance. Problem: I have successfully installed an hvm domU running Windows XP on opensolaris 2005.11 (build 94), and when the laptop (lenovo t61, core2 9300) is connected via the e1000g0 interface networking works

When trying to boot the OpenSolaris b75a dvd in a pv domU (using the linux phy:/dev/cdrom device as the source for the boot media), running on an Ubuntu 7.10 x86_64 dom0 box with xen 3.1.0 hypervisor, using the following config file... ======================================== # # Hostname # name = ''solaris-install2'' # # Kernel + memory size # kernel =

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

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

Hi All, I successfully installed a 32bit W2003 domu using the following config file (as the CD image wasn''t persistent between reboots, otherwise I would have used virt-install ;-) ) : isk = [ ''file:/images/xvm/w2003/w2003-disk.raw,hdc,w'',''file:/images/isos/en_win_srv_2003_r2_enterprise_cd1. iso,hda:cdrom,r'' ] memory = 512 name = "w2003"

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

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

After an "exaustive" search on what may be causing this, I still can''t figure it out. I keep getting this same error when trying to run virt-install: # virt-install Traceback (most recent call last): File "/usr/bin/virt-install", line 666, in ? main() File "/usr/bin/virt-install", line 518, in main conn = libvirt.open(options.connect) File

I''m wondering if Open Solaris + xVM will allow me to do the following: I currently have 2 Solaris 10 servers sucking down electrons that I would like to consolidate into 2 xVM instances on a Solaris 11 quad core box. This is what it looks like: Internet --->A sol 10 FW/Web B>---->C Sol 10 app/mail D---> local LAN So interface A is connected to the Internet. The FW/Web box

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

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

(Reply directly, as I''m not subscribed here.) As you may have seen, ARC recently approved my case to remove the ancient sbpro driver Solaris. I''m intent on doing that, because it really helps with our OSS integration effort, which I''m now leading. The problem is, will this impact qemu? I''m not sure of the answer. I *think* qemu emulates an older ESS1370

Short:     Which package do I need to install to get "auto/I18N/Langinfo/autosplit.ix"? Long: The problem I have was discussed almost a year ago (see this thread), but the resolution was not complete... I''m using Mark Johnson''s slim.py script (package list below), against repo=http://pkg.opensolaris.org/dev, followed by `pkg install xvm-gui` and `svcadm enable

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.

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)

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

Bfu 91 to 92 looks good Proceed with xVM upgrade . After running:- # sunos.hg/bin/build-all nondebug bash-3.2# cd packages-nondebug bash-3.2# pwd /usr/tmp/packages-nondebug bash-3.2# ls -l total 20 drwxr-xr-x 4 root root 512 Jun 21 08:57 SUNWlibvirt drwxr-xr-x 4 root root 512 Jun 21 08:57 SUNWlibvirtr drwxr-xr-x 4 root root 512 Jun 21 08:57 SUNWurlgrabber

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?