Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUse VM name in error notifications #2814
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
May 21, 2017
Member
The kernel issue sounds like #2757.
I take it that this issue is only about enhancing the text of dom0 notifications to include the name of the VM whenever a VM is mentioned.
|
The kernel issue sounds like #2757. I take it that this issue is only about enhancing the text of dom0 notifications to include the name of the VM whenever a VM is mentioned. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
anoadragon453
May 21, 2017
anoadragon453
commented
May 21, 2017
|
I take it that this issue is only about enhancing the text of dom0
notifications to include the name of the VM whenever a VM is mentioned
That's correct.
…On 05/20/2017 05:21 PM, Andrew David Wong wrote:
The kernel issue sounds like #2757
<#2757>.
I take it that this issue is only about enhancing the text of dom0
notifications to include the name of the VM whenever a VM is mentioned.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2814 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABR7mOg8AHkbjBrsgH65ovkWJBouEk7Yks5r74NsgaJpZM4NdfXz>.
|
andrewdavidwong
added
C: qubes-manager
enhancement
P: minor
UX
labels
May 21, 2017
andrewdavidwong
added this to the Release 4.0 milestone
May 21, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
May 21, 2017
Member
I'm labeling this with C: qubes-manager since these notifications could be thought of as part of the "decomposed" Qubes Manager in 4.0 (#2132).
|
I'm labeling this with |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
rename issue to "Use VM name in error messages"? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
anoadragon453
commented
May 24, 2017
|
Good idea. |
anoadragon453
changed the title from
Slight Usability Improvement Suggestion
to
Use VM name in error notifications
May 24, 2017
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.1
Mar 31, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarta
Jul 13, 2018
Better notifications for VM start errors have been added here: QubesOS/qubes-desktop-linux-manager@fbc1ec1
marmarta
commented
Jul 13, 2018
|
Better notifications for VM start errors have been added here: QubesOS/qubes-desktop-linux-manager@fbc1ec1 |
anoadragon453 commentedMay 17, 2017
Qubes OS version (e.g.,
R3.2):R3.2
Earlier today I was updating to a new Linux Xen Kernel and since a few of my AppVMs were using an older kernel I kept receiving an error message pop up when trying to start them, even after changing their kernels in the Qubes-Manager GUI.
Turns out the issue lay not in the AppVMs I was starting, but starting the Proxy/NetVMs that they required. Typical n00b mistake I know, but if the error notification stating that "VM could not be started: Linux kernel blah blah..." contained the name of the VM that was generating that message instead of just "VM" it would have saved me about 15 min of pointless Googling :)