all these attempts and tests I've been doing in
2.6.39-200.32.1.el6uek.x86_64(oracle)
now when I try rhel 2.6.32-279.5.1.el6.x86_64(everything
else, hw&soft stay the same) I get:
,for win7-64 guest:
pci-stub 0000:26:00.0: irq 104 for MSI/MSI-X
pci-stub 0000:26:00.0: restoring config space at offset 0x1
(was 0x100400, writing 0x100407)
pci-stub 0000:26:00.0: irq 104 for MSI/MSI-X
pci-stub 0000:26:00.0: irq 104 for MSI/MSI-X
pci-stub 0000:26:00.0: irq 104 for MSI/MSI-X
pci-stub 0000:26:00.0: irq 104 for MSI/MSI-X
do_IRQ: 12.146 No irq handler for vector (irq -1)
and the guest(win7-64) hans/freezes on boot, no devices
passed/assigned - guest boots up fine
whereas XP-32-bit stays OK for both with device passed and
without
can this be helped?
On 01/10/12 12:10, lejeczek wrote:
hmm, still cannot get readon 5450 to work on win7-64, have
changed -cpu to host but no fix
no vfio in qemu-kvm-0.12.1.2-2.295.el6_3.2.x86_64
yes, I do blacklist modules at grub level and later in
modprobe also
is primary/secondary VGA setup somehow helped by
qemu/components? in guest I can do anything since device
is disabled.
pci-assign.multifunction=on/off - that would be the case
with VGAs like radeon and nvidia - audio part - is it
optional or always has to be ON for such devices?
where one gets hold of information like: addr= ?
I understand these are needed only! if pci-assign.host is
not enough and qemu has no way of knowing/finding it, when
may this happen?
many thanks
On 28/09/12 20:48, Alex Williamson wrote:
On Fri, 2012-09-28 at 19:46 +0100, lejeczek wrote:
thanks Alex for your patience, appreciate it I do
what would be the droids I need?
I'm experiencing guests' "puzzling" behavior and was
suggested that command line arguments were
wrong/incomplete.
same box/hardware and radeon 5450 and ...
- winXP-32bit -> OK - I assumed getting the guest on a
external computer monitor was an ultimate test
- win7-64bit -> OS reports device as disabled cause the
device reported an error
I've had this same card working with both of these
guests. I believe
one trick on win7 was to use -cpu host. Also, don't try
to disable the
emulated vga device, just set it up like a dual-head
system. Once you
load the catalyst driver windows will switch to use the
assigned device
exclusively. I was using the new vfio assignment driver,
but someone
else recently report it working with the existing driver
as well. The
5450 should be a secondary graphics card on the host
system, trying to
assign the primary graphics is going to cause more
problems. Also
blacklist the radeon driver on the host, we don't need
any leftover
state from the Linux driver causing problems since most
of these
graphics cards don't support a reset mechanism.
same box as above and geforce gt640 and ..
for both XP and 7 report device with exclamation marks
(thus
did not even bother to connect any screens like in working
case with XP & radeon)
I don't think we've seen any reports yet of Nvidia cards
working,
there's another thread on the kvm list speculating at
some of the
problems.
I'll try to get hold of ROMs of the cards, meanwhile, how
can I troubleshoot it? how to get more verbose feedback and
what to specifically look for?
ROMs are only going to help if you're getting errors
trying to read the
ROM. Nvidia seems to have this problem, but I don't
think radeons
typical do. There's a #define in the code that can be
enabled to get
more logging, but it's not terribly useful unless you
know what you're
looking at. VGA has plenty of issues with legacy PC
address ranges that
are known problems, but there are also plenty of unknown
problems that
make it a pretty difficult black box debugging project.
Thanks,
Alex
