[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] PVHVM example for xen 4.3.1


  • To: Wei Liu <wei.liu2@xxxxxxxxxx>
  • From: johnnadre <johnnadre@xxxxxxxx>
  • Date: Sun, 05 Jan 2014 12:30:54 -0800
  • Cc: xen-users@xxxxxxxxxxxxx
  • Delivery-date: Sun, 05 Jan 2014 20:32:09 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:cc:message-id:in-reply-to:references:subject:mime-version:content-type:user-agent; b=ZFJrSKobCoz/usyUPUbqCR1FeYCIrr7eRTWp/1O1cqlYzEs3ws8EWeSpoDOnIvPBpXylik5vcvHt GeClac7S0c/xtuwCz/sxiLtKvGm1V8K4Q3OyaAJVG7FB9Js0Jbpr
  • List-id: Xen user discussion <xen-users.lists.xen.org>

---- On Fri, 27 Dec 2013 06:14:38 -0800 Wei Liu  wrote ---- 

>On Wed, Dec 25, 2013 at 06:56:14PM -0800, johnnadre wrote: 
>> 
>> Hello, 
>> 
>> 
>> I'm looking for an example configuration for a PVHVM domU that works with 
>> 4.3.1. The one at http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers 
>> causes 3 warnings and some errors: 
>> 
>> WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" 
>> instead if you really want a non-default firmware 
> 
>You have kernel= option in your config file which is not necessary. 
> 
>> WARNING: ignoring device_model directive. 
> 
>You have device_model= option in your config file which is not 
>necessary. 
> 
>> WARNING: Use "device_model_override" instead if you really want a 
>> non-default device_model 
>> xc: info: VIRTUAL MEMORY ARRANGEMENT: 
>> Loader: 0000000000100000->000000000019ed04 
>> Modules: 0000000000000000->0000000000000000 
>> TOTAL: 0000000000000000->000000000f800000 
>> ENTRY ADDRESS: 0000000000100000 
>> xc: info: PHYSICAL MEMORY ALLOCATION: 
>> 4KB PAGES: 0x0000000000000200 
>> 2MB PAGES: 0x000000000000007b 
>> 1GB PAGES: 0x0000000000000000 
>> libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 2 device 
>> model: spawn failed (rc=-3) 
>> libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model 
>> did not start: -3 
>> libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model 
>> already exited 
>> 
>> If I follow the suggestions in the warning messages and specify 
>> firmware_override and device_model_override like so: 
>> 
>> firmware_override = "/usr/lib64/xen/boot/hvmloader" 
>> device_model_override = '/usr/lib64/xen/bin/qemu-dm' 
>> 
> 
>You don't need these lines. 
> 
>> 
>> it only removes some of the warnings but not the errors: 
>> 
>> WARNING: device model override given without specific DM version 
>> same errors as above 
>> 
>> 
>> Does anybody have a config that works or any idea what's wrong with my 
>> config? 
>> 
>> One more noteworthy thing: 
>> 
>> # cat /var/log/xen/qemu-dm-auth.log 
>> /usr/lib64/xen/bin/qemu-dm: invalid option -- '-xen-domid' 
>> 
> 
>You overrided device_model with qemu-dm, but xl passes -xen-domid 
>which only works for qemu upstream. 
> 
>If you want to use qemu traditional, you should use 
>device_model_version="qemu-xen-traditional" then xl will arrange 
>everything for you. 
> 
>Wei. 
>

Thanks a lot, it works now!


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.