search for: on_xend_start

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

on_xend_stop can be set to ''suspend''. However, on_xend_start cannot be set to ''resume'' as far as I can see, and it''s not automatic. This seems like an easy way to create a config that ends up corrupting the domU filesystem. Are there further changes planned here? Presumably it will involve on_xend_start=''start'' ju...

Hi all, Long time no speak. Well, since I''ve chosen to stick with the XML Xen configs; config.sxp, how do I; 1) Have a domain truly shutdown upon xend shutting down (not save state but halt -p). 2) Have certain VMs start before others. Startup is (on-xend_start start) But thats all I could really muster at this point. Thanks in advance, - Brian

Is there a "xen" or "opensolaris" way to auto-start DomU''s ? I love xen but if i can''t auto-start it kind of makes things a pain. thnaks -- This message posted from opensolaris.org

Hi, I''ve just made changes on xend config xend-config.sxp file, but I''m not sure if restarting xend daemon also restart domUs? Thoughts? thanks in advance. -- Regards; Israel Garcia _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'', ''osc''], [''memory'', 512], [''vcpus'', 1], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6.18.8-xen''], [''ramdisk'', ''/boot/initrd-2.6.18-x...

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

...nd managed domain -p, --paused Do not unpause domain after starting it ----------------- Now how to make this guest domain active again. While reading through "xvm" man pages, I found that, we can set the following properties for the domain. 1) on_xend_stop=ignore 2) on_xend_start=start Que 1) How to set this properties for the domain, to make guest domain running when we reboot the host itself. The user manual of Xen 3.0 say, you can put the domain config file under /etc/xen/auto dir for automatic domain booting... But I dont see /etc/xen dir on the host machine and...

...to a save folder (which does not exist) My configuration files are located at /vm/cfg/vm-xxxx/vm-xxxx.xen   In my config file I have: on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' on_xend_stop = ''suspend'' on_xend_start = ''start'' But, after calling "shutdown -r now", the DomUs are turned off and do not start. My DomU''s are Windows 2003 Servers running in HVM virtualization. Alexander Zherdev azherdev@yahoo.com _______________________________________________ Xen-users mailin...

...-000000000000/image/kernel= /vm/00000000-0000-0000-0000-000000000000/image/cmdline= /vm/00000000-0000-0000-0000-000000000000/image/ramdisk= /vm/00000000-0000-0000-0000-000000000000/on_poweroff=destroy /vm/00000000-0000-0000-0000-000000000000/bootloader_args= /vm/00000000-0000-0000-0000-000000000000/on_xend_start=ignore /vm/00000000-0000-0000-0000-000000000000/on_crash=restart /vm/00000000-0000-0000-0000-000000000000/xend/restart_count=0 /vm/00000000-0000-0000-0000-000000000000/vcpus=4 /vm/00000000-0000-0000-0000-000000000000/vcpu_avail=15 /vm/00000000-0000-0000-0000-000000000000/bootloader= /vm/00000000-00...

...0) (on_crash restart) (uuid blah) (bootloader_args -q) (vcpus 1) (name leela) (on_poweroff destroy) (on_reboot restart) (cpus (())) (description ) (bootloader /usr/bin/pygrub-4.1b) (maxmem 1024) (memory 1024) (shadow_memory 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (cpu_time 0.0) (online_vcpus 0) (image (linux (kernel ) (superpages 0) (tsc_mode 0) (videoram 4) (pci ()) (nomigrate 0) ) ) (status 1) (state --p---)...

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal This issue is similar to http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-March/003217.html but since I was not able to find a bug report I'm reporting this now. Steps to reproduce: 1) cat << EOF > config name = 'squeeze64' vcpus = '4' memory = '512' disk = [

I had an issue late yesterday where some windows domU''s were down. The person who "owns" those domUs let windows updates install and then restart, which they failed to restart. When I tried to manually restart them I was getting can''t allocate memory errors. In the past I''ve had can''t allocate memory errors when trying to bring up a new domU.

...ams to be rebooting the host. I'm going to update the host to latest Xen 4.4 now hoping this is a old bug. Here's from xen logs [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:105) XendDomainInfo.create(['vm', ['name', 'xxx'], ['memory', 2048], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 2], ['oos', 1], ['image', ['linux', ['kernel', '/kernels/vmlinux-2.6.18.8-4'], ['videoram', 4], ['args', 'root=/dev/xvda ro xencons=tty console=tty1...

...-000000000000/image/kernel= /vm/00000000-0000-0000-0000-000000000000/image/cmdline= /vm/00000000-0000-0000-0000-000000000000/image/ramdisk= /vm/00000000-0000-0000-0000-000000000000/on_poweroff=destroy /vm/00000000-0000-0000-0000-000000000000/bootloader_args= /vm/00000000-0000-0000-0000-000000000000/on_xend_start=ignore /vm/00000000-0000-0000-0000-000000000000/on_crash=restart /vm/00000000-0000-0000-0000-000000000000/xend/restart_count=0 /vm/00000000-0000-0000-0000-000000000000/vcpus=4 /vm/00000000-0000-0000-0000-000000000000/vcpu_avail=15 /vm/00000000-0000-0000-0000-000000000000/bootloader= /vm/00000000-00...

...In my xend.log I can find the following entries: [2009-09-30 15:42:57 23165] DEBUG (XendDomainInfo:89) XendDomainInfo.create([''vm'', [''name'', ''de-smartnet-asterisk''], [''memory'', 128], [''vcpus'', 6], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''cpus'', ''2-7''], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz_domU''], [''args&...

....... log output from xend.log: [2007-02-27 12:46:59 xend.XendDomainInfo 9551] DEBUG (XendDomainInfo:94) XendDomainInfo.create([''vm'', [''name'', ''freebsd-xen-INSTALL''], [''memory'', 512], [''vcpus'', 1], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''image'', [''linux'', [''kernel'', ''/xenvm/fbsd/freebsd-XENU_INSTALL''], [''args'', ''boot_verbose,boot_...

...extra = '' xencons=tty1 3'' ----- xend.log ----- [2007-09-02 05:26:42 8597] DEBUG (XendDomainInfo:78) XendDomainInfo.create([''vm'', [''name'', ''xen002''], [''memory'', 512], [''vcpus'', 4], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-xen''], [''ramdisk'', ''/boot/initrd-xen''], [...

I''m not able to start, destroy, or delete a DomU: > xen1:~ # xm start test4 > Error: Domain is already running > Usage: xm start <DomainName> > > Start a Xend managed domain >   -p, --paused                   Do not unpause domain after starting it    >   -c, --console_autoconnect      Connect to the console after the domain   

...latest Xen >>4.4 now >> hoping this is a old bug. >> Here's from xen logs >> [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:105) >> XendDomainInfo.create(['vm', ['name', 'xxx'], ['memory', 2048], >> ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', >>2], >> ['oos', 1], ['image', ['linux', ['kernel', >>'/kernels/vmlinux-2.6.18.8-4'], >> ['videoram', 4], ['args', 'ro...