Problems booting VM using unified Xen kernel

Problems booting VM using unified Xen kernel

[David F. Barrera]

I am having trouble booting a guest domain using the unified Xen kernel (it
works fine when using the XenU kernel). Whenever I try to create the domain, I get
the following message: 

bl2-1:/tmp/xen # xm create -c vm1.cfg
Using config file "vm1.cfg".
Error: (9, 'Bad file descriptor')


---------------------------------
The build was done using 'make world' and 'make install', and there were no
build errors:

Xen version 3.0-unstable (root@ltc.austin.ibm.com <mailto:root@ltc.austin.ibm.com>) (gcc version 3.3.3 (SuSE
Linux)) Wed May  3 14:23:44 CDT 2006
 Latest ChangeSet: Wed May  3 07:33:01 2006 +0100 9920:915d5af5dc18
-----------
'strace' shows that files are missing:

stat("/usr/lib64/python/xen/xm/signal", 0x7fffffe08e40) = -1 ENOENT (No such
file or directory)
open("/usr/lib64/python/xen/xm/signal.so", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/lib64/python/xen/xm/signalmodule.so", O_RDONLY) = -1 ENOENT (No such
file or directory)
open("/usr/lib64/python/xen/xm/signal.py", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/lib64/python/xen/xm/signal.pyc", O_RDONLY) = -1 ENOENT (No such file
or directory)
futex(0x501680, FUTEX_WAKE, 1)          = 0
write(2, "Error:", 6Error:)                   = 6
write(2, " ", 1 )                        = 1
write(2, "(9, \'Bad file descriptor\')", 26(9, 'Bad file descriptor')) = 26
write(2, "\n", 1

----------------------------------------

domU config file:

kernel = "/boot/vmlinuz-2.6-xen"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.16-xen"
# The domain build function. Default is 'linux'.
builder='linux'
# Initial memory allocation (in megabytes) for the new domain.
memory = 256
# A name for your domain. All domains must have different names.
name = "vm1"
disk = [ 'phy:sdb3,0813,w','phy:sdb2,0812,w' ]
# Set if you want dhcp to allocate the IP address.
# vif = [ 'mac= AA:00:00:47:CB:34, bridge=xen-br0' ]
vif = [ '' ]
# Set root device.
root = "/dev/sdb3 ro"

-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                       Euripides

Re: Problems booting VM using unified Xen kernel (x86_64)

[David F. Barrera]

I need to pint out that I am seeing this problem only on an x86_64 
machine. i386 is working as expected.

-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                       Euripides




David F. Barrera wrote:

> I am having trouble booting a guest domain using the unified Xen 
> kernel (it
> works fine when using the XenU kernel). Whenever I try to create the 
> domain, I get
> the following message:
> bl2-1:/tmp/xen # xm create -c vm1.cfg
> Using config file "vm1.cfg".
> Error: (9, 'Bad file descriptor')
>
>
> ---------------------------------
> The build was done using 'make world' and 'make install', and there 
> were no
> build errors:
>
> Xen version 3.0-unstable (root@ltc.austin.ibm.com 
> <mailto:root@ltc.austin.ibm.com>) (gcc version 3.3.3 (SuSE
> Linux)) Wed May  3 14:23:44 CDT 2006
> Latest ChangeSet: Wed May  3 07:33:01 2006 +0100 9920:915d5af5dc18
> -----------
> 'strace' shows that files are missing:
>
> stat("/usr/lib64/python/xen/xm/signal", 0x7fffffe08e40) = -1 ENOENT 
> (No such
> file or directory)
> open("/usr/lib64/python/xen/xm/signal.so", O_RDONLY) = -1 ENOENT (No 
> such file
> or directory)
> open("/usr/lib64/python/xen/xm/signalmodule.so", O_RDONLY) = -1 ENOENT 
> (No such
> file or directory)
> open("/usr/lib64/python/xen/xm/signal.py", O_RDONLY) = -1 ENOENT (No 
> such file
> or directory)
> open("/usr/lib64/python/xen/xm/signal.pyc", O_RDONLY) = -1 ENOENT (No 
> such file
> or directory)
> futex(0x501680, FUTEX_WAKE, 1)          = 0
> write(2, "Error:", 6Error:)                   = 6
> write(2, " ", 1 )                        = 1
> write(2, "(9, \'Bad file descriptor\')", 26(9, 'Bad file descriptor')) 
> = 26
> write(2, "\n", 1
>
> ----------------------------------------
>
> domU config file:
>
> kernel = "/boot/vmlinuz-2.6-xen"
> # Optional ramdisk.
> ramdisk = "/boot/initrd-2.6.16-xen"
> # The domain build function. Default is 'linux'.
> builder='linux'
> # Initial memory allocation (in megabytes) for the new domain.
> memory = 256
> # A name for your domain. All domains must have different names.
> name = "vm1"
> disk = [ 'phy:sdb3,0813,w','phy:sdb2,0812,w' ]
> # Set if you want dhcp to allocate the IP address.
> # vif = [ 'mac= AA:00:00:47:CB:34, bridge=xen-br0' ]
> vif = [ '' ]
> # Set root device.
> root = "/dev/sdb3 ro"
>

Re: Problems booting VM using unified Xen kernel (x86_64)

[David F. Barrera]

Actually, I need to retract that last statement. I am seeing this same 
problem on a SLES 9 SP3 based i386 machine. The x86_64 is also SLES 9 
SP3 based.

-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                       Euripides




David F. Barrera wrote:

> I need to pint out that I am seeing this problem only on an x86_64 
> machine. i386 is working as expected.
>