similar to: restarting xend

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.

Jup, 64 Bit Kernel build is done now and works, but 32 Bit kernel config is different, as I use 64 Bit in Dom0 and DomU, 32 Bit only in DomU incl. DomU with DVB etc. XEN options are the same, it''s only the selection of drivers... Andrew, any idea? Boris, do you know a safe way to create a 64 Bit config out of a 32 Bit one? Sorry, I am not so used to kernel building... BR, Carsten.

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

What are the settings that I must specify to have DomU be saved and then automatically started on reboot of the physical server? In my /etc/sysconfi/xendomains it points 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 =

Hi, i read the xenpm wiki page, but i cannot use the "p-states". xenpm shows: xenpm cpu id : 0 total C-states : 2 idle time(ms) : 1776034 C0 : transition [00000000000000000000] residency [00000000000000000000 ms] C1 : transition [00000000000000260278] residency

Hi, It seems to be a very basic question, but need confirmation. I am using Centos as my Dom0, running xen, using paravirtualization. Can I run NON-CentOS (more specifically Debian) operating system on domU, -- Regards, Meghanand N. Acharekar " A proud Linux User " Reg Linux User #397975 ------------------------------------------ I was born free! No Gates and Windows can restrict

I create this class pmaster in order to restart puppetmaster daemon after /etc/puppet/puppet.conf file change. class pmaster { file { "/etc/puppet/puppet.conf": ensure => "file"; } service { "puppetmaster": ensure => "running", enable => "true", hasrestart => "true", subscribe => File [

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

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

Thanks Anna, this was also quite interesting for me. Did you mean that I just have to eliminate the else branch or raise arround "All devices behind the uppermost PCI/PCI-X bridge must be co-assigned to the same guest." or do I have to eliminate more in order to prevent an FLR (whatever that is). For my board it''s definitely necessary to move PCI devices in different guests,

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to

It''s everytime when cpufreq_ondemand or cpufreq-set changes the frequency, aprox. 3 messages per event. Is that occasional? I tend to say: no. Please see an excerpt below. And if it''s not occasional, what could I do? And by the way: I found no code that TSC will get adjusted, so I think it will get worse over the time... Thanks, Carsten. messages.0:Jan 9 12:25:15 data kernel:

Hello, We''re running Xen Unstable changeset 15468 with SLES10 on a Unisys ES7000/one 56x cpu and 160GB memory. Xen is built with NR_DYNIRQS=1024 and max_phys_cpus=64, and booted with dom0_mem=1024 and xenheap_megabytes=64. We have 320 para-virtualized SLES10 VMs on external storage. Our script starts a VM, waits for the start to complete, then starts the next: "for i in *.cfg;

Yesterday, I had a PV OpenSolaris DomU stop responding. I looked on my xen machine and it was in a paused state. I ended up destroying it and then doing xm create to bring it back up. It won''t boot, and I think PyGrub is hanging. Not sure how to resolve this, there aren''t any errors being presented in xen/xm itself. If I try ''xm create config.conf'' it just

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   

Hi everyone, i have a problem on a running xen installation. The server on which the following problem occurs manages 7 VMs at the moment. Now I wanted to create a new one. After sending the xm create command I get the following error: Using config file "/etc/xen/de-smartnet-asterisk". Error: Creating domain failed: name=de-smartnet-asterisk In my xend.log I can find the following

Hi, I don''t want to hijack this thread. But as I lately posted a question which mainly was about weight and cap and this fits in perfectly (and also you seem to be an expert here), I repeat it below. In the meantime I saw an academic article Ludmilla Cherkasova et al. from which I understood that you have to careful that a Dom0 doesn''t get too much weight, as otherwise

Hi! Attached patch makes xen-tools and stubdom-dm going independent from hardcoded pathes. It is no possible to install into /usr/local or any other non-default directory and use it out-of-the box. This allows us to have different Xen versions in different directories, simplifies packaging for distributions. It also finds ''hvmloader'' and

Hello, I''m trying to get a freebsd virtual machine running following : http://www.yuanjue.net/xen/howto.html But I get : # xm create freebsd_xen_INSTALL -c Using config file "./freebsd_xen_INSTALL". Error: (14, ''Bad address'') Am I missing something? I am using xen 3.0.4. Thanks and regards, Sergi .... log output from xend.log: [2007-02-27 12:46:59

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =