Re: [Xen-devel] Fwd: 3.0.2 domu files not working on 3.0.3

[Ewan Mellor <ewan@xxxxxxxxxxxxx>]

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.

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