similar to: unable to access xen guest's console

Hello all, I have a NFSroot'ed a couple of OS platforms so that servers can have the option (web access) to: a. boot off a CentOS NFS root over the network b. or LOCAL hardrive (FreeBSD). A Simple script controls this so that if user selects NFS root - - /etc/dhcpd.conf will be updated to include the filename "pxelinux.0" parameter and it will find its configuration file based

Hello all, I have a Xen kernel running on a CentOS 5.1: xen-users@lists.xensource.com The Xen versions I have are: rpm -qa | grep xen kernel-xen-2.6.18-53.1.21.el5 xen-libs-3.0.3-41.el5_1.6 xen-3.0.3-41.el5_1.6 xen-devel-3.0.3-41.el5_1.6 So far I have a few Guest DOMU''s installed successfully - various CentOS flavors ... 1. I am able to successfully install Ubuntu 6.06 as a Xen

Hello all, I have seen various reports on this error posted in the past few years, but was unable to find a resolution to the various postings. I've googled the error messages too, and have hit on various sporadic similar problems encountered with no resolutions .. Apologize if this has been exhaustively queried upon in the past; however, I'd like to try asking again, nevertheless:

Greetings Users! On March 24th we're hosting the first of a new series of webinars entitled "Asterisk Tech-Tips". Our goal is to present a new "episode" or "issue" or "webisode" (or whatever you want to call it) every other week. Here's the idea: Asterisk Tech-Tips are all about helping people get the most from their Asterisk systems. Each

Greetings User's List, Just a last minute reminder that Malcolm Davenport will be headlining our first Asterisk Tech Tips webinar covering the cool ways you can integrate Asterisk with Google Chat and Google Voice. Register now and join us in 30 minutes. Here's the link: http://www.asterisk.org/techtips Thanks! -S Steve Sokol Asterisk Marketing Director Digium, Inc.

Hello all, I have finally successfully booted a diskless NFS Gentoo client and I am very pleased with it! I only have one issue left I'd like to understand; the master Gentoo server that I based my diskless image from boots nicely via dhcp and accepts the hostname parameter its DHCP server passes along with its leased IP address. I have posted in the Gentoo forum, but thought I'd post

Hi all, I''m a newbie on this list. I''m using xen 3.0.3 on CentOS50. I installed a new flavor of kernel in a domU via a standard RPM, which modified my grub.conf by adding a new entry to boot on the new kernel. When rebooting the domU by pygrub, I didn''t see the new grub entry. I tried to restart xend, with no effect. By googling a little, I understood that kernel

Hi all, authentication forwarding depends much on the environment it is used in, but generally on shared hosts it is considered insecure, as this documentation and common sense tell us: http://unixwiz.net/techtips/ssh-agent-forwarding.html Anyway, I have an auth forwarding security enhancement proposal. I hope I am not duplicating someone else's words/thoughts, please notify me if this is

Dear admins, My centos wiki username: MarkSmulders Proposed subject: Nested virtualization on CentOS 6 Proposed location: under Howto > Virtualization Content is ready for preview under "Steps to enable nested virtualization on CentOS 6" in my online notes at https://sites.google.com/a/nocoffee.nl/technotes/nested-virtualization-on-centos-6 Thanks, Mark (using alias

HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The

There should be no functional changes here Signed-off-by: Lyude Paul <lyude at redhat.com> Cc: Juston Li <juston.li at intel.com> --- drivers/gpu/drm/drm_dp_mst_topology.c | 71 ++++++++++++++++----------- 1 file changed, 42 insertions(+), 29 deletions(-) diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c index 9b1b5c9b1fa0..2ab16c9e6243

When reprobing an MST topology during resume, we have to account for the fact that while we were suspended it's possible that mstbs may have been removed from any ports in the topology. Since iterating downwards in the topology requires that we hold &mgr->lock, destroying MSTBs from this context would result in attempting to lock &mgr->lock a second time and deadlocking. So, fix

When reprobing an MST topology during resume, we have to account for the fact that while we were suspended it's possible that mstbs may have been removed from any ports in the topology. Since iterating downwards in the topology requires that we hold &mgr->lock, destroying MSTBs from this context would result in attempting to lock &mgr->lock a second time and deadlocking. So, fix

On Wed, 2019-09-25 at 14:16 -0400, Sean Paul wrote: > On Tue, Sep 03, 2019 at 04:45:41PM -0400, Lyude Paul wrote: > > When reprobing an MST topology during resume, we have to account for the > > fact that while we were suspended it's possible that mstbs may have been > > removed from any ports in the topology. Since iterating downwards in the > > topology requires

On Thu, Dec 13, 2018 at 08:25:31PM -0500, Lyude Paul wrote: > There should be no functional changes here Would be good to explain what you did refactor here, instead of me trying to reconstruct it from the patch. Especially pre-coffee that helps :-) > > Signed-off-by: Lyude Paul <lyude at redhat.com> > Cc: Juston Li <juston.li at intel.com> > --- >

s/drm_dp_get_validated_port_ref/drm_dp_mst_topology_get_port_validated/ s/drm_dp_put_port/drm_dp_mst_topology_put_port/ s/drm_dp_get_validated_mstb_ref/drm_dp_mst_topology_get_mstb_validated/ s/drm_dp_put_mst_branch_device/drm_dp_mst_topology_put_mstb/ This is a much more consistent naming scheme, and will make even more sense once we redesign how the current refcounting scheme here works.

Which reduces indentation and makes this function more legible. Cc: Juston Li <juston.li at intel.com> Cc: Imre Deak <imre.deak at intel.com> Cc: Ville Syrjälä <ville.syrjala at linux.intel.com> Cc: Harry Wentland <hwentlan at amd.com> Cc: Daniel Vetter <daniel.vetter at ffwll.ch> Signed-off-by: Lyude Paul <lyude at redhat.com> ---

Once upon a time, hotplugging devices on MST branches actually worked in DRM. Now, it only works in amdgpu (likely because of how it's hotplug handlers are implemented). On both i915 and nouveau, hotplug notifications from MST branches are noticed - but trying to respond to them causes messaging timeouts and causes the whole topology state to go out of sync with reality, usually resulting in

Once upon a time, hotplugging devices on MST branches actually worked in DRM. Now, it only works in amdgpu (likely because of how it's hotplug handlers are implemented). On both i915 and nouveau, hotplug notifications from MST branches are noticed - but trying to respond to them causes messaging timeouts and causes the whole topology state to go out of sync with reality, usually resulting in

On Wed, Sep 25, 2019 at 04:08:22PM -0400, Lyude Paul wrote: > On Wed, 2019-09-25 at 14:16 -0400, Sean Paul wrote: > > On Tue, Sep 03, 2019 at 04:45:41PM -0400, Lyude Paul wrote: > > > When reprobing an MST topology during resume, we have to account for the > > > fact that while we were suspended it's possible that mstbs may have been > > > removed from any