similar to: architecture-specific stuff in xend

Hi, For virtio block device, actually there is no a hard limit for max request size, and virtio_blk driver set -1 to blk_queue_max_hw_sectors(q, -1U);. But it doesn't work, because there is a default upper limitation BLK_DEF_MAX_SECTORS (1280 sectors). So this series want to add a new helper blk_queue_max_hw_sectors_no_limit to set a proper max reqeust size. Weiping Zhang (2): blk-setting:

Hi, For virtio block device, actually there is no a hard limit for max request size, and virtio_blk driver set -1 to blk_queue_max_hw_sectors(q, -1U);. But it doesn't work, because there is a default upper limitation BLK_DEF_MAX_SECTORS (1280 sectors). So this series want to add a new helper blk_queue_max_hw_sectors_no_limit to set a proper max reqeust size. Weiping Zhang (2): blk-setting:

The stub domain device model needs to trap the termination signal so as to actually destroy the stub domain. SIGKILL can''t be trapped, SIGTERM is caught by SDL and so may be unnoticed. SIGHUP can be trapped and is not caught by SDL (and by default causes a process termination without core). Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 2407a61c0d30

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

I pulled unstable yesterday and noticed xc_dom_create.py does not have a default value for cpu, so python complains Traceback (most recent call last): File "/usr/bin/xc_dom_create.py", line 408, in ? (current_id, current_port) = make_domain() File "/usr/bin/xc_dom_create.py", line 234, in make_domain id = xc.domain_create( mem_kb=mem_size*1024,

Hi, I''m trying to use a Gentoo whit Xem 4.0, but I try: xm create windows2008r2.hvm I get the error: Error: coercing to Unicode: need string or buffer, NoneType found. Does anybody knows how to solve that? windows2008r2.hvm: kernel = "hvmloader" builder=''hvm'' memory = 512 name = "Windows2008R2" vcpus=2 acpi=1 apic=1 disk = [

Package: xen-utils-4.0 Version: 4.0.1~rc6-1 Severity: important Tags: patch The patch is not necessary for HVM DomU guests. The Error: 'NoneType' object has no attribute 'rfind' was fixed by installing xen-qemu-dm-4.0. [1] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588888 -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''ve installed a Fedora Core 5 2054 and Xen 3.0.4.1 on a Intel 945 mainboard with xen3.0 user manual, everything seemed fine then. After I rebooted and chosed to enter into xen kernel , I find xend doesn''t run . when I try to run manually by input: /etc/init.d/xend start there some dot(indicating time maybe) appeared, and then nothing happened, the xend jun didn''t get

Hi Orazio, Is "NoneType object is unsubscriptable" the full and complete error message? I'd have expected some sort of accompanying backtrace, if not on the console then in /var/log/xen/* Is this issue by any chance fixed by installing the xen-qemu-dm-4.0 package? Lastly, does this happen with the packages from Wheezy? Thanks, Ian.

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.

Hi, I have been trying to get Xen 3.1 running on Fedora 7 since yesterday and no luck. At the beginning I thought it was a problem with teh installation of Fedora 7 so I reinstalled it. Still, I have the same problem. I have never had this problem with Xen (FC5,FC6). The xend.log (below) includes a line "VmError: Device 0 (vif) could not be connected. Hotplug scripts not working."

I''ve put together two patches. The first introduces a new dom0_op, set_max_vcpus, which with an associated variable and a check in the VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP, VCPUOP_create, which handles all of the vcpu creation tasks and leaves initialization and unpausing to VCPUOP_initialize. The separation allows for build-time allocation of vcpus which

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

> [6] ctivating swap partitions: swapon: /dev/hda7: No such device or address > [6] [FAILED] > [6] ioctl 80041272 not supported by xl_block > [6] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.24-xeno/modules.dep for writing > [6] [FAILED] > [6] Checking filesystems > [6] Couldn''t find matching filesystem: LABEL=/policy Edit your

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

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

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

If a volume is not an exact multiple of 512 bytes, qemu-img will report its size rounded down to a 512 byte boundary. However, when copying, the file is still read until EOF, which will return more data than was expected. This change prevents that causing a failure in itself. The situation is still not resolved, however, as there are still situations where this will cause a failure. For example,