[Bug 1792144] Re: missing patch for i915 in 4.15.0-33-generic => black screen on boot
I have the same bug on a similar motherboard - Asrock j4105-itx (j4105 CPU, asmedia asm1061, realtek rtl8111h) After the boot sequence KUbuntu 18.04 fully updated to Nov-19-2018 Bios 4.0.0.1245Intel GOP 13.0.1011 I doubt this is the same as the freedesktop 105549 bug since the hardware is quite different (no lspcon chip on this motherboard) Also note that the problem only arises when a disk is connected to one of the asmedia sata ports on this motherboard. If no disk on asmedia all is good. No HDMI or DVI screen if disk on asmedia port Windows (8.1) does not experience this issue BUT does not have drivers for this chip at all (Vesa only)> I don't currently have access to Windows 10 When the VGA port is connected to a screen then BOTH the vga and hdmi / dvi screens are active ie. the hdmi / dvi output is live if vga simultaneously connected ... though vga is primary May be spurious, but fwiw, under these conditions ... The system will not power down correctly (even if both VGA and hdmi / dvi connected). Powerdown seems to stop after a message about "ata3 SError" "failed command STANDBY IMMEDIATE" and then a manual power off is required Any debug data I can provide ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792144 Title: missing patch for i915 in 4.15.0-33-generic => black screen on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa
the emulated HDA works fine in Windows 7 VM using the above, with proviso that
I run VM as root, ie.
/etc/libvirt/qemu.conf includes (in my case, which works)
user = "root"
group = "root"
cgroup_device_acl = [
"/dev/null", "/dev/full", "/dev/zero",
"/dev/random", "/dev/urandom",
"/dev/ptmx", "/dev/kvm", "/dev/kqemu",
"/dev/rtc","/dev/hpet", "/dev/vfio/vfio",
"/dev/vfio/1", "/dev/vfio/14", "/dev/vfio/15", "/dev/vfio/16",
"/dev/vfio/17",
"/dev/shm", "/root/.config/pulse", "/dev/snd",
]
nographics_allow_host_audio = 1
security_require_confined = 0
hugetlbfs_mount = "/dev/hugepages"
clear_emulator_capabilities = 0
relaxed_acs_check = 1
If using VNC rather than Spice, you may also need
vnc_allow_host_audio = 1
and /etc/apparmor.d/abstractions/libvirt/qemu contains the following additional
lines (in my case)
/{dev,run}/shm/pulse-shm* rw,
@{HOME}/.config/puls** rwk,
@{HOME}/** r,
/root/.config/puls** rwk,
/root/.asoundrc r,
/dev/vfio/* rw,
This works nicely with a Windows 7 guest using the following xml (where a
graphics card is apssed through at 01:00.0 and a USB card is passed at 02:00.0,
note that the inbuilt audio device on the graphics card is NOT passed through
i'ts still attached to pci-stub)
!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
virsh edit ssd-win7
or other application using the libvirt API.
-->
ssd-win7
92faa169-292a-4086-a398-31df57266eb1
6291456
6291456
2
hvm
/mnt/programming_data/virtualisation/bios/bios.bin
Haswell
destroy
restart
destroy
/usr/bin/qemu-system-x86_64
If you'd rather grant access at the VM level you can update the apparmor
entries in /etc/apparmor.d/libvirt/libivrt-
What worked best for me was to create a new permissions file based on the
"libvirt-.files" entry which was autmatically generated. The new file
contains the following
# Added by R E to support use of VFIO.
"/dev/vfio/*" rw,
# Needed for ALSA sound (based on error messages about not having access).
"/dev/shm/pulse-shm*" rwk,
"/run/shm/pulse-shm*" rwk,
"/root/.config/puls**" rwk,
"/root/.asoundrc" r,
# Rather than specifying individual files, allow the whole directory
"/mnt/programming_data/isos/**" r,
# don't audit writes to readonly files
deny "/mnt/programming_data/isos/**" w,
Then add a pointer to that file in the master at "libvirt-" ie. to
look like this (see the last entry, the file which i created)
#
# This profile is for the domain whose UUID matches this file.
#
#include
profile libvirt-c1a86cb2-82b4-4db9-89c2-ced5be57b39e {
#include
#include
#include
}
For some reason, when I do the same for a Ubuntu Trusty VM it initially worked
but now shows a "device busy" error for some reason, which i'm unable to
overcome - even though a Windows VM operating in exactly the same manner works
fine. Arcane magic involved - sacrifice may be required
Both the AC97 and the HDA devices work on Windows ie. go into Control Panel /
Sound and select one, run a test and it works fine. Neither of them is a PCI
pasthrough card. As it happens I have a separate USB soundcard I can use in
Windows because it's attached to the USB controller with is passed through via
PCI passthrough, but that's a spearate story.
In my situation, the host is Ubuntu Trusty running kvm, qemu, libvirt
and virt-manager from the standard repos. The kernel is patched to
support VGA passthrough (mostly to deal with Intel graphics poor
handling of VGA arbitration)
Have you tried this arrangement ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246929
Title:
no audio in KVM virtual machines : cannot select alsa or pa
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1246929/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa
Libvirt / Virt-Manager and host Alsa based sound
==
I have battled the same problem ... and managed to get it working on Trusty
(1) this is all down to AppArmor
(2) In order to run ALSA you will need the following apparmor entries,
preferably in ...abstractions/libvirt-qemu
# Changes #
/{dev,run}/shm/pulse-shm* rw,
@{HOME}/.config/puls** rwk,
@{HOME}/* r,
# Changes #
In my case I run libvirt as Root because it is accessing virtio and vga
passthrough. I've also added dev/vfio to support vfio based PCI passthrough ie.
/dev/vfio/* rw,
The VM definition xml contains the following
This setup works very nicely with the following (both defined and working, in
guest select preferred mode, I prefer the HDA device)
I prefer the second (HDA) for quality - Note that I am using the Q35
motherboard. Furthermore Pulseaudio was much easier to get working BUT
running system wide (because libvirt runs as root) is not good and it
has terrible lag and is not suitable for somepurposes eg. game machines
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246929
Title:
no audio in KVM virtual machines : cannot select alsa or pa
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1246929/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363567] Re: Virsh Define Does Not Create AppArmor Profile
CLOSE the bug ... it' s related to this bug https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/77 Copying the key file /usr/share/qemu/bios.bin (which is a link to /usr/share/seabios.bin) to a "non-system" directory enables generation of a valid, though incomplete apparmor definition In order to support Virtio access, a second apparmor file was generated (copy the file libvirt-.files as a starting point) and added as an entry in the master ie. libvirt- This resolevd the app-armor issues ** Changed in: libvirt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363567 Title: Virsh Define Does Not Create AppArmor Profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1363567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363567] [NEW] Virsh Define Does Not Create AppArmor Profile
Public bug reported: When creating a new VM definition using "virsh define" no apparmor profile was created and consequently the VM cannot be started Furthermore, a manually created apparmor definition could not be loaded (according to error message) Release Ubuntu Trusty, uname -r 3.13.0-34-generic Libvirt package versions ||/ Name Version Architecture Description +++--===-===-== ii libvirt-bin 1.2.2-0ubuntu13.1.2 amd64 programs for the libvirt library ii libvirt-doc 1.2.2-0ubuntu13.1.2 all documentation for the libvirt library ii libvirt0 1.2.2-0ubuntu13.1.2 amd64 library for interfacing with different virtualization systems ii libvirtodbc0 6.1.6+repack-0ubuntu3 amd64 high-performance database - ODBC libraries Qemu package versions ||/ Name Version Architecture Description +++--===-===-== un qemu (no description available) un qemu-common (no description available) ii qemu-keymaps 2.0.0+dfsg-2ubuntu1.2 all QEMU keyboard maps ii qemu-kvm 2.0.0+dfsg-2ubuntu1.2 amd64 QEMU Full virtualization on x86 hardware (transitional package) un qemu-kvm-spice (no description available) ii qemu-launcher1.7.4-1ubuntu2 all GTK+ front-end to QEMU computer emulator un qemu-system (no description available) ii qemu-system-common 2.0.0+dfsg-2ubuntu1.2 amd64 QEMU full system emulation binaries (common files) un qemu-system-i386 (no description available) ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.2 amd64 QEMU full system emulation binaries (x86) un qemu-system-x86-64 (no description available) un qemu-user (no description available) un qemu-user-static (no description available) ii qemu-utils 2.0.0+dfsg-2ubuntu1.2 amd64 QEMU utilities un qemuctl (no description available) AppArmor package versions ||/ Name Version Architecture Description +++--===-===-== ii apparmor 2.8.95~2430-0ubuntu5amd64 User-space parser utility for AppArmor un apparmor-docs (no description available) un apparmor-easyprof (no description available) un apparmor-easyprof-ubuntu (no description available) un apparmor-parser (no description available) un apparmor-profiles (no description available) un apparmor-utils (no description available) xml imported via virsh define === win7_wd2t 1c19f09f-9e6c-4c2e-a13a-8bed5628f6f0 6291456 6291456 2 hvm /usr/share/qemu/bios.bin Haswell destroy restart destroy /usr/bin/qemu-system-x86_64 xml created by virsh === win7_wd2t 1c19f09f-9e6c-4c2e-a13a-8bed5628f6f0 6291456 62
Re: [Bug 152160] Re: distribution upgrade failed (ubuntu 7.10 beta 27-9-07)
Michael, done Regards Rob Michael Vogt wrote: > Thanks for taking the time to report this bug and helping to make Ubuntu > better. Could you please add the log files from '/var/log/dist- > upgrade/' to this bugreport as attachments to your bug report? Thanks > in advance. > ** Changed in: update-manager (Ubuntu) > Assignee: (unassigned) => Michael Vogt (mvo) >Status: New => Incomplete > > -- distribution upgrade failed (ubuntu 7.10 beta 27-9-07) https://bugs.launchpad.net/bugs/152160 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152160] Re: distribution upgrade failed (ubuntu 7.10 beta 27-9-07)
added the log files from '/var/log/dist-upgrade/' to this bugreport as attachments . as requested ** Attachment added: "APT Log as requested" http://launchpadlibrarian.net/10048188/apt.log -- distribution upgrade failed (ubuntu 7.10 beta 27-9-07) https://bugs.launchpad.net/bugs/152160 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152160] Re: distribution upgrade failed (ubuntu 7.10 beta 27-9-07)
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/9959696/Dependencies.txt -- distribution upgrade failed (ubuntu 7.10 beta 27-9-07) https://bugs.launchpad.net/bugs/152160 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152160] Re: distribution upgrade failed (ubuntu 7.10 beta 27-9-07)
really just needs a helpful message back to the user -- distribution upgrade failed (ubuntu 7.10 beta 27-9-07) https://bugs.launchpad.net/bugs/152160 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152160] distribution upgrade failed (ubuntu 7.10 beta 27-9-07)
Public bug reported: Binary package hint: update-manager Synaptec was open at the time of the update. Updater found the required packages, downloaded tham, failde when it commenced the install Closed Synaptec and re-ran ... successfully Perhaps a check for conflicts is appropriate ? ProblemType: Package Architecture: i386 Date: Sat Oct 13 09:11:28 2007 DistroRelease: Ubuntu 7.10 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2) Package: update-manager 1:0.76 PackageArchitecture: all SourcePackage: update-manager Title: package update-manager 1:0.76 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an error code (2), E:Sub-process /usr/bin/dpkg returned an err
