similar to: [PATCH][XM-TEST] Make sure rcS is executable before ramdisk build

This patch adds a test that tries to create a domain with only 16MB of RAM. It verifies that the domain is created and that the console works. Right now this test fails for me: the domain just dies immediately with no indication of why, or with any useful console data. Should we put a sanity check on xm''s create and mem-set commands that prevent the user from doing something we know

The following patch allows the network tests to pass with hvm support enabled. More specifically: 02_network_local_ping_pos.py REASON: ping loopback failed for size 65507. ping eth0 failed for size 65507. (but all other size pings work) 05_network_dom0_ping_pos.py REASON: Ping to dom0 failed for size 65507. (but all other size pings work) 11_network_domU_ping_pos.py passes 100% (even the large

This patch -Displays[1] current parameters for running domains ala xm list -Allow users to set[2] one or more parameters[3] without having to provide values for parameters they do not wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for

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()

The attached patch: 1. Converts the shutdown driver and xend to use the store instead of control messages, 2. Includes Anthony''s xenstore notification code, and 3. Changes xend so that sysrq''s are no longer sent as "special case" shutdown messages. Store keys are cheap, so making the sysrq delivery less obscure is good. I think I have made all of the

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

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

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

Hello, I have a problem with a 2.5.62 kernel and ramdisk. I am using isolinux to create a cd that loads some of its partition in ramdisk. The script involves mounting a ramdisk (e2fs) on /fake/ramdisk, copying part of the cd to that mount point, unmounting it, and remounting it on /fake/needwrite. The problem is that, although the content of /fake/needwrite gets correctly copied, the content of

This patch fixes the bug that "xm reboot <domid>" can not reboot vmx domain. In xm reboot process, control panel will wait until DomU notified it. Unlike DomU, vmx domain can not passively do that, since it runs unmodified OS. This patch adds the missing logic in control panel. Any comment? Signed-off-by: Xu Dan <dan.d.xu@intel.com > Yu Ke

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

Hello! I'd like to load a ramdisk with syslinux, but from another disk. And I've found this in the syslinux faq: "An initrd is loaded from a DOS file if the option "initrd=filename" (where filename is the filename of the initrd image; the file must be located in the root directory on the boot floppy)"

Way are not a ramdisk included with the images from jailtime.org That seems this is needed _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I'm having loads of problems with recordings, as in crappy audio quality and lost pieces of the recordings. I've been searching for a solution and the solutions i find on the interwebs include a ramdisk, for local recording, or another machine, handling the recording. I guess the ramdisk would be the "easy" solution and the external machine would be little harder to set up. I do

I'm supporting a number of consumer devices (e.g. small NAS devices) in Debian. They typically don't export the serial console and don't have any other output devices. We perform the installation via SSH on such devices and start SSH automatically when the system boots so people can login. This works pretty well but sometimes a device stops to boot for no good reason. This is

On Centos 4.x 32 I want to create like a 64Mbyte ramdisk. Is there a problem putting 30k to 80k empty files on a ramdisk? Is there a simple howto on creating a ramdisk that anyone knows of off the top of there head? Matt

I''m trying to boot a PV guest using the "old method" of passing kernel= and ramdisk= and it appears to work fine with a "small" initrd but not with a "large" one. (Small is 4MB, large is 154MB.) I''m sure both of the initrd''s are properly gzip''ed etc. Unpacked, the large one approaches 400M. By doing some kernel startup debugging,

Hi All, I am using Centos4.0 and running Squid Reverse Proxy for image caching , i have configured RAMDISK of 265 MB for one cache folder in preproduction environment for testing now i have upgraded RAM upto 8GB, but when i change ramdisk_size parameter in grub.conf and rebooted the server when i tried to format and mount it doesn't work. Can anyone please help me how to increase RAMDISK

I'm still running CentOS 5 with Xen. We recently replaced a virtual host system board with an Intel S1400FP4, so the host went from a 4 core Xeon with 32G RAM to a 6 core Xeon with 48G RAM, max 96G. The drives are SSD. I was recently asked to move an InterBase server from Windows 7 to Windows Server. The database is 30G. I'm speculating that if I put the database on a 35G

I've built a domain member. It works pretty good with the exception that I want on-the-fly home directories being built. I'm not sure this is doable with a domain member as everything I've tried isn't even called - as far as I can tell. Using log level 3. If anyone can shed light on how to dynamically create home directories, that'd be great. anyway, here's my