There is a problem with the recent xen 3.0.2+ & kernel and ztdummy. The RTC modules needs access to irq 8 which isn't properly emulated in the domU. No clue if this will be fixed. It's been brought up on the xen-devel list a bunch of times but nobody seems to address the issue.
I have been able to get ztdummy to work pretty decent under Xen 3.0.1 (kernel 2.6.12). See results below. Funny enough as long I run the domU with the 2.6.12 kernel I can run Xen 3.0.2 (kernel 2.6.16) on the dom0 without any problems. I don't have any clue what changed for the RTC between 2.6.12 and 2.6.16 to remove this functionality. Depending on the type of High Availability you need look into DRBD and Heartbeat. DRBD is like a disk Raid 1 over the network. I'm currently playing with it for some of my own setups. Zttest under a domU --- Results after 287 passes --- Best: 99.987793 -- Worst: 99.975586 -- Average: 99.976386 I've tested this with about 3 domU's running and the timing seems fairly stable. Unless there is a lot of disk activity and then it seems to start to drop. Hope this helps John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, October 09, 2006 8:17 PM To: TAUG Subject: Re: [on-asterisk] asterisk (trixbox) on xen -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "sacha" == sacha panasuik <[EMAIL PROTECTED]> writes: sacha> to worry about integrating a PCI card into the mix. This sacha> does mean that I am without conference capabilities (I sacha> haven't managed to get ztdummy compiled and running happily sacha> but I haven't tried too hard), but for my installation, ztdummy won't work, I think. It needs support from the Xen hypervisor. I know how to make all of this work, but just haven't got the time to do it... maybe in January. sacha> One of my next projects is to see if I can integrate some sacha> high availability into my installation, that is, have two sacha> computers each running xen be able to keep the filesystems in sacha> sync and take over a downed virtual machine in the case of a sacha> failure (or for maintenance): since my asterisk installation sacha> just needs an IP address, I should be able to bounce it sacha> around the network without too much trouble. You need to at least store your /etc/asterisk on some kind of network store, or at least rsync it and voice mail regularly. - -- ] Bear: "Me, I'm just the shape of a bear." | firewalls [ ] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[ ] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/mcr/ |device driver[ ] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Finger me for keys iQEVAwUBRSrmboCLcPvd0N1lAQLwGgf/UeNmLD6KycnqShH7yd148MpU/inrxBWS JbUGmenplz7fz3qIjggVcv8RW1fTzy8yKo5tgXiSh7eXAxq7a+wA//kb3M3K1sBl lMfEvkQeABYpqauALnIddY0Gl7LtUbOxBpEGt/yfVuI9L4zAG1M+cmcvPN9l/RkC HESNgF+GfbGpvNy7ed+PqSK9OXD06nUIPoPflYlcIsW+kHU/NcwJyoNzyputFo1O LQI8k4w/aaYk9vQplQqFwbYFVtizd9zNJoHh2X2ep5uRQhSSx4uy0LBw//4m6T6Z iB4tCAKr4Pw7Lnd5Djbq/I/YEC+JdgZm0XhdLDspsgkVGtjYvhbIRw== =CwWS -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
