alking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
551620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
P
Jan Luebbe writes:
> Hi!
>
> On Mon, 2009-10-19 at 16:23 +0200, Goswin von Brederlow wrote:
>> sudo kvm -m 256 -drive
>> file=/scratch/ramdisk/build/build/hda.img,if=ide,boot=on -drive
>> file=/scratch/ramdisk/build/build/hdb.img,if=ide,boot=off -net
>> nic,model=e1000,macaddr=54:52:00:00:42:12 -
Hi!
On Mon, 2009-10-19 at 16:23 +0200, Goswin von Brederlow wrote:
> sudo kvm -m 256 -drive
> file=/scratch/ramdisk/build/build/hda.img,if=ide,boot=on -drive
> file=/scratch/ramdisk/build/build/hdb.img,if=ide,boot=off -net
> nic,model=e1000,macaddr=54:52:00:00:42:12 -net tap -net
> nic,model=e1000
Hi,
setting VLAN=xx to different values for each interfaces solves this
problem. By default interfaces seem to be put into the same VLAN and
that creates a loop with the bridge. The default should put each
interface in a different VLAN. I can't even think of a use case where
devices should be in t
Package: kvm
Version: 85+dfsg-4
Severity: critical
Hi,
I'm starting kvm with 2 network interfaces like this:
sudo kvm -m 256 -drive file=/scratch/ramdisk/build/build/hda.img,if=ide,boot=on
-drive file=/scratch/ramdisk/build/build/hdb.img,if=ide,boot=off -net
nic,model=e1000,macaddr=54:52:00:00
5 matches
Mail list logo
