I've been having some problem with recent releases when it comes to tap
initialization. It seems that the script is ran after the tap is opened. I
think this is a bit weird and useless as I want the script to setup the
tap by itself.
In net.c, the initialization (I assume) happen in
static int
I've been having some problem with recent releases when it comes to tap
initialization. It seems that the script is ran after the tap is opened. I
think this is a bit weird and useless as I want the script to setup the
tap by itself.
In net.c, the initialization (I assume) happen in
static
You need to add a vlan option to one of them, for example vlan=2
Otherwise kvm will bridge the interfaces together, and it's going to create
a packet storm.
I wondered about that -- but what's the relationship of a KVM vlan to
my existing bridge interfaces, and how can I control which one gets
m
bridge name bridge id STP enabled interfaces
br0 8000.00144fa1f17a no eth0
tap0
tap1
device tap11 is already a member of a bridge; can't enslave it to bridge br0.
/etc/kvm/kvm-ifup: could not launch network script
Could not initialize device 'tap'
That's because your kvm-ifup scripts tries to connect the tap to the
bridge and it's already there. You should either remove it f
I was wondering the kvm live migration function is reliable? I read that if
the TSC is not monotonically increasing, then the guest will hang. How to
prevent this?
No idea about that problem.
For migration, it usually works for me, but the clock of the guest starts
running way too fast.
--
To
This is my first patch, so I apoligize for breaking any convention.
This patch modifies the order used in net.c for tap initialization.
It runs the script before the device is opened. This permits the creation
of the tap device via a script instead of having to do it in advance.
It also waits
Stephane Bakhos wrote:
This is my first patch, so I apoligize for breaking any convention.
This patch modifies the order used in net.c for tap initialization.
It runs the script before the device is opened.
This will break existing scripts that do not rely on explicitly setting
ifname
since upgrade from qemu-kvm 0.10.5 to 0.10.6 (Debian Lenny, Packages from
http://www.corpit.ru/debian/tls/kvm/, kvm module from kernel 2.6.30)
live-migration does not work anymore.
After "migrate -d tcp:192.168.0.2:" info says "migration completed",
but "incoming" kvm machine dies.
Any
Not sure if this is related but this is what happens on my system when I
try to do a live migration with kvm-88 and the latest kernel 2.6.30
(gentoo 2.6.30-gentoo-r5).
[ 73.168871] general protection fault: [#1] SMP
[ 73.169409] last sysfs file: /sys/kernel/uevent_seqnum
[ 73.169
Hi,
This is the sysexit instruction.
I recently stumbled upon a similar issue.
Can you try the following patch? This is not a very nice one,
but it cured the problem I had.
Do you see anything in the guest? I had some messages on the console
about a faulting init (at boot time, when I was booti
On Tue, 18 Aug 2009, Avi Kivity wrote:
On 08/18/2009 11:11 AM, Stephane Bakhos wrote:
I've tried the patch and it did not help, however I could only have it on
the receiver of the migration. Would it need to be installed on the one
sending the data ?
The guest kernel and userlan
12 matches
Mail list logo
