similar to: [PATCH] Fix e820 mapping limit

Displaying 20 results from an estimated 2000 matches similar to: "[PATCH] Fix e820 mapping limit"

2007 Sep 06
4
Ghost domain ???
Hi, I''m running Xen 3.0.4 with suse (kernel 2.6.16.46-0.12-xen). I''ve a problem with a "ghost" (paravirt) domain that appear in the output of xm list. As an example: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 4 r----- 29.0 vm-xyz
2010 May 19
0
Hi - Regarding xend - xm create Error
Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',
2010 Oct 06
1
unknown bootloader
Hullo Everybody ; I am failing to start my new VM and it tells me unkown bootloader . Below are my parameters and output . Could somebody be having an idea of putting right this problem? [root@virtualintranet /]# xe vm-param-list uuid=70645ba3-bcbc-683b-099e-ed197301fcc2 uuid ( RO) : 70645ba3-bcbc-683b-099e-ed197301fcc2 name-label ( RW): PVG1
2011 Feb 08
1
[PATCH][git-pull] MEMDISK: Process "mem=" parameter and apply to e820 ranges
git://git.zytor.com/users/genec/syslinux.git Branch memdisk-maxmem-for-hpa The goal of the changes was to process a "mem=" parameter (ie "mem=128M" or "mem=134217728"; same value) and alter the memory map that MEMDISK returns in INT15h AXe820h by changing any type 1 (available) ranges above the "mem=" value to type 2 (reserved) and splitting a type 1 that
2010 Jun 24
1
VGA passthrough - guest shows blank screen on startup
Greetings, I''m attempting to do gfx_passthru with the primary graphics adapter (03:00.0), passing it to a guest. I can unbind it from the host but when I fire up the guest OS my monitor loses signal from the graphics card and that''s that. The GFX card is dual DVI, I''ve tried both slots. Host is Linux 2.6.32.14-1.2.105.xendom0.fc12.x86_64, Guest is Windows 7. PC is an
2009 Jul 28
0
Xen 3.2 @ Debian 5.0 / Debian 4.0 DomU crashes daily
Hello, on my xen host, Debian 5.0 I have few domU''s running, most of them are Lenny''s, a couple is running at Etch (Debian 4.0). All domU''s are running stable except of one (Etch / Debian 4.0). This one crashes almost daily and I wasn''t able figure out the reason why. Inside the domU there is nothing installed except of base system and Zimbra ZCS 5.0 and its
2010 Oct 24
1
Bug#601271: xen-utils-4.0: domain fails to reboot (AttributeError: 'NoneType' object has no attribute 'getBitSize')
Package: xen-utils-4.0 Version: 4.0.1-1 Severity: important I'm running a 32-bit Ubuntu 10.04 domU on a 32-bit Debian squeeze dom0. xm create works fine, but whenever I try to reboot this domU it fails with the following traceback in xend.log: [2010-10-23 17:48:58 1679] INFO (XendDomainInfo:2088) Domain has shutdown: name= onini id=2 reason=reboot. [2010-10-23 17:48:58 1679] DEBUG
2008 Mar 25
1
Xen3.1 Etch-backports | VE already running
Hi guys, actually i use the following packages from etch-backports: =========================== ii linux-headers-2.6.18-6-xen-vserver 2.6.18.dfsg.1-18etch1 Common header files for Linux 2.6.18 ii linux-headers-2.6.18-6-xen-vserver-amd64 2.6.18.dfsg.1-18etch1 Header files for Linux 2.6.18 on AMD64 ii linux-image-2.6.18-6-xen-vserver-amd64
2010 Apr 28
4
XCP - VM creation from template and netinst
Hi all, i still have problem.. Some time I am able to install and other not. I tried this on different machine either in a pool and either in a single installation of XCP. These are the steps I use to create a VM: # set disk size xe template-param-set uuid=9d8c3be5-f16b-7446-b978-e23551d8a77e other-config:disks="<provision><disk device=\"0\"
2008 Aug 09
4
Upgrade 3.0.3 to 3.2.1
Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but
2013 Jul 28
4
Fedora 19 installation with virt-install
Hello, I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the following versions... ii libc6-xen:i386 2.13-38 i386 Embedded GNU C Library: Shared libraries [Xen version] ii libxen-4.1 4.1.4-3+deb7u1 i386 Public libs for Xen ii libxenstore3.0 4.1.4-3+deb7u1 i386
2011 Oct 29
0
Bug#644100: Boot loader didn't return any data! if reboot domU with disk DRBD
Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk
2009 May 07
1
[PATCH 5/5] xen: reserve Xen start_info rather than e820 reserving
Use reserve_early rather than e820 reservations for Xen start info and mfn->pfn table, so that the memory use is a bit more self-documenting. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> --- arch/x86/xen/setup.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c index 15c6c68..ad0047f 100644
2006 Jul 30
1
[PATCH] move e820 ACPI entries into RAM
move e820 ACPI entries into RAM. ACPI RAM maybe used as RAM after ACPI data is parsed, but current e820 entries don''t comply to this. Signed-off-by: Xin Li <xin.b.li@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 May 25
1
pxelinux/mboot confused about e820 memory maps on HP Proliant BIOS's
All, When attempting to pxeboot the latest Xen3.0 hypervisor/kernel it was failing with the following error: ------ \ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ / \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |____(_)___/ \__,_|_|
2002 Dec 20
0
[Fwd: [PATCH] zero-size E820 memory (kernel start-up failure)]
The following was just sent to me... since some people have experienced these kinds of problems and asked about them I thought I'd forward it. Please leave the discussion on the linux-kernel mailing list, however. -hpa -------------- next part -------------- An embedded message was scrubbed... From: achen at t-online.de (Alexander Achenbach) Subject: [PATCH] zero-size E820 memory (kernel
2006 Mar 11
5
mboot.c32, weird e820 map on HP blade machine, possible memory corruption
I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at
2011 Apr 07
3
Re: xen: do not create the extra e820 region at an addr lower than 4G
I can''t find this patch on any mailing list to respond to so starting a new thread. In case I''ve not missed it but instead it really wasn''t posted -- in the future can we try and ensure that any patches have been posted at least once. Same for the pull request, it should go to a list. BTW the version in Konrad''s tree is Stefano''s 2.6.39-rc1-fixes
2007 Sep 26
0
''memory_dynamic_max must be greater than zero'' when using xend.domain.create via xml-rpc
After receiving no answer on xen-users, I post my question here: --- When trying to create domains with "xend.domain.create" called via xml-rpc, xend always returns "memory_dynamic_max must be greater than zero". xend.log says [2007-09-23 23:35:53 30064] DEBUG (__init__:1072) XendDomainInfo.create(www2.cfg) but the domain is never created. Issuing "xm create
2012 May 15
3
Missing memory when using maxmem
I am trying to allow domains'' memory allocation to be altered by using both the "memory" and "maxmem" options in my config files (i.e. set maxmem to some large value to allow the domain to be resized up to that amount, and memory to set the initial allocation). However I appear to lose potentially quite a large chunk of memory as I use a larger "maxmem"