Changes are already in proposed, so soon to be fully fix released.
** Changed in: virt-manager (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741617
T
On 30/01/18 06:55, ChristianEhrhardt wrote:
> Yes I was after the video part, but as I assumed we both have the same
> default.
> Hmm, I'm soon out of ideas :-/ (maybe trying with the different video
> devices, no not really)
>
>
> OTOH the next thing I wanted to check were input devices - and th
Yes I was after the video part, but as I assumed we both have the same default.
Hmm, I'm soon out of ideas :-/ (maybe trying with the different video devices,
no not really)
OTOH the next thing I wanted to check were input devices - and there is a
difference that might be related.
I have this
Here it is:
(assuming you're just after the graphics which is (I was sure qxl):
virsh dumpxml xub_64 |grep qxl
If not - here is the whole thing:
virsh dumpxml xub_64
xub_64
50fea9df-e318-490a-aca6-725c8bcb75e3
393216
393216
1
hvm
Hasw
> Just to be sure we're both on the same page re mouse integration -
> currently I'm having to Ctrl+AltL to release mouse to host, VBox works
> fine here (have it installed for when qemu/virt-manager falls over
> locally)
Hmm - for Ubuntu guests on Ubuntu host with the stack from Bionic +
the ppa
Did all those things - before my cuppa ...
vm's now boot so the apparmor thing appears to have done the trick there
- thanks very much :)
Re The Original Issue ...
Just to be sure we're both on the same page re mouse integration -
currently I'm having to Ctrl+AltL to release mouse to host, VBox
libvirt_4.0.0-1ubuntu1~ppa5 is building in the ppa and once available
(~1h) will have the fix included.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741617
Title:
Mouse integration not working
To
Ok, the following is what you can add to your local override until in the next
version of libvirt:
Add to "/etc/apparmor.d/local/usr.sbin.libvirtd"
unix (send, receive) type=stream addr=none
peer=(label=libvirt-[0-9a-f]*-[0-9a-f]*-[0-9a-f]*-[0-9a-f]*-[0-9a-f]*),
# required if guests run without
Note: about the original issue of the integration, there are many things around
wayland still.
I heard that the Desktop Team will switch back to X11 for stability in 18.04 -
didn't happen yet but should be on the way and resolve many similar issues.
On the apparmor Deny we found while testing as
Thank,
so that comes down to
operation="file_receive" profile="/usr/sbin/libvirtd" pid=8341
comm="qemu-system-x86" family="unix" sock_type="stream" requested_mask="send
receive" denied_mask="send receive" addr=none peer_addr=none
peer="libvirt-50fea9df-e318-490a-aca6-725c8bcb75e3"
operation="fi
@ paelzer
ok - apparmor file did in fact contain the line you quote.
I re-added the ppa and upgraded, following the upgrade dmesg had this:
[ 2764.569019] audit: type=1400 audit(1516979522.226:28): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="virt-aa-helper" pid=765
Thanks for your fast response, you are in my top league of bug
reporters!
I'd not assume it is qemu.conf.
But I have seen a similar issue in the past.
This should be fixed since bug 1668681.
Sanity check ... yes the latest package did not by accident drop it.
Your file: /etc/apparmor.d/abstractio
@paelzer - absolutely can ;)
But ...
Error connecting to graphical console:
internal error: unable to execute QEMU command 'getfd': No file descriptor
supplied via SCM_RIGHTS
Possibly to do with my change to /etc/libvirt/qemu.conf
Upgrading asked me whether to change this file to default - I s
Hi Kev,
there are major changes everywhere in 18.04 still.
Do you think you have a chance to test your 18.04 with everything updated to
the latest plus the following ppa?
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3108
--
You received this bug notification because you are a mem
@paelzer -
I get no mouse integration with any of the current *buntu guests - and
bionic of course.
If there are some sort of logs (either host or guest) which I could
supply that would help - just ask and I'll do so asap.
--
You received this bug notification because you are a member of Ubuntu
On Mon, Jan 8, 2018 at 6:50 PM, Kev Bowring <1741...@bugs.launchpad.net> wrote:
> @paelzer
>
> Hi Christian - using this on Xubuntu, host and guest(s) - no wayland ;)
>
> FTR - had the same during the artful cycle.
Interesting, but also killing parts of my hope/theory :-/
I tried a bit around (I'm
What is the guest release you are running btw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741617
Title:
Mouse integration not working
To manage notifications about this bug go to:
https://bugs.
@paelzer
Hi Christian - using this on Xubuntu, host and guest(s) - no wayland ;)
FTR - had the same during the artful cycle.
Thanks for looking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741617
Hi Kev,
there is a bunch of issues in relation to Wayland on either the host, the guest
or both.
In most cases like this it is "just" that.
The uploads I plan to virt-manager and more of the virt stack should cover this.
Once ready we should evaluate your case, but until then I have to ask for you
19 matches
Mail list logo
