https://bugzilla.novell.com/show_bug.cgi?id=489735 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489735#c2 --- Comment #2 from pgnet _ <pgnet.trash@gmail.com> 2009-03-30 09:43:26 MDT --- (In reply to comment #1)
Try putting the device in a different slot, so that it ends up on a different bus.
unfortunately, not an option in these micro-atx boxes (card/slot geometry is inflexible :-( ), without removing something completely. can get around to trying that, eventually ...
I assume you're running into the situation where all devices behind a bridge need to be assigned to the same domain.
i'm not clear whether that's a system "need" (which exists?) or my "need", which doesn't. i just need to assign this _one_ card (04:07.0) to this domain. 04:08.0 is inisting on tagging-along for the ride -- when i actually need/want it to 'stay' @ Dom0.
This is definitely a requirement when using an IOMMU, but the tools may just always require this to be the case.
atm, i'm booting to root (hd0,0) kernel /xen.gz dom0_mem=768M loglvl=all loglvl_guest=all vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1 module /vmlinuz-xen root=/dev/vg0/ROOT resume=/dev/vgS/SWAP showopts console=tty0 console=xvc0,57600 elevator=cfq max_loop=64 physdev_dom0_hide=(04:07.0)(04:08.0) reassigndev=(04:07.0) module /initrd-xen i.e., no IOMMU you've CLOSED this bug as INVALID ... is that to say that you consider the inability to split these device assignments (1 to Dom0, 1 to DomU)normal function, and not an issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.