Re: [Xen-users] xen 3.0.4 - 22, 'Invalid argument' when starting domain.

[Håkan <xenhberg@xxxxxxxxxxxxx>]

xensource@xxxxxxxxxx wrote:
> Thanks for this answer.
> 
> However it didn't helped me. I feel a bit lost now. I really don't know what 
> to do...
> I don't know how to set or not PAE and how to check if it's enabled, but to 
> be 
> sure I rebuild a domU kernel with the same sources as dom0. And I got exactly 
> the same error. Only my dom0 boots correctly, not my domUs.
> 
> Here are additionnal informations :
> 
> When restarting xend, I have these strange lines in my /var/log/messages 
> logfile, however this does not prevent xend to work correctly. (At least for 
> the xm list command)
> 
> # /var/log/messages
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: blktapctrl: v1.0.0
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: Found driver: [raw image (aio)]
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: Found driver: [raw image (sync)]
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: Found driver: [vmware image (vmdk)]
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: Found driver: [ramdisk image (ram)]
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: Found driver: [qcow disk (qcow)]
> Feb 20 21:15:08 homer BLKTAPCTRL[18731]: Unable to start blktapctrl

I had a similar problem when I upgraded from 3.0.3 to 3.0.4. In my domU
config files I had
cpus = ""
which caused 3.0.4 to give me a "Invalid argument" (if I recall
correctly), upon running xm create.
Commenting this out helped for me.


/Håkan

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