The alias has device_type as "type-PCI"
pci_alias = {"name": "QuickAssist", "product_id": "0435", "vendor_id": "8086",
"device_type": "type-PCI"}
But from the maria DB output, you can see that the devices are "type-PF".
Please change the device_type in the alias if you intend to attach physical
Hi Moshe,
Thank you for your response. Did not find any errors in nova-compute log.
Here goes the output.
2016-06-07 02:10:45.181 118672 INFO nova.compute.resource_tracker
[req-5f0325a6-2dd8-4a25-b518-9143cc0aac0c - - - - -] Auditing locally
available compute resources for node localhost
2016
Can you look if you have errors in the nova-computes log?
Also check if you passed the PciPassthroughFilter in the nova-scheduler log
From: Chinmaya Dwibedy [mailto:ckdwib...@gmail.com]
Sent: Tuesday, June 07, 2016 8:29 AM
To: openstack@lists.openstack.org
Subject: [Openstack] Issue with assignm
Hi All,
I want the Intel’s QAT Card to be used for PCI Passthrough device. But to
implement PCI-passthrough, when I launch a VM using a flavor configured for
passthrough, it gives the below errors in nova-conductor.log and instance
goes into Error state. Note that, I have installed
openstack-m
it’s a permissions issue,
check cinder.conf for nfs..
check the logs see what it says when you try to mount it automatically.. if
you rebooted do you have the nfs mount automatically ? is it in the fstab?
Remo
> On Jun 6, 2016, at 01:14, Jean-Pierre Ribeauville
> wrote:
>
> Hi,
>
> I jus
Good it works!
Althought I still encourage to look at devstack and any kind of VM.
Best regards,
Darek
> On Jun 5, 2016, at 11:40 PM, shivkumar gupta
> wrote:
>
> Hello Derek,
>
> Issue got resolved after re-installation of cygwin64 actually i missed one
> package during earlier installatio
Hi,
I added a channel device within an instance while this one is shutoff. ( via
virsh edit ).
When the instance is restarted , this device has been removed from the
instance configuration .
How may I avoid this and have this channel persistent ?
Thx for help.
Regards,
Jean-Pierre RIBEAUV
Hi Eugen,
Yes I think I was mixing it up.
I've used the Mitaka guide now.
Got past orchestra now.
Can't get the telemetry to work. Keeps giving me a blank list.
[root@controller ceilometer]# ceilometer meter-list
+--+--+--+-+-++
| Name | Type | Unit |
Hi,
I just disable it :
>sestatus
SELinux status: disabled
>
But mount still fails :
mount: wrong fs type, bad option, bad superblock on ….
Regards,
J.P.
From: Remo Mattei [mailto:r...@italy1.com]
Sent: lundi 6 juin 2016 10:03
To: Jean-Pierre Ribeauville
Cc: openstack@lists.
Hi,
I just launch an instance by using Fedora-cloud-23-2015 image. ( booted from
image )
Now , I try to mount a NFS directory ; I got following error :
mount: wrong fs type, bad option, bad superblock on
I try to mount this directory on the compute node itself ; it's O.K.
I use Liberty
Do you have selinux enabled?
Inviato da iPhone
> Il giorno 06 giu 2016, alle ore 00:53, Jean-Pierre Ribeauville
> ha scritto:
>
> Hi,
>
> I just launch an instance by using Fedora-cloud-23-2015 image. ( booted from
> image )
>
> Now , I try to mount a NFS directory ; I got following er
Hi Michael,
your statements regarding the Openstack version don't fit.
I've been following the install guide found at
http://docs.openstack.org/juno/install-guide/install/yum/content/ch_preface.html
and
I've only just started the openstack installation a couple of weeks
ago. So I'm using t
12 matches
Mail list logo
