Re: [Xen-devel] xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu <fantonifabio@xxxxxxxxxx>]

Thanks for reply.

ls /var/run/xen
xenconsoled.pid  xen-hotplug/     xenstored/       xenstored.pid


Ian Campbell-10 wrote
> 
> On Thu, 2012-02-23 at 08:49 +0000, Fantu wrote:
>> #/var/log/xen/qemu-dm-PRECISEHVM.log
>> bind(unix:/var/run/xen/qmp-libxl-2): No such file or directory
> 
> Does /var/run/xen exist? IIRC this was an issue in some versions of the
> Wheezy packages.
> 
> BTW, please could you try and quote some context in each of your posts
> for those of us not reading via nabble. As it stands your posts are very
> hard to follow due to the lack of context -- that requires me us skip up
> and down the thread to figure out what is going on -- which, at least in
> my case, makes it all the more likely that I'll get distracted by
> something else.
> 
> In fact I would encourage you to post using a normal email client rather
> than nabble -- you can subscribe, so that your posts go straight through
> without moderation, but disable mail delivery in your mailman options if
> you don't want to receive the full firehose of xen-devel -- we always CC
> people with replies on this list so you won't miss anything in threads
> which you start.
> 
> Ian.
> 
>> chardev: opening backend "socket" failed: No such file or directory
>> 
>> --
>> View this message in context:
>> http://xen.1045712.n5.nabble.com/xen-unstable-Qemu-upstream-domUs-not-start-on-Wheezy-tp5505409p5507375.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@.xen
>> http://lists.xen.org/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 

Fantu wrote
> 
> Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from
> xen-unstable.hg changeset 24858:a88ba599add1 plus these patch for not fail
> build:
> http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html
> And also this change for lib patch modified with multiarch support:
> vi config/StdGNU.mk
> LIBLEAFDIR_x86_64 ?= lib
> 
> DomUs PV working, domUs with qemu-upstream not start.
> 
> The xl configuration file:
> ---------------------------------
> name='PRECISEHVM'
> builder="hvm"
> memory=1024
> vcpus=2
> hap=1
> pae=1
> acpi=1
> apic=1
> nx=1
> vif=['bridge=xenbr0']
> #vfb=['vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap="it"']
> disk=['/mnt/vm/disks/PRECISEHVM.disk1.xm,raw,hda,rw',
> '/dev/sr0,raw,hdb,ro,cdrom']
> boot='c'
> xen_platform_pci=1
> device_model_version='qemu-xen'
> vnc=1
> vncunused=1
> vnclisten="0.0.0.0"
> keymap="it"
> #stdvga=1
> #videoram=16
> sdl=0
> #spice=1
> #spicehost='192.168.1.137'
> #spiceport=6000
> #spicepasswd='test'
> #on_crash='preserve'
> ---------------------------------
> 
> xl create /etc/xen/PRECISEHVM.cfg
> Parsing config file /etc/xen/PRECISEHVM.cfg
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019dc88
>   TOTAL:         0000000000000000->000000003f800000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x00000000000001fb
>   1GB PAGES: 0x0000000000000000
> libxl: error: libxl_qmp.c:638:libxl__qmp_initialize: Connection error: No
> such file or directory
> libxl: error: libxl_exec.c:200:libxl__wait_for_offspring: Device Model
> died during startup
> libxl: error: libxl_create.c:602:do_domain_create: device model did not
> start: -1
> 
> The same with change only device_model_version to qemu-xen-traditional
> work
> 
> 
> If you need more test and data ask me and I will do and post.
> Thanks for any reply and sorry for bad english.
> 

--
View this message in context: 
http://xen.1045712.n5.nabble.com/xen-unstable-Qemu-upstream-domUs-not-start-on-Wheezy-tp5505409p5507435.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

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