similar to: Hypervisor kernel confusion

Hi, I hope I''m right here. If not then please point me in the right direction. My problem in short: I have problems using (pinning, mmu_update) physical pages from 0x900000 to 0xB1000 usualy. I''m writing my own little amd64 64bit toy kernel (based on Mini-OS as starting point) for xen and I run into problems with the way the start of day sets up the physical pages. My kernel

I own an Athlon 64 X2 Dual Core Processor 5200+. I enabled SVM extensions on BIOS. I did a power cycle. xm dmesg shows me: (XEN) AMD SVM: ASIDs enabled (XEN) HVM: SVM enabled I run a 64 bit Xen kernel (OpenSuse 11). Xen version is 3.2.1_16881_04-8.6 I _can not_ run any x86_64 O.S on a HVM domU, because it appears something like this: "your cpu does not support long mode. use a 32bit

I''m trying to install RHEL 4 on an HVM (Core 2 Duo). However, when the RHEL installer tries to start the kernel, it complains that the CPU doesn''t support extended mode, and that I should use a 32-bit installer. However: hrm@willow:~$ sudo xm info | grep xen_caps xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 Is there some magic I

Hello list, I have two differents installation Xen Hypervisor on two identical physical server, on the same switch : The problem is on my new server (Xen 4.0.1 with pvops kernel 2.6.32.24), I have bad performance on bandwidth I have test with a files copy and "iperf". Result iperf average: Transfert Bandwidth XEN-A -> Windows

Hello, Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on

Hello everyone, i just updated from 4.2.1 to 4.2.2. If i try to fire up my win2k8 domU with a pci device attached, the dom0 machine hardcrashes. my system log (idrac) shows the following: CPU 2 has an internal error (IERR). A bus fatal error was detected on a component at bus 0 device 0 function 0. CPU 1 machine check detected. and plenty of other entries. The machine hardresets then. If i

Hello. We have a number of Xen 3.4.2. boxes which have constant iowaits at around 10% with spikes up to 100% when accessing data over NFS. We have been unable to nail down the issue. Any advice? System info: release : 2.6.18-194.3.1.el5xen version : #1 SMP Thu May 13 13:49:53 EDT 2010 machine : x86_64 nr_cpus : 16 nr_nodes

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

Hello. I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). Tried it with netBSD-5.1-RC3-1 i386 PAE & amd64, netBSD-5.0 and even 4, all with the same result. On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel

Hello Community, I successfully installed and run xen (xm list and xm info can output appropriately). However, while I was installing domU image by using virt-install -p at domU OS. I encountered an error information" Host does not support virtualization type ''xen'' ". I built xen from source. Some of my friends have the same issue, but if they use pre-build xen, the

List, here''s how I got 4.1 up on suse 11.4 There is a small bug with the xencommons init script preventing xenstored from starting. Add this repo for 4.1 RPM''s ------------- zypper ar http://download.opensuse.org/repositories/Virtualization/openSUSE_11.4 Virt zypper ref zypper in xen-4.1.0_01-106.1 Fix the xen inits  (observe the order here) ------------ chkconfig -s

Hello I have Debian Linux 2.6.32-5-xen-amd64 Xen 4.0.1, 2 SAS drives in RAID 1, 16GB ram. I have virtualized Windows 2003R2 32bit where you install the latest version 0.11.0.295 gplpv After reading and reading forums and post testing, I noticed that the hard disk performance drops significantly when I assign the windows domU 9GB ram. (below I leave the config files) If I run the

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hello, I am not sure if this is the correct Mailing list for the issue I have. I have a new system with 18GB of Physical memory on the system. I loaded CentOS 6.4. But when I boot into Dom0, I only see (xm info) 2GB of total memory? I set 1GB for Dom0, but I am not sure why the hypervisor does not see all the memory. [root at barbaro images]# xm info host :

Hi, During the install of the univention.de-signed GPLPV drivers (gplpv_Vista2008x64_signed_0.11.0.308.msi) on my Windows 7 guest, I get a BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL" in xenvbd.sys. Afterwards, Windows won''t start. I''m now trying to do a System Restore. I will try not installing the VBD driver afterwards and see if the others do work. Full BSOD:

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

hi all i am trying to boot from rhel5.1 x86_64 image. with the following configuration kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 3048 name = "rhel51" vcpus=1 cpus = "" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [ ''phy:/dev/cciss/c0d0p7,ioemu:hda,w'',