Magiea 8; Install Win 10 KMV with Virt-Manager

This forum is dedicated to advanced help and support :

Ask here your questions about advanced usage of Mageia. For example you may post here all your questions about network and automated installs, complex server configurations, kernel tuning, creating your own Mageia mirrors, and all tasks likely to be touchy even for skilled users.

Magiea 8; Install Win 10 KMV with Virt-Manager

Postby Sabungayam » Apr 27th, '21, 08:57

First', I have searched the FORUM as thoroughly as I know how about Virt-manager and it's set up here in Mageia... Hopefully I have done that right.
I followed instructions from the Wiki and a post here in the forum.

https://wiki.mageia.org/en/Virt-Manager

viewtopic.php?f=41&t=12043


Now I have some GUIDES here and I am expecting the Guides for Redhat/Fedora (He says it's the same steps for both) to be what should work here in Mageia.

https://getlabsdone.com/10-easy-steps-t ... linux-kvm/

However, I was wondering if there are any here who have installed Windoz 10 in a KVM in Mageia and what steps did they use or were there things that did not need to be done or things that perhaps
needed to be added according to these steps.

https://getlabsdone.com/install-windows ... buntu-kvm/

The other guide also by the same person but for ubuntu. What I found noteworthy for myself anyway as a total NEWB with KVM and Virt-Manager is the graphic set up for Windoz between them. Very
different process and if anyone knows, which process would be used for Mageia?

Lastly, I was using or going to use Virtualbox. It seems easier from the setup and use, but is basically subject to kernel changes that may break it.

This is why after a little reading, I think KVM/QEMU is better for stability.

I have no PERSONAL NEED of Windoz, but I unfortunately need it for some companies Windoz only software that they want to be used for some work. This is why I need Windoz and why because it will be
work related, I have a concern with Virtual-box and kernel upgrades. (At this time, Windoz duelboot is not an option. To be honest everything I have seen and read about it, it is the MOST UNSTAbLE and
troublesome fight that I really want to avoid when I just need a couple simple programs in Windoz. Plus I hate Windoz Interface and really prefer not to work in it.)

However, I have never done anything with KVM. I am not a DISTRO HOPPER and so also have little need of virtual machines for testing or anything.

If any here have done anything with Windoz in KVM in Mageia, your knowledge and help would be greatly appreciated.

I have can do nothing as of yet. No time. Waiting until next week when I may have a couple days off.

If any of those guides will work fine without any modifications as well... I hope someone can let me know and I shall just go with one of those.

Thank you in advance.
Sabungayam
 
Posts: 128
Joined: Aug 18th, '20, 06:52

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby doktor5000 » Apr 27th, '21, 17:30

If you really need such a lengthy guide to setup a VM, then I'd say better go with virtualbox.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16664
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby Sabungayam » Apr 28th, '21, 03:24

:lol: I would agree, except I stated already why I want to try this. I am familiar with Virtual Box and it seems aimed at being easy and simple.

However, it's the behavior of Windoz that is the problem as well as the scenario that I need it for.

1. The infamous Windoz license which one has to buy. Unless my understanding is wrong, it may be because I really don't bother with Windoz and
since beginning work in China in 2005 haven't delt with Windoz since XP. ;) But as I understand it, you can't transfer your license to another install
unless you go into Windoz and do something to basically REMOVE that license from the current install.

So, let's say my VB is broken or down for a bit pending fixes with a new Kernel, like it was when I posted some months ago I think last year when indeed
I tried to use Virtual Box to install Windoz. If I am using it for work, then it goes down and I didn't remove than license and I can't access it to do so.

Bit of trouble I expect if I'm using it for work and I can't access it. It seems that VB was down for a while until they got up with a fix for the current Kernels.

I don't have the money at the moment to just buy a cheap backup Windoz machine.

So I have a concern and of course if the VB goes down again due to changes in Kernel I would eventually end up needing to find another solution anyway.

2. :lol: Like your sense of humor, well, there are SHORTER guides and I can actually see what the steps are so maybe I can put my concern another way and hope it's
understandable.


In his two guides, the person wrote up some steps for enabling the QXL driver needed for Windows. For the RPM or Redhat/Fedora install, he wrote that it uses the
Cirrus adapter upon install and then you have to add the QXL driver and fix this post install before rebooting it then some steps for removing all that stuff after install.

So, I guess my basic question is with Mageia is that necessary?

It's his 3rd step where he's talking about all that. I don't know if Mageia uses that and I do know that Redhat tends to be behind quite a bit when it comes to hardware
compared to Mageia and Fedora. So maybe that's not needed anymore though his article was written in 2020.

In his other guide which uses Ubuntu, non of these steps were mentioned getting QXL driver in. I will have to find my link to it, one of my shorter guides also didn't mention this.

So there's my basic question. are the steps in his guide for Redhat to get the QXL driver up in the install needed or can it be done just as in his other guide which one of my shorter guides
also sets up that way but I have to look at it to see which distro he was using again.

Likewise, I choose the long drawn out guide to look at because though Virt-Manager is a very nice to use GUI for this purpose until I kind of go through the steps of using it and seeing
what options are etc. I am quite unfamiliar with it. VB is VB and Virt-Manager in Virt- Manager. I wouldn't try to go in expecting similar ways of working with them.

So I am trying to get as much detail as I can because I am unlikely to have time to FIX any mistakes I make due to my doubled work schedule at the moment.

So I was just wondering if anyone had installed Windoz 10 using Virt-Manager and what were their steps and experience with doing so.

But I will give Virt-Manager a try. It seems a more stable solution and I don't have any more time to search other "options" at this time. :|

Generally, if possible, before attempting something I try to read and find as much information as possible before I start to avoid problems and issues. ;)
Sabungayam
 
Posts: 128
Joined: Aug 18th, '20, 06:52

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby doktor5000 » Apr 28th, '21, 18:07

I don't get why you're making something like that more complex then it needs to be. If you want to try out libvirt, then try it out.
That does not change anything about the windows license BTW, if your KVM breaks you have the exact same issue as with virtualbox.

You've probably already put more time into posting this, compared to simply trying out if it works for you or if it doesn't.
And for the VirtIO drivers under Windows, yes that is necessary the same way as you need virtualbox guest additions, at least the last time I tested it still was.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16664
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby Sabungayam » May 7th, '21, 07:08

Thank you, but time wise, I post often when I have a few moments or on break at work. I can't do things such as install a VM at work though.

Trying it out verses getting information to avoid trouble is not my preferred method. I would rather avoid trouble. Whatever the Cirrus thing he was talking about was not necessary.

Seems just following the Ubuntu instructions will work here. It's done. Except the issue with sound which is universal.

Easy solution, USB sound card. They're so cheap now and I was using one because one of my computers has a dumb sound card that is a pain with Linux.

Try installing Scream when I get time since there is an easy install script that says it's compatible with Fedora but does NOT work with Mageia.

Thanks for everyone's responses.
Sabungayam
 
Posts: 128
Joined: Aug 18th, '20, 06:52

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby Sabungayam » May 7th, '21, 09:04

Because I started this post about trying specifically to deal with Windoz 10 in KVM using virt-manager. I am adding this sound question here.

If it should go in another post then sorry.

I mentioned I would give scream a try.

These are the instructions in the Scream readme. Followed and I have a binary for receiver.
# scream

scream is a Scream audio receiver using Pulseaudio, ALSA or stdout as audio output.

## Compile

Compilation is done using CMake.

If Pulseaudio or ALSA headers are found, support for those will be compiled in (see below for distro packages to install). If Pulseaudio is compiled in, it will be the default output, otherwise ALSA will be the default. If both Pulseaudio and ALSA are not compiled in, raw/stdout will be the default.

```shell
$ mkdir build && cd build
$ cmake ..
$ make
```

### Pulseaudio

```shell
$ sudo yum install pulseaudio-libs-devel # Redhat, CentOS, etc.
or
$ sudo apt-get install libpulse-dev # Debian, Ubuntu, etc.
```

### ALSA

```shell
$ sudo yum install alsa-lib-devel # Redhat, CentOS, etc.
or
$ sudo apt-get install libasound2-dev # Debian, Ubuntu, etc.
```

## Usage

You can see the accepted options by using the -h (help) option.

```shell
$ scream -h
```

### Network mode

```shell
$ scream
```

This starts the Scream client in multicast mode, using the default audio output.
Unicast mode is also supported, and can be used by passing the -u option. If your machine has more than one network interface, you may need to set the interface name which receives scream packets.

```shell
$ scream -i eth0
```

### libpcap mode

This starts the Scream client in libpcap (sniffer) mode. This mode is mostly useful if you are able to the UDP
multicast/unicast transmission in `wireshark`/`tcpdump` but unable to have it be delivered to the
user-space Scream client.

```shell
$ scream -P -i macvtap0
```

If you have the hard requirement of having to run the receiver as non-root due to `pulseaudio`/`alsa`
uid/gid issues, you can do the following:

```shell
# setcap cap_net_raw,cap_net_admin=eip ./scream
```

### IVSHMEM (Shared memory) mode

Make sure to have read permission for the shared memory device and execute

```shell
$ scream -m /dev/shm/scream-ivshmem
```

### ALSA output

If you experience excessive underruns under normal operating conditions,
lower the process niceness; if it still underruns, raise the default
target latency (50 ms) with `-t`:

```shell
$ scream -o alsa -t 100
```

Note that audio hardware typically has small buffers that result in a
latency lower than the target latency.

Run with `-v` to dump ALSA PCM setup information.

Run with `env LIBASOUND_DEBUG=1` to debug ALSA problems.


I am including the output from this process which seems to have gone through just fine.

Code: Select all

[peppermint@localhost unix]$ mkdir build && cd build
[peppermint@localhost build]$  cmake ..
-- The C compiler identification is GNU 10.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.7.3")
-- Checking for module 'libpulse-simple'
--   Found libpulse-simple, version 14.2.0-2.1.mga8
-- Checking for module 'alsa'
--   Package 'alsa', required by 'virtual:world', not found
-- Checking for module 'jack'
--   Package 'jack', required by 'virtual:world', not found
-- Checking for module 'soxr'
--   Package 'soxr', required by 'virtual:world', not found
-- Checking for module 'libpcap'
--   Package 'libpcap', required by 'virtual:world', not found
-- Configuring done
-- Generating done
-- Build files have been written to: /home/peppermint/vmsound/scream-master/Receivers/unix/build
[peppermint@localhost build]$ make
Scanning dependencies of target scream
[ 16%] Building C object CMakeFiles/scream.dir/scream.c.o
[ 33%] Building C object CMakeFiles/scream.dir/network.c.o
[ 50%] Building C object CMakeFiles/scream.dir/shmem.c.o
[ 66%] Building C object CMakeFiles/scream.dir/raw.c.o
[ 83%] Building C object CMakeFiles/scream.dir/pulseaudio.c.o
[100%] Linking C executable scream
[100%] Built target scream
[peppermint@localhost build]$
peppermint@localhost build]$ sream -h
bash: sream: command not found
[peppermint@localhost build]$



so, following the read me, none of these "scream" commands are available. Don't work don't start.

This is a video link which is a couple years old since the "make" instructions have changed. It's from 2019.

However it's also for Ubuntu but, the basic setup seems like it should work. Creating the "service"

Code: Select all
[peppermint@localhost build]$ scream -h
bash: scream: command not found
[peppermint@localhost build]$ systemctl status scream.service
● scream.service - Scream
     Loaded: loaded (/etc/systemd/system/scream.service; enabled; vendor preset>
     Active: inactive (dead)
lines 1-3/3 (END)




I did follow his directions but, I guess the inital commands from the Scream readme are which says "scream command unavailable" is why nothing is working.

Yes, I modified his commands from the video and actually just used "scream -i" as in the readme versus his old commands from 2 years ago. I pointed to the folder correctly.

Does anyone have any idea why the scream receiver is simply not available? After it's compiled? I have also tried the commands in SU as well with no result.

I did not build it as super user. I followed directions and it is built as user.

But it just seems like it's not here? I also clicked it as it is an executable and still no results here.

This is beyond my meager skill level to sort out what is missing or not connected here. By the way per the instructions of the readme file I did install the dev lib for pulseaudio. before doing the compile.

https://github.com/duncanthrax/scream

The primary project page in case I missed something.

Receivers
Unix with Pulseaudio, JACK or ALSA: Not included in the installer package. Please see the README in the Receivers/unix folder. Various contributors have written code for this receiver:

@roovio: JACK support.
@ivan: Original ALSA code.
@martinellimarco: IVSHMEM support.
@accumulator: Refactoring into single binary and cmake support.
@F5OEO: Raw output support.
Windows: ScreamReader, contributed by @MrShoenel. Included in the installer package as of version 1.2. This receiver does not support positional mapping of multichannel (more than stereo) setups - meaning a mismatch in speaker setup can lead to channels being played in the wrong position.

A 3rd-party receiver that supports Scream streams is https://github.com/mincequi/cornrow. It's primarily meant for embedded devices.

@tomek-o wrote receivers for low-power embedded systems, great for building ethernet-attached active speakers.

STM32F429 (ARM) Scream Receiver
ESP32 Scream (and RTP) Receiver
Receivers can usually be run as unprivileged users. Receiver systems that have an input firewall need to open UDP port 4010, or whatever custom port you use.



On the primary project page.

These are all the details as I can think of them. If there is other information needed please let me know what and "how" to provide it for you. Thank you.
Sabungayam
 
Posts: 128
Joined: Aug 18th, '20, 06:52

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby Sabungayam » May 7th, '21, 11:10

Can reproduce same issue on my Mageia 7 box at versus my work box. I also have Mageia 8 here but don't think at this point without further instruction or input to try building this "scream" there. I don't have a VM here but just wanted to see what was going on with this "scream".


Code: Select all
[nomadic@nomadic build]$ cmake ..
-- The C compiler identification is GNU 8.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.6.1")
-- Checking for module 'libpulse-simple'
--   Found libpulse-simple, version 12.2.0-5.mga7
-- Checking for module 'alsa'
--   Found alsa, version 1.1.9
-- Checking for module 'jack'
--   Package 'jack', required by 'virtual:world', not found
-- Checking for module 'soxr'
--   Package 'soxr', required by 'virtual:world', not found
-- Checking for module 'libpcap'
--   Package 'libpcap', required by 'virtual:world', not found
-- Configuring done
-- Generating done
-- Build files have been written to: /home/nomadic/Scream/scream-master/Receivers/unix/build
[nomadic@nomadic build]$ make
Scanning dependencies of target scream
[ 14%] Building C object CMakeFiles/scream.dir/scream.c.o
[ 28%] Building C object CMakeFiles/scream.dir/network.c.o
[ 42%] Building C object CMakeFiles/scream.dir/shmem.c.o
[ 57%] Building C object CMakeFiles/scream.dir/raw.c.o
[ 71%] Building C object CMakeFiles/scream.dir/pulseaudio.c.o
[ 85%] Building C object CMakeFiles/scream.dir/alsa.c.o
[100%] Linking C executable scream
[100%] Built target scream
[nomadic@nomadic build]$ scream -h
bash: scream: command not found
[nomadic@nomadic build]$ scream
bash: scream: command not found
[nomadic@nomadic build]$ su
Password:
[root@nomadic build]# scream
bash: scream: command not found
[root@nomadic build]# exit
exit
[nomadic@nomadic build]$ scream
bash: scream: command not found
[nomadic@nomadic build]$



I didn't do anything else other than just build "scream" according to the instructions in the "readme".
Sabungayam
 
Posts: 128
Joined: Aug 18th, '20, 06:52

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby doktor5000 » May 7th, '21, 15:54

Please create a separate thread for that as that has nothing to do with virt-manager or VM.

Apart from that, you only compiled scream, but you didn't install it (make install as root) hence the binary will only be located in the build directory, which is probably not in your PATH.

./scream should work if the binary is located directly in the top build folder.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16664
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Magiea 8; Install Win 10 KMV with Virt-Manager

Postby Sabungayam » May 8th, '21, 20:22

Thank you, as it is meant to work with the VM and solve the lack of sound of Windoz in VM that's why I thought it fit here. Sorry. Was not sure.

Ok, I was following their instructions and the readme didn't say.

So I should run

Code: Select all

make install



as root?

I will try that when I am back on that machine.

Thank you
Sabungayam
 
Posts: 128
Joined: Aug 18th, '20, 06:52


Return to Advanced support

Who is online

Users browsing this forum: No registered users and 1 guest