similar to: Problems accessing to the image

Ok So I''ve been able to successfully create a CentOS5 virt-install on xen using LVM created partitions. But have many problems trying to install 4.4 (It does not work with virt-install hence you have to try another method). I Created a name, name-tmp, name-swap, name-root paritions. I did mke2fs and mkswap no problem everything is good. I went on further to mount the name-tmp and

I am having an issue getting a DomU to boot properly. There is never any indication of a stop error or kernel panic, it simply hangs after "Starting crond [ OK ]" and never continues. I''ve included my mkinitrd and output from xm create... please help! ##### XENBUS errors ##### XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050

Hello, i will describe my approach 1) I have downloaded Centos5-64bit xen image from jailtime.org 2) I have created own swap image with 512MB file size 3) I have used same as dom0 kernel 2.6.18-53.1.19.el5xen 4) I have mounted my image file and copied /lib/modules/2.6.18-53.1.19.el5xen 5) I have created custom ramdisk for domU with mkinitrd --with=xennet --preload=xenblk

I followed the book called "Professional Xen Virtualization" written by William von Hagen,and published by Wiley Publishing,Inc. Here are some configuration files: #cat /xen/ubuntu/ubuntu.xen3.cfg kernel = "/boot/vmlinuz-2.6.18-128.1.16.el5xen" ramdisk = "/boot/initrd-2.6.18-128.1.16.el5xen-no-scsi.img" memory = "512" name = "Ubuntu804" vif =

Thanks you all guys. I am able to create the RHEL5 PVM on RHEL5 host successfully. Only thing that i need to add is /mnt/etc/fstab in inintrd command and preload to both the fronthend drivers. As blow. # mount /home/disk /mnt # mkinirtd /boot//boot/initrd-2.6.18-8.el5xenU.img 2.6.18-8.el5xen --fstab /mnt/ etc/fstab --with xenblk --with xennet --preload xenblk --preload xennet Thanks a lot,

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

Good morning, I need to use pciback.hide to hide a pci card because I want to pci passthrough that card to a domU. My hardware neither supports Intel-Vt-d nor AMD's IOMMU. Unfortunately this doesn't seem to work in Centos 54 anymore. I guess it doesn't work because it is not compiled into the kernel, but as a module. I got the following error in dmesg and the pci device is still

Hi, I just noticed one of my XEN domU''s rebooting by itself. No one was logged in and it wasn''t under load, but just rebooted. It rebooted again about an hour or 2 later Is there any way to see why to see what caused this, either from domU, or dom0 ? /var/log/messages has no indicative reason, but here it is: Aug 1 18:47:06 venus shutdown[13758]: shutting down for system

more /etc/xen/scalix2 kernel="/boot/vmlinuz-2.6.18-8.1.6.el5xen" memory = 512 name = "hating-xen" vif = [''ip = "10.0.1.150", bridge=xenbr0''] disk = [ ''/dev/XEN/scalixroot,sda1,w'', ''/dev/XEN/scalixvar,sda3,w'', ''/dev/XEN/scalixswap,sda2,w'' ] It

Quoting Ulf Volmer <u.volmer at u-v.de>: > On 12/18/2014 08:11 PM, Dave Stevens wrote: >> ran routine updates on the lernel this morning and got this: >> >> WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, >> continuing anyway > > i'm not sure that i can help you, i have currently no centos5 vm on xen. > > But i guess the warning is

ran routine updates on the lernel this morning and got this: WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, continuing anyway The only references I can find are a year or so old. Anyone able to comment? or refer me? Have not rebooted. uname -a Linux bulkley.bvserver.ca 2.6.18-400.el5xen #1 SMP Thu Dec 4 13:29:23 EST 2014 x86_64 x86_64 x86_64 GNU/Linux Thanks, Dave --

Hi everyone! I''m sorry, I think I''m missing something obvious, but I can''t figure out what :/ I have a CentOS 5.2 dom0 on a HP Proliant ML150 with - kernel 2.6.18-92.1.18.el5xen - Xen 3.2.1 and I''m trying to boot a domU installation from the CentOS DVD. I made a custom initrd with mkinitrd /boot/initrd-vm `uname -r` --with xenblk --with xennet --preload

Hi all- I''m hoping someone can help me with this problem with Xen under CentOS 5.1 (RHEL 5.1) I''m having... This is the Xen package that comes stock with the distribution, I didn''t compile it from source. I can boot Domain0 and the hypervisor just fine. I''m trying to bring up a Xen guest VM and it crashes on boot, with this error: # xm create -c tcga1

On 12/18/2014 08:11 PM, Dave Stevens wrote: > ran routine updates on the lernel this morning and got this: > > WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, > continuing anyway i'm not sure that i can help you, i have currently no centos5 vm on xen. But i guess the warning is from the normal, not xen enabled kernel. Does /boot/vmlinuz-2.6.18-400.1.1.el5xen

On 12/23/2014 11:11 PM, Dave Stevens wrote: > Quoting Ulf Volmer <u.volmer at u-v.de>: > >> On 12/18/2014 08:11 PM, Dave Stevens wrote: >>> ran routine updates on the lernel this morning and got this: >>> >>> WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, >>> continuing anyway >> >> i'm not sure that i can help

Hi all, I just installed centos 5.4 xen-kernel on intel core i5 machine as dom0. After some hours of syncing a raid10 array (8 sata disk) I noticed a steadily increasing loadavg. I think without reasonable i/o wait or cpu utilization the loadavg on this system should be very lower. If this loadavg is normal I would be greatful if somone could explain why. The screenshots below show that there is

I'm trying to get a PVR-150 PCI card imported into a Xen DomU, however the driver blows up the kernel when loaded. The work around for this mentioned in various places is to use swiotlb=force on the DomU kernel. That leads to a fast and furious kernel panic. I've tried this with all Dom0 & DomU running kernel-xen-2.6.18-53.el5 kernel-xen-2.6.18-53.1.6.el5, bot x86 and 86_64

I have an F7 host that''s running the 2.6.20-2925.11.fc7xen 64-bit kernel on a Dell 2950 using the latest 64-bit Xen packages in F7, 3.1.0-2.f7. I''m trying to install RHEL 5 386 as a guest which I hear is possible. 64-bit RHEL5 isn''t available to use anyway. When I try to paravirtualize the install and only utilize 1 CPU, I always get a kernel oops right before the

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a

Hello all: I was getting a reproducible crash during an update of a xen system. The problem went away after I set SELinux to permissive, but the fact that it crashed was alarming (first one on a non-dev system that I've had in over a year). I attempted the update earlier but it crashed at the same point after attempting to update selinux. After verifying hardware (all clean) I ran it again