similar to: Xen on EC2 | Debian Squeeze AMD 64

Hi, I have compiled xen-unstable (using hg clone http://xenbits.xensource.com/xen-unstable.hg). I have successfully booted into the dom0 kernel. output of xm list: Name ID Mem VCPUs State Time(s) Domain-0 0 932 1 r----- 591.2 But whenever I xm create, I get: # xm create /etc/xen/domu1 Using config file

Hi, do somebody knows how to sniff RTP and SIP traffic only for a faster debugging ? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090629/5e160c92/attachment.htm

Hi, I''m trying to install Xen on Ubuntu 11.04. I read somewhere (please correct me if this is wrong) that Ubuntu hasn''t had dom0 support since 8.04 LTS, and the recommended action was to grab a dom0-enabled kernel from Debian, so I did. I''m running 2.6.32-5-xen-amd64 and built Xen 4.1.1 from source. After installation and some troubleshooting, I tried to start

Just wondering if this is a known bug? Trying to migrate the VM off to a diff dom0 results in the below error. Other VMs migrated off fine (started at around the same time as this vm) and I''ve tried a few different target servers, all resulting in the same thing. [2011-09-13 13:48:24 3996] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 29 77 0 0 1 [2011-09-13

Hi, I've managed to get HYLAFAX---->T38MODEM----->ASTERISK---->CISCOAS5400 working, but when they are negotiating asterisk drops a message telling "Unknown RTP codec 96 received from gateway" Do somebody know how to fix it ? Thank you ! << [ TYPE: Control (4) SUBCLASS: Ringing (3) ] [SIP/GWCISCO5400O-600bfcc8] << [ TYPE: Control (4) SUBCLASS: Answer (4) ]

I encounter PV domain restore failure on r14770. Are you guys aware of this? ======================================================================== [2007-04-10 09:57:24 4664] DEBUG (balloon:113) Balloon: 754076 KiB free; need 65536; done. [2007-04-10 09:57:24 4664] DEBUG (XendCheckpoint:220) [xc_restore]: /usr/lib/xen/bin/xc_restore 24 4 1 2 0 0 0 [2007-04-10 09:57:24 4664] INFO

Trying to migrate a 64bit PV guest with 64GB running medium to heavy load on xen 3.4.0, it is showing lot of soft lockups. The softlockups are causing dom0 reboot by the cluster FS. The hardware has 256GB and 32 CPUs. Looking into the hypervisor thru kdb, I see one cpu in sh_resync_all() while all other 31 appear spinning on the shadow_lock. I vaguely remember seeing some thread on this while

I''m having issues with HVM live migration and every xen version I''ve tried - 3.0.1, 3.1.x, 3.3.0 and 3.3.1. Migrations will fail intermittently with messages like this on the receiving hypervisor: [2009-02-02 11:35:19 12629] DEBUG (XendCheckpoint:264) [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 4 2 3 1 1 1 [2009-02-02 11:35:19 12629] INFO (XendCheckpoint:403)

---------- Forwarded message ---------- From: Xavier Cardil <cardil.xavier at gmail.com> Date: Wed, Jul 1, 2009 at 10:51 AM Subject: Unknown udp ports listening experts calling ! To: asterisk-users-request at lists.digium.com Hello, last days we run under an very heavy issue with one audio stream getting mixed with our RTP traffic. The audio source was unknown and changing the asterisks to

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Dear fellow Xen''ers! I''m having a problem with my new Xen-enabled colocation server.. I hope ( at least ;) ) one of you guys know how to fix this problem.. For a certain amount of time ( 1-2 days ) the domU runs fine.. until the console starts spitting out messages like these: [80182.004456] clocksource/0: Time went backwards: delta=-6917292717540055641 shadow=80182004054805

Hi, I downloaded XEN 3.1 source code on a fedora 6 machine. I did # make world # make install It did not give me an error then when I restarted the machine the Grub did not have 2 options. It had only one option that was the kernel. On loading the OS, when i gave # xend it gives the following errors: [root@localhost sbin]# xend ERROR Internal error: Could not obtain handle on privileged command

Hi all, I am using Xen 4.0.0 on top of Ubuntu Lucid (amd64), with the Jeremy kernel taken from git (xen/stable-2.6.32.x branch, 2.6.32.12 when I am writing this email). This kernel is also used in my domu. I can save a domu without any problem, but restoring it may need from 2 to 5 minutes, from a 1G checkpoint file (domu has 1GB RAM). There also errors in /var/log/xen/xend.log :

Hi all, I am using Xen 4.0.0 on top of Ubuntu Lucid (amd64), with the Jeremy kernel taken from git (xen/stable-2.6.32.x branch, 2.6.32.12 when I am writing this email). This kernel is also used in my domu. I can save a domu without any problem, but restoring it may need from 2 to 5 minutes, from a 1G checkpoint file (domu has 1GB RAM). There also errors in /var/log/xen/xend.log :

Hello again, now my xen works. But a strange thing: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2514 4 r----- 76.2 vx1 1 256 1 -b---- 6.1 vx2 2 256 1 -b---- 5.8 vx3 3 256 1 -b---- 5.3 vx4

Hi folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

I got latest (13601) yesterday evening. This doesn''t seem to work to do Restore (at least of the Windows test-image that I''ve been using for testing previously). The VM restores reasonably OK, but it jumps to an invalid address shortly after restoring, giving a D1 blue-screen error (DRIVER_IRQL_LESS_OR_EQUAL), which turns out to be "page-fault in driver" after I

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",