similar to: autostarting domUs

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

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

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

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

I''ve searched all night long on google, discussions, threads, and the xen wiki... but I can''t find how to do this: vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] where should I put this? I have sxce94, dom0 works nicely, and domUs too, but I''d like to select ne2k for an hvm openbsd dom0 that I''ve created because I''ve read

I have a xVm b75 server and use zfs for storage (zfs root mirror and a raid-z2 datapool.) I see everywhere that it is recommended to have a lot of memory on a zfs file server... but I also need to relinquish a lot of my memory to be used by the domUs. What would a good value for dom0_mem on a box with 4 gig of ram?

Hi there, as i stated before in my talk with Ben Johnson, I hacked a little bit and here it is - autostarting jobs. I think someone (eh... Ezra) should review it and check to see if i made any mistakes. Also i dont have the possibility to test it on other-than-Windows systems, but since the calling process works just the same, it should do well... Now the neccesary evil, the documentation... If

I''m trying to figure out what the CURRENT requirements are for configuring the xVM domains to start at boot-time and stop on shutdown. The closest to current I''ve seen is http://opensolaris.org/os/community/xen/docs/xVM_lowres.pdf which does not address the problem, and http://opensolaris.org/os/community/xen/docs/xvm-ktde-20070917.pdf which states: *

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#

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

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

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

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

Hello everyone, I''m wondering what the current status of hardware performance counter usability in Xen is. I see some old posts describing the diffculties of virtualizing hardware counters within dom0 and the domUs, but not much else. Have they been implemented or are they in the process of being implemented? Or are there no future plans for implementation? Any help would be

I''ve implemented code to send out bogus gratuitous ARP packet from vna in order to fix CR 6701114. The webrev is at: http://jurassic.eng/net/consulte.prc/export/build/xvm-6701114/webrev Some backgroud information (see CR 6701114 for more detail): During live migration of an xVM domain from one dom0 to another, the VNIC will be moved from one switch port to another. But, the

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

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:

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