similar to: unable to create the Unpriviledge domain

Hi   Below is what i get while creating a guest domain, please someone help me.   [root@xenserver xen]# uname -a Linux xenserver 2.6.21-2950.fc8xen #1 SMP Tue Oct 23 12:24:34 EDT 2007 i686 i686 i386 GNU/Linux [root@xenserver xen]# [root@xenserver xen]# xm list Name                                      ID   Mem VCPUs      State   Time(s) Domain-0                                   0   930     2    

I''m starting to go nuts I have tried this several ways and can''t get my doamin to boot up, I am using Fedora 5 as dom0 and trying to boot up ubuntu 5.10. I am using a file but my dom0 is using lvm and I am not in the ubuntu installation, here are my output of my domain file and error......I have edited the fstab on my ubuntu installation to match the domain file, any help would

I have Xen3 installed on Ubuntu 6.10 server, $ sudo xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 250 8 r----- 748.2 but whenever i try to create a new domain with anything listed for kernel at all, i get this: $ sudo xm create domu1 Using config file "domu1". Xend has probably crashed!

Hi, I wanted to ask it on elli_dbergs''s thread ''problem with xm create'', but it seems that my message was never gonna be published (waited for 24 hours til i figured it was taking way too much time). So i''m working with Xen unstable, installed dom0 over Ubuntu 8.10, no problem so far apparently, reboot on Xen, then I go to /etc/xen to get some example config

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

After a yum update my two guests that had been shutdown do not start any more. I have two other guests running that seem to work okay but I am now afraid that they won't come up again if I restart them. I am running CentOS5 with kernel 2.6.18-8.1.8.el5xen. Previously I had following xen versions installed: Oct 14 23:45:10 Updated: xen-libs.i386 3.0.3-25.0.4.el5 Oct 14 23:46:05 Updated:

Hi, I am trying out Xen for the first time and I am having a few problems with getting it working. The computer is a quad core Intel Xeon with VT enabled, 8gb of RAM and 2 x 15,000rpm SAS drives in RAID1. I have installed CentOS 5 64bit and installed Xen 3.3.0 via yum. I have successfully booted in to dom0. Here is my grub.conf on dom0: > # grub.conf generated by anaconda > # > #

Hi again! More TPM + XEN stuff. have look at the following: ================= "xl list -l centos7.0" ============== [ { "domid": 31, "config": { "c_info": { "type": "hvm", "name": "centos7.0", "uuid":

I installed xen on top of Cent OS 5.3 64bit OS with gitco rpm sources. Everything works fine except that I can''t run 64bit pv guest with virsh command. With xm commands I can load the same guest. 32bit pv guest, 32 bit and 64bit hvm works fine with both virsh and xm command. Has anyon have any idea? any help will be largely appreciated. **This is dumpxml for 64bit configuration* **

I finally fixed it. The issue seems to be with the tpm-tis/cpu backend (wonder why it shows up with a different error) For the sake of community, I am attaching the new xml file so that you can do forensics on what changed (I prettymuch did a virt-install --import --print-xml to redo the config keeping everything intact) I found another issue If I switch the suspend-to-disk

Hi, I am using Centos 5.4 x86_64 with kernel 2.6.18-164.11.1.el5xen. I've installed a Centos 5.4 (64 bit too) DomU (paravirtualized), process was apparently with no problems, but DomU refuses to start, this the error: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File

Hi. I'm testing a centos 5.4 xen PV guest on top of a centos 5.4 host. for some reason, the disk performance from the guest is awful. when I do an import , the io is fine for a while then climbs to 100% and stays there most of the time. at first I tougth it was because I was using file-backed disks, so deleted those and changed to LVM, but the situation did't improve. Here's an

I am working on S5000VSA Intel Server Board with the following cpu spec. XEN-PEER-RHEL5 $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz stepping : 7 cpu MHz : 2327.512 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0

All, I have been trying to get PCI pass through working for sometime and need to know if I have a hardware problem (does my hardware support PCI pass through) or if I am doing something in correct. 1) My BIOS does allow me to enable VT support 2) *cat /proc/cpuinfo* processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU

virt-p2v was able to convert my centOS 5.2 physical machine to xen virtual machine and it runs great. Now, I am working on to convert this full virt machine to para virt . Under my domU i have installed kernel-xen (since it is needed ) , and edited my grub menu to use the installed kernel. My grub menu file in domU looks like: ---- kernel /vmlinuz-2.6.18-92.1.17.el5xen ro

Hello All, We would appreciate your advice on the following issue. We have created a full virtualized Xen guest that its disk is an image file of 4GB. We want to use this image file as a template for creating Xen guests which their disk will be an LVM device. The disk image file is of type: file /var/lib/xen/images/rhel52.img /var/lib/xen/images/rhel52.img: x86 boot sector;

my install config file is: ******************************** ostype="sles10" name="suse10" memory=256 vcpus=1 on_crash="destroy" on_poweroff="destroy" on_reboot="destroy" localtime=0 builder="linux" kernel = "/boot/vmlinuz-2.6.18-92.el5xen" ramdisk = "/boot/initrd-2.6.18-92.el5xen-no-scsi.img" extra="TERM=xterm

Hi, In continuation with my previous mail, I changed the vif entry in the config file as, vif = ["mac=00:16:3e:43:b7:99,bridge=xenbr0"] and I was able to boot into the guest, but I was not able to ping any system from the guest. I have attached the snapshot of the boot error messages. Thank you Regards Ananth -----Original Message----- From: CB, Anantha Padmanabhan Sent: Wednesday,

Hi all. I am comming back to the virtualization... Days ago I installed Centos 5.5 and I want to tray xen Full virtualization.. so I create and installed my Full virtual machine. I use virt-manager... the VM run pretty well... But... If I connect remotly using ssh to domain0 and then use "xm console ID" I get nothing.... and I have to ctrl + ].... (this happen too if I am locally in

I''ve done something apparently, but can''t for the life of me figure out what. Perhaps someone can help: I have an LVM based domU which has been working without problem for weeks. I made some final changes to it last week, shut it down and ran the following to create a backup image: dd if=/dev/VolGroup00/wspd of=mail2.img bs=1M At least this is the only thing I can