similar to: VT-x enabled but xm dmesg does not show anything about vmx info

Hi I have a setup where I have an eth2 10GB interface setup a loop back between two dell 1950 servers. I have enabled VT in the bios. The eth0 interface is on a 1GB network. I am using an iscsi shared drive for the HVM image. I have followed the instruction provided in http://www.osrg.net/kemari/usage.html Now once everything is setup: After launching the HVM, I execute the following

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

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 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 :

I am having an issue with Megacli when adding or removing virtual disks. I will post a link to fpaste that has the issue shown. In brief whenever i add, or remove, a virtual disk via MegaCli the attempt succeeds and the adapter is configured but the OS remounts dm-0 in read only. dm-0 is my root lv. This issue does not happen if i boot into the default, non Xen, CentOS kernel. On stock

Hi, we have a couple of nodes based on CentOS 6 and Xen4CentOS. Unfortunately some of these nodes keep crashing frequenly. We use the latest versions: # uname -r 3.10.43-11.el6.centos.alt.x86_64 # xm info host : vserver20 release : 3.10.43-11.el6.centos.alt.x86_64 version : #1 SMP Mon Jun 16 14:22:02 UTC 2014 machine : x86_64

Hi everybody, I wanted to test the new hypervisor Xen 4.0.0 with the pvops kernel 2.6.31.13 version 64 bit No concerns regarding the compilation and installation, but after install a Windows 2003 server 32 bit I can''t install the drivers gplpv_2003x32_0.11.0.213.msi i had an error: "There is a problem with this Windows Installer package" see attachment Before, i had the

Hello, I am tryiong to set up a Dom0, right now my problem is creating the first guest. This is xen unstable tip ubuntu running jeremy kernel I have this: daniel@dani-ubuntu-xen:/usr/sbin$ sudo xm info [sudo] password for daniel: Error: Unable to connect to xend: No such file or directory. Is xend running? daniel@dani-ubuntu-xen:/usr/sbin$ Yet, xl reports this: daniel@dani-ubuntu-xen:/usr/sbin$

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, After saving and restoring a DomU (teste on the same server), doing a reboot to the newly restored domU will cause it to crash. This happens on PV and PVHVM domUs. I am using qemu upstream for the HVM guests, but I don''t really think it matters as long as PV guests behave the same. I want to confirm this if possible, before submitting a bug report and more details. I am using

Hello , I use Centos 5.4 , with the redhat version of xen . I need for some guest to change the hardware for the network . So in my xen config i add the model option in the vif line . When the guest boot , i had the right emulation , but after a reboot , the guest loose the configuration . Someone can confirm the bug in centos 5.5 ? Have someone a patch ? Extract of my config : builder

Hello, Fedora 19 running Xen 4.2.3 rpms, "xl list" after dom0 reboot: [root@localhost ~]# xl list Name ID Mem VCPUs State Time(s) (null) 0 1024 8 r----- 16.3 Why is dom0''s name "(null)" ? It seems also xenstore is quite empty: [root@localhost ~]# xenstore-ls tool =

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Package: xen-utils-4.0 Version: 4.0.1-5.2 After clean upgrade from Lenny I got xend highly use CPU resources causing domU don't being created - due to timeouts for vifs and vbds (mostly CPU Steal Time was increasing - no iowaits). Tried Xen boot options acpi=noirq|ht without success. Option acpi=off solved that issue, but performance of the server was horrible. The final workaround was to

Hi guys, i''ve read, a few threads ago, that suspend/resume should work on 3.4 kernels. Actually it doesn''t work for me, the system goes on suspend, keeping monitors on and power led blinking, but it never resumes, I always have to brutally shutdown it. CONFIG_XEN_ACPI_PROCESSOR is set. Same thing it always did with previouses kernels. It works flawlessy if I start the system

I have a couple sles11 servers running xen 3.4: # xm info host : xen03 release : 2.6.27.19-5-xen version : #1 SMP 2009-02-28 04:40:21 +0100 machine : x86_64 nr_cpus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2533 hw_caps :

Hi, i want to start domain with 2 cpus avail, but also have the opportunity to change on-the-fly the number of cpus to, for example, 4. in my domain.cfg i have: vcpus = 2 vcpu_avail = 7 The domain starts with 2 cpus, as expected, but rising the number does not work. It silently fails. Lowering the number works as expected. $ xm vcpu-set domain 3 $ xm list Name

hello, Env: Ubuntu Karmic Server 9.10 Xen 4.0 rc8 kernel 2.6.32.10 pv_ops Trying to import a working xen cfg file into domain management causes this crash. This ability is not so vital, but maybe someone can shed light on the missing packages/thing. tlviewer@ubsvr91:~$ sudo xm new /etc/xen/vm/karmic.py Unexpected error: <type ''exceptions.ImportError''> Please report to

After turning off hibernation this issue did not occur anymore in Squeeze. Now we've turned on hibernation again, ran the test to reproduce this issue and this issue occurred within 10 minutes on Squeeze with Hibernation on. Then we've upgraded our test environment from Squeeze to Wheezy and ran the test to reproduce this issue again on Wheezy with hibernation turned on. This test