From: Jerone Young <jyoung5@us.ibm.com>
To: Anand Gupta <xen.mails@gmail.com>
Cc: xen-devel@lists.xensource.com,
Harry Butterworth <harry@hebutterworth.freeserve.co.uk>,
Xen Users <Xen-users@lists.xensource.com>,
Andi Kleen <ak@suse.de>
Subject: Re: [Xen-devel] Re: need to compile 32bit on x86_64 cpu
Date: Thu, 22 Jun 2006 15:57:57 -0500 [thread overview]
Message-ID: <1151009877.3543.2.camel@localhost.localdomain> (raw)
In-Reply-To: <acb757c00606221348y3a033d6fpcbd9d6eef2b82d5b@mail.gmail.com>
If you are using paravirutal Xen (which I believe you are). You "cannot"
use a 32-bit Xen domU kernel with it. You have you use 64-bit Xen domU
kernel with it. I can tell by the path you are using 64bit Xen
"/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py". Best to stick with 32-bit Xen if you want to run 32bit domUs.
On Fri, 2006-06-23 at 02:18 +0530, Anand Gupta wrote:
> I finally got the compilation done and copied the kernel and init
> image for use for domU for 32bit OS.
>
> When i try to use the kernel i get an error "Error: (9, 'Bad file
> descriptor')"
>
> Here is the extract from xend.log,
>
> [2006-06-22 13:33:16 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
> XendDomainInfo.handleShutdownWatch
> [2006-06-22 13:33:16 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
> XendDomainInfo.handleShutdownWatch
> [2006-06-22 13:33:30 xend.XendDomainInfo] INFO (XendDomainInfo:836)
> Domain has shutdown: name=anand01 id=5 reason=poweroff.
> [2006-06-22 13:33:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
> XendDomainInfo.destroy : domid=5
> [2006-06-22 13:33:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
> XendDomainInfo.destroyDomain(5)
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
> XendDomainInfo.create(['vm', ['name', 'anand01'], ['memory', 256],
> ['vcpus', 1], ['image', ['linux', ['kernel', '/home/vmlinuz-
> 2.6.16.13-xen-x86_32'], ['ramdisk',
> '/home/initrd-2.6.16-xen-x86_32.img'], ['ip',
> 'x.x.x.x:1.2.3.4:y.y.y.y:255.255.255.128::eth0:off'], ['root',
> '/dev/sda1 ro'], ['args', 'selinux=0 3']]], ['device', ['vbd',
> ['uname', 'phy:/dev/vg01/anand01'], ['dev', 'sda1'], ['mode', 'w']]],
> ['device', ['vbd', ['uname', 'phy:/dev/vg01/anand01-swap'], ['dev',
> 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip', ' x.x.x.x'],
> ['mac', '00:16:00:18:99:FB'], ['vifname', 'anand01'], ['bridge',
> 'xenbr0']]]])
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:284)
> parseConfig: config is ['vm', ['name', 'anand01'], ['memory', 256],
> ['vcpus', 1], ['image', ['linux', ['kernel', '/home/vmlinuz-
> 2.6.16.13-xen-x86_32'], ['ramdisk',
> '/home/initrd-2.6.16-xen-x86_32.img'], ['ip',
> 'x.x.x.x:1.2.3.4:y.y.y.y:255.255.255.128::eth0:off'], ['root',
> '/dev/sda1 ro'], ['args', 'selinux=0 3']]], ['device', ['vbd',
> ['uname', 'phy:/dev/vg01/anand01'], ['dev', 'sda1'], ['mode', 'w']]],
> ['device', ['vbd', ['uname', 'phy:/dev/vg01/anand01-swap'], ['dev',
> 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip', ' x.x.x.x'],
> ['mac', '00:16:00:18:99:FB'], ['vifname', 'anand01'], ['bridge',
> 'xenbr0']]]]
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:380)
> parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash':
> None, 'on_reboot': None, 'image': ['linux', ['kernel', '/home/vmlinuz-
> 2.6.16.13-xen-x86_32'], ['ramdisk',
> '/home/initrd-2.6.16-xen-x86_32.img'], ['ip',
> 'x.x.x.x:1.2.3.4:y.y.y.y:255.255.255.128::eth0:off'], ['root',
> '/dev/sda1 ro'], ['args', 'selinux=0 3']], 'on_poweroff': None,
> 'cpus': None, 'name': 'anand01', 'backend': [], 'vcpus': 1,
> 'cpu_weight': None, 'vcpu_avail': None, 'memory': 256, 'device':
> [('vbd', ['vbd', ['uname', 'phy:/dev/vg01/anand01'], ['dev', 'sda1'],
> ['mode', 'w']]), ('vbd', ['vbd', ['uname',
> 'phy:/dev/vg01/anand01-swap'], ['dev', 'sda2'], ['mode', 'w']]),
> ('vif', ['vif', ['ip', ' x.x.x.x'], ['mac', '00:16:00:18:99:FB'],
> ['vifname', 'anand01'], ['bridge', 'xenbr0']])], 'bootloader': None,
> 'cpu': None, 'maxmem': None}
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
> XendDomainInfo.construct : None 0
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196)
> XendDomainInfo.initDomain: 6 1.0
> [2006-06-22 13:34:10 xend] DEBUG (balloon:126) Balloon: free 257; need
> 257; done.
> [2006-06-22 13:34:10 xend] INFO (image:135) buildDomain os=linux dom=6
> vcpus=1
> [2006-06-22 13:34:10 xend] DEBUG (image:173) dom = 6
> [2006-06-22 13:34:10 xend] DEBUG (image:174) image
> = /home/vmlinuz-2.6.16.13-xen-x86_32
> [2006-06-22 13:34:10 xend] DEBUG (image:175) store_evtchn = 1
> [2006-06-22 13:34:10 xend] DEBUG (image:176) console_evtchn = 2
> [2006-06-22 13:34:10 xend] DEBUG (image:177) cmdline =
> ip=x.x.x.x:1.2.3.4:y.y.y.y:255.255.255.128::eth0:off root=/dev/sda1 ro
> selinux=0 3
> [2006-06-22 13:34:10 xend] DEBUG (image:178) ramdisk
> = /home/initrd- 2.6.16-xen-x86_32.img
> [2006-06-22 13:34:10 xend] DEBUG (image:179) vcpus = 1
> [2006-06-22 13:34:10 xend] DEBUG (image:180) features =
> [2006-06-22 13:34:10 xend.XendDomainInfo] ERROR (XendDomainInfo:190)
> Domain construction failed
> Traceback (most recent call last):
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", line 183, in create
> vm.initDomain()
> File
> "/home/xen/xen-3.0.2-2 /dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1225, in initDomain
> channel_details = self.image.createImage()
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/image.py", line 118, in createImage
> return self.createDomain()
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/image.py", line 137, in createDomain
> result = self.buildDomain()
> File
> "/home/xen/xen-3.0.2-2 /dist/install/usr/lib64/python/xen/xend/image.py", line 188, in buildDomain
> features = self.features)
> error: (9, 'Bad file descriptor')
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
> XendDomainInfo.destroy: domid=6
> [2006-06-22 13:34:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
> XendDomainInfo.destroyDomain(6)
> [2006-06-22 13:34:10 xend] ERROR (xmlrpclib2:124) (9, 'Bad file
> descriptor')
> Traceback (most recent call last):
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/util/xmlrpclib2.py", line 103, in _marshaled_dispatch
> response = self._dispatch(method, params)
> File "/usr/lib64/python2.3/SimpleXMLRPCServer.py", line 407, in
> _dispatch
> return func(*params)
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/server/XMLRPCServer.py", line 63, in domain_create
> info = XendDomain.instance().domain_create(config)
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/XendDomain.py", line 227, in domain_create
> dominfo = XendDomainInfo.create(config)
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", line 183, in create
> vm.initDomain()
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1225, in initDomain
> channel_details = self.image.createImage()
> File "/home/xen/xen-
> 3.0.2-2/dist/install/usr/lib64/python/xen/xend/image.py", line 118, in
> createImage
> return self.createDomain()
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/image.py", line 137, in createDomain
> result = self.buildDomain()
> File
> "/home/xen/xen-3.0.2-2/dist/install/usr/lib64/python/xen/xend/image.py", line 188, in buildDomain
> features = self.features)
> error: (9, 'Bad file descriptor')
>
> This probably would mean that the kernel compiled is a non xen
> kernel ? (Please correct me if i am wrong)
>
> I used the following to compile the kernel (after i used setarch
> linux32 bash)
>
> make linux-2.6-xen-config CONFIGMODE=menuconfig
> make linux-2.6-xen-build
>
> I then copied the dist/install/lib/modules to /lib/modules and then
> used depmod and mkinitrd to create the initrd image. Moved the kernel
> from dist/install/boot to /home where i call them from inside the
> config files.
>
> Can anyone tell me how to resolve the above problem ?
>
> --
> regards,
>
> Anand Gupta
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-06-22 20:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 14:16 need to compile 32bit on x86_64 cpu Anand Gupta
2006-06-22 14:24 ` Harald Schioeberg
2006-06-22 14:36 ` [Xen-users] " Anand Gupta
2006-06-22 14:28 ` Harry Butterworth
2006-06-22 15:10 ` Keir Fraser
2006-06-22 16:41 ` [Xen-devel] " Anand Gupta
2006-06-22 16:57 ` Anand Gupta
2006-06-22 17:02 ` Re: [Xen-devel] " Petersson, Mats
2006-06-22 17:00 ` Petersson, Mats
2006-06-22 17:06 ` Anand Gupta
2006-06-22 17:15 ` Harry Butterworth
2006-06-22 17:33 ` [Xen-devel] " Anand Gupta
2006-06-22 17:16 ` Andi Kleen
2006-06-22 17:36 ` Anand Gupta
2006-06-22 17:52 ` Andi Kleen
2006-06-22 17:54 ` Anand Gupta
2006-06-22 18:06 ` Andi Kleen
2006-06-22 18:36 ` Anand Gupta
2006-06-22 20:48 ` Anand Gupta
2006-06-22 20:57 ` Jerone Young [this message]
2006-06-22 21:25 ` [Xen-devel] " Anand Gupta
2006-06-22 21:34 ` Petersson, Mats
2006-06-22 21:43 ` [Xen-users] " Anand Gupta
2006-06-22 17:44 ` Anand Gupta
2006-06-22 17:56 ` Luciano Miguel Ferreira Rocha
2006-06-22 18:08 ` Anand Gupta
2006-06-22 18:03 ` Anand Gupta
2006-06-22 18:10 ` Re: [Xen-devel] " Petersson, Mats
2006-06-22 15:13 ` Hans-Christian Armingeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1151009877.3543.2.camel@localhost.localdomain \
--to=jyoung5@us.ibm.com \
--cc=Xen-users@lists.xensource.com \
--cc=ak@suse.de \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen.mails@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.