On Tue, Dec 04, 2007 at 05:49:10PM +, Daniel P. Berrange wrote:
> On Tue, Dec 04, 2007 at 05:40:44PM +, Richard W.M. Jones wrote:
> > Daniel P. Berrange wrote:
> > >For the QEMU / KVM driver, if the user doesn't specify an explicit name for
> > >the TAP device associated with a virtual NIC,
Daniel P. Berrange wrote:
On Tue, Dec 04, 2007 at 05:40:44PM +, Richard W.M. Jones wrote:
Daniel P. Berrange wrote:
For the QEMU / KVM driver, if the user doesn't specify an explicit name for
the TAP device associated with a virtual NIC, we auto-generate one with a
name vnetXXX. You can se
On Tue, Dec 04, 2007 at 05:40:44PM +, Richard W.M. Jones wrote:
> Daniel P. Berrange wrote:
> >For the QEMU / KVM driver, if the user doesn't specify an explicit name for
> >the TAP device associated with a virtual NIC, we auto-generate one with a
> >name vnetXXX. You can see this if you dump
Daniel P. Berrange wrote:
For the QEMU / KVM driver, if the user doesn't specify an explicit name for
the TAP device associated with a virtual NIC, we auto-generate one with a
name vnetXXX. You can see this if you dump XML for a running QEMU guest.
Unfortunately if you dump XML, make a change an
For the QEMU / KVM driver, if the user doesn't specify an explicit name for
the TAP device associated with a virtual NIC, we auto-generate one with a
name vnetXXX. You can see this if you dump XML for a running QEMU guest.
Unfortunately if you dump XML, make a change and then feed it back in with
