Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Error starting Pfsense VM

Featured Replies

I have been following Spaceinvaderone with his excellent Pfsense setup.

 

I have used ACS to split the IOMMU of my 4 port intel nic.

 

I have stubbed it on the flash drive and removed the virtual nic from the VM.

 

But when I start the VM I get the error below.

 

internal error: qemu unexpectedly closed the monitor: 2019-11-13T11:58:52.452469Z qemu-system-x86_64: -device vfio-pci,host=0000:07:00.0,id=hostdev0,bus=pci.1,addr=0x0: vfio 0000:07:00.0: failed to setup container for group 29: Failed to set iommu for container: Operation not permitted

 

If it take the first port off the second one shows the same error.

 

Any help would be appreciated.

12 minutes ago, Beaker69 said:

failed to setup container for group 29:

You should post the diagnostics

  • Author

Here is the VM log file.

 

-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
-device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \
-device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-drive file=/mnt/user/isos/Software/pfSense-CE-2.4.4-RELEASE-p3-amd64.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \
-device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \
-drive file=/mnt/user/domains/Pfesense/vdisk1.img,format=qcow2,if=none,id=drive-sata0-0-2,cache=writeback \
-device ide-hd,bus=ide.2,drive=drive-sata0-0-2,id=sata0-0-2,bootindex=1,write-cache=on \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-vnc 0.0.0.0:0,websocket=5700 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device vfio-pci,host=0000:07:00.0,id=hostdev0,bus=pci.1,addr=0x0 \
-device vfio-pci,host=0000:07:00.1,id=hostdev1,bus=pci.3,addr=0x0 \
-device vfio-pci,host=0000:08:00.0,id=hostdev2,bus=pci.4,addr=0x0 \
-device vfio-pci,host=0000:08:00.1,id=hostdev3,bus=pci.5,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2019-11-13 13:28:32.907+0000: Domain id=7 is tainted: high-privileges
2019-11-13 13:28:32.907+0000: Domain id=7 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2019-11-13T13:28:33.025860Z qemu-system-x86_64: -device vfio-pci,host=0000:07:00.0,id=hostdev0,bus=pci.1,addr=0x0: vfio 0000:07:00.0: failed to setup container for group 29: Failed to set iommu for container: Operation not permitted
2019-11-13 13:28:33.028+0000: shutting down, reason=failed

1 hour ago, Squid said:

You should post the diagnostics

 

54 minutes ago, Beaker69 said:

Here is the VM log file.

That is not the diagnostics zip file from the tools menu.

  • 4 months later...

I'm in this same boat anyone of assistance help out?

 

  • 3 weeks later...
  • 11 months later...

How do I get help for this? This CLEARLY is a software issue, and no one is supporting this issue. I've paid money for this software, and it's not doing what I bought it for.

 

  • 1 year later...

Me too. Facing same issue.
I’ve post on the general support forum but been moved to KVM support tread where the request wasn’t been respond.


Sent from my iPhone using Tapatalk

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.