June 30, 201511 yr Solution: Adjustments for AMD hardware to the syslinux.cfg file were still needed and not mentioned in the wiki. append amd_iommu=on iommu=pt iommu=1 vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream initrd=/bzroot The above fixed my issue allowing me to pass my only GPU through to a VM. Problem: I did some searching on the topic, not finding any results. I remember reading something to the effect of this ONCE. Anyone remember what I'm talking about and know how to look it up or have the link handy? Edit 1 (aka I fail at troubleshooting as the night grows late): I'm trying to make a Kodibuntu VM on my AMD system: CPU: AMD FX 6300 MB: Biostar TA970 (v5.0-5.2) RAM: 8GB DDR3 PCIEx16: XFX One AMD 5450 PCIEx1: RocketRaid 2xxx (four port controller, quick boot BIOS, full) PCIEx4: SuperMicro AOC-SASLP-MV8 2xSAS (full) My VM config (needed larger than 4G, ignore that): The error: Edit 2: IOMMU Groups: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:02.0 /sys/kernel/iommu_groups/2/devices/0000:00:04.0 /sys/kernel/iommu_groups/3/devices/0000:00:09.0 /sys/kernel/iommu_groups/4/devices/0000:00:11.0 /sys/kernel/iommu_groups/5/devices/0000:00:12.0 /sys/kernel/iommu_groups/5/devices/0000:00:12.2 /sys/kernel/iommu_groups/6/devices/0000:00:13.0 /sys/kernel/iommu_groups/6/devices/0000:00:13.2 /sys/kernel/iommu_groups/7/devices/0000:00:14.0 /sys/kernel/iommu_groups/8/devices/0000:00:14.1 /sys/kernel/iommu_groups/9/devices/0000:00:14.3 /sys/kernel/iommu_groups/10/devices/0000:00:14.4 /sys/kernel/iommu_groups/11/devices/0000:00:14.5 /sys/kernel/iommu_groups/12/devices/0000:00:15.0 /sys/kernel/iommu_groups/12/devices/0000:00:15.1 /sys/kernel/iommu_groups/12/devices/0000:00:15.2 /sys/kernel/iommu_groups/12/devices/0000:06:00.0 /sys/kernel/iommu_groups/12/devices/0000:07:00.0 /sys/kernel/iommu_groups/13/devices/0000:00:16.0 /sys/kernel/iommu_groups/13/devices/0000:00:16.2 /sys/kernel/iommu_groups/14/devices/0000:01:00.0 /sys/kernel/iommu_groups/14/devices/0000:01:00.1 /sys/kernel/iommu_groups/15/devices/0000:02:00.0 /sys/kernel/iommu_groups/16/devices/0000:03:00.0
June 30, 201511 yr I used your subject line as a search and got 10 results, but don't know if any of them are what you're looking for. See search tips in my sig.
June 30, 201511 yr I did some searching on the topic, not finding any results. I remember reading something to the effect of this ONCE. Anyone remember what I'm talking about and know how to look it up or have the link handy? Can you explain what you're trying to accomplish? Might be easier to help you.
June 30, 201511 yr Author Can you explain what you're trying to accomplish? Might be easier to help you. Sorry, I'm trying to make a Kodibuntu VM on my AMD system. Biostar 970 with SecureVM and IOMMU enabled in BIOS with a 5450 in the x16 PCIE slot. My config (booted in VNC mode, need larger than 4G, ignore that): The error:
June 30, 201511 yr Ok, first, go to the Tools -> System Devices page, and copy / paste the IOMMU groups section back here. It is possible that your GPU is bound to an IOMMU group with another in-use device (SATA, Ethernet, or USB controller). If that is the case, you can't assign the GPU to a VM without accepting some other potential risks. Another solution could be to move the card to another PCI slot and see if that puts it in a different group.
June 30, 201511 yr Author Ok, first, go to the Tools -> System Devices page, and copy / paste the IOMMU groups section back here. It is possible that your GPU is bound to an IOMMU group with another in-use device (SATA, Ethernet, or USB controller). If that is the case, you can't assign the GPU to a VM without accepting some other potential risks. Another solution could be to move the card to another PCI slot and see if that puts it in a different group. Well, I only have two x16 size slots (one x16, one x4) so moving it wouldn't net me anything. I may end up getting a PCIEx16 into x1 adapter and try that if you think that would be better. I can then move the RocketRaid card into the x16 and put it in the same IOMMU group as the SuperMicro card to make this cleaner all around.At this point, I'm committed to having a VM on this machine as I have to replace a HTPC without putting another machine in this room. The real trick will be seeing if I still have the low profile adapter. IOMMU Groups: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:02.0 /sys/kernel/iommu_groups/2/devices/0000:00:04.0 /sys/kernel/iommu_groups/3/devices/0000:00:09.0 /sys/kernel/iommu_groups/4/devices/0000:00:11.0 /sys/kernel/iommu_groups/5/devices/0000:00:12.0 /sys/kernel/iommu_groups/5/devices/0000:00:12.2 /sys/kernel/iommu_groups/6/devices/0000:00:13.0 /sys/kernel/iommu_groups/6/devices/0000:00:13.2 /sys/kernel/iommu_groups/7/devices/0000:00:14.0 /sys/kernel/iommu_groups/8/devices/0000:00:14.1 /sys/kernel/iommu_groups/9/devices/0000:00:14.3 /sys/kernel/iommu_groups/10/devices/0000:00:14.4 /sys/kernel/iommu_groups/11/devices/0000:00:14.5 /sys/kernel/iommu_groups/12/devices/0000:00:15.0 /sys/kernel/iommu_groups/12/devices/0000:00:15.1 /sys/kernel/iommu_groups/12/devices/0000:00:15.2 /sys/kernel/iommu_groups/12/devices/0000:06:00.0 /sys/kernel/iommu_groups/12/devices/0000:07:00.0 /sys/kernel/iommu_groups/13/devices/0000:00:16.0 /sys/kernel/iommu_groups/13/devices/0000:00:16.2 /sys/kernel/iommu_groups/14/devices/0000:01:00.0 /sys/kernel/iommu_groups/14/devices/0000:01:00.1 /sys/kernel/iommu_groups/15/devices/0000:02:00.0 /sys/kernel/iommu_groups/16/devices/0000:03:00.0
July 1, 201511 yr Do you have any plugins installed? You gpu is in an IOMMU group by itself, so that isn't what's causing the issue.
July 1, 201511 yr Author Just "Community Applications" by Squid/gfjardim/bergware. When I went to retail I did a fresh install (originally a 6b6 install).
July 1, 201511 yr Just "Community Applications" by Squid/gfjardim/bergware. When I went to retail I did a fresh install (originally a 6b6 install). Did you have the old VM Manager plugin from dmacias at one point when you were on 6b6?
July 1, 201511 yr Author Just "Community Applications" by Squid/gfjardim/bergware. When I went to retail I did a fresh install (originally a 6b6 install). Did you have the old VM Manager plugin from dmacias at one point when you were on 6b6? I shouldn't, I did a fresh install for the retail release of 6.0. /boot/config/plugins/ contains: community.applications dockerMan dynamix dynamix.apcupsd dynamix.kvm.manager community.applications.plg
July 1, 201511 yr Ok, in the dynamix.KVM.Manager folder, you should have a domain.img file. How big is that file?
July 1, 201511 yr Author Ok, in the dynamix.KVM.Manager folder, you should have a domain.img file. How big is that file? 3.7 MB
July 1, 201511 yr Hmm, ok, that's right... If you click "info" in the webgui, what does it say for IOMMU?
July 1, 201511 yr Author Hmm, ok, that's right... If you click "info" in the webgui, what does it say for IOMMU? It says "Enabled" as does HVM. I tried setting this whole thing up through the web GUI, no manual tweaking. Also tried not passing the GPU as a sound card.
July 1, 201511 yr Author Tried: Setting a manual ROM for the GPU per your sig link. Playing around with a passive x16 to x1 adapter, does not even boot. Even with an extra GPU in the mix. Setting PCIe ACS Override to On, didn't help. I'd be happy to play with some BIOS settings, but the manual and searching the internet don't reveal much information.
July 1, 201511 yr From a console session, type the following command: cat /etc/libvirt/libvirtd.conf Copy the contents displayed to a reply post here...
July 1, 201511 yr Author ################################################################# # # Authorization controls # # Flag to disable verification of our own server certificates # # When libvirtd starts it performs some sanity checks against # its own certificates. # # Default is to always run sanity checks. Uncommenting this # will disable sanity checks which is not a good idea #tls_no_sanity_certificate = 1 # Flag to disable verification of client certificates # # Client certificate verification is the primary authentication mechanism. # Any client which does not present a certificate signed by the CA # will be rejected. # # Default is to always verify. Uncommenting this will disable # verification - make sure an IP whitelist is set #tls_no_verify_certificate = 1 # A whitelist of allowed x509 Distinguished Names # This list may contain wildcards such as # # "C=GB,ST=London,L=London,O=Red Hat,CN=*" # # See the POSIX fnmatch function for the format of the wildcards. # # NB If this is an empty list, no client can connect, so comment out # entirely rather than using empty list to disable these checks # # By default, no DN's are checked #tls_allowed_dn_list = ["DN1", "DN2"] # A whitelist of allowed SASL usernames. The format for usernames # depends on the SASL authentication mechanism. Kerberos usernames # look like username@REALM # # This list may contain wildcards such as # # "*@EXAMPLE.COM" # # See the POSIX fnmatch function for the format of the wildcards. # # NB If this is an empty list, no client can connect, so comment out # entirely rather than using empty list to disable these checks # # By default, no Username's are checked #sasl_allowed_username_list = ["[email protected]", "[email protected]" ] ################################################################# # # Processing controls # # The maximum number of concurrent client connections to allow # over all sockets combined. #max_clients = 5000 # The maximum length of queue of connections waiting to be # accepted by the daemon. Note, that some protocols supporting # retransmission may obey this so that a later reattempt at # connection succeeds. #max_queued_clients = 1000 # The maximum length of queue of accepted but not yet not # authenticated clients. The default value is zero, meaning # the feature is disabled. #max_anonymous_clients = 20 # The minimum limit sets the number of workers to start up # initially. If the number of active clients exceeds this, # then more threads are spawned, up to max_workers limit. # Typically you'd want max_workers to equal maximum number # of clients allowed #min_workers = 5 #max_workers = 20 # The number of priority workers. If all workers from above # pool are stuck, some calls marked as high priority # (notably domainDestroy) can be executed in this pool. #prio_workers = 5 # Total global limit on concurrent RPC calls. Should be # at least as large as max_workers. Beyond this, RPC requests # will be read into memory and queued. This directly impacts # memory usage, currently each request requires 256 KB of # memory. So by default up to 5 MB of memory is used # # XXX this isn't actually enforced yet, only the per-client # limit is used so far #max_requests = 20 # Limit on concurrent requests from a single client # connection. To avoid one client monopolizing the server # this should be a small fraction of the global max_requests # and max_workers parameter #max_client_requests = 5 ################################################################# # # Logging controls # # Logging level: 4 errors, 3 warnings, 2 information, 1 debug # basically 1 will log everything possible #log_level = 3 # Logging filters: # A filter allows to select a different logging level for a given category # of logs # The format for a filter is one of: # x:name # x:+name # where name is a string which is matched against source file name, # e.g., "remote", "qemu", or "util/json", the optional "+" prefix # tells libvirt to log stack trace for each message matching name, # and x is the minimal level where matching messages should be logged: # 1: DEBUG # 2: INFO # 3: WARNING # 4: ERROR # # Multiple filters can be defined in a single @filters, they just need to be # separated by spaces. # # e.g. to only get warning or errors from the remote layer and only errors # from the event layer: #log_filters="3:remote 4:event" # Logging outputs: # An output is one of the places to save logging information # The format for an output can be: # x:stderr # output goes to stderr # x:syslog:name # use syslog for the output and use the given name as the ident # x:file:file_path # output to a file, with the given filepath # In all case the x prefix is the minimal level, acting as a filter # 1: DEBUG # 2: INFO # 3: WARNING # 4: ERROR # # Multiple outputs can be defined, they just need to be separated by spaces. # e.g. to log all warnings and errors to syslog under the libvirtd ident: #log_outputs="3:syslog:libvirtd" # # Log debug buffer size: # # This configuration option is no longer used, since the global # log buffer functionality has been removed. Please configure # suitable log_outputs/log_filters settings to obtain logs. #log_buffer_size = 64 ################################################################## # # Auditing # # This setting allows usage of the auditing subsystem to be altered: # # audit_level == 0 -> disable all auditing # audit_level == 1 -> enable auditing, only if enabled on host (default) # audit_level == 2 -> enable auditing, and exit if disabled on host # #audit_level = 2 # # If set to 1, then audit messages will also be sent # via libvirt logging infrastructure. Defaults to 0 # #audit_logging = 1 ################################################################### # UUID of the host: # Provide the UUID of the host here in case the command # 'dmidecode -s system-uuid' does not provide a valid uuid. In case # 'dmidecode' does not provide a valid UUID and none is provided here, a # temporary UUID will be generated. # Keep the format of the example UUID below. UUID must not have all digits # be the same. # NB This default all-zeros UUID will not work. Replace # it with the output of the 'uuidgen' command and then # uncomment this entry #host_uuid = "00000000-0000-0000-0000-000000000000" ################################################################### # Keepalive protocol: # This allows libvirtd to detect broken client connections or even # dead clients. A keepalive message is sent to a client after # keepalive_interval seconds of inactivity to check if the client is # still responding; keepalive_count is a maximum number of keepalive # messages that are allowed to be sent to the client without getting # any response before the connection is considered broken. In other # words, the connection is automatically closed approximately after # keepalive_interval * (keepalive_count + 1) seconds since the last # message received from the client. If keepalive_interval is set to # -1, libvirtd will never send keepalive requests; however clients # can still send them and the daemon will send responses. When # keepalive_count is set to 0, connections will be automatically # closed after keepalive_interval seconds of inactivity without # sending any keepalive messages. # #keepalive_interval = 5 #keepalive_count = 5 # # If set to 1, libvirtd will refuse to talk to clients that do not # support keepalive protocol. Defaults to 0. # #keepalive_required = 1 root@Server:~#
July 2, 201511 yr Author cat /etc/libvirt/qemu.conf # Master configuration file for the QEMU driver. # All settings described here are optional - if omitted, sensible # defaults are used. # VNC is configured to listen on 127.0.0.1 by default. # To make it listen on all public interfaces, uncomment # this next option. # # NB, strong recommendation to enable TLS + x509 certificate # verification when allowing public access # #vnc_listen = "0.0.0.0" # Enable this option to have VNC served over an automatically created # unix socket. This prevents unprivileged access from users on the # host machine, though most VNC clients do not support it. # # This will only be enabled for VNC configurations that do not have # a hardcoded 'listen' or 'socket' value. This setting takes preference # over vnc_listen. # #vnc_auto_unix_socket = 1 # Enable use of TLS encryption on the VNC server. This requires # a VNC client which supports the VeNCrypt protocol extension. # Examples include vinagre, virt-viewer, virt-manager and vencrypt # itself. UltraVNC, RealVNC, TightVNC do not support this # # It is necessary to setup CA and issue a server certificate # before enabling this. # #vnc_tls = 1 # Use of TLS requires that x509 certificates be issued. The # default it to keep them in /etc/pki/libvirt-vnc. This directory # must contain # # ca-cert.pem - the CA master certificate # server-cert.pem - the server certificate signed with ca-cert.pem # server-key.pem - the server private key # # This option allows the certificate directory to be changed # #vnc_tls_x509_cert_dir = "/etc/pki/libvirt-vnc" # The default TLS configuration only uses certificates for the server # allowing the client to verify the server's identity and establish # an encrypted channel. # # It is possible to use x509 certificates for authentication too, by # issuing a x509 certificate to every client who needs to connect. # # Enabling this option will reject any client who does not have a # certificate signed by the CA in /etc/pki/libvirt-vnc/ca-cert.pem # #vnc_tls_x509_verify = 1 # The default VNC password. Only 8 bytes are significant for # VNC passwords. This parameter is only used if the per-domain # XML config does not already provide a password. To allow # access without passwords, leave this commented out. An empty # string will still enable passwords, but be rejected by QEMU, # effectively preventing any use of VNC. Obviously change this # example here before you set this. # #vnc_password = "XYZ12345" # Enable use of SASL encryption on the VNC server. This requires # a VNC client which supports the SASL protocol extension. # Examples include vinagre, virt-viewer and virt-manager # itself. UltraVNC, RealVNC, TightVNC do not support this # # It is necessary to configure /etc/sasl2/qemu.conf to choose # the desired SASL plugin (eg, GSSPI for Kerberos) # #vnc_sasl = 1 # The default SASL configuration file is located in /etc/sasl2/ # When running libvirtd unprivileged, it may be desirable to # override the configs in this location. Set this parameter to # point to the directory, and create a qemu.conf in that location # #vnc_sasl_dir = "/some/directory/sasl2" # QEMU implements an extension for providing audio over a VNC connection, # though if your VNC client does not support it, your only chance for getting # sound output is through regular audio backends. By default, libvirt will # disable all QEMU sound backends if using VNC, since they can cause # permissions issues. Enabling this option will make libvirtd honor the # QEMU_AUDIO_DRV environment variable when using VNC. # #vnc_allow_host_audio = 0 # SPICE is configured to listen on 127.0.0.1 by default. # To make it listen on all public interfaces, uncomment # this next option. # # NB, strong recommendation to enable TLS + x509 certificate # verification when allowing public access # #spice_listen = "0.0.0.0" # Enable use of TLS encryption on the SPICE server. # # It is necessary to setup CA and issue a server certificate # before enabling this. # #spice_tls = 1 # Use of TLS requires that x509 certificates be issued. The # default it to keep them in /etc/pki/libvirt-spice. This directory # must contain # # ca-cert.pem - the CA master certificate # server-cert.pem - the server certificate signed with ca-cert.pem # server-key.pem - the server private key # # This option allows the certificate directory to be changed. # #spice_tls_x509_cert_dir = "/etc/pki/libvirt-spice" # The default SPICE password. This parameter is only used if the # per-domain XML config does not already provide a password. To # allow access without passwords, leave this commented out. An # empty string will still enable passwords, but be rejected by # QEMU, effectively preventing any use of SPICE. Obviously change # this example here before you set this. # #spice_password = "XYZ12345" # Enable use of SASL encryption on the SPICE server. This requires # a SPICE client which supports the SASL protocol extension. # # It is necessary to configure /etc/sasl2/qemu.conf to choose # the desired SASL plugin (eg, GSSPI for Kerberos) # #spice_sasl = 1 # The default SASL configuration file is located in /etc/sasl2/ # When running libvirtd unprivileged, it may be desirable to # override the configs in this location. Set this parameter to # point to the directory, and create a qemu.conf in that location # #spice_sasl_dir = "/some/directory/sasl2" # By default, if no graphical front end is configured, libvirt will disable # QEMU audio output since directly talking to alsa/pulseaudio may not work # with various security settings. If you know what you're doing, enable # the setting below and libvirt will passthrough the QEMU_AUDIO_DRV # environment variable when using nographics. # #nographics_allow_host_audio = 1 # Override the port for creating both VNC and SPICE sessions (min). # This defaults to 5900 and increases for consecutive sessions # or when ports are occupied, until it hits the maximum. # # Minimum must be greater than or equal to 5900 as lower number would # result into negative vnc display number. # # Maximum must be less than 65536, because higher numbers do not make # sense as a port number. # #remote_display_port_min = 5900 #remote_display_port_max = 65535 # VNC WebSocket port policies, same rules apply as with remote display # ports. VNC WebSockets use similar display <-> port mappings, with # the exception being that ports start from 5700 instead of 5900. # #remote_websocket_port_min = 5700 #remote_websocket_port_max = 65535 # The default security driver is SELinux. If SELinux is disabled # on the host, then the security driver will automatically disable # itself. If you wish to disable QEMU SELinux security driver while # leaving SELinux enabled for the host in general, then set this # to 'none' instead. It's also possible to use more than one security # driver at the same time, for this use a list of names separated by # comma and delimited by square brackets. For example: # # security_driver = [ "selinux", "apparmor" ] # # Notes: The DAC security driver is always enabled; as a result, the # value of security_driver cannot contain "dac". The value "none" is # a special value; security_driver can be set to that value in # isolation, but it cannot appear in a list of drivers. # #security_driver = "selinux" # If set to non-zero, then the default security labeling # will make guests confined. If set to zero, then guests # will be unconfined by default. Defaults to 1. #security_default_confined = 1 # If set to non-zero, then attempts to create unconfined # guests will be blocked. Defaults to 0. #security_require_confined = 1 # The user for QEMU processes run by the system instance. It can be # specified as a user name or as a user id. The qemu driver will try to # parse this value first as a name and then, if the name doesn't exist, # as a user id. # # Since a sequence of digits is a valid user name, a leading plus sign # can be used to ensure that a user id will not be interpreted as a user # name. # # Some examples of valid values are: # # user = "qemu" # A user named "qemu" # user = "+0" # Super user (uid=0) # user = "100" # A user named "100" or a user with uid=100 # #user = "root" # The group for QEMU processes run by the system instance. It can be # specified in a similar way to user. group = "users" # Whether libvirt should dynamically change file ownership # to match the configured user/group above. Defaults to 1. # Set to 0 to disable file ownership changes. #dynamic_ownership = 1 # What cgroup controllers to make use of with QEMU guests # # - 'cpu' - use for schedular tunables # - 'devices' - use for device whitelisting # - 'memory' - use for memory tunables # - 'blkio' - use for block devices I/O tunables # - 'cpuset' - use for CPUs and memory nodes # - 'cpuacct' - use for CPUs statistics. # # NB, even if configured here, they won't be used unless # the administrator has mounted cgroups, e.g.: # # mkdir /dev/cgroup # mount -t cgroup -o devices,cpu,memory,blkio,cpuset none /dev/cgroup # # They can be mounted anywhere, and different controllers # can be mounted in different locations. libvirt will detect # where they are located. # #cgroup_controllers = [ "cpu", "devices", "memory", "blkio", "cpuset", "cpuacct" ] # This is the basic set of devices allowed / required by # all virtual machines. # # As well as this, any configured block backed disks, # all sound device, and all PTY devices are allowed. # # This will only need setting if newer QEMU suddenly # wants some device we don't already know about. # cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc","/dev/hpet", "/dev/vfio/vfio", "/dev/vfio/1","/dev/vfio/2","/dev/vfio/3", "/dev/vfio/4","/dev/vfio/5","/dev/vfio/6", "/dev/vfio/7","/dev/vfio/8","/dev/vfio/9", "/dev/vfio/10","/dev/vfio/11","/dev/vfio/12", "/dev/vfio/13","/dev/vfio/14","/dev/vfio/15", "/dev/vfio/16","/dev/vfio/17","/dev/vfio/18", "/dev/vfio/19","/dev/vfio/20","/dev/vfio/21", "/dev/vfio/22","/dev/vfio/23","/dev/vfio/24", "/dev/vfio/25","/dev/vfio/26","/dev/vfio/27", "/dev/vfio/28","/dev/vfio/29","/dev/vfio/30", "/dev/vfio/31","/dev/vfio/32" ] # The default format for Qemu/KVM guest save images is raw; that is, the # memory from the domain is dumped out directly to a file. If you have # guests with a large amount of memory, however, this can take up quite # a bit of space. If you would like to compress the images while they # are being saved to disk, you can also set "lzop", "gzip", "bzip2", or "xz" # for save_image_format. Note that this means you slow down the process of # saving a domain in order to save disk space; the list above is in descending # order by performance and ascending order by compression ratio. # # save_image_format is used when you use 'virsh save' or 'virsh managedsave' # at scheduled saving, and it is an error if the specified save_image_format # is not valid, or the requested compression program can't be found. # # dump_image_format is used when you use 'virsh dump' at emergency # crashdump, and if the specified dump_image_format is not valid, or # the requested compression program can't be found, this falls # back to "raw" compression. # # snapshot_image_format specifies the compression algorithm of the memory save # image when an external snapshot of a domain is taken. This does not apply # on disk image format. It is an error if the specified format isn't valid, # or the requested compression program can't be found. # #save_image_format = "raw" #dump_image_format = "raw" #snapshot_image_format = "raw" # When a domain is configured to be auto-dumped when libvirtd receives a # watchdog event from qemu guest, libvirtd will save dump files in directory # specified by auto_dump_path. Default value is /var/lib/libvirt/qemu/dump # #auto_dump_path = "/var/lib/libvirt/qemu/dump" # When a domain is configured to be auto-dumped, enabling this flag # has the same effect as using the VIR_DUMP_BYPASS_CACHE flag with the # virDomainCoreDump API. That is, the system will avoid using the # file system cache while writing the dump file, but may cause # slower operation. # #auto_dump_bypass_cache = 0 # When a domain is configured to be auto-started, enabling this flag # has the same effect as using the VIR_DOMAIN_START_BYPASS_CACHE flag # with the virDomainCreateWithFlags API. That is, the system will # avoid using the file system cache when restoring any managed state # file, but may cause slower operation. # #auto_start_bypass_cache = 0 # If provided by the host and a hugetlbfs mount point is configured, # a guest may request huge page backing. When this mount point is # unspecified here, determination of a host mount point in /proc/mounts # will be attempted. Specifying an explicit mount overrides detection # of the same in /proc/mounts. Setting the mount point to "" will # disable guest hugepage backing. If desired, multiple mount points can # be specified at once, separated by comma and enclosed in square # brackets, for example: # # hugetlbfs_mount = ["/dev/hugepages2M", "/dev/hugepages1G"] # # The size of huge page served by specific mount point is determined by # libvirt at the daemon startup. # # NB, within this mount point, guests will create memory backing files # in a location of $MOUNTPOINT/libvirt/qemu # #hugetlbfs_mount = "/dev/hugepages" # Path to the setuid helper for creating tap devices. This executable # is used to create <source type='bridge'> interfaces when libvirtd is # running unprivileged. libvirt invokes the helper directly, instead # of using "-netdev bridge", for security reasons. #bridge_helper = "/usr/libexec/qemu-bridge-helper" # If clear_emulator_capabilities is enabled, libvirt will drop all # privileged capabilities of the QEmu/KVM emulator. This is enabled by # default. # # Warning: Disabling this option means that a compromised guest can # exploit the privileges and possibly do damage to the host. # #clear_emulator_capabilities = 1 # If enabled, libvirt will have QEMU set its process name to # "qemu:VM_NAME", where VM_NAME is the name of the VM. The QEMU # process will appear as "qemu:VM_NAME" in process listings and # other system monitoring tools. By default, QEMU does not set # its process title, so the complete QEMU command (emulator and # its arguments) appear in process listings. # #set_process_name = 1 # If max_processes is set to a positive integer, libvirt will use # it to set the maximum number of processes that can be run by qemu # user. This can be used to override default value set by host OS. # The same applies to max_files which sets the limit on the maximum # number of opened files. # #max_processes = 0 #max_files = 0 # mac_filter enables MAC addressed based filtering on bridge ports. # This currently requires ebtables to be installed. # #mac_filter = 1 # By default, PCI devices below non-ACS switch are not allowed to be assigned # to guests. By setting relaxed_acs_check to 1 such devices will be allowed to # be assigned to guests. # #relaxed_acs_check = 1 # If allow_disk_format_probing is enabled, libvirt will probe disk # images to attempt to identify their format, when not otherwise # specified in the XML. This is disabled by default. # # WARNING: Enabling probing is a security hole in almost all # deployments. It is strongly recommended that users update their # guest XML <disk> elements to include <driver type='XXXX'/> # elements instead of enabling this option. # #allow_disk_format_probing = 1 # In order to prevent accidentally starting two domains that # share one writable disk, libvirt offers two approaches for # locking files. The first one is sanlock, the other one, # virtlockd, is then our own implementation. Accepted values # are "sanlock" and "lockd". # #lock_manager = "lockd" # Set limit of maximum APIs queued on one domain. All other APIs # over this threshold will fail on acquiring job lock. Specially, # setting to zero turns this feature off. # Note, that job lock is per domain. # #max_queued = 0 ################################################################### # Keepalive protocol: # This allows qemu driver to detect broken connections to remote # libvirtd during peer-to-peer migration. A keepalive message is # sent to the daemon after keepalive_interval seconds of inactivity # to check if the daemon is still responding; keepalive_count is a # maximum number of keepalive messages that are allowed to be sent # to the daemon without getting any response before the connection # is considered broken. In other words, the connection is # automatically closed approximately after # keepalive_interval * (keepalive_count + 1) seconds since the last # message received from the daemon. If keepalive_interval is set to # -1, qemu driver will not send keepalive requests during # peer-to-peer migration; however, the remote libvirtd can still # send them and source libvirtd will send responses. When # keepalive_count is set to 0, connections will be automatically # closed after keepalive_interval seconds of inactivity without # sending any keepalive messages. # #keepalive_interval = 5 #keepalive_count = 5 # Use seccomp syscall whitelisting in QEMU. # 1 = on, 0 = off, -1 = use QEMU default # Defaults to -1. # #seccomp_sandbox = 1 # Override the listen address for all incoming migrations. Defaults to # 0.0.0.0, or :: if both host and qemu are capable of IPv6. #migration_address = "127.0.0.1" # The default hostname or IP address which will be used by a migration # source for transferring migration data to this host. The migration # source has to be able to resolve this hostname and connect to it so # setting "localhost" will not work. By default, the host's configured # hostname is used. #migration_host = "host.example.com" # Override the port range used for incoming migrations. # # Minimum must be greater than 0, however when QEMU is not running as root, # setting the minimum to be lower than 1024 will not work. # # Maximum must not be greater than 65535. # #migration_port_min = 49152 #migration_port_max = 49215 # Timestamp QEMU's log messages (if QEMU supports it) # # Defaults to 1. # #log_timestamp = 0
July 8, 201510 yr Author The only thing I can think of is that the GPU isn't being removed/detached from unRAID use.
July 8, 201510 yr The only thing I can think of is that the GPU isn't being removed/detached from unRAID use. Doubtful (as previous posts/testing suggests UnRaid does not bind those devices), however if you think so try stubbing it in your go file, and unRAID won't use it regardless. Edit:... I'm not sure if that means the VM manager will list it as available or not, if it doesn't then you'd have to manually add the entry of the GPU and sound card into the XML. Not that difficult, but you may not want to do that.
July 8, 201510 yr Have you ever been successful in getting this card to output? I ask this because if so, the card may just be "stuck" in some odd state. The error only complains about the GPU and not the sound portion of it. I have a GPU that doesn't like to reset for nothing, and will require a complete power off state to the server, pull power, wait....., power back on, all is well. IDK, it's worth a shot if you are out of options. At the time of testing (back in beta days) I believe I would receive similar errors for my issue with that card.
July 8, 201510 yr Author Have you ever been successful in getting this card to output? I ask this because if so, the card may just be "stuck" in some odd state. The error only complains about the GPU and not the sound portion of it. I have a GPU that doesn't like to reset for nothing, and will require a complete power off state to the server, pull power, wait....., power back on, all is well. IDK, it's worth a shot if you are out of options. At the time of testing (back in beta days) I believe I would receive similar errors for my issue with that card. If by output you mean seen video, yes, this card used to be in a HTPC running OpenELEC, and is used to configure the BIOS on this MB. The only thing I can think of is that the GPU isn't being removed/detached from unRAID use. Doubtful (as previous posts/testing suggests UnRaid does not bind those devices), however if you think so try stubbing it in your go file, and unRAID won't use it regardless. Edit:... I'm not sure if that means the VM manager will list it as available or not, if it doesn't then you'd have to manually add the entry of the GPU and sound card into the XML. Not that difficult, but you may not want to do that. I don't mind doing manual edits for the sake of troubleshooting. I will also try a complete power down and pull power to see if that fixes it. It's not like I reboot this machine often... or at all really. I've also tried using an NVIDIA GT 520 and had the same errors. I'm going to look at the firmware on the MB and see if there is an update.
Archived
This topic is now archived and is closed to further replies.