similar to: DomU boot hangs after cron; XENBUS errors

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

Hello, Maybe someone can help me.... I have a guest XEN image that ran well until today. I use an LVM partition to host the guest and today on Dom0 I added another LVM to be available to this domU. This were all the commands I issued : On hypervisor lvcreate -n lintra02data -L 30G rootvg vi /etc/xen/lintra02 and add volume to file like this : disk = [

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

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

RHEL5 32bit xen 3.3.0 rpms? Anyone? ;) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello Dear everybody! I just installed CentOS 5.3 and try the built-in Xen 3.1 with it. But even the typical ttyLinux doesn''t work when the domain is created.-- it just doesn''t give me the login prompt while the domain ttylinux is booted. [root@soe-hd513-pc102 nimbus]# xm create ttylinux-xen.conf -c Using config file "./ttylinux-xen.conf". Started domain ttylinux

I build a DomU kernel on RHEL AS5.1. But when I boot this Guest DomU with the kernel, it gives me error message: Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') Can someone give me any suggestion about this problem? Thank you! Joe _______________________________________________ Xen-users

Hello, I just gain experiences in using XEN and hope you can help me. My hostsystem is Centos5 that I installed on a Software-Raid (Level 1). Afterwards I downloaded the debian-tarball from the jailtime.org website, extracted/mounted the image and copied the "*/lib/modules/*<kernelversion>"-folder from my host to the guest. My XEN-Configfile looks like this: kernel =

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

I am trying to create a para-virtualized guest with the same kernel image and initrd image as dom0. The configuration is below ================================================================================ kernel = "/boot/vmlinuz-2.6.21.7-3.fc8xen" ramdisk = "/boot/initrd-2.6.21.7-3.fc8xen.img" memory = 428 name = "fedora.fc8" vif = [ '''' ] dhcp =

Hi all, I have a problem during the lauching of my first virtual image. First thing : domain 0 is on fedora core 6 (probably a xen package made in fedora :-S, sorry ...) Second thing : the error is really traditional (i already had it with uml) but there i am blocking. here my config file (for image on logical volume, swap too) root = "/dev/sda1 ro" [root@p-virtvip8 xen]# cat p-virtser9

I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950. In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64. I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues. Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my

Hello everyone, I''m quite a newbie with Xen and I''m currently having an issue. I run Xen 4 on Debian Squeeze x64 and I''m trying to build an OpenFiler DomU from the Xen domU filesystem tarbal they provide (See http://www.openfiler.com/community/download/). I downloaded the tarball and run ''tar xzpvf /root/soft/openfiler-2.3-x86_64.tar.gz'' to extract

I have a physical SLES11SP2/OES11 system that I''ve converted to a domU. It''s boots ok as an HVM, but when I try to boot as a PV it gets stuck. I have the kernel-xen packages installed and confident the menu.lst is correct. If I look at xm console for the VM I get the output below: Any ideas? Thanks James [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]

here is my problem: Parsing config file vir2.cfg Daemon running with PID 11570 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.0.0 (root@localhost.localdomain) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Mon Oct 28 00:35:01 CST 2013 Command line: root=/dev/hda1 ro ACPI in unprivileged domain disabled released 0 pages

Hi, Am trying to build SMP kernel. Took kernel-2.6.18-194.src.rpm, extracted, rpmbuilded with SMP option. Successfully compile the new kernel and when using that kernel to boot up, following errors were shown up(highlighted in bold & red color): My kernel config file has ACPI and PCI configs enabled. Any pointers to what caused the problem are appreciated. ******************************

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other