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@xxxxxxxxx>
> Subject: 3.0.2 domu files not working on 3.0.3
> To: XenUsers <xen-users@xxxxxxxxxxxxxxxxxxx>
>
> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home