similar to: xVM filas on SXCE 127

Hello, I recently installed SunOS 5.11 snv_91 onto a Ultra 60 UPA/PCI with OpenBoot 3.31 and two 300GB SCSI disks. The root file system is UFS on c0t0d0s0. Following the steps in ZFS Admin I have attempted to convert root to ZFS utilizing c0t1d0s0. However, upon "init 6" I am always presented with: Bad magic number in disk label can''t open disk label package My Steps: 1)

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

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

Last night I upgraded from b127 to b130 and now I can''t mark autostart domains: # virsh autostart lunar-1 error: Failed to mark domain lunar-1 as autostarted error: failed to serialize S-Expr: (domain (on_crash restart) (uuid 91c21040-2098-bc0d-b401-3908f3a21667) (bootloader_args) (vcpus 1) (name lunar-1) (on_poweroff destroy) (on_reboot restart) (cpus ( Searching the archives

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

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

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

I''m currently running snv_76 on my laptop to run a windows XP hvm domU. Everything has been working great until recently when I started getting the following messages during boot (from dmesg): Dec 11 16:31:19 pdlaptop xenstored: [ID 702911 daemon.error] Checking store ... Dec 11 16:31:19 pdlaptop xenstored: [ID 702911 daemon.error] Checking store complete. Dec 11 16:31:19 pdlaptop

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

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

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

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

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

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''m completely new to the technology, please bare with me :) I have installed build 78 on VMware server and in grub, selected to boot xVM. However, it doesn''t boot up. It got to the point where it says: WARNING: cpu0: failed to update microcode code from version 0x3 to 0xc SunOS Release 5.11 Version snv_78 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights

I''m running Xen on Nexenta Core, and I haven''t yet figured out how to control which DomU''s are started with svcadm enable svc:/system/xvm/domains:default. virsh doesn''t seem to be available with Nexenta Core, so I''d rather edit the configuration files by hand. However, I''ve found neither OpenSolaris or Nexenta documentation on how this is

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)

One of my test domUs is a opensuse 10.3 PV domain, and it has a /boot/grub/menu.lst file. pygrub is used as bootloader. With xVM 3.1.4, the arrow keys can be used in the pygrub screen. With xVM 3.3-unstable, the arrow keys don''t work for me any more. What I''ve found out so far is that: - gnome-terminal, xterm or dtterm are running with "vt100 application key