Normally, yast does that just nicely. One wild guess, maybe the device is not linked to the guest anymore. Please check with:
modprobe vmcp vmcp query virtual <device> Berthold On Wed, 11 Mar 2015 07:46:16 -0400 Michael Weiner <mwei...@infinite-blue.com> wrote: > Thanks. I did everything but activate the device through yast. I just > linked the device through command line. -- ---------------------------------------------------------------------- Berthold Gunreben Build Service Team http://www.suse.de/ Maxfeldstr. 5 SUSE LINUX GmbH D-90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nürnberg) ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
