xen-unstable: Qemu upstream domUs not start on Wheezy

xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

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-tp5505409p5505409.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Stefano Stabellini]

On Wed, 22 Feb 2012, 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.

Please post your qemu log file (/var/log/xen/qemu-dm-PRECISEHVM.log

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

#/var/log/xen/qemu-dm-PRECISEHVM.log
bind(unix:/var/run/xen/qmp-libxl-2): No such file or directory
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.

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Ian Campbell]

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@lists.xen.org
> http://lists.xen.org/xen-devel

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

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.

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

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-tp5505409p5507438.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

Does Xen and all of its parts (include qemu upstream) has debug on build-time
enabled by default or must be enabled?

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

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Stefano Stabellini]

On Fri, 24 Feb 2012, Fantu wrote:
> Does Xen and all of its parts (include qemu upstream) has debug on build-time
> enabled by default or must be enabled?

Yes, they are enabled by default.
Unfortunately from the log you posted in the previous email I am not
sure what could cause QEMU to fail opening the unix socket in
/var/run/xen.

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

Stefano Stabellini-3 wrote
> 
> On Fri, 24 Feb 2012, Fantu wrote:
>> Does Xen and all of its parts (include qemu upstream) has debug on
>> build-time
>> enabled by default or must be enabled?
> 
> Yes, they are enabled by default.
> Unfortunately from the log you posted in the previous email I am not
> sure what could cause QEMU to fail opening the unix socket in
> /var/run/xen.
> 

Problem found, /var/run/xen is erased at every reboot, probably by Wheezy.


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

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Ian Campbell]

On Tue, 2012-03-06 at 08:51 -0500, Fantu wrote:
> Stefano Stabellini-3 wrote
> > 
> > On Fri, 24 Feb 2012, Fantu wrote:
> >> Does Xen and all of its parts (include qemu upstream) has debug on
> >> build-time
> >> enabled by default or must be enabled?
> > 
> > Yes, they are enabled by default.
> > Unfortunately from the log you posted in the previous email I am not
> > sure what could cause QEMU to fail opening the unix socket in
> > /var/run/xen.
> > 
> 
> Problem found, /var/run/xen is erased at every reboot, probably by Wheezy.

/var/run is a tmpfs these days, I think and its been reasonably common
for distros to clear it out on boot more or less aggressively for some
time.

I think the xencommons initscript should be made to mkdir /var/run/xen
on every boot, or everything in Xen which needs it needs to be made to
mkdir it as necessary (which would be a pain).

Can you knock up a patch to add the mkdir to the initscript please?

Ian.

Re: xen-unstable: Qemu upstream domUs not start on Wheezy

[Fantu]

Ian Campbell-10 wrote
> 
> /var/run is a tmpfs these days, I think and its been reasonably common
> for distros to clear it out on boot more or less aggressively for some
> time.
> 
> I think the xencommons initscript should be made to mkdir /var/run/xen
> on every boot, or everything in Xen which needs it needs to be made to
> mkdir it as necessary (which would be a pain).
> 
> Can you knock up a patch to add the mkdir to the initscript please?
> 
> Ian.
> 
Patch done and sent:
http://xen.1045712.n5.nabble.com/PATCH-tools-hotplug-Linux-init-d-create-var-run-xen-if-not-exists-td5544288.html

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