similar to: Which ring the dom0 run at?

I am not clear with the working of hypervisor xen. How does an instruction executed by kernel in Ring0 of DomU gets mapped or executed by hypervisor and then is excuted in Dom0. Is this thing some where on the wiki page? -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I am not clear with the working of hypervisor xen. How does an instruction executed by kernel in Ring0 of DomU gets mapped or executed by hypervisor and then is excuted in Dom0. Is this thing some where on the wiki page? -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I have an issue with my XEN servers, in that when I do a yum upgrade, it upgrades the kernels, and then updates the grub.conf file to boot with the normal Linux kernel, and not the XEN kernel - and I tend to forget to update the grub.conf, until I reboot and see XEN isn't running. So, is it safe to remove the normal kernel & kernel-development, and only run the XEN kernel? This is

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: important The amd64 Dom0 crashes in early boot-stage. For debugging purpose I logged Kernel-Dump with minicom over Serial Console: System is: Dell Poweredge R710 2x Intel XEON X5650 96GB RAM Perc H200 SAS Controller 3x SAS-Drive I see a possible conjunction with Bug #600241 but acpi=off doesn't solve this problem. Regards,

Hey everyone, I was hoping you all could help me with a problem. I''m trying to run the xen kernel 2.6.18-164.11.1.el5xen on CentOS 5.4 X86_64. The dom0 machine boots the 2.6.18-164.11.1.el5 kernel without an issue, so I can get into it and get any information you might need, however the issue I''m having is that once I select the xen option from my grub menu, it will go into the

Hi, can anyone provide any pointers as to how to avoid this issue? A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm dom0: haggis:~$ uname -a SunOS haggis 5.11 snv_111 i86pc i386 i86xpv Name: SUNWxvm Summary: Hypervisor Header Files Category: System/Virtualization State: Installed

I started a new thread because this not a pv-ops dom0 anymore. I''m running Andrew Lyon''s 2.6.31-4 patches for a non-pv-ops kernel. Got it again, after issuing "poweroff" from the domU. (XEN) (XEN) NMI - MEMORY ERROR (XEN) ----[ Xen-3.5-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48011f55c>] remove_from_heap+0x8f/0xd0

I was giving a try to Debian Xen packages (it looks very promising by the way ; I just happen to love the ? new ? grub which handles xen images, for instance!) ; I have a box which boots correctly with xen-hypervisor-3.0-i386_3.0.2+hg9697-2 and a 2.6.16 dom0 kernel, but crashes when trying to boot linux-image-2.6.17-2-xen-686_2.6.17-7 The result is the same on two boxen (my Pentium M laptop and a

Hello, I have installed rpm version of xen 3.4.3+ libvirt 0.7.0-6 on my server with Centos 5.4 (kernel 2.6.18-238.12.1.el5xen) When I run reboot a domU (para virtualized Linux) by command "virsh reboot [vm]", sometimes domU cannot be rebooted but sometimes can, pattern is random. Also sometimes when domU reboots by "virsh reboot [vm]" , my ssh connection to dom0

Dear experts, to monitor performance of applications on our private clouds I decided to use Xenoprof. For that, I installed patched OProfile 0.9.5 on Dom0 and DomU. Then, I started the daemon on Dom0 opcontrol --start-daemon --active-domains=1 --separate=library --event=LLC_MISSES:90000 and received the following error: /usr/local/bin/opcontrol: line 1171: echo write error: invalid

http://www.kerneltraffic.org/kernel-traffic/kt20031201_243.html --- Relevant section --- Nuno Silva mentioned: The good people at Cambridge made a (very nice) VMM that exploits ring0/1/3 to let one machine run various kernels independently (the kernels need to be ported to the xen arch). Xen itself executes in ring0 and the "guest" operating systems execute in ring1.

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from Debian 7 to Debian 8, the dom0 becomes unresponsive via ssh after an hour or so, although the domUs still remain accessible. Initially we thought it may be a disk space issue on / or /boot so action was taken to increase those

************************ Installation profile ************************ [root@ServerRHL51 vm]# cat snv85.install name = "Solaris85pvm" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-85" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk =

Hello, With kernel 2.6.32.21 (from Jeremy) : - System size : 3945 kB, gzip compressed kernel size 4051553 Bytes -> works well - System size : 3968 kB, gzip compressed kernel size 4074976 Bytes -> fault (see below) I''ve attached the 2 configurations files and xen boot error. __ __ _ _ ___ _ \ \/ /___ _ __ | || | / _ \ / | \ // _ \

retitle Traffic forwarding issue between Xen domU/dom0 thanks This week again this bug occurred again so we are trying to create some kind of reproduce algorithm. First we've created two virtual machines named koekiemonster.bofh.hq.mendix.net and netappsim.bofh.hq.mendix.net. We've added 29 vifs to koekiemonster.bofh.hq.mendix.net. During this tests we've always had a ping

As far as I work out the version of the Dom0 linux kernel has to be 2.6.18. This is causing me a lot of problem, because the driver support in 2.6.18 is slowly falling behind, and I finding that more modern hardware isn''t supported by the 2.6.18 drivers. Is it possible to use a more recent version of the kernel for Dom0, or am I stuck with 2.6.18? Is there another way I can use more

Hi. I''m using Xen 3 on Debian Testing. Until the last week I was using the kernel 2.6.18-3-xen-686 from the Debian repository and all was working well. When I upgraded the kernel to 2.6.18-4-xen-686, my dom0 system cannot startup and I get this error during the kernel loading: PANIC on CPU0: Could not setup DOM0 guest OS Reboot in five seconds... After five seconds the dom0 reboots

Hi, This is the specifications dom0 -------- [root@server ]# uname -r 2.6.18-238.12.1.el5xen [root@server ]# uname -m x86_64 domu -------- root@test:~# uname -r 2.6.18-238.12.1.el5xen root@test:~# uname -m x86_64 My issue is like dom0 clock is moving too fast. Interestingly, it is affecting ubuntu & debian domU. centos domU is just working fine. Here is how I could recreate the problem.

Hi Folks, Can anybody advise me which if any 3D (GLX) graphics card works well in 3D mode under a Xen dom0 kernel? My current hardware [Nvidia GEForce 7300LE] requires an Nvidia-supplied driver for GLX that appears to be incompatible with a xen-compatible linux kernel (at least 2.6.18-xen built from the xen-3.1.0 source tarball). My requirements are: - Must be 3D/GLX compatible so I can run

Hey, I was looking for step by step installation for RHEL5 as dom0 and RHEL5 as domU, but could not find it.I put some instructions, hope it will save some time for somebody. If you will find some errors please fix them :) I assume that you already have rhel 5 up and running (webserver as well).I will install guest system in paravirtualized mode (mine processor does not support full