similar to: xen-3.0-x86_32 not supported by xen kernel

Hi, I am trying to (live-)migrate a paravirtualized machine from hosta to hostb: -----8<---- hosta:~ # xm list pvm Name ID Mem VCPUs State Time(s) pvm 64 384 1 -b---- 0.5 hostb:~ # xm list pvm Error: Domain ''pvm'' does not exist. hosta:~ # xm migrate pvm 192.168.0.2 Error:

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

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

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

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

Hi, DomU is a Win2008 R2 64 When i install the GPLPV drivers the network latency goes from 15ms to random numbers up to 1200ms and eventually dies. If you run a ping from the DomU to another host the network stays alive but the high latency is still there. Further more if i try and uninstall the network driver i am unable to use the old one (realtek) as it cannot detect the device.

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

Hey, everyone, I''m having some issues with a Xen DomU right related to performance. We have an application that cross-compiles a Linux distribution from scratch for embedded systems. We''re attempting to run this application inside a Xen DomU (paravirtualized, modified guest kernel), and the performance is really bad. The culprit seems to be high I/O wait times related to the

I''m trying to contain my frustration...but I''m wondering if *anyone* has *ever* gotten the Import functionality to work in XCP? I''ve tried several times, and keep getting the same obnoxious and useless error that is absolutely no help to anyone: Failed to Import. I have made sure that the transfer VM is installed (View -> Show Hidden Objects, transfer VM is there),

In my experiments with setting up a NAS as a VM, I can only successfully import three drives; the root drive, the cd and one more. However, I have plenty that I want to use: disk=[''file:/vserver/vm_disks/Patch.disk.xm,hda,w'', ''phy:/dev/sda,ioemu:hdd,w'', ''phy:/dev/sdb,ioemu:hde,w'', ''phy:sdc,ioemu:hdf,w'',

Well, you have two options: 1) If your hardware supports VT, you can boot this in a Xen HVM domU (fully virtualized). To do this, you need to make sure that the initrd images in the Linux partition are set up correctly to support the PIIX IDE/ATA chipset and that your root and fstab entries use the correct device. 2) If you can install a Xen domU kernel into the Linux partition install, you can

Hi, folks, I''m attempting to run an e-mail server on Xen. The e-mail system is Novell GroupWise, and it serves about 250 users. The disk volume for the e-mail is on my SAN, and I''ve attached the FC LUN to my Xen host, then used the "phy:/dev..." method to forward the disk through to the domU. I''m running into an issue with high I/O wait on the box (~250%)

Well, I seem to have developed a strange issue with the GPL PV drivers in Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some Windows XP HVM domUs. Most (12-15) of my Windows machines work just fine. Two of them, though, have started exhibiting a strange behavior with intermittent network connectivity. Basically, the network starts up and connects initially. After some

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

After upgrade via http://download.opensuse.org/repositories/Virtualization:/openSUSE11.3/openSUSE_11.3/src/xen-4.0.1_21326_01-1.1.src.rpm with any "kotd" or 2.6.34.4-2.2-xen VFB gets broken . It worked with original  Xen 4.0, no matter of  some additional patching to support ZFS 24 has been done and 4.0 src.rpm has been rebuilt to reinstall 4.0   In particular,  virt-install fails to

I''m running xen on SLES10SP2. It''s been much more stable than SP1, but I still occasionally have issues. For example, one of my servers (8 CPU/32GB RAM) has five sles pv domUs and five fully virtualized windows 2k3 domUs. It had been up for almost 60 days. Yesterday afternoon one of the sles domU''s stopped responding. I went to check on it and I couldn''t using

Hey, everyone, I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU to run correctly. I''ve followed a couple of the instruction sets out on the Xen wiki and other folks blogs, but I''m running into an issue with the domU crashing. The OpenSolaris version is the latest development release - 5.11-0.128. The config looks like this:

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

This may be a better question for the Xen-Devel list, but I''ll start here... Does anyone know if there is any easy way to replace the gPXE ROM with a newer version in Xen? Also, anyone know if there are any plans to have some sort of option in the domU config file to specify a boot rom? Looks like qemu-dm has an "-option-rom" option - is there any way in Xen to make use of