[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu
** No longer affects: qemu
** Project changed: linux => qemu
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
And all work after killing qemu with ^C.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu clock control doesn`t work after guest reboot
Status in The Linux Kernel:
In text mode and on net console there are no errors, host system just
freezes after guest poweroff. This may be a hang-up the pcie?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Are you attempting to rebind the HD6850 to host drivers after qemu is
shutdown
No, I did not rebind HD6850 to the host system. System hangs at shutdown
guest
HD6850 - works fully, host hang on guest poweroff
Yes.
--
You received this bug notification because you are a member of qemu-
So the result is:
HD6850 - works fully, host hang on guest poweroff
GT210 - works fully, no host issues
Is that correct? Are you attempting to rebind the HD6850 to host
drivers after qemu is shutdown, or does the host hang happen prior to
where that would be possible? What about killing qemu
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu clock control doesn`t work after guest reboot
With VFIO_PCI_VGA, vfio-vga-reset branches and -vga none -device vfio-
pci,host=02:00.0,x-vga=on host system hangs after guest restarting or
turning off.
With no VFIO_PCI_VGA, vfio-vga-reset branches and -vga none -device
vfio-pci,host=02:00.0 catalyst drivers works fine in guest. But after
guest
With VFIO_PCI_VGA, vfio-vga-reset branches and -vga none -device vfio-
pci,host=02:00.0,x-vga=on I also received an error:
qemu-system-x86_64: Attempt to reset PCI bus for VGA support failed
(Inappropriate ioctl for device). VGA may not work.
But the drivers were run without problems.
--
You
I installed Windows 8 with VFIO_PCI_VGA, vfio-vga-reset branches and
-vga none -device vfio-pci,host=02:00.0,x-vga=on I received an error:
qemu-system-x86_64: Attempt to reset PCI bus for VGA support failed
(Inappropriate ioctl for device). VGA may not work. on start.
Then I installed the
Please confirm that you're running the kernel from this branch on the
host system:
git://github.com/awilliam/linux-vfio.git vfio-vga-reset
Both host kernel and qemu changes are required. Unfortunately the error
code from the ioctl makes it difficult to tell if it isn't available in
the kernel
When I use vga none -device vfio-pci,host=02:00.0,x-vga=on with Linux
localhost 3.9.0-rc2 #2 SMP PREEMPT Sat May 4 11:45:12 MSK 2013 x86_64
AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux and
VFIO_PCI_VGA support. System starting with qemu-system-x86_64: Attempt
to reset PCI bus for
The above linux tree is based on 3.9.0, not -rc2, so it appears you're
not using the correct kernel.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu clock control
Sry. With x-vga=on and Linux localhost 3.9.0+ #3 SMP PREEMPT Sun May 5
00:58:56 MSK 2013 x86_64 AMD FX(tm)-8120 Eight-Core Processor
AuthenticAMD GNU/Linux it`s work fine.
On Sunday or Monday I will test Geforce gt210 and gt610.
--
You received this bug notification because you are a member of
And bad news too. System hangs after guest poweroff.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu clock control doesn`t work after guest reboot
Status in QEMU:
Also I tested nvidia gt210. All works fine: 3D, reboot, poweroff,
clocks control, bios initialization.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu clock control
Try these:
git://github.com/awilliam/linux-vfio.git vfio-vga-reset
git://github.com/awilliam/qemu-vfio.git vfio-vga-reset
When using both this kernel and this qemu, we'll do a PCI bus reset,
which should give you much more consistent behavior both between
instances of the guest and at guest
First I added radeon.ko and fglrx.ko to the blacklist.
Second I ran the
modprobe vfio-pci
echo :02:00.0 /sys/bus/pci/devices/\:02\:00.0/driver/unbind
echo :02:00.1 /sys/bus/pci/devices/\:02\:00.1/driver/unbind
echo 1002 6739 /sys/bus/pci/drivers/vfio-pci/new_id
echo 1002 aa88
** Summary changed:
- Qemu 1.5.0 gpu clock control doesn`t work after guest reboot
+ Qemu 1.5-git gpu clock control doesn`t work after guest reboot
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
With kernel-3.9.0 host system hangs after guest (win 7) poweroff or
reboot.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1175513
Title:
Qemu 1.5-git gpu clock control doesn`t work after guest
21 matches
Mail list logo
