From: Thomas Huth <thuth@redhat.com>
To: liebrecht@grossmann-venter.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu the right way.
Date: Wed, 26 Dec 2018 08:14:26 +0100 [thread overview]
Message-ID: <665ec250-c4a5-18ba-ad71-90966a1b9e12@redhat.com> (raw)
In-Reply-To: <b0d70556767952dc739454d074bdab52@grossmann-venter.com>
On 2018-12-25 23:46, liebrecht@grossmann-venter.com wrote:
> I have been using Qemu in the past about 8 years ago or so to run legacy
> windows software.
>
> I installed the latest qemu and noticed a lot changed and cant find
> conclusive answers online.
>
> I am writing this post to find what is the right way to start to set up
> qemu with a windows 7 pro guest. I want to try and eliminate the
> iterations and find out what is really possible for the guest.
>
> Hardware used"
> 24 Core AMD rackserver.
> Host OS Debian 9 Stretch
> Guest Windows 7 Pro 32 bit
>
> Requirements:
> 1) I need to be able to run at least 4 processors in the guest. Is this
> possible with qemu as hosts ?
Try to run QEMU with "-smp 4".
> 2) I need to at least have sound working from applications in the guest
> with pulseaudio on the Debian host. Is it possible ?
Should be possible. Run the configure script before compiling with
--audio-drv-list=pa
and then make sure to give a soundcard to the guest (e.g. with the
-soundhw option).
> 3) USB, what is the level of support 2.0 3.0 ?
> ( However windo$ 7 cannot really do USB3. so usb-3 is moot anyway)
QEMU supports both, e.g. with "-device usb-ehci" for a USB 2.0
controller or with "-device nec-usb-xhci" for a USB 3.0 controller.
> 4) What kind of devices can be run through usb ?
Do you mean emulated devices? You can get a list with:
qemu-system-x86_64 -device help | grep usb
Or do you want to pass-through a real device from the host?
> The answers to 1-4 will be really helpful to decide if I should even be
> using it. The documentation is schetchy about all this.
> I tried Virtualbox, but it is just a nice looking empty promisebox
> yielding nothing. Since Qemu helped me a lot in the past I will have
> better chances here.
>
> 5) I am currently installing win7pro guest with command
> $] qemu-system-x86_64 -boot c -cdrom /dev/cdrom -m 2048M
>
> and left out all the network card and sound driver switches as I have no
> clue what I should choose.
> Can they be configured afterwards ?
I don't have much clue about Windows, but I think you can change it
afterwards - it's like you're changing PCI cards of a real system in
that case.
HTH,
Thomas
next prev parent reply other threads:[~2018-12-26 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 22:46 [Qemu-devel] Qemu the right way liebrecht
2018-12-26 7:14 ` Thomas Huth [this message]
2018-12-26 23:42 ` liebrecht
2018-12-27 0:46 ` liebrecht
2018-12-27 1:13 ` liebrecht
2018-12-27 1:14 ` liebrecht
2018-12-27 2:46 ` liebrecht
2019-02-04 10:49 ` [Qemu-devel] Usb device disappears from linux after Qemu starts liebrecht
-- strict thread matches above, loose matches on Subject: below --
2018-12-25 22:48 [Qemu-devel] Qemu the right way liebrecht
2019-01-04 15:14 ` Stefan Hajnoczi
[not found] <201812270613.51558.randrianasulu@gmail.com>
2018-12-27 22:06 ` liebrecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=665ec250-c4a5-18ba-ad71-90966a1b9e12@redhat.com \
--to=thuth@redhat.com \
--cc=liebrecht@grossmann-venter.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).