I have several systems running Xen 3.0.2 on Fedora Core 5. Today, I started playing with Xen 3.0.3 also on FC5. dom0 starts up fine without any problem. However, I cannot create any domU''s (domU CentOS 4.4). This is the error being reported: [root@xenmgt ~]# xm create -c meta Using config file "/etc/xen/meta". Error: Device 0 (vtpm) could not be connected. Backend device not found. this is in xend-debug.log: Traceback (most recent call last): File "/usr/lib/python2.3/SocketServer.py", line 463, in process_request_thread self.finish_request(request, client_address) File "/usr/lib/python2.3/SocketServer.py", line 254, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/lib/python2.3/SocketServer.py", line 521, in __init__ self.handle() File "/usr/lib/python2.3/BaseHTTPServer.py", line 324, in handle self.handle_one_request() File "/usr/lib/python2.3/BaseHTTPServer.py", line 318, in handle_one_request method() File "/obj/BUILD/tmp/xen-3.0.3.0-3.0.3.0-local_2006-10-16-14-13-24+0100_57fa367206fb-root/usr/lib/python/xen/util/xmlrpclib2.py", line 66, in do_POST File "/usr/lib/python2.3/BaseHTTPServer.py", line 374, in send_response self.wfile.write("%s %d %s\r\n" % File "/usr/lib/python2.3/socket.py", line 254, in write self.flush() File "/usr/lib/python2.3/socket.py", line 241, in flush self._sock.sendall(buffer) error: (32, ''Broken pipe'') Errors in xen-hotplug.log: /etc/xen/scripts/vtpm-impl: line 73: /var/vtpm/fifos/from_console.fifo: No such file or directory Nothing to flush. cat: /etc/xen/vtpm.db: No such file or directory cat: /etc/xen/vtpm.db: No such file or directory xend.log has the following info: [2006-10-18 00:09:48 xend 13309] DEBUG (DevController:112) DevController: writing {''domain'': ''meta'', ''frontend'': ''/local/domain/9/de vice/vtpm/0'', ''pref_instance'': ''1'', ''resume'': ''False'', ''frontend-id'': ''9'', ''online'': ''1'', ''state'': ''1''} to /local/domain/0/backend/v tpm/9/0. [2006-10-18 00:09:48 xend.XendDomainInfo 13309] DEBUG (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', ''uuid'': ''8222d 98d-22e2-92c6-c995-70bf961a9398'', ''on_reboot'': ''restart'', ''start_time'': ''1161130188.58'', ''on_poweroff'': ''destroy'', ''name'': ''meta'', '' xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''512'', ''on_crash'': ''restart'', ''image'': "(linux (kernel /boot/xe nkernel) (ramdisk /boot/xeninitrd) (root ''/dev/sda2 ro'') (args 3))", ''maxmem'': ''512''} [2006-10-18 00:09:48 xend.XendDomainInfo 13309] DEBUG (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': ''814422'', ''c onsole/port'': ''2'', ''name'': ''meta'', ''console/limit'': ''1048576'', ''vm'': ''/vm/8222d98d-22e2-92c6-c995-70bf961a9398'', ''domid'': ''9'', ''cpu/ 0/availability'': ''online'', ''memory/target'': ''524288'', ''store/ring-ref'': ''814423'', ''store/port'': ''1''} [2006-10-18 00:09:48 xend.XendDomainInfo 8699] DEBUG (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch [2006-10-18 00:09:48 xend 13607] DEBUG (DevController:143) Waiting for devices vif. [2006-10-18 00:09:48 xend 13607] DEBUG (DevController:149) Waiting for 0. [2006-10-18 00:09:48 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-10-18 00:09:51 xend 13607] DEBUG (DevController:143) Waiting for devices usb. [2006-10-18 00:09:51 xend 13607] DEBUG (DevController:143) Waiting for devices vbd. [2006-10-18 00:09:51 xend 13607] DEBUG (DevController:149) Waiting for 2050. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/9/2050/hotplug-status. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-10-18 00:09:51 xend 13607] DEBUG (DevController:149) Waiting for 2051. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/9/2051/hotplug-status. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-10-18 00:09:51 xend 13607] DEBUG (DevController:149) Waiting for 2052. [2006-10-18 00:09:51 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/9/2052/hotplug-status. [2006-10-18 00:11:27 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/9/2052/hotplug-status. [2006-10-18 00:11:27 xend 8699] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:149) Waiting for 2053. [2006-10-18 00:11:27 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/9/2053/hotplug-status. [2006-10-18 00:11:27 xend 8699] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:143) Waiting for devices irq. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:143) Waiting for devices pci. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:143) Waiting for devices ioports. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:143) Waiting for devices tap. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:143) Waiting for devices vtpm. [2006-10-18 00:11:27 xend 13607] DEBUG (DevController:149) Waiting for 0. [2006-10-18 00:11:27 xend 8699] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vtpm/9/0/hotplug-status. THe config file: kernel = "/boot/xenkernel" ramdisk = "/boot/xeninitrd" memory = 512 name = "meta" vif = [ ''mac=00:16:3e:00:14:12, bridge=xenbr0'' ] disk = [ ''phy:xenvg/metaroot,sda2,w'', ''phy:xenvg/metausr,sda3,w'', ''phy:xenvg/metavar,sda4,w'', ''phy:xenvg/metaswap,sda5,w'' ] vtpm = [ ''instance=1,backend=0'' ] root = "/dev/sda2 ro" extra = "3" Any idea what''s wrong. thanks for any help. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fong Vang wrote:> I have several systems running Xen 3.0.2 on Fedora Core 5. > > Today, I started playing with Xen 3.0.3 also on FC5. dom0 starts up > fine without any problem. However, I cannot create any domU''s (domU > CentOS 4.4). This is the error being reported: > > > [root@xenmgt ~]# xm create -c meta > Using config file "/etc/xen/meta". > Error: Device 0 (vtpm) could not be connected. Backend device not found.Same happened to me on Debian with 3.0.3 RCs. Didn''t manage to fix it, so I am still using version 3.0.2. -- Jaume Sabater http://linuxsilo.net/ "Ubi sapientas ibi libertas" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/18/06, Jaume Sabater <jsabater@linuxsilo.net> wrote:> Fong Vang wrote: > > > I have several systems running Xen 3.0.2 on Fedora Core 5. > > > > Today, I started playing with Xen 3.0.3 also on FC5. dom0 starts up > > fine without any problem. However, I cannot create any domU''s (domU > > CentOS 4.4). This is the error being reported: > > > > > > [root@xenmgt ~]# xm create -c meta > > Using config file "/etc/xen/meta". > > Error: Device 0 (vtpm) could not be connected. Backend device not found. > > Same happened to me on Debian with 3.0.3 RCs. Didn''t manage to fix it, > so I am still using version 3.0.2.Thanks for the input. The list is kinda quiet. Unfortunately, with the newer hardware I''ve been getting, dom0 running 3.0.2 kernel panics all the time (consistently across multiple hardware so memory or other hardware problem is unlikely). The good news is that 3.0.3 appears to be running very stable on the new hardware, except that I cannot create any domU''s. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
what do you use vtpm for? does it work if you comment out the vtpm stuff? 3.0.3 works for me with rhel 3 and 4 domUs On Wed, 18 Oct 2006, Fong Vang wrote:> Date: Wed, 18 Oct 2006 09:24:26 -0700 > From: Fong Vang <sudoyang@gmail.com> > To: Jaume Sabater <jsabater@linuxsilo.net> > Cc: Xen-users@lists.xensource.com > Subject: Re: [Xen-users] xen 3.0.3 > > On 10/18/06, Jaume Sabater <jsabater@linuxsilo.net> wrote: >> Fong Vang wrote: >> >> > I have several systems running Xen 3.0.2 on Fedora Core 5. >> > >> > Today, I started playing with Xen 3.0.3 also on FC5. dom0 starts up >> > fine without any problem. However, I cannot create any domU''s (domU >> > CentOS 4.4). This is the error being reported: >> > >> > >> > [root@xenmgt ~]# xm create -c meta >> > Using config file "/etc/xen/meta". >> > Error: Device 0 (vtpm) could not be connected. Backend device not found. >> >> Same happened to me on Debian with 3.0.3 RCs. Didn''t manage to fix it, >> so I am still using version 3.0.2. > > Thanks for the input. The list is kinda quiet. Unfortunately, with > the newer hardware I''ve been getting, dom0 running 3.0.2 kernel panics > all the time (consistently across multiple hardware so memory or other > hardware problem is unlikely). The good news is that 3.0.3 appears to > be running very stable on the new hardware, except that I cannot > create any domU''s. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
This works! I didn''t know it was not needed. What exactly is vtpm? What is a trusted platform module. I was looking for a good definition/description of it on the web but did not find any that describes this precisely. Thank you! This will get me going and will investigate vtpm problem later. On 10/18/06, Luke Crawford <lsc@prgmr.com> wrote:> > what do you use vtpm for? does it work if you comment out the vtpm stuff? > > 3.0.3 works for me with rhel 3 and 4 domUs > > > On Wed, 18 Oct 2006, Fong Vang wrote: > > > Date: Wed, 18 Oct 2006 09:24:26 -0700 > > From: Fong Vang <sudoyang@gmail.com> > > To: Jaume Sabater <jsabater@linuxsilo.net> > > Cc: Xen-users@lists.xensource.com > > Subject: Re: [Xen-users] xen 3.0.3 > > > > On 10/18/06, Jaume Sabater <jsabater@linuxsilo.net> wrote: > >> Fong Vang wrote: > >> > >> > I have several systems running Xen 3.0.2 on Fedora Core 5. > >> > > >> > Today, I started playing with Xen 3.0.3 also on FC5. dom0 starts up > >> > fine without any problem. However, I cannot create any domU''s (domU > >> > CentOS 4.4). This is the error being reported: > >> > > >> > > >> > [root@xenmgt ~]# xm create -c meta > >> > Using config file "/etc/xen/meta". > >> > Error: Device 0 (vtpm) could not be connected. Backend device not found. > >> > >> Same happened to me on Debian with 3.0.3 RCs. Didn''t manage to fix it, > >> so I am still using version 3.0.2. > > > > Thanks for the input. The list is kinda quiet. Unfortunately, with > > the newer hardware I''ve been getting, dom0 running 3.0.2 kernel panics > > all the time (consistently across multiple hardware so memory or other > > hardware problem is unlikely). The good news is that 3.0.3 appears to > > be running very stable on the new hardware, except that I cannot > > create any domU''s. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Fong Vang > Sent: 18 October 2006 17:24 > To: Jaume Sabater > Cc: Xen-users@lists.xensource.com > Subject: Re: [Xen-users] xen 3.0.3 > > On 10/18/06, Jaume Sabater <jsabater@linuxsilo.net> wrote: > > Fong Vang wrote: > > > > > I have several systems running Xen 3.0.2 on Fedora Core 5. > > > > > > Today, I started playing with Xen 3.0.3 also on FC5. > dom0 starts up > > > fine without any problem. However, I cannot create any > domU''s (domU > > > CentOS 4.4). This is the error being reported: > > > > > > > > > [root@xenmgt ~]# xm create -c meta > > > Using config file "/etc/xen/meta". > > > Error: Device 0 (vtpm) could not be connected. Backend > device not found. > > > > Same happened to me on Debian with 3.0.3 RCs. Didn''t manage > to fix it, > > so I am still using version 3.0.2. > > Thanks for the input. The list is kinda quiet. Unfortunately, with > the newer hardware I''ve been getting, dom0 running 3.0.2 kernel panics > all the time (consistently across multiple hardware so memory or other > hardware problem is unlikely). The good news is that 3.0.3 appears to > be running very stable on the new hardware, except that I cannot > create any domU''s.(vtpm) indicates that you''re using the virtual TPM. Is this something you wanted to do, or just accidentally switched on (or didn''t switch off?). Check the latest config files and see if they say anything on how to switch this off if you can live without a virtual TPM... -- Mats> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Fong Vang > Sent: 18 October 2006 17:49 > To: Luke Crawford > Cc: Xen-users@lists.xensource.com; Jaume Sabater > Subject: Re: [Xen-users] xen 3.0.3 > > This works! I didn''t know it was not needed. > > What exactly is vtpm? What is a trusted platform module. I was > looking for a good definition/description of it on the web but did not > find any that describes this precisely.A "real" TPM is a "safe storage module", which means that it''s a safe place where software can''t just arbitrarily read the content, and the data-link from the processor to the TPM is encrypted so that you can''t just hook somehting to it to "listen in". The defition of the TPM is made by "Trusted Computing Group", if you google that, you should be able to find some useful info. Basicly, you need a TPM if you want to be able to run secure software - because you need some storage that can''t be compromized by other software to verify (for example) that the kernel code you''re loading hasn''t been modified since you installed it. Likewise, you may want some software to check that the web-browser you''re loading (including plug-ins and other additions) haven''t been replaced with something that alters the bank-transactions when you pay your bills over the ''net - for example someone may add some "spyware" to alter the "to-account" so as to send the money somewhere completely different. By the time you discover that your bill wasn''t actually paid, your money is probably long gone... Of course, if we use regular memory to store check-sums for the applications, the malware could just alter the content of that memory too - so you wouldn''t know that the web-browser has been altered... This is where the TPM becomes useful. -- Mats> > Thank you! This will get me going and will investigate vtpm > problem later. > > > On 10/18/06, Luke Crawford <lsc@prgmr.com> wrote: > > > > what do you use vtpm for? does it work if you comment out > the vtpm stuff? > > > > 3.0.3 works for me with rhel 3 and 4 domUs > > > > > > On Wed, 18 Oct 2006, Fong Vang wrote: > > > > > Date: Wed, 18 Oct 2006 09:24:26 -0700 > > > From: Fong Vang <sudoyang@gmail.com> > > > To: Jaume Sabater <jsabater@linuxsilo.net> > > > Cc: Xen-users@lists.xensource.com > > > Subject: Re: [Xen-users] xen 3.0.3 > > > > > > On 10/18/06, Jaume Sabater <jsabater@linuxsilo.net> wrote: > > >> Fong Vang wrote: > > >> > > >> > I have several systems running Xen 3.0.2 on Fedora Core 5. > > >> > > > >> > Today, I started playing with Xen 3.0.3 also on FC5. > dom0 starts up > > >> > fine without any problem. However, I cannot create > any domU''s (domU > > >> > CentOS 4.4). This is the error being reported: > > >> > > > >> > > > >> > [root@xenmgt ~]# xm create -c meta > > >> > Using config file "/etc/xen/meta". > > >> > Error: Device 0 (vtpm) could not be connected. Backend > device not found. > > >> > > >> Same happened to me on Debian with 3.0.3 RCs. Didn''t > manage to fix it, > > >> so I am still using version 3.0.2. > > > > > > Thanks for the input. The list is kinda quiet. > Unfortunately, with > > > the newer hardware I''ve been getting, dom0 running 3.0.2 > kernel panics > > > all the time (consistently across multiple hardware so > memory or other > > > hardware problem is unlikely). The good news is that > 3.0.3 appears to > > > be running very stable on the new hardware, except that I cannot > > > create any domU''s. > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m experience something strange in the new domU running Xen 3.0.3. I cannot install some packages, even when trying to force an rpm install using --force and --nodeps. # rpm -Uvh --force --nodeps ''http://10.1.34.99/L1/IBM_db2cliv81-8.1.0-89.i386.rpm'' Retrieving http://10.1.34.99/L1/IBM_db2cliv81-8.1.0-89.i386.rpm Preparing... ########################################### [100%] error: %pre(IBM_db2cliv81-8.1.0-89.i386) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping IBM_db2cliv81-8.1.0-89 This same command works fine on a system outside of Xen. As you can see, it fails during the %pre section which only sets a variable: preinstall scriptlet (using /bin/sh): DB2DIR="/opt/IBM/db2/V8.1" exit 0 postinstall scriptlet (using /bin/sh): DB2DIR="/opt/IBM/db2/V8.1" SPBDIR="${DB2DIR?}/spb" DOCDIR="${DB2DIR?}/doc" DQPDIR="${DB2DIR?}/qp" Could this be that vtpm is disabled? This works fine on a xen 3.0.2 system with vtpm enabled. On 10/18/06, Petersson, Mats <Mats.Petersson@amd.com> wrote:> > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Fong Vang > > Sent: 18 October 2006 17:24 > > To: Jaume Sabater > > Cc: Xen-users@lists.xensource.com > > Subject: Re: [Xen-users] xen 3.0.3 > > > > On 10/18/06, Jaume Sabater <jsabater@linuxsilo.net> wrote: > > > Fong Vang wrote: > > > > > > > I have several systems running Xen 3.0.2 on Fedora Core 5. > > > > > > > > Today, I started playing with Xen 3.0.3 also on FC5. > > dom0 starts up > > > > fine without any problem. However, I cannot create any > > domU''s (domU > > > > CentOS 4.4). This is the error being reported: > > > > > > > > > > > > [root@xenmgt ~]# xm create -c meta > > > > Using config file "/etc/xen/meta". > > > > Error: Device 0 (vtpm) could not be connected. Backend > > device not found. > > > > > > Same happened to me on Debian with 3.0.3 RCs. Didn''t manage > > to fix it, > > > so I am still using version 3.0.2. > > > > Thanks for the input. The list is kinda quiet. Unfortunately, with > > the newer hardware I''ve been getting, dom0 running 3.0.2 kernel panics > > all the time (consistently across multiple hardware so memory or other > > hardware problem is unlikely). The good news is that 3.0.3 appears to > > be running very stable on the new hardware, except that I cannot > > create any domU''s. > > (vtpm) indicates that you''re using the virtual TPM. Is this something > you wanted to do, or just accidentally switched on (or didn''t switch > off?). Check the latest config files and see if they say anything on how > to switch this off if you can live without a virtual TPM... > > -- > Mats > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Freemon
2006-Oct-19 19:54 UTC
[Xen-users] mkinitrd problem when LVM volume group names differ between Dom0 and DomU
How can I make "mkinitrd" generate a correct ramdisk image when the LVM volume group names differ between the Dom0 and DomU? The details: In Dom0, the root filesystem is LVM in volume group "VGShark", as follows: # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VGShark-LogVol00 450G 119G 308G 28% / /dev/sda1 99M 45M 49M 48% /boot tmpfs 1.9G 0 1.9G 0% /dev/shm In the DomU, the root filesystem is LVM in volume group "VolGroup00". Back in Dom0, I run the following to create the initrd... #mkinitrd -f initrd-2.6.16.29-xen.img 2.6.16.29-xen ...which produces the following (snippet) in the generated "init" file in the ramdisk image: echo Making device-mapper control node mkdmnod mkblkdevs echo Scanning logical volumes lvm vgscan --ignorelockingfailure echo Activating logical volumes lvm vgchange -ay --ignorelockingfailure VGShark resume /dev/VGShark/LogVol01 echo Creating root device. mkrootdev -t ext3 -o defaults,ro /dev/VGShark/LogVol00 echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot echo Switching to new root and running init. switchroot The DomU config file is: kernel = "/boot/vmlinuz-2.6.16.29-xen" ramdisk = "/boot/initrd-2.6.16.29-xen.img" root = "/dev/VolGroup00/LogVol00 ro" name = "minnow" memory = "512" disk = [ ''file:/var/vm/minnow/disk0.img,xvda,w'' ] vif = [ ''mac=00:16:3e:00:e6:8f'' ] uuid = "7e6aa8bb-37da-3a7f-e72e-63290fcf2713" ..which produces the following error at domU boot time: Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 Activating logical volumes Unable to find volume group "VGShark" Creating root device. Mounting root filesystem. mount: could not find filesystem ''/dev/root'' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! So -- Here is the /etc/fstab (in Dom0): #cat fstab /dev/VGShark/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /dev/VGShark/LogVol01 swap swap defaults 0 0 I copy this file to create fstab.domU, and change the references to VGShark to VolGroup00, which is: #cat fstab.domU /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 This matches exactly what DomU is expecting. I rebuild initrd with the following command: # mkinitrd -f --fstab=/etc/fstab.domU initrd-2.6.16.29-xen.img 2.6.16.29-xen ...which produces the following (snippet) in the generated "init" file in the ramdisk image: mkblkdevs resume /dev/VolGroup00/LogVol01 echo Creating root device. mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00 echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot echo Switching to new root and running init. switchroot I try again to boot the DomU with the same config file listed above and I get this error: Creating root device. Mounting root filesystem. mount: could not find filesystem ''/dev/root'' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! Next -- I modify the generated "init" file in the ramdisk image to the following (replace VGShark with VolGroup00): mkdmnod mkblkdevs echo Scanning logical volumes lvm vgscan --ignorelockingfailure echo Activating logical volumes lvm vgchange -ay --ignorelockingfailure VolGroup00 resume /dev/VolGroup00/LogVol01 echo Creating root device. mkrootdev -t ext3 -o defaults,ro /dev/VolGroup/LogVol00 echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot echo Switching to new root and running init. switchroot I rebuild the initrd image, and change the ramdisk line in the domU config to: kernel = "/boot/vmlinuz-2.6.16.29-xen" ramdisk = "/boot/initrdDomU.img" root = "/dev/VolGroup00/LogVol00 ro" name = "minnow" memory = "512" disk = [ ''file:/var/vm/minnow/disk0.img,xvda,w'' ] vif = [ ''mac=00:16:3e:00:e6:8f'' ] uuid = "7e6aa8bb-37da-3a7f-e72e-63290fcf2713" ...and the DomU boots up! The conclusion I draw is that mkinitrd is not creating a good ramdisk image. How can I make mkinitrd generate a correct ramdisk image when the volume group names differ between the Dom0 and DomU? TIA, - Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Freemon
2006-Oct-20 15:50 UTC
Re: [Xen-users] mkinitrd problem when LVM volume group names differ between Dom0 and DomU
Hi Tim, Thanks for the reply. I was unable to find the "-k" option you mentioned. I''m running mkinitrd 5.0.32. I think the main issue is a design assumption on the part of the mkinitrd script (at the time quite reasonable), that it (the script) would be running on the same system that the ramdisk will be running on. Xen (paravirtualized) violates this assumption. I have also added to this mkinitrd bugzilla entry: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190274 - Mike At 10/19/2006 03:21 PM Thursday, Tim Post wrote:>Try mkinitrd -k (keep files used in creating in /tmp/mkinitrd.xxxx), go >edit as needed, and mkfs.cramfs using the initrd root left >in /tmp/mkinitrd.xxxx/initrd > >HTH > >Best, >-Tim > > >On Thu, 2006-10-19 at 14:54 -0500, Mike Freemon wrote: > > How can I make "mkinitrd" generate a correct ramdisk image when the LVM > > volume group names differ between the Dom0 and DomU? > > > > The details: > > > > In Dom0, the root filesystem is LVM in volume group "VGShark", as follows: > > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > > /dev/mapper/VGShark-LogVol00 > > 450G 119G 308G 28% / > > /dev/sda1 99M 45M 49M 48% /boot > > tmpfs 1.9G 0 1.9G 0% /dev/shm > > > > In the DomU, the root filesystem is LVM in volume group "VolGroup00". > > > > Back in Dom0, I run the following to create the initrd... > > > > #mkinitrd -f initrd-2.6.16.29-xen.img 2.6.16.29-xen > > > > ...which produces the following (snippet) in the generated "init" file in > > the ramdisk image: > > > > echo Making device-mapper control node > > mkdmnod > > mkblkdevs > > echo Scanning logical volumes > > lvm vgscan --ignorelockingfailure > > echo Activating logical volumes > > lvm vgchange -ay --ignorelockingfailure VGShark > > resume /dev/VGShark/LogVol01 > > echo Creating root device. > > mkrootdev -t ext3 -o defaults,ro /dev/VGShark/LogVol00 > > echo Mounting root filesystem. > > mount /sysroot > > echo Setting up other filesystems. > > setuproot > > echo Switching to new root and running init. > > switchroot > > > > The DomU config file is: > > > > kernel = "/boot/vmlinuz-2.6.16.29-xen" > > ramdisk = "/boot/initrd-2.6.16.29-xen.img" > > root = "/dev/VolGroup00/LogVol00 ro" > > name = "minnow" > > memory = "512" > > disk = [ ''file:/var/vm/minnow/disk0.img,xvda,w'' ] > > vif = [ ''mac=00:16:3e:00:e6:8f'' ] > > uuid = "7e6aa8bb-37da-3a7f-e72e-63290fcf2713" > > > > ..which produces the following error at domU boot time: > > > > Making device-mapper control node > > Scanning logical volumes > > Reading all physical volumes. This may take a while... > > Found volume group "VolGroup00" using metadata type lvm2 > > Activating logical volumes > > Unable to find volume group "VGShark" > > Creating root device. > > Mounting root filesystem. > > mount: could not find filesystem ''/dev/root'' > > Setting up other filesystems. > > Setting up new root fs > > setuproot: moving /dev failed: No such file or directory > > no fstab.sys, mounting internal defaults > > setuproot: error mounting /proc: No such file or directory > > setuproot: error mounting /sys: No such file or directory > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > switchroot: mount failed: No such file or directory > > Kernel panic - not syncing: Attempted to kill init! > > > > So -- > > > > Here is the /etc/fstab (in Dom0): > > > > #cat fstab > > /dev/VGShark/LogVol00 / ext3 defaults 1 1 > > LABEL=/boot /boot ext3 defaults 1 2 > > devpts /dev/pts devpts gid=5,mode=620 0 0 > > tmpfs /dev/shm tmpfs defaults 0 0 > > proc /proc proc defaults 0 0 > > sysfs /sys sysfs defaults 0 0 > > /dev/VGShark/LogVol01 swap swap defaults 0 0 > > > > I copy this file to create fstab.domU, and change the references to > VGShark > > to VolGroup00, which is: > > > > #cat fstab.domU > > /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 > > LABEL=/boot /boot ext3 defaults 1 2 > > devpts /dev/pts devpts gid=5,mode=620 0 0 > > tmpfs /dev/shm tmpfs defaults 0 0 > > proc /proc proc defaults 0 0 > > sysfs /sys sysfs defaults 0 0 > > /dev/VolGroup00/LogVol01 swap swap defaults 0 0 > > > > This matches exactly what DomU is expecting. > > > > I rebuild initrd with the following command: > > > > # mkinitrd -f --fstab=/etc/fstab.domU initrd-2.6.16.29-xen.img > 2.6.16.29-xen > > > > ...which produces the following (snippet) in the generated "init" file in > > the ramdisk image: > > > > mkblkdevs > > resume /dev/VolGroup00/LogVol01 > > echo Creating root device. > > mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00 > > echo Mounting root filesystem. > > mount /sysroot > > echo Setting up other filesystems. > > setuproot > > echo Switching to new root and running init. > > switchroot > > > > I try again to boot the DomU with the same config file listed above and I > > get this error: > > > > Creating root device. > > Mounting root filesystem. > > mount: could not find filesystem ''/dev/root'' > > Setting up other filesystems. > > Setting up new root fs > > setuproot: moving /dev failed: No such file or directory > > no fstab.sys, mounting internal defaults > > setuproot: error mounting /proc: No such file or directory > > setuproot: error mounting /sys: No such file or directory > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > switchroot: mount failed: No such file or directory > > Kernel panic - not syncing: Attempted to kill init! > > > > Next -- > > > > I modify the generated "init" file in the ramdisk image to the following > > (replace VGShark with VolGroup00): > > > > mkdmnod > > mkblkdevs > > echo Scanning logical volumes > > lvm vgscan --ignorelockingfailure > > echo Activating logical volumes > > lvm vgchange -ay --ignorelockingfailure VolGroup00 > > resume /dev/VolGroup00/LogVol01 > > echo Creating root device. > > mkrootdev -t ext3 -o defaults,ro /dev/VolGroup/LogVol00 > > echo Mounting root filesystem. > > mount /sysroot > > echo Setting up other filesystems. > > setuproot > > echo Switching to new root and running init. > > switchroot > > > > I rebuild the initrd image, and change the ramdisk line in the domU > config to: > > > > kernel = "/boot/vmlinuz-2.6.16.29-xen" > > ramdisk = "/boot/initrdDomU.img" > > root = "/dev/VolGroup00/LogVol00 ro" > > name = "minnow" > > memory = "512" > > disk = [ ''file:/var/vm/minnow/disk0.img,xvda,w'' ] > > vif = [ ''mac=00:16:3e:00:e6:8f'' ] > > uuid = "7e6aa8bb-37da-3a7f-e72e-63290fcf2713" > > > > ...and the DomU boots up! > > > > The conclusion I draw is that mkinitrd is not creating a good ramdisk > image. > > > > How can I make mkinitrd generate a correct ramdisk image when the volume > > group names differ between the Dom0 and DomU? > > > > TIA, > > > > - Mike > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Freemon
2006-Oct-31 22:55 UTC
[Xen-users] Xen 3.0.3 boot-time kernel panic with prebuilt binaries and source but not demo CD
Hi All, I have an ordinary system that has been running xen 3.0.2 perfectly for quite a while. It also boots up from the Xen 3.0.3 Demo CD just fine. But when I install the prebuilt Xen 3.0.3 binaries, it kernel panics. It also kernel panics with the same symptoms when I build Xen 3.0.3 from source. See below for full text of the logs. The first log is the serial console when booting the xen 303 prebuilt binaries. Kernel panic. The second log is the dmesg file from the xen 303 demo CD (debian dom0 gui). Same machine. Works. The third section is the output of lspci from a non-xen boot of the same machine (because I was thinking this is a PCI issue, but I''m not so sure now). Any advice is appreciated. TIA, - Mike *** XEN 3.0.3 PREBUILT KERNEL - KERNEL PANIC Booting ''Fedora Core (xen-3.0.3-0_prebuilt)'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen-3.0.3-0.gz com1=9600,8n1 sync_console watchdog [Multiboot-elf, <0x100000:0x7e5d8:0x47a28>, shtab=0x1c6078, entry=0x100000] module /vmlinuz-2.6.16.29-xen ro root=/dev/VolGroup00/LogVol00 console=ttyS0,96 00 console=tty0 selinux=0 ramdisk_size=32758 [Multiboot-module @ 0x1c7000, 0x2e29c0 bytes] module /initrd-2.6.16.29-xen.img [Multiboot-module @ 0x4aa000, 0x3a0e00 bytes] __ __ _____ ___ _____ ___ \ \/ /___ _ __ |___ / / _ \ |___ / / _ \ \ // _ \ ''_ \ |_ \| | | | |_ \ __| | | | / \ __/ | | | ___) | |_| | ___) |__| |_| | /_/\_\___|_| |_| |____(_)___(_)____/ \___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0.3-0 (shand@localdomain) (gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) Sun Oct 15 13:22:06 BST 2006 Latest ChangeSet: Sun Oct 15 13:22:03 2006 +0100 11773:433e39d54b0e (XEN) Console output is synchronous. (XEN) Command line: /xen-3.0.3-0.gz com1=9600,8n1 sync_console watchdog (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009b800 (usable) (XEN) 000000000009b800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000003fef0000 (usable) (XEN) 000000003fef0000 - 000000003fefc000 (ACPI data) (XEN) 000000003fefc000 - 000000003ff00000 (ACPI NVS) (XEN) 000000003ff00000 - 000000003ff80000 (usable) (XEN) 000000003ff80000 - 0000000040000000 (reserved) (XEN) 00000000fec00000 - 00000000fec10000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff800000 - 00000000ffc00000 (reserved) (XEN) 00000000fff00000 - 0000000100000000 (reserved) (XEN) System RAM: 1023MB (1047596kB) (XEN) Xen heap: 10MB (10440kB) (XEN) PAE disabled. (XEN) found SMP MP-table at 000f64d0 (XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 PTLTD ) @ 0x000f6500 (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x3fef8674 (XEN) ACPI: FADT (v001 Intel SE7501CW 0x06040000 PTL 0x00000008) @ 0x3fefbe94 (XEN) ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @ 0x3fefbf08 (XEN) ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x3fefbf88 (XEN) ACPI: SPCR (v001 PTLTD $UCRTBL$ 0x06040000 PTL 0x00000001) @ 0x3fefbfb0 (XEN) ACPI: DSDT (v001 INTEL PLUMAS 0x06040000 MSFT 0x0100000e) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 15:2 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 15:2 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24]) (XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47 (XEN) ACPI: IOAPIC (id[0x04] address[0xfec80400] gsi_base[48]) (XEN) IOAPIC[2]: apic_id 4, version 32, address 0xfec80400, GSI 48-71 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2392.094 MHz processor. (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K (XEN) CPU: L2 cache: 512K (XEN) CPU: Physical Processor ID: 0 (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (12) available (XEN) CPU0: Thermal monitoring enabled (XEN) CPU0: Intel(R) Xeon(TM) CPU 2.40GHz stepping 09 (XEN) Booting processor 1/1 eip 90000 (XEN) Initializing CPU#1 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K (XEN) CPU: L2 cache: 512K (XEN) CPU: Physical Processor ID: 0 (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#1. (XEN) CPU1: Intel P4/Xeon Extended MCE MSRs (12) available (XEN) CPU1: Thermal monitoring enabled (XEN) CPU1: Intel(R) Xeon(TM) CPU 2.40GHz stepping 09 (XEN) Total of 2 processors activated. (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 okay. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 2 CPUs: passed. (XEN) Platform timer is 1.193MHz PIT (XEN) Brought up 2 CPUs (XEN) Machine check exception polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Domain 0 kernel supports features = { 0000001f }. (XEN) Domain 0 kernel requires features = { 00000000 }. (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 3e000000->3f000000 (236249 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c04784bc (XEN) Init. ramdisk: c0479000->c0819e00 (XEN) Phys-Mach map: c081a000->c0904b64 (XEN) Start info: c0905000->c090546c (XEN) Page tables: c0906000->c090a000 (XEN) Boot stack: c090a000->c090b000 (XEN) TOTAL: c0000000->c0c00000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Dom0 has maximum 2 VCPUs (XEN) Initrd len 0x3a0e00, start at 0xc0479000 (XEN) Scrubbing Free RAM: ...........done. (XEN) Xen trace buffers: disabled (XEN) ********************************************** (XEN) ******* WARNING: CONSOLE OUTPUT IS SYCHRONOUS (XEN) ******* This option is intended to aid debugging of Xen by ensuring (XEN) ******* that all output is synchronously delivered on the serial line. (XEN) ******* However it can introduce SIGNIFICANT latencies and affect (XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) #5 SMP Sun Oct 15 13:23:34 BST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000003b2d9000 (usable) 114MB HIGHMEM available. 831MB LOWMEM available. found SMP MP-table at 000f64d0 DMI present. ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24]) IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47 ACPI: IOAPIC (id[0x04] address[0xfec80400] gsi_base[48]) IOAPIC[2]: apic_id 4, version 32, address 0xfec80400, GSI 48-71 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Enabling APIC mode: Flat. Using 3 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000) Built 1 zonelists Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0,9600 console=tty0 selinux=0 ramdisk_size=32758 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 9363.144 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB enabled: Aperture: 2 megabytes Kernel range: 0x00000000c09ff000 - 0x00000000c0bff000 vmalloc area: f4800000-fb7fe000, maxmem 33ffe000 Memory: 940104k/969572k available (1955k kernel code, 20672k reserved, 752k data, 188k init, 117612k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5542.50 BogoMIPS (lpj=27712530) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Checking ''hlt'' instruction... OK. ENABLING IO-APIC IRQs Enabling SMP... Initializing CPU#1 Brought up 2 CPUs migration_cost=9 checking if image is initramfs... it is Freeing initrd memory: 3715k freed Grant table initialized NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 1180-11bf claimed by ICH4 GPIO PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 *10 11 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *10 11 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 10 11 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 *11 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 *11 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 *10 11 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 13 devices xen_mem: Initialising balloon driver. PCI: Using ACPI for IRQ routing PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a report PCI: Bridge: 0000:01:1d.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:01:1f.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:02.0 IO window: disabled. MEM window: fc100000-fc1fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1e.0 IO window: 7000-7fff MEM window: fc200000-fdffffff PREFETCH window: 50000000-500fffff Simple Boot Flag at 0x35 set to 0x1 IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1162307471.039:1): initialized highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Floppy drive(s): fd0 is 1.44M Timer ISR/0: Time went backwards: delta=-10041940 delta_cpu=19958060 shadow=6488683338 off=800829825 processed=7299554859 cpu_processed=7269554859 0: 7269554859 1: 7295880586 FDC 0 is a post-1991 82077 Timer ISR/0: Time went backwards: delta=-17181583 delta_cpu=12818417 shadow=6488683338 off=883690089 processed=7389554859 cpu_processed=7359554859 0: 7359554859 1: 7385880586 Timer ISR/0: Time went backwards: delta=-556197212 delta_cpu=73802788 shadow=6488683338 off=954674426 processed=7999554859 cpu_processed=7369554859 0: 7369554859 1: 7995880586 Timer ISR/0: Time went backwards: delta=-119906257 delta_cpu=590093743 shadow=7985138870 off=44510018 processed=8149554859 cpu_processed=7439554859 0: 7439554859 1: 8145880586 Timer ISR/0: Time went backwards: delta=-130717103 delta_cpu=149282897 shadow=7985138870 off=193699150 processed=8309554859 cpu_processed=8029554859 0: 8029554859 1: 8305880586 Timer ISR/0: Time went backwards: delta=-140704093 delta_cpu=159295907 shadow=7985138870 off=343712209 processed=8469554859 cpu_processed=8169554859 0: 8169554859 1: 8465880586 Timer ISR/0: Time went backwards: delta=-140691522 delta_cpu=159308478 shadow=7985138870 off=493724725 processed=8619554859 cpu_processed=8319554859 0: 8319554859 1: 8615880586 Timer ISR/0: Time went backwards: delta=-150677760 delta_cpu=159322240 shadow=7985138870 off=643738489 processed=8779554859 cpu_processed=8469554859 0: 8469554859 1: 8775880586 Timer ISR/0: Time went backwards: delta=-150664958 delta_cpu=159335042 shadow=7985138870 off=793751291 processed=8929554859 cpu_processed=8619554859 0: 8619554859 1: 8925880586 Timer ISR/0: Time went backwards: delta=-160321852 delta_cpu=159678148 shadow=7985138870 off=944094397 processed=9089554859 cpu_processed=8769554859 0: 8769554859 1: 9085880586 RAMDISK driver initialized: 16 RAM disks of 32758K size 1024 blocksize loop: loaded (max 8 devices) Xen virtual console successfully installed as ttyS0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 2 input: AT Translated Set 2 keyboard as /class/input/input0 logips2pp: Detected unknown logitech mouse model 1 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 NET: Registered protocol family 17 input: PS/2 Logitech Mouse as /class/input/input1 Using IPI No-Shortcut mode Freeing unused kernel memory: 188k freed *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is ** ** slow. To ensure full performance you should ** ** install a ''xen-friendly'' (nosegneg) version of ** ** the library, or disable tls support by executing ** ** the following as root: ** ** mv /lib/tls /lib/tls.disabled ** ** Offending process: init (pid=1) ** *************************************************************** *************************************************************** Pausing... 5 Pausing... 4 <4>printk: 53 messages suppressed. Timer ISR/0: Time went backwards: delta=-130007508 delta_cpu=49992492 shadow=11558657534 off=771780783 processed=12429554859 cpu_processed=12249554859 0: 12249554859 1: 12425880586 Pausing... 3 Pausing... 2 Pausing... 1 Continuing... device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com Kernel panic - not syncing: Attempted to kill init! (XEN) Domain 0 crashed: rebooting machine in 5 seconds. *** XEN 3.0.3 DEMO CD - WORKS (Debian Dom0 non-text mode) Linux version 2.6.16.29-xen (apeace@paploo) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Mon Oct 16 12:11:52 BST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000003b4b9000 (usable) 220MB HIGHMEM available. 727MB LOWMEM available. On node 0 totalpages: 242873 DMA zone: 186366 pages, LIFO batch:31 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 0 pages, LIFO batch:0 HighMem zone: 56507 pages, LIFO batch:15 found SMP MP-table at 000f64d0 DMI present. ACPI: RSDP (v000 PTLTD ) @ 0x000f6500 ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x3fef8674 ACPI: FADT (v001 Intel SE7501CW 0x06040000 PTL 0x00000008) @ 0x3fefbe94 ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @ 0x3fefbf08 ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x3fefbf88 ACPI: SPCR (v001 PTLTD $UCRTBL$ 0x06040000 PTL 0x00000001) @ 0x3fefbfb0 ACPI: DSDT (v001 INTEL PLUMAS 0x06040000 MSFT 0x0100000e) @ 0x00000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24]) IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47 ACPI: IOAPIC (id[0x04] address[0xfec80400] gsi_base[48]) IOAPIC[2]: apic_id 4, version 32, address 0xfec80400, GSI 48-71 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 3 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000) Built 1 zonelists Kernel command line: ro selinux=0 ramdisk_size=32758 image=rootfs.img boot=cow quiet Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 2392.094 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB enabled: Aperture: 2 megabytes Kernel range: 0x00000000c1afb000 - 0x00000000c1cfb000 vmalloc area: ee000000-f51fe000, maxmem 2d7fe000 Memory: 933788k/971492k available (1922k kernel code, 28792k reserved, 724k data, 188k init, 226028k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4788.12 BogoMIPS (lpj=23940615) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebd3f1 00000000 00000000 00000000 00004400 00000000 00000000 CPU: After vendor identify, caps: bfebd3f1 00000000 00000000 00000000 00004400 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: After all inits, caps: bfebd3f1 00000000 00000000 00000080 00004400 00000000 00000000 Checking ''hlt'' instruction... OK. ENABLING IO-APIC IRQs Enabling SMP... Initializing CPU#1 Brought up 2 CPUs migration_cost=6 checking if image is initramfs... it is Freeing initrd memory: 11250k freed Grant table initialized NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 1180-11bf claimed by ICH4 GPIO PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Boot video device is 0000:04:03.0 PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 *10 11 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *10 11 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 10 11 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 *11 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 *11 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 *10 11 14 15) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.ICH3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HLB_.Z000._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HLB_.Z001._PRT] Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 13 devices xen_mem: Initialising balloon driver. PCI: Using ACPI for IRQ routing PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a report PCI: Bridge: 0000:01:1d.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:01:1f.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:02.0 IO window: disabled. MEM window: fc100000-fc1fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1e.0 IO window: 7000-7fff MEM window: fc200000-fdffffff PREFETCH window: 50000000-500fffff PCI: Setting latency timer of device 0000:00:1e.0 to 64 Simple Boot Flag at 0x35 set to 0x1 IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1162292863.160:1): initialized highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 32758K size 1024 blocksize loop: loaded (max 128 devices) Xen virtual console successfully installed as ttyS0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 2 input: AT Translated Set 2 keyboard as /class/input/input0 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode Freeing unused kernel memory: 188k freed logips2pp: Detected unknown logitech mouse model 1 dm_mod: no version for "struct_module" found: kernel tainted. device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com input: PS/2 Logitech Mouse as /class/input/input1 e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI e100: Copyright(c) 1999-2005 Intel Corporation ACPI: PCI Interrupt 0000:04:04.0[A] -> GSI 20 (level, low) -> IRQ 16 e100: eth0: e100_probe: addr 0xfc241000, irq 16, MAC addr 00:02:B3:EA:66:32 usbcore: registered new driver usbfs usbcore: registered new driver hub Intel(R) PRO/1000 Network Driver - version 6.3.9-k4-NAPI Copyright (c) 1999-2005 Intel Corporation. ACPI: PCI Interrupt 0000:04:05.0[A] -> GSI 23 (level, low) -> IRQ 17 e1000: 0000:04:05.0: e1000_probe: (PCI:33MHz:32-bit) 00:02:b3:ea:66:57 e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection ICH3: IDE controller at PCI slot 0000:00:1f.1 ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 ICH3: chipset revision 2 ICH3: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x6c60-0x6c67, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x6c68-0x6c6f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... USB Universal Host Controller Interface driver v2.3 hda: WDC WD1200JB-00FUA0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: SAMSUNG CD-ROM SH-152A, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 19 PCI: Setting latency timer of device 0000:00:1d.0 to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 19, io base 0x00006c00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected hda: max request size: 512KiB hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100) hda: cache flushes supported hda: hda1 hda2 hdc: ATAPI 52X CD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20 PCI: Setting latency timer of device 0000:00:1d.1 to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 20, io base 0x00006c20 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.2: irq 18, io base 0x00006c40 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ISO 9660 Extensions: Microsoft Joliet Level 3 Unable to load NLS charset utf8 Unable to load NLS charset utf8 ISO 9660 Extensions: RRIP_1991A ISO 9660 Extensions: Microsoft Joliet Level 3 Unable to load NLS charset utf8 Unable to load NLS charset utf8 ISO 9660 Extensions: RRIP_1991A Real Time Clock Driver v1.12ac MC: drivers/edac/edac_mc.c version edac_mc Ver: 2.0.0 Oct 16 2006 tolm = 40000, remapbase = ffc000, remaplimit = 0 EDAC MC0: Giving out device to "e7xxx_edac" E7501: PCI 0000:00:00.0 ts: Compaq touchscreen protocol output input: PC Speaker as /class/input/input2 parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled 8250_pnp: Unknown symbol serial8250_unregister_port 8250_pnp: Unknown symbol serial8250_register_port hw_random hardware driver 1.0.0 loaded 8250_pnp: Unknown symbol serial8250_unregister_port 8250_pnp: Unknown symbol serial8250_register_port *** LSPCI OUTPUT (WHEN RUNNING NON-XEN KERNEL) # lspci -v 00:00.0 Host bridge: Intel Corporation E7501 Memory Controller Hub (rev 01) Flags: bus master, fast devsel, latency 0 Capabilities: [40] Vendor Specific Information 00:00.1 Class ff00: Intel Corporation E7500/E7501 Host RASUM Controller (rev 01) Subsystem: Intel Corporation Unknown device 3425 Flags: fast devsel 00:02.0 PCI bridge: Intel Corporation E7500/E7501 Hub Interface B PCI-to-PCI Bridge (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, fast devsel, latency 32 Bus: primary=00, secondary=01, subordinate=03, sec-latency=0 Memory behind bridge: fc100000-fc1fffff 00:02.1 Class ff00: Intel Corporation E7500/E7501 Hub Interface B RASUM Controller (rev 01) Subsystem: Intel Corporation Unknown device 3425 Flags: fast devsel 00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev 02) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, medium devsel, latency 0, IRQ 17 I/O ports at 6c00 [size=32] 00:1d.1 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #2) (rev 02) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 6c20 [size=32] 00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #3) (rev 02) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at 6c40 [size=32] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 42) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=32 I/O behind bridge: 00007000-00007fff Memory behind bridge: fc200000-fdffffff Prefetchable memory behind bridge: 50000000-500fffff 00:1f.0 ISA bridge: Intel Corporation 82801CA LPC Interface Controller (rev 02) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corporation 82801CA Ultra ATA Storage Controller (rev 02) (prog- if 8a [Master SecP PriP]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at <unassigned> I/O ports at <unassigned> I/O ports at <unassigned> I/O ports at <unassigned> I/O ports at 6c60 [size=16] Memory at 50100000 (32-bit, non-prefetchable) [size=1K] 00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 02) Subsystem: Intel Corporation Unknown device 3425 Flags: medium devsel I/O ports at 1100 [size=32] 01:1c.0 PIC: Intel Corporation 82870P2 P64H2 I/OxAPIC (rev 04) (prog-if 20 [IO(X)-APIC]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, 66MHz, fast devsel, latency 0 Memory at fc100000 (32-bit, non-prefetchable) [size=4K] Capabilities: [50] PCI-X non-bridge device 01:1d.0 PCI bridge: Intel Corporation 82870P2 P64H2 Hub PCI Bridge (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, fast devsel, latency 40 Bus: primary=01, secondary=02, subordinate=02, sec-latency=64 Capabilities: [50] PCI-X bridge device 01:1e.0 PIC: Intel Corporation 82870P2 P64H2 I/OxAPIC (rev 04) (prog-if 20 [IO(X)-APIC]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, 66MHz, fast devsel, latency 0 Memory at fc101000 (32-bit, non-prefetchable) [size=4K] Capabilities: [50] PCI-X non-bridge device 01:1f.0 PCI bridge: Intel Corporation 82870P2 P64H2 Hub PCI Bridge (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, fast devsel, latency 40 Bus: primary=01, secondary=03, subordinate=03, sec-latency=64 Capabilities: [50] PCI-X bridge device 04:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA]) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, stepping, medium devsel, latency 66, IRQ 11 Memory at fd000000 (32-bit, non-prefetchable) [size=16M] I/O ports at 7000 [size=256] Memory at fc240000 (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 50000000 [disabled] [size=128K] Capabilities: [5c] Power Management version 2 04:04.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 0d) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, medium devsel, latency 66, IRQ 20 Memory at fc241000 (32-bit, non-prefetchable) [size=4K] I/O ports at 7400 [size=64] Memory at fc200000 (32-bit, non-prefetchable) [size=128K] Capabilities: [dc] Power Management version 2 04:05.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) Subsystem: Intel Corporation Unknown device 3425 Flags: bus master, 66MHz, medium devsel, latency 52, IRQ 19 Memory at fc220000 (32-bit, non-prefetchable) [size=128K] I/O ports at 7440 [size=64] Capabilities: [dc] Power Management version 2 Capabilities: [e4] PCI-X non-bridge device Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users