Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I'm trying to setup a MythTV backend with Mythbuntu in a VM. I'm running Fedora 12 as host. I have 2 DVB-C cards in my system. The system contains an AM2 cpu which supports AMD's virtualization technology (which is switched on in bios). I've enabled SELinux to:
- Allow virt to manage devince configuration, (pci)
- Allow virt to use usb devices
The error which I get is:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest: char device redirected to /dev/pts/1
Failed to assign irq for "01:06.0": Operation not permitted
Perhaps you are assigning a device that shares an IRQ with another device?
Failed to initialize assigned device host=01:06.0
Which I think means that no IRQs are shared. Devices 16 & 17 are the one I want to Passthrough. Can someone point me in the right direction on how to solve this problem?
Last edited by martdj; 01-20-2010 at 03:26 AM.
Reason: removed some garbage
I'll answer my own question as no one else did and it might benefit someone.
KVM needs hardware support to function (otherwise you're using Qemu emulation and that's slow and not really KVM). There are however gradations in this hardware support:
- The 1st gradation is virtualization support in the cpu. AMD support this kind of virtualization since the Athlon on AM2 generation, Intel supports it in the Core cpu's though cheaper Core cpu's might lack this support. Check Intel website to see if your Intel cpu supports it or not
- The 2nd gradation is support in the northbridge. As far as I know, so far only intel chipsets for the Core i9, i7 and i5 have this "IOMMU" support. AMD's new 8x0 chipsets with mainboards containing them due to be released this month are also suspected of containing this IOMMU support.
In short KVM needs the first gradation to function at all. KVM needs the 2nd gradation for functionality like PCI Passthrough. My cpu only has AMD-V, so PCI passthrough won't work for me. If I want PCI passthrough in a VM I'd have to use Xen.
Thanks for that clarification. I'm also running a MythTV backend in a virtual machine on an AMD-V machine. I'm working in a Debian/Ubuntu based environment so I was interested in migrating to KVM since Ubuntu has stopped supporting Xen and it's unclear to me what Debian has planned for Xen in the future. I'd tried setting up KVM and got the exact same error messages that you did. I've been banging my head against a wall, and while I wish there was a solution it's at least good to have the knowledge that it's a hardware problem so I can just work with what I've got.
@dyasny It's not relevant to skug67's problem. He wants to use PCI passthrough. AMD-V alone is not enough for that and there are no AMD systems available yet that will support PCI passthrough on KVM. He'll have to revert to Xen or use the host for MythTV. The latter is what I did.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.