tim@desktop-tim:~$ uname -a
Linux desktop-tim 4.0.1-040001-generic #201504290935 SMP Wed Apr 29 09:36:55
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
No bug, I'll pull the other kernels down and test them over the next few
days
--
You received this bug notification because you are a member of Ubunt
I was having the same problem with a number of USB3 harddisks, upgrading
to 4.0.1 from the mainline PPA has fixed it for me.
I think it might be triggered by my Yubikey security key. I get "WARN
Event TRB for slot 8 ep 4 with no TDs queued?" when gpg accesses the
key.
--
You received this bug no
Installing the package from Vivid on my Utopic desktop has fixed my
problems with my Yubikey neo acting as a smart card, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regressi
I believe this is the problematic git commit:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=d0d4b8ad76d3e8a859ee90701a21a3f003a22c1f;hp=dae7054b7697d30f2b88cd5dff3dfb954323d40b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Correction the bug number for the other bug is #1004606
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/453335
Title:
apparmor complains about write access to a readonly file
To manage notifications
I think this is actually causing a moderately serious regression with
snapshots.
If you look at the contents of an apparmor define for an example VM the
deny that silences the error here also prevents snapshot commits from
working and because the error is hidden makes this extra difficult to
debu
I think I have found the cause of this problem, in bug number 453335 an
apparmor fix was put in place to deny access to certain read only media
and also to hide the error message about access being denied.
I think this is causing the duplicate entries in apparmor and also
hiding the errors about
Experimenting further if I take out the seclabel line (shown below) from
my VM definition everything works as expected with snapshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004606
Title:
Definitely still a problem in utopic, I think the issue is caused by
this part of the apparmor config:
/var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext4.img-
zfs-1.qcow2 is my current snapshot and I am trying to commit it back to
/var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext
Definitely still a bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223730
Title:
mDNS failure with openvswitch 1.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
I've now updated to Saucy and I still have the same problem on multiple
machines with openswitch.
I have a KVM test machine that has a ubuntu VM running on it plugged
into a vswitch that is in turn plugged in via the quad port bond you can
see here.
Iron is the KVM host, the host shows no mDNS ac
Ah sorry, I had updated to the latest OVS version from saucy by enabling
the saucy repos and just updating relevant libvirt and OVS packages.
The show command I included was run on 1.9 after I downgraded again to
get printing working (printers found via mDNS)
I've looked at the packets on the raw
openvswitch setup
root@tim-6460b:~# ovs-vsctl show
ccdda6ff-e90d-41f5-9f87-5e68f562b73c
Bridge private
Port private
Interface private
type: internal
Bridge internal
Port internal
Interface internal
type: internal
Public bug reported:
I have upgraded my Ubuntu 13.04 KVM test machine to the latest version
of QEMU/openvswitch/libvirt and I am having problems with mDNS. I've not
upgraded the kernel on the host machine so I am using current
(3.8.0-30).
Fully internal openvswitch:
VM -> VM mDNS works
VM -> in
This seems to be related to the iscsi opcode
ATA COMMAND PASS THROUGH (16)
However I'm not sure what is triggering it, could it be related to
spinning down of disk during idle?
--
iscsi_trgt: scsi_cmnd_start(1035) Unsupported 85
https://bugs.launchpad.net/bugs/584668
You received this bug notif
15 matches
Mail list logo
