similar to: Migration of solaris instances

Yesterday night I've tuned F7 DomU for Oracle 11g install successfully installed Oracle , made checks for EM Console and shutdown DomU. Today morning :- # xm start FDR7PVM # xm console FDR7PVM Fedora release 7 (Moonshine) Kernel 2.6.20-2925.9.fc7xen on an x86_64 Server11G login: root Password: Module is unknown Fedora release 7 (Moonshine) Kernel 2.6.20-2925.9.fc7xen on an x86_64

Hi, from my testing xm reboot and xm shutdown does not work for Solaris DomUs yet, is this correct? regards Bernd This message posted from opensolaris.org

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

Hi! I''m running svn_99 and just tried to install Fedora using the following script: #!/bin/sh ISO=nfs:dom0:/storage/misc/Downloads/ISOs/Linux/Fedora9/Fedora-9-x86_64 zfs create -V 20G storage/fedora virt-install \ --hvm \ --os-type linux \ --os-variant fedora8 \ -n fedora \ -f /dev/zvol/dsk/storage/fedora \ -l ${ISO} \ --vnc \

Greetings, I have a problem that is baffling me. My host machine is an older Dual Xeon machine that does not support HVM - PAE is supported. I have 2008.11 b98 installed as Dom0. I''m trying to install the same as a DomU. In the DomU, I''m starting the ssh service, logging in with X forwarding and starting the gui with: (dom1) jack$ pfexec gui-install The gui displays on my

Hi, Live migration was working well for me with 3.1. Recently I move to 3.2, and now live migration does not work anymore. Here is what i obtain on source node : ---- xm migrate --live webdav node2 Error: /usr/lib/xen-3.2-1/bin/xc_save 26 6 0 0 1 failed Usage: xm migrate <Domain> <Host> [...] ---- And in the xend.log (still on the source node) : ---- [2008-03-03 10:12:52 15205] INFO

I''m happy to announce that we have moved the xen-unstable.hg Solaris dom0 development out to the OpenSolaris community. For hard core developers, you can download, build, and run Solaris dom0 and xen-unstable bits following the instructions at the end of this post. We are currently sync''d up to changeset #17644 (~May 15th). Hopefully we will sync up with xen-unstable.hg every

Hello, I''ve installed a OpenSolaris dom0 snv_44 on a x4100 server, and booted a 32-bit xen kernel. I''m trying to create a OpenSolaris DOMU (snv_44) by following the howto described at http://www.opensolaris.org/os/community/xen/howto/create-osox-domu/. I did not manage to create a diskless environment by using SUNWCXall. I''ve created SUNWCreq instead and add the

What have I done wrong? I installed an xp (service pack 2) domU using the virt-install example from the man page, on a zfs volume. I noticed this behavior on build 129, and I replicated the behavior on build 130: root@opensolaris:/tmp# virsh version Compiled against library: libvir 0.7.0 Using library: libvir 0.7.0 Using API: Xen 3.0.1 Running hypervisor: Xen 3.4 root@opensolaris:/tmp#

Perhaps someone has ideas on this topic, a recent attempt to play with Xen was a reather unlucky event, all what I will be able to demonstrate on that system is a PV ONNV domU which ikely will not be very attractive to the audience :( HW: U40M2, 2 x 2 core AMD revF procs, 8GB MEM, Phonix BIOS 1.5 (latest) 1 x 200GB internal SATA drive SW: dom0 ONNV build 82, latest VirtManager from

Hi All, I have installed Solaris 11 Build snv_77 on x86 box. I have been facing problem while working with Xen (xm command)... I have installed guest domain/VM/OS(Solaris 11 Build snv_77) on x86 box, using "virt-install" utility. After rebooting the host machine, my guest domain has become inactive. I am not able to perform any task on guest domain, including getting console. It

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, I''m running snv84 on a SunFire x2200M2, 2 dualcore opterons, 8GB ram, 2 mirror sata disks (zfs). I tried to install both Ubuntu 7.1 Desktop and Fedora 8 into a HVM domU but failed everytime. The VNC-Server for the domU dies, but the domain still consumes CPU time, disks go idle after a while (zpool iostat or iostat show zero I/O). The domUs booted up fine, the installer started,

Hi, In the installation docs for a Solaris Xen 07/07 DomU (http://www.opensolaris.org/os/community/xen/docs/install-solaris-domu-iso.htm) the config file for the Solaris DomU is name = "solaris-install" memory = "1024" disk = [ ''file:/ws/public/isos/65-0604-nd.iso,6:cdrom,r'', ''file:/export/root/solaris_domu/disk.img,0,w'' ] vif = [

I''m trying to get linux domU going with opensolaris ''130. The CPU is a plain P4 3.2Ghz (no hardware Virt) but all I''m trying is --paravirt Here''s the command line I''m trying..... virt-install --paravirt --name=dom1 --ram=1024 --vnc \ --os-type=linux --os-variant=fedora8 \ --network bridge \ --file /dev/zvol/dsk/rpool/dom1 \ --location

I have just installed Nevada build 75 and am tyring to create an HVM domain using the recipe posted @ http://opensolaris.org/os/community/xen/docs/windows.guest.html. When executing the ''xm create winxp.hvm'' command, I instantly receive the following output: "ERROR Internal error: Could not obtain handle on privileged common interface (2 = No such file or directory) Using

hi all, I can''t create domU with the virt-manager, but I''d like to use it anyway. If I start domUs from command line (xm create ~) I can see them in the virt-manager, but they''re gone after I pause them or stop them. I assume that the virt-manager has some place where it saves config files for domUs, on linux it is usually /etc/xen/vm. I went in some obvious places

Hi all heve been trying (in vain) to get a Solaris b44 DomU (dowloaded from Sun) running on a Linux Xenhost I followed exactly how, and it looked ok when it starts booting... But it never boots . adapted the configfile to boot with -v (that I can see at least something) and this is what I get ===SNIP=== root@Xen-VT02:/export/xc/xvm/solaris-b44# xm create solaris-b44-64.py -c Using config

I have followed a combination of instructions from this post and have been able to get an Ubuntu paravirtualized instance running under snv_96. Is there a way to "list" the fact that it is paravirtualized? For example, xm list, virsh list, etc. thanks -- This message posted from opensolaris.org

Copied ramdisk and kernel to Dom0 root@ServerXen331:/mnt/home/boris/isos# cat copy.sh mount -o loop,ro os200906.iso /mnt cp /mnt/boot/x86.microroot /home/boris/solaris cp /mnt/platform/i86xpv/kernel/amd64/unix /home/boris/solaris Created profile like for osol 2008.11 root@ServerXen331:/mnt/home/boris/solaris# cat osol200906.install name = "sol0906" vcpus = 1 memory =