On 01.12.2011 16:09, Vladimir Stavrinov wrote: > On Thu, Dec 01, 2011 at 02:40:45PM +0400, Michael Tokarev wrote: > >> I installed winXP in numerous versions of kvm while trying to > ^^^^^^^^^^^^^^^^^ > First, You don't need "numerous versions", but last 0.15.1+dfsg-1 would
In initial report, the guest has been installed in qemu-kvm v. 0.11, and that was the only guest that shows network problem when qemu-kvm is updated to 0.15 (and the problem goes away when downgrading to 0.14). Hence numerous versions which I tried. > be enough. And second, not only "WinXP", but debian should be fresh > installed too, I think. Here is more info may help You: XP service pack 3 What is a fresh install of debian - how it is different from installing some older version and updating to current -testing? > and Command line: > > kvm -net nic,model=rtl8139,macaddr=52:54:00:12:34:57 -net > tap,ifname=tap0,script=no -hda vmx/wxp-c.img I just reinstalled winXP SP3 32bit using qemu-kvm-0.15.1 (current from testing), on 3.0.12 kernel on an AMD machine, using very similar command: qemu-img create wxptst.img 4G kvm \ -net nic,model=rtl8139,macaddr=52:54:00:12:34:57 \ -net tap,ifname=tap-kvm,script=no \ -drive file=wxptst.img,cache=unsafe \ -m 512 \ -monitor stdio \ -vga std -cdrom winXP.iso that guest works just fine, as are all other guests I tried so far. > I am using bridged networking with brctl. Try different nics. Try to > replace nic few times to get new "Local Area Connection 1"(2,3, etc.) And it all works just fine here. >> "Upstream" (which is a team) can't reproduce it either, we >> discussed this matter several times with different people >> already. > > This is bad news. > >> I'm trying to help. But I need a reproducer. Here, it all Just Works. >> So far, it is just few people (3?) who can reproduce it, no one else > > How much do You need? 3000? I think 2 independent reports are enough to > indicate a real problem. First, if you think I don't believe you then you're wrong. Second, it does not matter how many people can reproduce the issue, be it 1 or 10000 or more - as long as they don't know the steps to reproduce it reliable. Well, with 3000 reports it probably will be better to find out something common in their environment. So far, my environment does not let me to reproduce the issue - say, it only happens on intel Core i3 CPU, and not on any other CPU (just as an example). I'm not going to argue with you here - this is pointless. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
