Error internal error qemu unexpectedly closed the monitor

I am trying to setup a XP vm with hardware passthrough of an old radeon 9250 and creative labs sound blaster card. I have the cards hooked to my unraid server via a pcie to dual pci adapter (example can be found here:  https://www.aliexpress.com/item/Desktop-PCI-Express-PCI-e-to-PCI-Adapter-Card-PCIe-to-Dual-Pci-Slot-Expansion-Card/32849431927.html ).

My IOMMU groups show the adapter, sound card and what i believe to be the two outputs of the graphics card all in the same group. I think this is fine as all the devices are to be passed to my vm.
 

IOMMU group 15:[12d8:e111] 01:00.0 PCI bridge: Pericom Semiconductor PI7C9X111SL PCIe-to-PCI Reversible Bridge (rev 02)

[1274:5880] 02:04.0 Multimedia audio controller: Ensoniq 5880B / Creative Labs CT5880 (rev 02)

[1002:5960] 02:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280 [Radeon 9200 PRO] (rev 01)

[1002:5940] 02:05.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280 [Radeon 9200 PRO] (Secondary) (rev 01)

however when i try to start the vm im greeted with a popup and the message in the title: «internal error: qemu unexpectedly closed the monitor»

the syslog isnt much help either. I tried to start several times in succession so that the errors would be evident in the logs:

Mar  7 20:57:52 unraid kernel: vfio-pci 0000:02:05.0: Refused to change power state, currently in D0
Mar  7 20:57:52 unraid kernel: vfio-pci 0000:02:05.1: Refused to change power state, currently in D0
Mar  7 20:57:52 unraid kernel: br0: port 2(vnet0) entered blocking state
Mar  7 20:57:52 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 20:57:52 unraid kernel: device vnet0 entered promiscuous mode
Mar  7 20:57:52 unraid kernel: br0: port 2(vnet0) entered blocking state
Mar  7 20:57:52 unraid kernel: br0: port 2(vnet0) entered forwarding state
Mar  7 20:57:52 unraid kernel: qemu-system-x86[11275]: segfault at a8 ip 000055f57ce3237a sp 00007ffea39fb520 error 4 in qemu-system-x86_64[55f57cb1b000+af2000]
Mar  7 20:57:52 unraid kernel: Code: f9 ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 55 53 48 89 fb 48 83 ec 08 48 8b 6f 58 e8 3e df ff ff 48 89 df e8 e6 e9 ff ff <48> 8b 85 a8 00 00 00 48 85 c0 74 2e 8b 93 a0 00 00 00 39 90 a0 00 
Mar  7 20:57:52 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 20:57:52 unraid kernel: device vnet0 left promiscuous mode
Mar  7 20:57:52 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 20:57:53 unraid kernel: vfio-pci 0000:02:05.1: Refused to change power state, currently in D0
Mar  7 20:57:53 unraid kernel: vfio-pci 0000:02:05.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Mar  7 21:08:20 unraid kernel: vfio-pci 0000:02:05.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Mar  7 21:08:20 unraid kernel: vfio-pci 0000:02:05.0: Refused to change power state, currently in D0
Mar  7 21:08:20 unraid kernel: vfio-pci 0000:02:05.1: Refused to change power state, currently in D0
Mar  7 21:08:20 unraid kernel: br0: port 2(vnet0) entered blocking state
Mar  7 21:08:20 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 21:08:20 unraid kernel: device vnet0 entered promiscuous mode
Mar  7 21:08:20 unraid kernel: br0: port 2(vnet0) entered blocking state
Mar  7 21:08:20 unraid kernel: br0: port 2(vnet0) entered forwarding state
Mar  7 21:08:21 unraid kernel: qemu-system-x86[7453]: segfault at a8 ip 00005590982c637a sp 00007fff8132e7b0 error 4 in qemu-system-x86_64[559097faf000+af2000]
Mar  7 21:08:21 unraid kernel: Code: f9 ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 55 53 48 89 fb 48 83 ec 08 48 8b 6f 58 e8 3e df ff ff 48 89 df e8 e6 e9 ff ff <48> 8b 85 a8 00 00 00 48 85 c0 74 2e 8b 93 a0 00 00 00 39 90 a0 00 
Mar  7 21:08:21 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 21:08:21 unraid kernel: device vnet0 left promiscuous mode
Mar  7 21:08:21 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 21:08:22 unraid kernel: vfio-pci 0000:02:05.1: Refused to change power state, currently in D0
Mar  7 21:08:22 unraid kernel: vfio-pci 0000:02:05.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Mar  7 21:15:46 unraid kernel: vfio-pci 0000:02:05.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Mar  7 21:15:46 unraid kernel: vfio-pci 0000:02:05.0: Refused to change power state, currently in D0
Mar  7 21:15:46 unraid kernel: vfio-pci 0000:02:05.1: Refused to change power state, currently in D0
Mar  7 21:15:46 unraid kernel: br0: port 2(vnet0) entered blocking state
Mar  7 21:15:46 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 21:15:46 unraid kernel: device vnet0 entered promiscuous mode
Mar  7 21:15:46 unraid kernel: br0: port 2(vnet0) entered blocking state
Mar  7 21:15:46 unraid kernel: br0: port 2(vnet0) entered forwarding state
Mar  7 21:15:46 unraid kernel: qemu-system-x86[27299]: segfault at a8 ip 000055982823137a sp 00007ffd38193ae0 error 4 in qemu-system-x86_64[559827f1a000+af2000]
Mar  7 21:15:46 unraid kernel: Code: f9 ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 55 53 48 89 fb 48 83 ec 08 48 8b 6f 58 e8 3e df ff ff 48 89 df e8 e6 e9 ff ff <48> 8b 85 a8 00 00 00 48 85 c0 74 2e 8b 93 a0 00 00 00 39 90 a0 00 
Mar  7 21:15:46 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 21:15:46 unraid kernel: device vnet0 left promiscuous mode
Mar  7 21:15:46 unraid kernel: br0: port 2(vnet0) entered disabled state
Mar  7 21:15:47 unraid kernel: vfio-pci 0000:02:05.1: Refused to change power state, currently in D0
Mar  7 21:15:47 unraid kernel: vfio-pci 0000:02:05.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none

vm xml below:

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows XP</name>
  <uuid>91230a79-b145-678a-dc42-52195269234d</uuid>
  <description>XP</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows XP" icon="windowsxp.png" os="windowsxp"/>
  </metadata>
  <memory unit='KiB'>3145728</memory>
  <currentMemory unit='KiB'>3145728</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='5'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='1' threads='2'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Windows XP/vdisk1.img'/>
      <target dev='hdc' bus='ide'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:e9:40:aa'/>
      <source bridge='br0'/>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x02' slot='0x05' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0461'/>
        <product id='0x4d17'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x062a'/>
        <product id='0x0201'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

Also in case its needed, here’s my syslinux config:

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pcie_acs_override=downstream,multifunction initrd=/bzroot vfio_iommu_type1.allow_unsafe_interrupts=1
label unRAID OS GUI Mode
  kernel /bzimage
  append pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot unraidsafemode
label unRAID OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

Any ideas on how to get this to boot?  

Edited March 8, 2019 by rottenpotatoes

qemu unexpectedly closed the monitor: Assertion `ret == cpu->kvm_msr_buf->nmsrs’ failed. #4277

The exact command to reproduce the issue:

$ minikube start
😄 minikube v1.0.1 on linux (amd64)
🤹 Downloading Kubernetes v1.14.1 images in the background .
💡 Tip: Use ‘minikube start -p ‘ to create a new cluster, or ‘minikube delete’ to delete this one.
🔄 Restarting existing kvm2 VM for «minikube» .

💣 Unable to start VM: start: Error creating VM: virError(Code=1, Domain=10, Message=’internal error: qemu unexpectedly closed the monitor: 2019-05-17T02:20:07.980140Z qemu-system-x86_64: error: failed to set MSR 0x38d to 0x0
qemu-system-x86_64: /build/qemu-lXHhGe/qemu-2.11+dfsg/target/i386/kvm.c:1807: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs’ failed.’)

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new

💣 command runner: getting ssh client for bootstrapper: Error creating new ssh host from driver: Error getting ssh host name for driver: host is not running

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new
The operating system version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

$ go version
go version go1.12.5 linux/amd64
$ kubectl version
Client Version: version.Info
The connection to the server localhost:8080 was refused — did you specify the right host or port?
$ minikube version
minikube version: v1.0.1
$ kvm -version
QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.13)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

The text was updated successfully, but these errors were encountered:

Источник

Arch Linux

You are not logged in.

#1 2020-10-19 13:52:52

[SOLVED] GVT-g libvirt qemu error «EGL_MESA_image_dma_bug_export»

I’m having three repeating errors running a Win VM via libvirt:

OpenGL not supported by the display

Failed to initialize EGL render node for SPICE GL

kvm_init_vcpu failed: Function not implemented

I begin with the following appended to my libvirt VM XML config:

I fix the first error with `xhost si:localuser:nobody`, but this results in the second error. Full trace:

According to https://www.mail-archive.com/qemu-devel … 04013.html I have to use ‘egl-headless’ and ‘gl=off’, so I edit the XML to:

(note: where does the ‘gtk’ argument go?)

But this then results in the third error. Full trace:

Have you run into this problem before? Would you share your solution?

(I have already fully installed Win in the VM, installed SPICE win guest binary, and shut down the VM. I’m now trying to switch over to vGPU.)

Last edited by miomio (2020-10-19 18:38:46)

#2 2020-10-19 17:30:43

Re: [SOLVED] GVT-g libvirt qemu error «EGL_MESA_image_dma_bug_export»

No matter the different options I re-arrange, libvrt keeps coming back around to EGL_MESA_image_dma_bug_export related error. Found some info on it here https://www.khronos.org/registry/EGL/ex … export.txt and an explanation from 5 years ago about what its function https://qemu-devel.nongnu.narkive.com/m … -detection

OK, may be getting somewhere now. I have dropped spice-gtk, and pursuing configuration via egl-headless. Also update acl in /etc/libvirt/qemu.conf per the last URL I referenced.

This then generates a lot of ALSA related errors but no error about EGL_MESA_image_dma_bug_export or dma related, so assuming progress. Solving most of the ALSA errors with:

Leaving behind a connection refusal from pulseaudio. Following the wiki to update qemu.conf https://wiki.archlinux.org/index.php/Libvirt#PulseAudio

Updated /etc/libvirt/qemu.conf with my $USER per the wiki, which results in another error:

Found a posted bug https://bugs.archlinux.org/task/66168 but the reporter describes closing the case due to having realised s/he made a mistake in their config, however doesn’t describe what the mistake was.

I changed qemu.conf to run under my $USER so I do `xhost +`. Error now reports OpenGL required:

But I’m using OpenGL:

So, I’ll sleep on it.

Needed to remove the MESA_LOADER_DRIVER_OVERRIDE line and VM works.

Last edited by miomio (2020-10-19 18:32:39)

Источник

Error internal error qemu unexpectedly closed the monitor

I’m running virt-manager as root and have enabled iommu in the kernel command line and in /etc/default/grub

Any help appreciated.

Последний раз редактировалось: dirtboxes (пн авг 02, 2021 9:27 am), всего редактировалось 1 раз Вернуться к началу

NyneR
n00b

Зарегистрирован: 19 дек 2020
Сообщений: 31

Вернуться к началу

Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах

Copyright 2001-2023 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy

Источник

Could not open ‘/root/CentOS-7-x86_64-Minimal-1611.iso’: Permission denied

An attempt to use virt-install to create a CentOS 7 guest virtual machine on a CentOS 7 host is generating the following error:

What specific steps need to be taken to resolve this error, so that the CentOS 7 guest virtual machine can be successfully installed?

The details are as follows:

Steps To Reproduce The Error:

First, I downloaded the iso file from a centos mirror:

Next, I ran the following installation command, which resulted in the error:

To assess the permission problem, I reviewed the contents of the directory, as follows:

Though I know that root should be able to access any other user’s files, I tried changing the user to root and re-running the command as follows:

As you can see, I got the same error. What else needs to be done to resolve this error, so that the guest virtual machine can be installed successfully?

3 Answers 3

You also have SELinux enabled (which is good), but the context of the ISO may be preventing qemu from reading it, too.

Try moving the ISO to /tmp . qemu should have access to read files in /tmp if the individual file context is appropriate.

If qemu is still unable to access the ISO after you’ve moved it to /tmp , check out the contents of /var/log/audit/audit.log to see if any access violations were recorded there.

To view the SELinux contexts, for instance, after moving the ISO to /tmp , use ls -lZ /tmp/ .

This won’t tell you what the contexts should be for the program to access the file, but will show you the current context. Comparing the context of other files (that the program can already access) to this file should help you narrow down what you could set the context of this file to.

In this scenario, as long as the ISO is located in a directory that qemu has access to, you can set the context of the ISO so qemu can read it with chcon -t virt_content_t .iso

The directory, /root , has permissions, 0550 , with owner and group owner, root . It also has an SELinux context as indicated by the . in dr-xr-x—. . Only users in the root group can read and execute files in the /root directory. Also, as long as SELinux is enforcing, then the wrong SELinux context can prevent file access. In other words, even if the directory permissions were 0777 (permitting all access to all users), the qemu user cannot read the file unless, in addition, the SELinux context has been set correctly. Use ls -lZ to show an SELinux context. The following is the default result for the /root directory.

As we can see, admin_home_t is not virt_image_t or some other permitted SELinux context.

There are more ways to do it, like using an FTP or Web server, as follow.

Using a Web Server

With this, use -l http://x.x.x.x/pub/centos instead of —cdrom .

Using an FTP Server

With this, use -l ftp://x.x.x.x/pub/centos instead of —cdrom .

In short, just get the permissions and SELinux context corrected, or use an alternate method, two of which were described above.

Источник

host port forward with qemu through libvirt in user-mode networking

I’m having trouble editing my libvirt’s host-xml to make qemu forward TCP connections to the guest. This questions linked to a blog post which recommended adding -redir to the Qemu command line. But that stopped working as of recently.

error: internal error: qemu unexpectedly closed the monitor: qemu-system-x86_64: -redir tcp:5564::3389: The -redir option is deprecated. Please use ‘-netdev user,hostfwd=. ‘ instead.

That, however, doesn’t work out of the box, i.e. I get the open port on the host, but it doesn’t go through to the client.

I edited my XML like this:

My test was to then run nc -l -p 8000 on the client and telnet localhost 8000 on the host. Telnet indicates an opened TCP connection but the client doesn’t receive anything.

I guess it’s because libvirt already included a -net user. option and somehow my newly defined option isn’t processed properly. ps aux | grep qemu shows this:

qemu-system-x86_64 -enable-kvm -name guest=myguestsname,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=

/.config/libvirt/qemu/lib/domain-28-myguestsname/master-key.aes -machine pc-i440fx-artful,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Skylake-Client -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 713287321 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=

/.config/libvirt/qemu/lib/domain-28-myguestsname/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=

/.local/share/libvirt/images/myguestsname.img,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=Cloud-Init-ISO/master-init.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -fsdev local,security_model=mapped,id=fsdev-fs0,path=

/guestfs -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=guestsfs,bus=pci.0,addr=0x9 -netdev user,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:aa:aa:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -net user,hostfwd=tcp::22222-:22,hostfwd=tcp::8000-:8000 -msg timestamp=on

We can see -netdev user,id=hostnet0 . I tried to use the same name in my custom command line, but that fails:

error: internal error: process exited while connecting to monitor: qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/23 (label charserial0)

qemu-system-x86_64: -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:aa:aa:0a,bus=pci.0,addr=0x3: Property ‘virtio-net-device.netdev’ can’t take value ‘hostnet0’, it’s in use

For non user-mode networking setups, several questions exist already. But I need to work with user-mode networking.

How would I properly forward ports using libvirt with qemu and user-mode networking?

The documentation is not really helpful, here, because it does not say how to sort of override already existing device definitions.

Источник

Adblock
detector

When starting the KVM (that was working fine in ubuntu 19.04) I am getting the following error:

Error starting domain: internal error: qemu unexpectedly closed the monitor: pulseaudio: pa_context_connect() failed pulseaudio: Reason: Connection refused pulseaudio: Failed to initialize PA contextaudio: warning: Using timer based audio emulation

Traceback (most recent call last):   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
    callback(asyncjob, *args, **kwargs)   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
    callback(*args, **kwargs)   File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
    ret = fn(self, *args, **kwargs)   File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup
    self._backend.create()   File "/usr/lib/python3/dist-packages/libvirt.py", line 1080, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: pulseaudio: pa_context_connect() failed pulseaudio: Reason: Connection refused pulseaudio: Failed to initialize PA contextaudio: warning: Using timer based audio emulation

I have made the changes to the config file. I have added the following lines to reflect the change from qemu 3.1 to 4.0

  <qemu:commandline>
    <qemu:env name="QEMU_AUDIO_DRV" value="pa"/>
    <qemu:env name="QEMU_PA_SERVER" value="/run/user/1000/pulse/native"/>
  </qemu:commandline>

If I remove these lines I cannot passthrough sound to pulseaudio.

yes the kvm audio user is me.

Any help will be appreciated. Is this a bug or a setup issue.
my guest is windows 10 (1903)

I’m having trouble editing my libvirt’s host-xml to make qemu forward TCP connections to the guest. This questions linked to a blog post which recommended adding -redir to the Qemu command line. But that stopped working as of recently.

error: internal error: qemu unexpectedly closed the monitor:
qemu-system-x86_64: -redir tcp:5564::3389: The -redir option is
deprecated. Please use ‘-netdev user,hostfwd=…’ instead.

That, however, doesn’t work out of the box, i.e. I get the open port on the host, but it doesn’t go through to the client.

I edited my XML like this:

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  .
  .
  .
  </devices>
  <qemu:commandline>
    <qemu:arg value='-net'/>
    <qemu:arg value='user,hostfwd=tcp::22222-:22,hostfwd=tcp::8000-:8000'/>
  </qemu:commandline>
</domain>

My test was to then run nc -l -p 8000 on the client and telnet localhost 8000 on the host. Telnet indicates an opened TCP connection but the client doesn’t receive anything.

I guess it’s because libvirt already included a -net user,... option and somehow my newly defined option isn’t processed properly. ps aux | grep qemu shows this:

qemu-system-x86_64 -enable-kvm -name guest=myguestsname,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=~/.config/libvirt/qemu/lib/domain-28-myguestsname/master-key.aes -machine pc-i440fx-artful,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Skylake-Client -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 713287321 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=~/.config/libvirt/qemu/lib/domain-28-myguestsname/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=~/.local/share/libvirt/images/myguestsname.img,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=Cloud-Init-ISO/master-init.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -fsdev local,security_model=mapped,id=fsdev-fs0,path=~/guestfs -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=guestsfs,bus=pci.0,addr=0x9 -netdev user,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:aa:aa:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -net user,hostfwd=tcp::22222-:22,hostfwd=tcp::8000-:8000 -msg timestamp=on

We can see -netdev user,id=hostnet0. I tried to use the same name in my custom command line, but that fails:

error: internal error: process exited while connecting to monitor:
qemu-system-x86_64: -chardev
pty,id=charserial0: char device redirected to /dev/pts/23 (label
charserial0)

qemu-system-x86_64: -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:aa:aa:0a,bus=pci.0,addr=0x3: Property ‘virtio-net-device.netdev’ can’t take value ‘hostnet0’, it’s
in use

For non user-mode networking setups, several questions exist already.
But I need to work with user-mode networking.

How would I properly forward ports using libvirt with qemu and user-mode networking?

The documentation is not really helpful, here, because it does not say how to sort of override already existing device definitions.