similar to: Sharing a partition between dom0 and domU

Hello there! I made Debian, Xen 2.0 and CLUSTER/GFS work together :). I wrote this little tutorial to help you setup yours. Any feedback is welcome, except comments about W3C validation of my code :p Note that I am talking about compiling CLUSTER with your XEN kernel, I don''t explain how to setup a working cluster. You can find how to setup those in official RedHat docs. You will see,

Are there people currently managing multiple Dom0''s and making significant use of migration? I''m loking at a potential setup of 16 or so physical systems with perhaps 64 or so virtual systems (DomU''s I suppose Dom0 is also a virtual system if I understand thing correctly, but that''s no twhat I mean here). It seems to me that making heavy use of migration for

Has any one had any success with cow implementation in xen ? I found this somewhere http://www.atconsultancy.nl/cowloop/, has anyone tried it out with xen ? -- regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I had this exact same problem with 2.0.7. I had done a little investigation and found scheduled_work gets called to schedule the shutdown in the user domain kernel, but the shutdown work that gets scheduled never actually gets called. I''m glad someone else is seeing this same problem now :-) Like you, it worked a number of times in a row, then would fail, and it didn''t seem to

Hi, I have installed debian 3.1 on an Intel Pentium D processor 920 ( including vanderpool.) The installation worked fine and i''m able to start guest-domains. When I try to start the 5.th Guest-Domain, I Get the following error: Error: Device 769 (vbd) could not be connected. Backend device not found. this problem exists still if i have shutdown or destroyed all guests, after

Hi, I don''t know whether this is a ruby, puppet, or facter bug. The whole issue is one of the "really weird" ones. I first noticed the problem when working with puppet on a train, without any internet connection. In such situation, two problems appear: 1) Mildly annoying, frequent 2-second pauses followed by: Timed out seeking value for ipaddress I think this is

Hi list, i tried to write my first type and provider that should create logical volumes. Seems like i''m missing something as i get nothing when i use it: No errors and no logical volume :-( type/logicalvolume.rb: ================= Puppet::Type.newtype(:logicalvolume) do @doc = "Manage logical volumes" ensurable newparam(:lvname) do desc "The logcal

Hi, We''re trying to follow the instructions at http://reductivelabs.com/trac/puppet/wiki/UsingMongrel (Just using a single puppetmaster/mongrel instance and plain mod_proxy for now, instead of balancer one) We got past the "Server is not a class" error by modifying mongrel.rb We also kind-of got past the: /opt/bin/puppetmasterd:293: undefined method `daemonize'' for

I''m having problems with a definition not being found. I get the following error when running puppetd -vt: err: Could not find type "manual_apt_get_update" in file /etc/puppet/manifests/definitions/apt_misc.pp at line 22 The definition is present for sure. Can anyone spot a problem with the code below? define manual_apt_get_update { exec { "/usr/bin/apt-get

All, Once the puppet clients are installed, is there a option to list the client in the server. mind you I never meant the cert - signing list.. which would be puppetca --list. Thanks for your help -Rajeshwaran -- He also serves Who only stands and waits.... _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

Hi, We have dedicated puppet master boxes, which basically only run a mongrel/puppetmasterd (6 instances), an apache proxy for mongrel and puppetd. Recently puppetmasterds seemed to have leaked almost all of the RAM, and the thrashing made the box painfully slow. We restarted the puppetmasterd processes, and started collecting some statistics. Attached is a graph of memory usage on one of the

Dear All, I''m trying to install Xen on Debian Sarge + testing (halfway updated system). Hardware P-IV, 256M Packages: -------- linux-image-2.6.17-2-xen-686 linux-modules-2.6.17-2-xen-686 xen-docs-3.0 xen-hypervisor-3.0-i386 xen-ioemu-3.0 xen-linux-system-2.6.17-2-xen-686 xen-tools xen-utils-3.0 /boot/grub/menu.lst: -------------------- title Debian Xen 3.0 root

Hi list, Here is the idea. I am running a domU out of a partition on a USB drive. I use the other partition to store the domU state. Then I carry this USB key to my office and restore the VM at the point where I left it. Thus I am trying to use xen''s virtualization to carry my desktop on a USB key. I have put up a web page explaining the details and a script to prepare the USB key.

packages.debian.org is lagging in terms of what it''s showing, but.... $ rmadison -u debian {puppet,facter} | grep unstable puppet | 0.25.4-1 | unstable | source, all facter | 1.5.7-1 | unstable | source, all they''re both up there now. -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

Hi, Is there a way to have puppetmaster sign new clients'' certificates when using apache+mongrel for serving, without having a separate puppetmaster instance running webrick on a different port/IP? I guess this does not work out of the box because apache is told to do the verification very early in the connection process, at which point it does not yet know that the client is going to

Hi, I have just successfully configured Puppet to run with Mongrel, and would like to update the documentation with what I''ve learned. However, since I''m not an expert with these things, I thought I''d share with the list before updating the wiki. So here''s what I''d change: + Remove this picture:

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

I made an attempt to switch to mongrel today and I''m running into a strange error message I can''t seem to track down: debug: puppetmaster: Setting servertype to ''mongrel'' Server is not a class Tracing through with the debugger shows: [snip] /foo/lib/gems/puppet-0.22.4/bin/puppetmasterd:248: case Puppet[:servertype] (rdb:1) n

I''m trying to write a wrapper definition for the file type to make it a bit smarter. I have a basic version working fairly well: define xfile($owner = root, $group = root, $mode = 644, $source, $backup = main, $recurse = false, $ensure = file) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup, recurse

On Thu, Jun 28, 2007 at 10:24:42AM -0000, puppet wrote: > #446: Require should stack not override [...] > Comment: > > Here is a patch against 0.23.0 which I think fixes this. It essentially > makes all relationship metaparameters stack up, rather than get overriden. > > --- puppet-0.23.0.orig/lib/puppet/parser/resource.rb 2007-06-17 [...] > > I strongly feel