similar to: vmx problem - no booting from cd

Hi. I am just trying to run unmodyfied guest OS on my Pentium D920. I found first problem - in my xen distribution (3.0.1) I cannot find vmxloader file. -- Rafał つた Zawadzki Release/Deploy Manager _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi. I''ve just upgrade my xen 3.0.1 to xen unstable. I noticed that there is no vmx driver here, only hvm. Actually I cannot start my VT domain: root@akira:/etc/xen# xm create bluszcz.hvm Using config file "bluszcz.hvm". Error: Device 768 (vbd) could not be connected. Backend device not found. root@akira:/etc/xen# my config: import os, re arch = os.uname()[4] if

Hi all I am trying to get VMX guests working on my new server here. The machine has a Pentium D 920 on an ASUS P5WD2-E motherboard. I''ve updated the BIOS to the latest 0401, which added the virtualization option. I am running a fresh installation of Gentoo (64-bit). When I try and run ''xm create'' on a vmx config file, I get the following error: Error: Error

Add GS base to the HVM VCPU context returned by xc_vcpu_getcontext() Signed-off-by: Aravindh Puthiyaparambil <aravindh@virtuata.com> diff -r e62ab14d44af -r babbb3e0f4d3 xen/arch/x86/domctl.c --- a/xen/arch/x86/domctl.c Fri Apr 20 11:36:02 2012 -0700 +++ b/xen/arch/x86/domctl.c Fri Apr 20 17:55:49 2012 -0700 @@ -1592,6 +1592,12 @@ void arch_get_info_guest(struct vcpu *v,

Hi! I was running lintian on our package... Among the copious errors and warnings there are: W: xen-utils: manpage-has-errors-from-man usr/share/man/man1/xm.1.gz 668: warning: can't find numbered character 160 Should we try to fix this, perhaps? E: xen-hypervisor-pae: unstripped-binary-or-object ./boot/xen_pae-syms-3.0.1 E: xen-hypervisor: unstripped-binary-or-object ./boot/xen-syms-3.0.1

Hi, I have buit Xen (32 bit) with PAE and can start multiple Paraguests with 4 gig memory, but cannot launch a single VM with more than 4 gb memory. I would like to launch 1 VM with 30GB or so memory. Are there any config paramters like kernel,/inittrd that need to be changed. I have the ramdisk set to the initrd I used to boot xen with PAE. Thanks - padma

This patch adds a check to see if v_end in setup_guest() wraps around to 0 and lets the builder exit gracefully when it does. Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> > -----Original Message----- > From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] > Sent: Thursday, June 01, 2006 6:14 AM > To: Puthiyaparambil, Aravindh > Cc:

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

destroy() is being called on exception in both start() and create(). It needs to be called only in create(). Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Sir/Madam, This is Aravindh,final year student of Anna University India.We are carrying on research in Cloud Computing and using Open Nebula toolkit for that;for which we need strong network connectivity. The problem i am facing is that i am not able to ping continuously to other nodes in the network. The connectivity is getting lost after 2-3 minutes. we have inspected the connectivity links ,

This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, calls to hvm_memory_event_cr3 and hvm_memory_event_cr4 were lost. These functions were originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in

I''ve checked in a patch that will hopefully fix ''acpi=off'' and ''acpi=ht'' modes for domain0. It''s been tested on just one machine so far, so it''d be good to get some wider feedback. :-) -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Fix the mistake for debug exception(#DB), overflow exception(#OF; generated by INTO) and int 3(#BP) instruction emulation. For INTn (CD ib), it should use type 4 (software interrupt). For INT3 (CC; NOT CD ib with ib=3) and INTO (CE; NOT CD ib with ib=4), it should use type 6 (software exception). For other exceptions (#DE, #DB, #BR, #UD, #NM, #TS, #NP, #SS, #GP, #PF, #MF, #AC, #MC, and #XM), it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello folks I played a lot with Xen last days, isnt it possible to access PCI devices which are hidden from dom0? I didnt get it - at least my windows domain didnt get it. Another question: Im using hvmloader but many pages also talk about the vmxloader, was it prior the hvmloader coz it doesnt exist anymore? cheers - -- Georg

Here is a patch for clustered xAPIC and Unisys ES7000 support in Xen. To turn the features on add CONFIG_X86_CLUSTERED_APIC and CONFIG_ES7000 defines to xen/include/asm-x86/config.h Signed off by Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

Yes, I saw that problem and removing the vif line or changing it to vif0 fixed it for me. Aravindh > -----Original Message----- > From: wei huang [mailto:huanwei@cse.ohio-state.edu] > Sent: Friday, November 04, 2005 12:14 PM > To: Puthiyaparambil, Aravindh > Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com > Subject: RE: [Xen-users] Error "Device 0

I am not able to build the latest x86_64 xen-unstable on SLES9 SP1 x86_64. Here is the build output. Am I doing anything wrong here? Aravindh gcc -DPIC -m64 -Wall -Werror -O3 -fno-strict-aliasing -I ../../tools/libxutil -I. -Wp,-MD,.xc_ptrace.opic.d -fPIC -c -o xc_ptrace.opic xc_ptrace.c In file included from /usr/include/asm/sigcontext.h:4, from

> > The patch I sent implements the minimum in the balloon driver and we are > currently building sles10 with my patch. > > K. Y I think I missed this patch when you sent it in. Could you please send it again so that I can take a look? Thanks, Aravindh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. issues: - No bocking issues. IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain Can bootup unmodified IA-32 WindowsXP SP1/SP2 in VMX domain Can bootup VMX & XenU with different memory size(VMX:128MB,256MB,512MB.XenU:256MB)