similar to: help to understand is_running _on_xen ?

problem in starting xend I tried to install xen, but got some errors when starting xend. as I logged in and tried to start xend (/etc/init.d/xend start). I just got six-seven dot (.) printed out, then it stops. I looked more closely and found that xend could not start. then I looked at /var/log/xend-debug.log. here is the last few lines: ^^^    Exception starting Xend: no element found:

about VIRQ & PIRQ what is VIRQ  ?How VIRQ is different from PIRQ ?How VIRQ & PIRQ are related each other ? DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any

During context switch is_running is set for the next vcpu before the gic state is actually saved. This leads to possible nasty races when interrupts need to be injected after is_running is set to the next vcpu but before the currently running gic state has been saved from the previous vcpu. Use current instead of is_running to check which one is the currently running vcpu: set_current is called

Hi linux/ia64 developers. Few days before Eddie posted the mail for Linux/IA64 paravirtualization. But only a few responded partially because there was no reviewable patches. Here is the patches for xen/ia64 Linux paravirtualization. The goal is to merge IA64 xen Linux paravirtualization for both domU and dom0 eventually. However the first step is to merge domU portion. As you can see from the

Hi. I has xen virtual machine in paravirtualisation. Host and guest sysstems are CentOS. When I use top in guest machine I see, that system use 20% resourses. But in host machine I see, that machine use 50% resourses. In config machine has 5 processors, and has cpu_cap 352. Processor is 2266MHz. Therefor for statistic in guest machine it use ~ 2266 MHz(1 processor), and for Xen hypervisor - 4000

Hi. Thank you for comments on asm code paravirtualization. Its direction is getting clear. Although it hasn't been finished yet, I'd like to start discussion on ia64 intrinsics paravirtualization. This patch set is just for discussion so that it is a subset of xen Linux/ia64 domU paravirtualization, not self complete. You can get the full patched tree by typing git clone

Hi. Thank you for comments on asm code paravirtualization. Its direction is getting clear. Although it hasn't been finished yet, I'd like to start discussion on ia64 intrinsics paravirtualization. This patch set is just for discussion so that it is a subset of xen Linux/ia64 domU paravirtualization, not self complete. You can get the full patched tree by typing git clone

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1322233890 0 # Node ID b4c07fbe3557ae501fc2d8a21b41f1b1cd5198cb # Parent 31e71820ce93b72b0223882f6c2e1f461920bda9 docs: xlexample.hvm: mention the viridian setting. Turning this on for Windows guests is recommended. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 31e71820ce93 -r b4c07fbe3557

Hi, Im trying to compile kernel 3.0.4 inside Centos 5 DomU The steps I do are Make bzImage Make modules Make modules_install Depmod -a mkinitrd /boot/initrd.img-3.0.4 3.0.4 but them im getting this -bash-3.2# mkinitrd /boot/initrd.img-3.0.4 3.0.4 ls: /etc/modprobe.d/*.conf: No such file or directory No module ehci-hcd found for kernel 3.0.4, aborting. If I exclude the

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

I''ve just uneventfully installed SLES10 as an HVM DomU (after finding out, the hard way, that OpenSUSE 10.3 won''t install on Intel VT). This almost went without a hitch, but I''ve been banging my head against a brick wall for a few hours trying to get VNC working. I can get a remote desktop, but a few seconds after I log in to the remote desktop, the screen goes

Hi, Here is a patch (on top of the paravirt patch queue) which makes xen guests use the hvc_console.c infrastructure for the console, thereby greatly reducing the amount console code. xvc0 is gone too, hvc0 is used instead. cheers, Gerd -- Gerd Hoffmann <kraxel@suse.de>

Hi, Here is a patch (on top of the paravirt patch queue) which makes xen guests use the hvc_console.c infrastructure for the console, thereby greatly reducing the amount console code. xvc0 is gone too, hvc0 is used instead. cheers, Gerd -- Gerd Hoffmann <kraxel@suse.de>

Hi, Here is a patch (on top of the paravirt patch queue) which makes xen guests use the hvc_console.c infrastructure for the console, thereby greatly reducing the amount console code. xvc0 is gone too, hvc0 is used instead. cheers, Gerd -- Gerd Hoffmann <kraxel@suse.de>

Hi, I am currently working on hypercalls from HVM guests. I started with a set of Intel patches posted to xen-devel last September. I currently have code running for both 32-bit and 64-bit HVM guests running on a 64-bit hypervisor. I am curious why none of the original patches were accepted, and what I might need to do to make them acceptable. Is other work being done in this area that

Hi, Host: CentOS 5.5 Guest: Ubuntu maverick I am having a horrid time trying to create a guest on my xen machine. I have tried several method. The method that I have had the most success with is `xm create`. The problem I have is that once the I have run: xm create -c myconfig.cfg install=true install-mirror=http://mirror.bytemark.co.uk/ubuntu/ install-suite=maverick and go all the way

Hi, thanks for great job do with xen .deb, we have a problem on xen 3.4.2 (certainly not just us) how is impossibile do hvm domu work because there isn't qemu-dm, i read a few months ago discussion of this but also now there is the problem, will be resolved soon? it possibile rebuild the current package with the simple addition of qemu? thanks in advance for any reply -------------- next

(The list appears to have eaten my previous attempt to send this. Apologies if you receive multiple copies.) The attached patches allow you to use paravirtualised network and block interfaces from fully virtualised domains, based on Intel''s patches from a few months ago. These are significantly faster than the equivalent ioemu devices, sometimes by more than an order of magnitude.

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1320922479 0 # Node ID bc79b560aafa1e4dc42af00e6a326dc651b5636a # Parent 460b507e15f864dd6712f5040e36538d6e076ae4 libxl: use named options for tsc_mode. It seems that this knob is expoerted from the hypervisor as a raw integer (no symbolic names) documented in xen/include/asm-x86. Propagating that all the way to the