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

Re: [Xen-devel] qemu-3.0 fails with staging


  • To: 'Olaf Hering' <olaf@xxxxxxxxx>, "'xen-devel@xxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxx>
  • From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
  • Date: Thu, 9 Aug 2018 10:22:51 +0000
  • Accept-language: en-GB, en-US
  • Delivery-date: Thu, 09 Aug 2018 10:22:55 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHUL7/uPI/yyax+Z0yph+rPtq8Ux6S3NUpAgAAA1eA=
  • Thread-topic: [Xen-devel] qemu-3.0 fails with staging

> -----Original Message-----
> From: Paul Durrant
> Sent: 09 August 2018 11:22
> To: 'Olaf Hering' <olaf@xxxxxxxxx>; xen-devel@xxxxxxxxxxxxx
> Subject: RE: [Xen-devel] qemu-3.0 fails with staging
> 
> > -----Original Message-----
> > From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On
> Behalf
> > Of Olaf Hering
> > Sent: 09 August 2018 10:03
> > To: xen-devel@xxxxxxxxxxxxx
> > Subject: [Xen-devel] qemu-3.0 fails with staging
> >
> > This domU.cfg fails for me with staging+qemu-3.0, but qemu-2.12 happens
> to
> > work:
> >
> > name='fv'
> > serial='pty'
> > vcpus='4'
> > memory='8888'
> > disk=[ 'vdev=xvda, format=raw, access=rw,
> > target=/nfs_vmimages/disk0.raw' ]
> > vif=[ 'bridge=br0,mac=3e:27:63:30:c0:46,type=vif' ]
> > builder="hvm"
> > device_model_version="qemu-xen"
> > device_model_override='/usr/lib64/qemu-3.0/bin/qemu-system-i386'
> >
> > libxl: error: libxl_dm.c:2429:device_model_spawn_outcome: Domain
> > 3:domain 3 device model: spawn failed (rc=-3)
> > libxl: error: libxl_create.c:1566:domcreate_devmodel_started: Domain
> > 3:device model did not start: -3
> > libxl: error: libxl_dm.c:2543:kill_device_model: Device Model already exited
> > libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 3:Non-
> > existant domain
> > libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 3:Unable
> to
> > destroy guest
> > libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 3:Destruction
> of
> > domain failed
> >
> >
> > tail: '/var/log/xen/qemu-dm-fv.log' has been replaced;  following new file
> > qemu-system-i386: -serial pty: char device redirected to /dev/pts/5 (label
> > serial0)
> > xenforeignmemory: error: ioctl failed: Invalid argument
> > qemu-system-i386: failed to map ioreq server resources: error 22
> > handle=0x561c17027040
> > qemu-system-i386: xen hardware virtual machine initialisation failed
> >
> >
> > Does it actually work for anyone? I think there is an OSS-TEST for
> > qemu.git#master.
> > I have to debug something else, so can not actually look further at this
> point.
> >
> 
> That sounds like an issue with direct resource map and privcmd. QEMU
> should be falling back to the old scheme gracefully though. What version of
> Xen was QEMU built against (I'm assuming it is also running on the same
> version) and what dom0 kernel version are you using? I can try to repro.
> 

Oh sorry, I see the xen version is just staging. Still need the dom0 kernel 
version though.

  Paul

>   Paul
> 
> >
> > Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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