On Fri, May 21, 2010 at 02:21:33AM +0400, Michael Tokarev wrote:
> I never had any problems with network at that place, and I always use
> pxelinux boot menu to choose the thing to run on the diskless (kvm)
> workstation, and edit kernel command line while in pxelinux.
>
> I used all supported network adaptors, and I re-verified it again before
> replying - it all works for me.
For pxelinux, we've been running:
# lenny
PXELINUX 3.71 Debian-2008-09-06 Copyright (C) 1994-2008 H. Peter Anvin
# Ubuntu lucid
PXELINUX 3.63 Debian-2008-07-15
On a whim, I just now tried:
# squeeze/sid
PXELINUX 3.86 debian-20100418 Copyright (C) 1994-2010 H. Peter Anvin et al
and this seems to have fixed it. I looked over the syslinux Debian and
upstream changelogs, but nothing jumps out at me.
Our other hosts run KVM 85 or qemu-kvm 0.11.1+dfsg-1. They had been fine
with pxelinux 3.63 or 3.71 (we PXE boot nearly all our new VMs for OS
installation). FWIW, they also seem to be fine with 3.86.
> 20.05.2010 22:20, Matthew Ernisse wrote:
> >We are using the following version of libvirt
> >ii libvirt-bin 0.8.1-1
> >ii libvirt0 0.8.1-1
> >
> >the XML for this domains is as follows:
>
> Um. How this translates into kvm command line please?
Sorry. It winds up being (switched to pcnet to avoid e1000):
/usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 1024 \
-smp 1,sockets=1,cores=1,threads=1 -name d-i.lab.isis \
-uuid b3ae7b86-d390-e563-bba9-4a1cd9966480 -nodefaults \
-chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/d-i.lab.isis.monitor,server,nowait
\
-mon chardev=monitor,mode=readline -rtc base=utc \
-boot n -drive
file=/var/lib/libvirt/images/d-i.lab.isis.raw,if=none,id=drive-ide0-0-0 \
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 \
-device pcnet,vlan=0,id=net0,mac=02:00:00:60:a7:70,bus=pci.0,addr=0x4 \
-net tap,fd=29,vlan=0,name=hostnet0 -chardev pty,id=serial0 \
-device isa-serial,chardev=serial0 -usb -vnc 0.0.0.0:12 \
-vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
> Does the problem occurs with other network cards?
It happened with the three we tried: e1000, virtio (bootrom built with
rom-o-matic) and pcnet. We usually use virtio; the e1000 was just us
flailing around trying to affect the problem.
john
--
John Morrissey _o /\ ---- __o
[email protected] _-< \_ / \ ---- < \,
www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
