August 2009 - openSUSE Virtual - openSUSE Mailing Lists

Re: [opensuse-virtual] correct IOMMU setup for AMD processor & xen pci passthrough?
by PGNet Dev 17 Aug '09

17 Aug '09

hi jan, On Mon, Aug 17, 2009 at 12:15 AM, Jan Beulich<JBeulich(a)novell.com> wrote: >>>> PGNet Dev <pgnet.dev+osvm(a)gmail.com> 14.08.09 00:24 >>> > Depends on what you mean by "verify" here: > The hypervisor/tools > should tell you whether the IOMMU is enabled (and being used). I don't > think there are any tests that you could run - at least I'm unaware of > any. Just like with other hard-/software, you'll have to trust it does > what it promises, and report any observation hinting at this not being > the case. heh, i usually tend towards "trust, but verify", myself ;-) i'll have to dig a bit to figure out what those hints might bein the first place. if i find nothing, looks like we'd have to code an attempt of x-guest DMA access ourselves. thanks! -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

[opensuse-virtual] correct IOMMU setup for AMD processor & xen pci passthrough?
by PGNet Dev 13 Aug '09

13 Aug '09

hi, i've an AMD processor, cat /proc/cpuinfo | egrep "vendor|model|flags" vendor_id : AuthenticAMD model : 4 model name : AMD Phenom(tm) II X4 920 Processor flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc rep_good nopl pni cx16 popcnt lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch i've openSUSE 11.1, running latest SL111 kernel, uname -ri 2.6.27.29-7-xen x86_64 with OBS Virtualization:Xen, xm dmesg | grep "Xen version" (XEN) Xen version 3.4.1_19711_01-9.1 (abuild@) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) Wed Aug 5 01:48:18 UTC 2009 i'm doing hardware passthrough of a sata PCI card to DomU, and want to ensure iommu is (un)set properly. reading @, "AMD64 specific boot options" http://www.kernel.org/doc/Documentation/x86/x86_64/boot-options.txt it seems i should (?) use, iommu=off,noagp,noaperture @ grub. however, comparing startup, (1) WITH "iommu=off,noagp,noaperture" @ grub/menu.lst dmesg | grep -i pciback pciback 0000:04:07.0: seizing device pciback 0000:04:07.0: enabling device (019d -> 019f) pciback 0000:04:07.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 pciback 0000:04:07.0: PCI INT A disabled pciback: vpci: 0000:04:07.0: assign to virtual slot 0 pciback 0000:04:07.0: enabling device (0080 -> 0083) pciback 0000:04:07.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 (2) WITHOUT "iommu=off,noagp,noaperture" @ grub/menu.lst dmesg | grep pciback pciback 0000:04:07.0: seizing device pciback 0000:04:07.0: enabling device (019d -> 019f) pciback 0000:04:07.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 pciback 0000:04:07.0: PCI INT A disabled i can see that there's a difference -- namely the, pciback: vpci: 0000:04:07.0: assign to virtual slot 0 but in both cases, @ DomU, the card is correctly passed through, lspci 00:00.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02) and, afaict, works fine. IS the aformentionted difference relevant? given my config, what is the recommended IOMMU config for kernel cmd line? thanks! -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 2

[opensuse-virtual] qemu, virtio and network card
by Paul Reeves 10 Aug '09

10 Aug '09

I'm running qemu-kvm and testing the use of virtio for network access. It seems to work. However, yast is confused. Sure, there is a device eth0 that is configured and is using the virtio_net module. However yast also claims that there is an unconfigured Virtio Network device that it cannot configure because: "Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details." This seems to be erroneous. The unconfigured Virtio network device should not show up at all, afaict. For example, if I boot the qemu session with the pcnet nc then yast just shows the eth0 device using the pcnet module. There are no unconfigured devices. So, I guess this is a bug - but is it yast, qemu, me or ? Paul -- Paul Reeves http://www.fleetriver.com -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 4

[opensuse-virtual] does xenpm work for opensuse kernel-xen?
by PGNet Dev 05 Aug '09

05 Aug '09

hi, i'm trying to get Xen cpu scaling & power management (either =xen _or_ =dom0-kernel), to no avail. @ kenel-default, cpufreq et al. works fine. @ kernel-xen, however, i've filed a bug (https://bugzilla.novell.com/show_bug.cgi?id=527800) with details included ... digging around, however, it seems that it 'worksforsome' w/ other configs & other distros -- and leaves me wondering if the problem is local or systemic :-/ can _anyone_ here report success with enabling xenpm under openSUSE's kernel-xen? thanks! -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 4