similar to: GP exception on vmxon

Hi guys, let me shortly introduce myself. I''m a student and recently work on my bachelor thesis. My goal is to write a little hypervisor. I''m not quite sure if this is the right mailing list, but i guess you''ll gonna tell me. i have two quick questions: 1. before i can use the vmxon instruction i do have to set vmxe flag in cr4 register. but what if some hypervisor is

hvm: clear vmxe if vmxoff The current Xen code keeps X86_CR4_VMXE set even if VMXON has not been executed. The stop_vmx() code assumes that it is possible to call VMXOFF if X86_CR4_VMXE is set which is not always true. Calling VMXOFF without VMXON results in an illegal opcode trap, and to avoid this condition this patch makes sure that X86_CR4_VMXE is only set when VMXON has been called.

Hi, I have a Dell opt 755 machine and installed Xen 3.3.1. The CPU is core 2 due E6550, which as the vmx flag. However, when I reboot the machine to xen 3.3.1. I can not find vmx in the /proc/cpuinfo. But vms appears in the kernel 2.6.29 (not xen kernel). Can anyone help on how to enable vt in this machine? Thanks. Steven _______________________________________________ Xen-users mailing list

Dear mailing list I just installed Suse 10.1 with Xen support on a computer with an dualcore Intel processor. Is ther any documantation around on how to configure the xen, that it supports the intels vt technologiy. Thanks for your help Damian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Am considering a new laptop, and I wonder if anyone here can share their Xen experiences with the newest Core 2 Duo CPUs, ref http://www.intel.com/products/processor/core2duo/specifications.htm The list at http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors doesn''t include any Core 2 Duos. Does that mean that people have had problems, or is the wiki just not up to date? I gather

I am trying to get QNX working with Xen. I''ve going about it in a similar way as installing windows with Xen, but when I start the guest up to install the OS it hangs on the line: ''Hit Esc for .altboot.......'' If anyone has managed to get this working, or has any ideas/advice for me here it would be greatly appreciated! Bryan

Hello group, I recently purchased an HP m7360n computer which has an Intel Pentium D 920 processor in it. Unfortunately there is no BIOS option to enable or disable VT. The board it sits on uses the Intel 945P chipset. If I am in linux and do a ''cat /proc/cpuinfo'' I get this: [root@localhost ia32]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family

************************ 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 =

I''m using FC5 with its Xen 3.0.2-2 package and 2.6.16-1.2118_FC5xen0 kernel. I''ve got a Pentium 9xx chip with virtualization enabled in the BIOS; it appears to be VT-enabled, since xm dmesg includes "(XEN) VMXON is done". I base my config file on example.hvm and on previous emails to this list. Unfortunately, I don''t get very far. xm create winxp.conf

hvm_enable() copies the table contents rather than storing the pointer, so there''s no need to keep these tables post-boot. Also constify the return values of the per-vendor initialization functions, making clear that once the per-vendor initialization is complete, the vendor specific tables won''t get modified anymore. Finally, in hvm_enable(), use the returned pointer for all

Hello, I''m trying to use the VT technology on box but when I start Xen VMX is disabled by Feature Control MSR as shown in the following message: Xen version 3.0.2-3 (guill@frec.bull.fr) (gcc version 3.3.5 (Debian 1:3.3.5-13)) Wed May 31 16:07:00 CEST 2006 Latest ChangeSet: Tue May 30 18:14:05 2006 +0100 9697:18e8e613deb9 ... (XEN) Initializing CPU#0 (XEN) Detected 3391.682 MHz

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''ve installed Xen kernel for dom0 on a CentOS 4.4 but when i reboot the kernel says: _/\_\___|_| |_| |____(_)___(_)____(_)___/ http://www.cl.cam.ac.uk/netos/xenmdev = 59.12 University of Cambridge Computer Laboratory6 Sep 26 01:52 qemu-dm.6463.log Xen version 3.0.3.0 (root@uk.xensource.com) (gcc version 3.4.6 20060404 (Red Hastart qemu- -rw-r--r-- 1 root root t 3.4.6-3)) Mon Oct

Hi, everyone, I installed the Xen3.1.0 based on Fedora8 and enter the Dom0 successfully. The kernel of dom0 is linux-2.6.18-xen0. But the Xorg could not start in the Dom0. When I use the "startx" command to start the X server, the error information is following: ......... (==) Using config file: "etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in

From: Yang Zhang <yang.z.zhang@Intel.com> The follwoing patches are adding the Posted Interrupt supporting to Xen: Posted Interrupt allows vAPIC interrupts to inject into guest directly without any vmexit. - When delivering a interrupt to guest, if target vcpu is running, update Posted-interrupt requests bitmap and send a notification event to the vcpu. Then the vcpu will handle this

I tried latest xen and linux-xen staging tree, but failed to run HVM domain on x86-64 environment. domU creation is OK. However the weird thing is not HVM domain itself. Instead system crashed on dom0 context. I saw once with some stack dump that xen''s page fault handler is executed on a dom0''s stack which then causes nested page fault due to unable to fetch vcpu pointer.

Hi, im using a fedora core 8 domU and fedora core 8 as my dom0 on xen3.1.0-13, my config file reads: kernel = "/boot/vmlinuz-2.6.21-2950.fc8xen" ramdisk="/boot/initrd-2.6.21-2950.fc8xen-no-scsi.img" memory = 428 name = "fedora1.fc8" vif = [ ''mac=00:16:3e:00:00:03,ip=192.168.2.105'' ] dhcp = "off" netmask = "255.255.255.0" gateway

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

Hi Xen Users, I would like to boot into a knoppix iso on an existing domU. In my config file i have: disk = [ "file:/var/lib/xen/images/machine-10.img,hda,w","file:/mnt/knoppix.iso, hdb:cdrom,hdb,r" ] Can''t seem to boot it though. Do I have to go into the VMs BIOS to tell it to boot it? Cheers CHris _______________________________________________ Xen-users