similar to: Error checking on migration?

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

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

Hi, The following patch implements a secure XML-RPC protocol for Xend. Instead of using HTTPS with basic authentication and dealing with all that nasty OpenSSL/PAM integration, it just uses SSH. This gives you all the properties you want (great security and PAM integration) with very little code. There are some minor issues so I''d rather it not be applied immediately.

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

> This is another thing that has always put me off. The > virtual block device driver has the ability to masquerade as > other types of block devices. It actually claims to be an > IDE or SCSI device allocating the appropriate major/minor numbers. > > This seems to be pretty evil and creating interesting failure > conditions for users who load IDE or SCSI modules.

> This is another thing that has always put me off. The > virtual block device driver has the ability to masquerade as > other types of block devices. It actually claims to be an > IDE or SCSI device allocating the appropriate major/minor numbers. > > This seems to be pretty evil and creating interesting failure > conditions for users who load IDE or SCSI modules.

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

Hi! On x86_64, changeset 18081, running/building on rhel5, trying to use the HVM direct boot causes the domain to reboot immediately and then the log says the domain is restarting too rapidly. No obvious hints as to where the problem is. If I build the in-tree ioemu code, things work. Any clues as to where to look or how to get some useful debugging output? Thanks, John Byrne

Signed-off-by: Jerone Young <jyoung5@us.ibm.com> -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

CentOS-6.10 We have a host with the following ifcfg file contents: BOOTPROTO=none BROADCAST="" DEFROUTE=yes DEVICE=eth1 . . . GATEWAY=X.Y.Z.234 IPADDR=A.B.C.2 IPV4_FAILURE_FATAL=yes NAME="LAN Link - eth1" NETMASK="255.255.255.128" NETWORK="A.B.C.0" NM_CONTROLLED=no ONBOOT=yes PREFIX=25 TYPE=Ethernet USERCTL=no And an aliased ifcfg containing this:

Hi folks, Xen''s qemu-dm version has a ''-vncunused'' command line switch which asks the internal vnc server to pick any unused tcp port to listen on. The actual port is communicated to the outside world via xenstore. I''m looking for a reasonable way to implement that functionality in upstream qemu. First, I think it shouldn''t be a separate command

This is the start of a paravirt_ops implementation for KVM. Most of it was done by Ingo Molnar, I just moved things around a bit. I don't think there's a measurable performance benefit just yet but there are a few more optimizations that I think we can get in time for 2.6.23 that will be measurable. Regards, Anthony Liguori

This is the start of a paravirt_ops implementation for KVM. Most of it was done by Ingo Molnar, I just moved things around a bit. I don't think there's a measurable performance benefit just yet but there are a few more optimizations that I think we can get in time for 2.6.23 that will be measurable. Regards, Anthony Liguori

Hi, would like to use LLVM as backend for a compiler. One of the features I would like to implement is segment based addressing for position independent data. For some it may sound strange, for others the opposite. No need to write complex story. Imagine you have a custom alocator that manages an area of 1GB of memory. Your application uses a custom allocator to allocate memory inside this area,

Anthony, please pull the following changes since commit 6a4e17711442849bf2cc731ccddef5a2a2d92d29: ssh://xenbits.xen.org/home/sstabellini/git/qemu-dm.git xen_fixes_20130603

Hi, This patch series is an update of my previous paravirt_ops patches. They are loosely based on Ingo's original paravirt_ops implementation for KVM. Some of the changes since the last series include: 1) Switch to using CPUID 0x40000000 instead of using MSR writes to discover shared memory area 2) Attempt to deal with SMP guests 3) Support for generic CR read caching 4) Support for

Hi, This patch series is an update of my previous paravirt_ops patches. They are loosely based on Ingo's original paravirt_ops implementation for KVM. Some of the changes since the last series include: 1) Switch to using CPUID 0x40000000 instead of using MSR writes to discover shared memory area 2) Attempt to deal with SMP guests 3) Support for generic CR read caching 4) Support for

Stefan Hajnoczi <stefanha at gmail.com> writes: > On Thu, May 30, 2013 at 7:23 AM, Rusty Russell <rusty at rustcorp.com.au> wrote: >> Anthony Liguori <anthony at codemonkey.ws> writes: >>> Rusty Russell <rusty at rustcorp.com.au> writes: >>>> On Fri, May 24, 2013 at 08:47:58AM -0500, Anthony Liguori wrote: >>>>> FWIW, I think

Stefan Hajnoczi <stefanha at gmail.com> writes: > On Thu, May 30, 2013 at 7:23 AM, Rusty Russell <rusty at rustcorp.com.au> wrote: >> Anthony Liguori <anthony at codemonkey.ws> writes: >>> Rusty Russell <rusty at rustcorp.com.au> writes: >>>> On Fri, May 24, 2013 at 08:47:58AM -0500, Anthony Liguori wrote: >>>>> FWIW, I think