similar to: no pci support in xen-3.0.1 with gentoo

Hallo, the device is working without problems in the dom0, found from parport_pc: dmesg small2 snip: parport_pc: ITE8875 found (1P) parport0: PC-style at 0xf000 [PCSPP,TRISTATE,EPP] parport0: Printer, Kyocera FS-1700+ parport_pc: ITE 8872 parallel port: io=0xF000 parport1: PC-style at 0x378 [PCSPP,TRISTATE] snap to assign this device to a domU I gave the boot-parmaters

Hi - Xen cannot detect a PATA drive connected to my on-board promise 20378 K8T Neon MSI mobo. When I boot using a non exen kernel, the PATA is dected accordingly. Any thoughts? Following is dmesg from a regular non-exen kernel #uname -a Linux localhost 2.6.17-gentoo-r8 #1 Sun Oct 29 14:58:57 EST 2006 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux #dmesg Bootdata ok (command

Hi   I tried to create a guest domain and it failed however from another window i used xm list and observed the below.. I''m unable to login to the guest domain. Please help me.   [root@xenserver xen]# xm create -c xenclient1 vmid=1 Using config file "./xenclient1". Started domain centos5.2 Linux version 2.6.21-2950.fc8xen (kojibuilder@xenbuilder2.fedora.redhat.com) (gcc version

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

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

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

Dear All, I am a newbie to Xen and I am trying to set up a Xen VM with more than one guest running on a single machine. As a setup, I have Xen 3.1.0 installed with fc7 core and trying to run debian-4.0 guest image on one of the guest environment. After starting the xm guest domain, the console gets hanged up at DHCP request command, the log is as below: [root@steelbug xen]# xm console

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

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

Subject: xen-hypervisor-unstable-amd64: Post update from 3.2 -> 3.3, initrd which previously worked failes Package: xen-hypervisor-unstable-amd64 Version: 3.3-unstable+hg17961-1 Severity: normal *** Please type your report below this line *** System was running hypervisor 3.2, and domUs were working correctly. System was updated to -unstable (3.3) hypervisor and utils. Unchanged kernel and

hi, im using xen on fedora core 8 as dom0, and i downloaded the fc8 image from jailtime.org, when i use "xm create /xen/fedora/fedora.fc8.xen3.cfg -c" i get the following on my terminal: Using config file "/xen/fedora/fedora.fc8.xen3.cfg". Started domain fedora.fc8 Linux version 2.6.21-2950.fc8xen ( kojibuilder@xenbuilder2.fedora.redhat.com) (gcc

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 setting up Xen for the first time and have run into a problem. My system was initially setup with Fedora Core 4. I was able to successfully create a File-backed VBD. When I boot the domain,I get an error message that is listed at the end of the below boot messages. I suspect the problem is casued by my fstab. However, I am not sure how it should be configured. Fstab listed also. Any pointers

Hi, when i try to set up a DomU with the following configuration: dir = /home/xen debootstrap = 1 size = 4Gb memory = 128Mb swap = 128Mb fs = ext3 dist = dapper image = sparse dhcp = 1 kernel = /boot/xen0-linux-2.6.16-11.1-generic initrd = /boot/xen-modules-2.6.16-11.1-generic mirror = http://archive.ubuntu.com/ubuntu/ and try to start it with: root@ubuntu:/etc/xen# xm create dapperDomU.cfg -c

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-4 Severity: critical Justification: breaks the whole system Hi! the error suddenly appeared when creating a domU using xm create <name> on our etch server The server freezes and isn't accessible via console/ssh anymore. The server is a Dell PowerEdge 2900 with 2 Quad-Core Xeon E5335 and 8Gb memory. pc307005:~# xm create -c

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

Hi, I found one weird thing: I heard RAMDISK is not required for domU, but it seems I have to add RAMDISK to my domU config file, otherwiese the domU will hang up when it is booting. Please see the message below, the domU booting hangs up after "Continuing..." Does anyone have any clue for this issue? BTW, xen-friendly glibc is already installed. Thanks, Liang ---Begin of domU