similar to: [RFC][PATCH] Secure XML-RPC for Xend

Attached patch fixes a problem in marshaling large integers. It seems to only occur on systems with very large memory. However, on those systems, it''s a show-stopper. I see this as a temporary solution until we can sanitize the XML-RPC functions and get rid of all the S-Expression stuff. I''ll run xm-test tomorrow against it. Right now I''ve only done basic

Hello, I am trying to see if the hypervisor can be used to detect deadlocks in the guest VMs. My goal is to detect if a guest OS is deadlocked, and if it is, then create a clone of the deadlocked OS without the locking condition, and letting the clone run. While the clone runs I am hoping to generate some hints that could tell me what caused the deadlock. I simulated a deadlock/hang

This seems exceptionally evil and is definitely a PITA. What was the original problem that led us to do this? I''d like to take a stab at correcting it so we can have a more sane installation. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

As any other daemon, I''d assume it should be possible to restart xenstored (i.e. if it crashed or if, during development, a fix was made to it that needs to be tested). However, as I learned after over a day of digging, things don''t work anymore after doing so: Since the watches are transient, they''re lost with the daemon going away. Right now I specifically need this in

On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > Hi, > > I''m working on verifying TCP checksums on incoming packets in Mirage, but > I''ve run into a bit of a problem. > > If TCP checksum offload is turned on on a virtual interface (this is the > default), and if the TCP connection is local to the machine, it looks like > Xen does not

Hi everybody, this e-mail is to let you know that the OpenMirage project is seeking to become a Xen.org hosted project. The prospective project lead of the Mirage Project - Anil Madhavapeddy - has requested a Review of the Mirage Project to become an Xen.org Incubation project. In line with Xen Project Governance (see http://www.xen.org/projects/governance.html), in particular sections -

This fixes a number of problems introduces in the recent XML-RPC check-in. The higher level errors are a great idea and I''ve also extended it a bit to have a slightly nicer interface. Please apply. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

After upgrading to 3.0.2 I tried rebooting a domU (a problem sometimes in 3.0.1 related to bug 514) it failed to come back up. This was in my xend.log. ("Refusing to restart to avoid loops." .... ) [2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) Storing domain details: {''console/ring-ref'': ''223144'', ''console/port'':

I have problem to start domU with errors: # xm create -c x335-hien1-vm4.cfg Using config file "x335-hien1-vm4.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working in changeset: changeset: 7700:98bcd8fbd5e36662c10becdcd0222a22161bb2b6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Nov 8 09:48:42 2005 summary: Fix alloc_skb()

I noticed that the changesets around 7378:bd3268de4145 introduced the xen_domain_handle_t param to xc_create_domain(), the struct domain, etc. and call it a "tool UUID". Can someone explain how this is envisioned being used (xend sets it to some magic values but I don''t see it get used anywhere)? Joe _______________________________________________ Xen-devel mailing list

Hi, Xm list and xm vcpu-list show wrong DomID(name). Under this situation, # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 1 r----- 1064.6 test1 13 64 1 r----- 83879.7 # xm list 1 13 Error: Domain ''1'' not found when running ''xm list'' # xm list

We have test latest xen (ChangeSet 7608) on VT platform with Intel 915 chipset and Here is the test summary: IA32: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32 issues contain: VMX can not be created IA32E: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32E issues

Hi! Does anyone tell me how to use the xm serve command? I''d like to try using this command. But I don''t know the usage and anything necessary, because I found no manual for this command. Regards, Watanabe, Takehiko _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi! Does anyone tell me how to use the xm serve command? I''d like to try using this command. But I don''t know the usage and anything necessary, because I found no manual for this command. Regards, Watanabe, Takehiko _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

This patch causes "xm mem-set" to be lower bound on domX-min-mem option in xend-config. Another configuration option called domU-min-mem has been introduced, which works similarly to dom0-min-mem. This is prevents users from freezing the system when doing "xm mem-set" on very low values like 32M. Signed-off-by: Aravindh Puthiyaparambil

Some time in the last few dozen changesets (I''m at 13662:5bb084098493 now) I''ve started getting this error on xm create: [2007-01-29 12:23:41 7373] ERROR (__init__:1072) (13, ''Permission denied'') Traceback (most recent call last): File "/home/brendan/dev/xen/xen-ss.hg/dist/install/usr/lib/python/xen/xend/Xen dDomain.py", line 1364, in

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''ve noticed that migration doesn''t fail if the VM cannot access the disk image on the new host. (xen-unstable 10273) The VM ends up on the new host and hangs when it does a disk access. This is a somewhat evil behavior. Does anyone have a fix for this in-hand, somewhere? If not, any advice where to look to fix the problem? Thanks, John Byrne