qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: fantonifabio@tiscali.it
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Advice on some configuration parameters
Date: Fri, 01 Mar 2013 13:45:34 +0100	[thread overview]
Message-ID: <5130A2EE.7080303@redhat.com> (raw)
In-Reply-To: <511A3E25.9010303@tiscali.it>

Il 12/02/2013 14:05, Fabio Fantoni ha scritto:
> I'm making patches to enable some qemu upstream features in xen that are
> missing in libxl.
> I'm trying to do it just by giving arguments to qemu, and I want them to
> be dynamic (e.g. without physical addresses if possible) and concise.

They should use physical addresses, otherwise changing the VM hardware
in trivial ways may cause a waterfall effect and cause Windows to
reactivate.

> If I try to set up virt-manager so that it doesn't point to a file, it
> uses this configuration:
> 
> -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7
> -device
> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
> 
> -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
> -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
> 
> This seems to differ from the configuration file, e.g. you have
> multifunzion=on only on the first uhci

That doesn't matter.

> , besides I can't understand how many physical ports are defined.

There are 6 ports, controlled by either the EHCI for USB 2.0 devices
(the EHCI controls 6 ports) or by one of the three UHCI for USB 1.1
ports (one UHCI has 2 ports).

> I tried setting 9 usbredirection
> channels in virt-manager but that configuration doesn't change and no
> errors are reported, but I doubt that physical ports are being define
> dynamically.

QEMU creates hubs automatically I think in that case.

> About spice vdagent at the moment I'm using this configuration that
> seems to work:
> -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device
> virtserialport,chardev=vdagent,name=com.redhat.spice.0
> 
> But I noticed that virt-manager use this slightly different one:
> -chardev pty,id=charserial0 -device
> isa-serial,chardev=charserial0,id=serial0 -chardev
> spicevmc,id=charchannel0,name=vdagent -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
> 
> Are there any problem with the more concise one I'm using?

It is the same.

Paolo

  parent reply	other threads:[~2013-03-01 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <511A3E25.9010303@tiscali.it>
2013-03-01 10:02 ` [Qemu-devel] Advice on some configuration parameters Fabio Fantoni
2013-03-05 10:19   ` [Qemu-devel] [Spice-devel] " Hans de Goede
2013-03-05 14:20     ` Fabio Fantoni
2013-03-01 12:45 ` Paolo Bonzini [this message]
2013-03-01 15:50   ` [Qemu-devel] " Fabio Fantoni
2013-03-01 18:38     ` Paolo Bonzini
2013-03-03 10:27     ` Alon Levy
2013-03-04  9:57       ` Fabio Fantoni

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=5130A2EE.7080303@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=fantonifabio@tiscali.it \
    --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).