On Fri, Oct 23, 2009 at 08:25:39PM +0400, Michael Tokarev wrote:
o why different -net guest -net host pairs are not getting different
vlan= indexes by default, to stop the above-mentioned packet
storms right away? I think it's a wise default to assign different
pairs to different
On Wed, Jul 15, 2009 at 05:54:14PM -0500, Michael Jinks wrote:
Now I want to bring up a VM with two NICs, one attached to tap12
(bridge 0), the other on tap11 (bridge 1), but I think I've
misunderstood the versious -net options as described in the kvm man
page. It *seems* to say that the
On Wed, Jul 15, 2009 at 07:05:48PM -0400, Stephane Bakhos wrote:
I tried fd= instead of name=, but that looks for a file descriptor
instead of a network interface name, and I didn't even know that Linux
had file descriptors for network interfaces let alone how to map them
to a tap. Nothing
On Wed, Jul 15, 2009 at 06:22:56PM -0500, Michael Jinks wrote:
# kvm -m 512M -net nic -net tap,name=tap11 -net nic -net
tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom
/path/to/my/Windows.iso -boot d
The parameter is ifname, not name.
In that case, what does the name parameter
On Thu, Jul 16, 2009 at 01:12:19AM +0200, Andreas Plesner Jacobsen wrote:
I tried fd= instead of name=, but that looks for a file descriptor
instead of a network interface name, and I didn't even know that Linux
had file descriptors for network interfaces let alone how to map them
On Thu, Apr 23, 2009 at 10:43:03AM +0200, Gerd v. Egidy wrote:
I am (or better libvirt is) starting the guest like this:
-drive file=/dev/VolGroup00/testboot,if=ide,index=0 \
-drive file=/dev/VolGroup00/testvirt,if=virtio,index=1 \
Both should have index=0 (or no index at all), since the
On Thu, Apr 23, 2009 at 06:57:45PM +0200, Gerd v. Egidy wrote:
sorry, I'm not getting that far to make this a problem. I just added the
second disk (the virtio one) to test if virtio is working when the guest is
running.
I first tried it with just one virtio disk and no ide ones: it
