Fwd: 3.0.2 domu files not working on 3.0.3

Fwd: 3.0.2 domu files not working on 3.0.3

[jdsw]

[-- Attachment #1.1: Type: text/plain, Size: 148 bytes --]

any ideas ? (did not get response on xen-users list)
/Jd


 
---------------------------------
Access over 1 million songs - Yahoo! Music Unlimited.

[-- Attachment #1.2: Type: text/html, Size: 244 bytes --]

[-- Attachment #2: Type: message/rfc822, Size: 6261 bytes --]

[-- Attachment #2.1.1.1: Type: text/plain, Size: 929 bytes --]

Hi
   I have the following file, which is not working on 3.0.3. I am on a HVM capable machine with xen 3.0.3 installed.
It fails with 

Using config file "/etc/xen/T1".
Error: (22, 'Invalid argument')

--------
ramdisk = '/var/cache/xenman/anaconda_install/initrd.default'
kernel = '/var/cache/xenman/anaconda_install/vmlinuz.default'
#vif = ''
name = 'T1'
on_reboot = 'destroy'
on_crash = 'destroy'
memory = 256
disk = ['file:/mnt/images/dom_disks/T1.disk.xm,hda,w']
-----
I tried it with vif = "" and vif = [ '']  (similar to xmexample1)

The xend log file is attached.

Any ideas. 
a. I am assuming that on HVM capable machine, u can still run paravirtualized domUs

b. Where can I set of  changes in 3.0.3 ? (I remember reading about cdrom directive being changed...)

Thanks
/Jd


 
---------------------------------
Sponsored Link

For just $24.99/mo., Vonage offers unlimited local and long- distance calling. Sign up now.

[-- Attachment #2.1.1.2: Type: text/html, Size: 1105 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.1.2: 851806766-xend.log --]
[-- Type: text/x-log; name="xend.log", Size: 3240 bytes --]

[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'T1'], ['memory', 256], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['vcpus', 1], ['image', ['linux', ['kernel', '/var/cache/xenman/anaconda_install/vmlinuz.default'], ['ramdisk', '/var/cache/xenman/anaconda_install/initrd.default']]], ['device', ['vbd', ['uname', 'file:/mnt/images/dom_disks/T1.disk.xm'], ['dev', 'hda'], ['mode', 'w']]]])
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'T1'], ['memory', 256], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['vcpus', 1], ['image', ['linux', ['kernel', '/var/cache/xenman/anaconda_install/vmlinuz.default'], ['ramdisk', '/var/cache/xenman/anaconda_install/initrd.default']]], ['device', ['vbd', ['uname', 'file:/mnt/images/dom_disks/T1.disk.xm'], ['dev', 'hda'], ['mode', 'w']]]]
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': 'destroy', 'on_reboot': 'destroy', 'localtime': None, 'image': ['linux', ['kernel', '/var/cache/xenman/anaconda_install/vmlinuz.default'], ['ramdisk', '/var/cache/xenman/anaconda_install/initrd.default']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'T1', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 256, 'device': [('vbd', ['vbd', ['uname', 'file:/mnt/images/dom_disks/T1.disk.xm'], ['dev', 'hda'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:1253) XendDomainInfo.construct: None
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:1285) XendDomainInfo.initDomain: 12 1.0
[2006-11-07 15:13:20 xend 3528] DEBUG (balloon:127) Balloon: 262732 KiB free; need 262144; done.
[2006-11-07 15:13:20 xend 3528] INFO (image:136) buildDomain os=linux dom=12 vcpus=1
[2006-11-07 15:13:20 xend 3528] DEBUG (image:191) dom            = 12
[2006-11-07 15:13:20 xend 3528] DEBUG (image:192) image          = /var/cache/xenman/anaconda_install/vmlinuz.default
[2006-11-07 15:13:20 xend 3528] DEBUG (image:193) store_evtchn   = 1
[2006-11-07 15:13:20 xend 3528] DEBUG (image:194) console_evtchn = 2
[2006-11-07 15:13:20 xend 3528] DEBUG (image:195) cmdline        =
[2006-11-07 15:13:20 xend 3528] DEBUG (image:196) ramdisk        = /var/cache/xenman/anaconda_install/initrd.default
[2006-11-07 15:13:20 xend 3528] DEBUG (image:197) vcpus          = 1
[2006-11-07 15:13:20 xend 3528] DEBUG (image:198) features       =
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] ERROR (XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
  File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 195, in create
    vm.initDomain()
  File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 1363, in initDomain
    raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=12
[2006-11-07 15:13:20 xend.XendDomainInfo 3528] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(12)


[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[Keir Fraser]

[-- Attachment #1.1: Type: text/plain, Size: 522 bytes --]

Do you have /var/log/xen/xend-debug.log?

That may contain something useful.

 -- Keir

On 9/11/06 6:47 pm, "jdsw" <jdsw2002@yahoo.com> wrote:

> any ideas ? (did not get response on xen-users list)
> /Jd
> 
> 
>  
> 
> Access over 1 million songs - Yahoo! Music Unlimited.
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=36035/*http://music.yahoo.com
> /unlimited/> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



[-- Attachment #1.2: Type: text/html, Size: 1371 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[Ewan Mellor]

On Thu, Nov 09, 2006 at 10:47:35AM -0800, jdsw wrote:

> Hi
>    I have the following file, which is not working on 3.0.3. I am on a HVM
> capable machine with xen 3.0.3 installed.
> It fails with
> 
> Using config file "/etc/xen/T1".
> Error: (22, 'Invalid argument')
> 
> --------
> ramdisk = '/var/cache/xenman/anaconda_install/initrd.default'
> kernel = '/var/cache/xenman/anaconda_install/vmlinuz.default'
> #vif = ''
> name = 'T1'
> on_reboot = 'destroy'
> on_crash = 'destroy'
> memory = 256
> disk = ['file:/mnt/images/dom_disks/T1.disk.xm,hda,w']
> -----
> I tried it with vif = "" and vif = [ '']  (similar to xmexample1)
> 
> The xend log file is attached.
> 
> Any ideas.
> a. I am assuming that on HVM capable machine, u can still run
> paravirtualized domUs

Yes you can.

> b. Where can I set of  changes in 3.0.3 ? (I remember reading about cdrom
> directive being changed...)

The example file in the 3.0.3 release should show you what's current:
tools/examples/xmexample.hvm shows you the new CD-ROM format, for example.

I don't think this is your problem though.  I suspect that you are using an
old version of libxenctrl.  This library and your hypervisor need to be
matched, otherwise you will get weird errors like this.

If that's not it, please send "xm dmesg" and /var/log/xen/xend-debug.log.

HTH,

Ewan.

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[Daniel P. Berrange]

On Thu, Nov 09, 2006 at 10:47:35AM -0800, jdsw wrote:
> any ideas ? (did not get response on xen-users list)
>  
> ---------------------------------
> Access over 1 million songs - Yahoo! Music Unlimited.
> Date: Wed, 8 Nov 2006 07:43:47 -0800 (PST)
> From: jdsw <jdsw2002@yahoo.com>
> Subject: 3.0.2 domu files not working on 3.0.3
> To: XenUsers <xen-users@lists.xensource.com>
> 
> Hi
>    I have the following file, which is not working on 3.0.3. I am on a HVM capable machine with xen 3.0.3 installed.
> It fails with 
> 
> Using config file "/etc/xen/T1".
> Error: (22, 'Invalid argument')

This typically means the kernel being used for the guest is incompatible
with the hypervisor or Dom0 kernel. Common causes being PAE vs non-PAE
mismatch, or wrong archtecture, or using a baremetal kernel. The xend.log
or xend-debug.log may give you further details on the precise error.

> 
> --------
> ramdisk = '/var/cache/xenman/anaconda_install/initrd.default'
> kernel = '/var/cache/xenman/anaconda_install/vmlinuz.default'
> #vif = ''
> name = 'T1'
> on_reboot = 'destroy'
> on_crash = 'destroy'
> memory = 256
> disk = ['file:/mnt/images/dom_disks/T1.disk.xm,hda,w']
> -----
> I tried it with vif = "" and vif = [ '']  (similar to xmexample1)
> 
> The xend log file is attached.
> 
> Any ideas. 
> a. I am assuming that on HVM capable machine, u can still run paravirtualized domUs
> 
> b. Where can I set of  changes in 3.0.3 ? (I remember reading about cdrom directive being changed...)
> 

Regards,
Dan.

-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[jdsw]

[-- Attachment #1.1: Type: text/plain, Size: 3593 bytes --]

My machine has PAE and xen with PAE.

I got the domU kernel and ramdisk from one of the fedora mirror from under the xen directory.  From the xend-debug.log it seems you may be right, these may not be PAE kernels.

example site :
 ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/
 
 The errors in the debug file
 xend-debug.log
  ERROR: Unrecognized image format
  ERROR: Error constructing guest OS
  ERROR: Unrecognized image format
  ERROR: Error constructing guest OS
  
1. how do I determine, if the kernel is PAE enabled or not. 
a. when the system is running 
b. when I just have the kernel files as in this case ? 

I tried the kernel from /boot/vmlinuz-2.6-xen  (as this is supposed to work with domU and Dom0 both right ?)  I used the old initrd.
The error 22, Invalid argument is gone...and the domU starts  but it  crashes. (probably because of the mismatched initrd ?)

2. Where do I get PAE enabled Xen kernels where I can possibly kick of installation similar to bare metal ?
 
When I tried the following... 
http://www.xensource.com/download/dl_303guest_rhel4.html

#rpm -i kernel-xenU-2.6.9-42.0.2.EL.xs148.i686.rpm
error: Failed dependencies:
        kernel < 2.6.13 conflicts with kudzu-1.2.34.3-1.i386
        kernel < 2.6.12 conflicts with initscripts-8.31.5-1.i386
        kernel < 2.6.15 conflicts with hal-0.5.7.1-2.fc5.i386

#uname -a 
Linux test 2.6.16.29-xen #4 SMP Sun Oct 15 13:20:46 BST 2006 i686 athlon i386 GNU/Linux

What are my options ? Any pointers ?

Thanks
/Jd

"Daniel P. Berrange" <berrange@redhat.com> wrote: On Thu, Nov 09, 2006 at 10:47:35AM -0800, jdsw wrote:
> any ideas ? (did not get response on xen-users list)
>  
> ---------------------------------
> Access over 1 million songs - Yahoo! Music Unlimited.
> Date: Wed, 8 Nov 2006 07:43:47 -0800 (PST)
> From: jdsw 
> Subject: 3.0.2 domu files not working on 3.0.3
> To: XenUsers 
> 
> Hi
>    I have the following file, which is not working on 3.0.3. I am on a HVM capable machine with xen 3.0.3 installed.
> It fails with 
> 
> Using config file "/etc/xen/T1".
> Error: (22, 'Invalid argument')

This typically means the kernel being used for the guest is incompatible
with the hypervisor or Dom0 kernel. Common causes being PAE vs non-PAE
mismatch, or wrong archtecture, or using a baremetal kernel. The xend.log
or xend-debug.log may give you further details on the precise error.

> 
> --------
> ramdisk = '/var/cache/xenman/anaconda_install/initrd.default'
> kernel = '/var/cache/xenman/anaconda_install/vmlinuz.default'
> #vif = ''
> name = 'T1'
> on_reboot = 'destroy'
> on_crash = 'destroy'
> memory = 256
> disk = ['file:/mnt/images/dom_disks/T1.disk.xm,hda,w']
> -----
> I tried it with vif = "" and vif = [ '']  (similar to xmexample1)
> 
> The xend log file is attached.
> 
> Any ideas. 
> a. I am assuming that on HVM capable machine, u can still run paravirtualized domUs
> 
> b. Where can I set of  changes in 3.0.3 ? (I remember reading about cdrom directive being changed...)
> 

Regards,
Dan.

-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel


 
---------------------------------
Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.

[-- Attachment #1.2: Type: text/html, Size: 4504 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[Daniel P. Berrange]

On Thu, Nov 09, 2006 at 01:53:54PM -0800, jdsw wrote:
> My machine has PAE and xen with PAE.
> 
> I got the domU kernel and ramdisk from one of the fedora mirror from under the xen directory.  From the xend-debug.log it seems you may be right, these may not be PAE kernels.
> 
> example site :
>  ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/
>  
>  The errors in the debug file
>  xend-debug.log
>   ERROR: Unrecognized image format
>   ERROR: Error constructing guest OS
>   ERROR: Unrecognized image format
>   ERROR: Error constructing guest OS
>   
> 1. how do I determine, if the kernel is PAE enabled or not. 
> a. when the system is running 
> b. when I just have the kernel files as in this case ? 

For Fedora the naming of the kernel tells you. The non-PAE kernels are
called kernel-xenU / kernel-xen0, while the PAE kernels are kernel-xen.
FC5 was non-PAE, but FC6 is PAE.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[Keir Fraser]

[-- Attachment #1.1: Type: text/plain, Size: 862 bytes --]

The error ³Unrecognized image format² means you didn¹t even get as far as
checking PAE vs non-PAE, or 64-bit vs 32-bit. The image wasn¹t recognised as
an Elf image at all. Perhaps you grabbed a native kernel image by mistake? A
valid Xen kernel image should be Elf or gzipped Elf. You might want to
confirm that (try gunzipping it, then try Œreadelf¹ on the result).

 -- Keir

On 9/11/06 9:53 pm, "jdsw" <jdsw2002@yahoo.com> wrote:

> I got the domU kernel and ramdisk from one of the fedora mirror from under the
> xen directory.  From the xend-debug.log it seems you may be right, these may
> not be PAE kernels.
> 
> example site :
>  ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/
>  
>  The errors in the debug file
>  xend-debug.log
>   ERROR: Unrecognized image format
>   ERROR: Error constructing guest OS



[-- Attachment #1.2: Type: text/html, Size: 1518 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Fwd: 3.0.2 domu files not working on 3.0.3

[jdsw]

[-- Attachment #1.1: Type: text/plain, Size: 1614 bytes --]

Keir/Daniel

oops.
The mirror had problems so it was a wrong file. (some 404 html).
Got the correct files now the error is meaningful.

ERROR: Non PAE-kernel on PAE host.
ERROR: Error constructing guest OS

This  kind of mismatch is irrelavent in HVM case, right ? i.e. I can install non-pae HVM DomUs on PAE Dom0 machines ?

Also, got kernels from FC6 and the DomU is starting.  :)

(This is not related to this thread.. but now the installation does not detect any drivers to do either network or CDROM installation)
Thanks
/Jd

Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3     The error &#8220;Unrecognized image format&#8221; means you didn&#8217;t even get as far as checking PAE vs non-PAE, or 64-bit vs 32-bit. The image wasn&#8217;t recognised as an Elf image at all. Perhaps you grabbed a native kernel image by mistake? A valid Xen kernel image should be Elf or gzipped Elf. You might want to confirm that (try gunzipping it, then try &#8216;readelf&#8217; on the result).
 
  -- Keir
 
 On 9/11/06 9:53 pm, "jdsw" <jdsw2002@yahoo.com> wrote:
 
 I got the domU kernel and ramdisk from one of the fedora mirror from under the xen directory.  From the xend-debug.log it seems you may be right, these may not be PAE kernels.
 
 example site :
  ftp://mirror.eas.muohio.edu/fedora/linux/core/5/i386/os/images/xen/
  
  The errors in the debug file
  xend-debug.log
   ERROR: Unrecognized image format
   ERROR: Error constructing guest OS
 
  

 
---------------------------------
Want to start your own business? Learn how on Yahoo! Small Business.

[-- Attachment #1.2: Type: text/html, Size: 2410 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel