Debian Bug report logs - #647312
windows XP Standard PC HAL does not work with qemu-kvm >= 0.15

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Kein Kommentar <klak@gmx.net>

To: submit@bugs.debian.org

Subject: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Tue, 1 Nov 2011 20:40:28 +0100

[Message part 1 (text/plain, inline)]

Package: qemu-kvm
Version: 0.15.1+dfsg-1
Severity: normal

Dear Maintainer,

after the update to 0.15.1+dfsg-1

my xp vm can't connect to other machines.

Only a slowly ping with 75 % packet loss is possible.


Gruss klak



<<<-------------------------------------->>>


processor       : 23
vendor_id       : GenuineIntel
cpu family      : 6
model           : 44
model name      : Intel(R) Xeon(R) CPU           L5640  @ 2.27GHz
stepping        : 2
cpu MHz         : 2266.587
cache size      : 12288 KB
physical id     : 1
siblings        : 12
core id         : 10
cpu cores       : 6
apicid          : 53
initial apicid  : 53
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2
ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt aes lahf_lm ida arat epb dts
tpr_shadow vnmi flexpriority ept vpid
bogomips        : 4533.20
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:




-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/24 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qemu-kvm depends on:
ii  adduser           3.113
ii  ipxe              1.0.0+git-2.149b50-1
ii  libaio1           0.3.109-2
ii  libasound2        1.0.24.1-4
ii  libattr1          1:2.4.46-3
ii  libbluetooth3     4.96-3
ii  libbrlapi0.5      4.2-8+b1
ii  libc6             2.13-21
ii  libcurl3-gnutls   7.21.7-3
ii  libgnutls26       2.12.11-1
ii  libjpeg8          8c-2
ii  libncurses5       5.9-2
ii  libpng12-0        1.2.46-3
ii  libpulse0         1.0-4
ii  librados2         0.35-1
ii  librbd1           0.35-1
ii  libsasl2-2        2.1.24~rc1.dfsg1+cvs2011-05-23-4
ii  libsdl1.2debian   1.2.14-6.4
ii  libspice-server1  0.8.2-2
ii  libtinfo5         5.9-2
ii  libuuid1          2.19.1-5
ii  libvdeplug2       2.2.3-3+b1
ii  libx11-6          2:1.4.4-2
ii  python            2.7.2-9
ii  qemu-keymaps      0.14.1+dfsg-3
ii  qemu-utils        0.14.1+dfsg-3
ii  seabios           0.6.1.2-3
ii  vgabios           0.6c-3
ii  zlib1g            1:1.2.3.4.dfsg-3

Versions of packages qemu-kvm recommends:
ii  bridge-utils  1.5-2
ii  iproute       20110629-1

Versions of packages qemu-kvm suggests:
ii  debootstrap  <none>
ii  samba        <none>
ii  vde2         2.2.3-3+b1

<<<------------------------------->>>

[Message part 2 (text/html, inline)]

[xpro01.xml (application/xml, attachment)]

Message #10 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: klak@gmx.net, 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Wed, 02 Nov 2011 00:33:34 +0400

tags 647312 + unreproducible moreinfo
thanks

On 01.11.2011 23:40, Kein Kommentar wrote:
> Package: qemu-kvm
> Version: 0.15.1+dfsg-1
> Severity: normal
> 
> Dear Maintainer,
> 
> after the update to 0.15.1+dfsg-1
> my xp vm can't connect to other machines.
> Only a slowly ping with 75 % packet loss is possible.


With this amount of information it is impossible to do anything.
I definitely can not confirm this, we have lots of windows
machines using various virtual network drivers and all are
working just fine with either of 0.12, 0.14 or 0.15 versions.

One possible reason is very old virtio driver in windows
guest.

So, at least, which kvm command line do you use?
which driver is used in windows?
Does it work again when reverting back to 0.14?
How can one reproduce this problem from scratch?

Thanks,

/mjt

Message #17 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: klak@gmx.net

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Wed, 02 Nov 2011 01:48:30 +0400

On 02.11.2011 01:24, Kein Kommentar wrote:
> Hello Michael,
> 
> 
> here is the command line:
> 
> 
> [22:12:24] kkadmin@kk-12x2260:~> ps -ef | grep xpro01
> 
> 105 8962 1 37 22:12 ? 00:00:06 /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name xpro01 -uuid c1f51e24-52f8-a1a1-759a-5a678ebb1e3d -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/xpro01.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -drive file=/dev/mapper/raid1-xpro01,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:63:4f:75,bus=pci.0,multifunction=on,addr=0x4.0x0 -chardev
> pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:3,password -k de -vga cirrus -device ES1370,id=sound0,bus=pci.0,multifunction=on,addr=0x5.0x0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x3.0x0

So it uses rtl8139 driver (as a multi-function PCI device),
and use pc-0.11 - you most likely installed it when qemu-kvm
was at version 0.11.  You also use ES1370 audio "card".

With this information I still can not reproduce the issue.

> rtl8139 driver is in use.

Yes i see it in the command line.

> on another maschine with 0.14 there is no problem.

Will you answer the rest of my questions?

>> Does it work again when reverting back to 0.14?
>> How can one reproduce this problem from scratch?

So far it looks like a problem in this particular windows
machine, nothing to do with kvm.

Thanks,

/mjt

Message #22 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: klak@gmx.net

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Wed, 02 Nov 2011 23:31:45 +0400

On 02.11.2011 19:37, Kein Kommentar wrote:
> Hello Micheal,
> 
> Currently it is not possible to go back to version 0.14.1+dfsg-4,

I don't understand.  The only thing you need is to run another
/usr/bin/kvm binary, from 0.14? with this very winXP virtual
machine.  I can't see how it is "not possible"

> but in the next few days I will install an XP VM from scratch.

If that will show the behavour you describe, that will be great.

Thanks!

/mjt

Message #27 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Adam Majer <adamm@zombino.com>

To: Debian Bug Tracking System <647312@bugs.debian.org>

Subject: Re: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 10 Nov 2011 13:08:42 -0600

Package: qemu-kvm
Version: 1:0.15.1+dfsg-1
Followup-For: Bug #647312

I have exactly the same problem. Packets are routed outside of the
guest but never make it back inside. For example, DHCP server receives
multiple requests for IP, sends it back, but the guest says no
response received. The guest was not changed. Actually, it was
installed number of years ago.

Downgrading to 0.14.1+dfsg-4 does indeed make networking function
again.

-net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup

It is using the rtl8139 driver.

- Adam



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kvm depends on:
ii  qemu-kvm  0.15.1+dfsg-1

kvm recommends no packages.

kvm suggests no packages.

Versions of packages qemu-kvm depends on:
ii  adduser           3.113               
ii  ipxe              1.0.0+git-2.149b50-1
ii  libaio1           0.3.109-2           
ii  libasound2        1.0.24.1-4          
ii  libattr1          1:2.4.46-3          
ii  libbluetooth3     4.96-3              
ii  libbrlapi0.5      4.2-8+b1            
ii  libc6             2.13-21             
ii  libcurl3-gnutls   7.21.7-3            
ii  libgnutls26       2.12.12-1           
ii  libjpeg8          8c-2                
ii  libncurses5       5.9-2               
ii  libpng12-0        1.2.46-3            
ii  libpulse0         1.0-4               
ii  librados2         0.35-1              
ii  librbd1           0.35-1              
ii  libsasl2-2        2.1.25.dfsg1-2      
ii  libsdl1.2debian   1.2.14-6.4          
ii  libspice-server1  0.8.2-2             
ii  libtinfo5         5.9-2               
ii  libuuid1          2.19.1-5            
ii  libvdeplug2       2.2.3-3+b1          
ii  libx11-6          2:1.4.4-2           
ii  python            2.7.2-9             
ii  qemu-keymaps      0.15.0+dfsg-1       
ii  qemu-utils        0.15.0+dfsg-1       
ii  seabios           0.6.1.2-3           
ii  vgabios           0.6c-3              
ii  zlib1g            1:1.2.5.dfsg-1      

Versions of packages qemu-kvm recommends:
ii  bridge-utils  1.5-2     
ii  iproute       20110629-1

Versions of packages qemu-kvm suggests:
pn  debootstrap  1.0.37
pn  samba        <none>
pn  vde2         <none>

-- no debconf information

Message #32 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Adam Majer <adamm@zombino.com>, 647312@bugs.debian.org

Cc: Kein Kommentar <klak@gmx.net>

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Fri, 11 Nov 2011 01:23:26 +0400

On 10.11.2011 23:08, Adam Majer wrote:
> Package: qemu-kvm
> Version: 1:0.15.1+dfsg-1
> Followup-For: Bug #647312
> 
> I have exactly the same problem. Packets are routed outside of the
> guest but never make it back inside. For example, DHCP server receives
> multiple requests for IP, sends it back, but the guest says no
> response received. The guest was not changed. Actually, it was
> installed number of years ago.
> 
> Downgrading to 0.14.1+dfsg-4 does indeed make networking function
> again.
> 
> -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup
> 
> It is using the rtl8139 driver.

I can't reproduce it.  I built qemu-kvm 0.10 and 0.11, tried installing
winxp in there and running it in 0.15.  I also tried to run it one
by one in 0.11, 0.12, 0.13, 0.14 and 0.15 -- in all cases network
functions correctly.

There was no guest-visible changes in rtl8139 virtual "hardware" between
0.14 and 0.15, at least not in the "card" itself (there were changes in
surrounding areas, like interrupt handling, which may affect this).

Maybe some of you can provide the images of windows which has this issue,
for me to find a change between 0.14 and 0.15 that broke it?

Also, does reinstalling the driver in windows help?

Thanks,

/mjt

Message #37 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Adam Majer <adamm@zombino.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org, Kein Kommentar <klak@gmx.net>

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 10 Nov 2011 15:35:35 -0600

On Fri, Nov 11, 2011 at 01:23:26AM +0400, Michael Tokarev wrote:
> Also, does reinstalling the driver in windows help?

Reinstalling driver (by removing device in Control Panel -> System)
and then reinstalling it does not do anything.

I will try to reproduce this bug with a clean install.

- Adam


-- 
Adam Majer
adamm@zombino.com

Message #42 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Debian Bug Tracking System <647312@bugs.debian.org>

Subject: Re: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 01 Dec 2011 11:09:33 +0300

Package: qemu-kvm
Followup-For: Bug #647312

I have tested this for all nics with the same results. With tcpdump I see the
problem is that packets are going out, but not going in. There are no such
problem with 2.6.32 kernel and for Windows-7 with any kernel.

Message #47 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Debian Bug Tracking System <647312@bugs.debian.org>

Subject: Re: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 1 Dec 2011 11:48:18 +0400

On Thu, Dec 01, 2011 at 11:09:33AM +0300, Vladimir Stavrinov wrote:

> problem is that packets are going out, but not going in. There are no such
> problem with 2.6.32 kernel and for Windows-7 with any kernel.

Downgrade qemu-kvm to 0.12.5+dfsg-5+squeeze6 also solve this problem - it is
working with any kernel. I think it is more likely kvm related problem then
kernel one.

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #52 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>, 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 01 Dec 2011 12:23:36 +0400

On 01.12.2011 12:09, Vladimir Stavrinov wrote:
> Package: qemu-kvm
> Followup-For: Bug #647312
> 
> I have tested this for all nics with the same results. With tcpdump I see the
> problem is that packets are going out, but not going in. There are no such
> problem with 2.6.32 kernel and for Windows-7 with any kernel.

So, is there some way to reproduce it?  Or maybe to fix it once
the problem appears?  I still can't do anything with it since I
failed to reproduce the problem.

Thanks,

/mjt

Message #57 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 1 Dec 2011 12:56:34 +0400

On Thu, Dec 01, 2011 at 12:23:36PM +0400, Michael Tokarev wrote:

> So, is there some way to reproduce it?  Or maybe to fix it once

This way is your experiments with newly installed systems (debian and
windows xp).

> the problem appears?  I still can't do anything with it since I

What You can do is to send this URL to upstream:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647312

> failed to reproduce the problem.

You are only who can not reproduce and You see I am third, who report
the same problem here. Do You think it is conspiracy against You?

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #62 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>, 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 01 Dec 2011 14:40:45 +0400

On 01.12.2011 12:56, Vladimir Stavrinov wrote
> On Thu, Dec 01, 2011 at 12:23:36PM +0400, Michael Tokarev wrote:
> 
>> So, is there some way to reproduce it?  Or maybe to fix it once
> 
> This way is your experiments with newly installed systems (debian and
> windows xp).

I installed winXP in numerous versions of kvm while trying to
reproduce this issue.  To no avail.

>> the problem appears?  I still can't do anything with it since I
> 
> What You can do is to send this URL to upstream:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647312

"Upstream" (which is a team) can't reproduce it either, we
discussed this matter several times with different people
already.

>> failed to reproduce the problem.
> 
> You are only who can not reproduce and You see I am third, who report
> the same problem here. Do You think it is conspiracy against You?

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
can.

/mjt

Message #67 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>, 647312@bugs.debian.org

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 1 Dec 2011 16:09:02 +0400

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
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
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 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.)

> "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.

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #72 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 01 Dec 2011 16:22:07 +0400

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

Message #77 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 01 Dec 2011 16:28:13 +0400

On 01.12.2011 16:24, Vladimir Stavrinov wrote:
[]
> Starting this conversation, I guess, and now see: as usual the problem
> arise when people don't listening or don't reading carefully. Look at
> very first message (from Kein Kommentar) in this bug report and You see
> the kernel 3.0.0. I think, if not only You, but upstream saw this
> conversation too, they noticed this fact. Summary, the problem exists
> when:

If you want to argue my competence this is not the right place to do that.

/mjt

Message #82 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 1 Dec 2011 16:46:39 +0400

On Thu, Dec 01, 2011 at 04:28:13PM +0400, Michael Tokarev wrote:

> If you want to argue my competence this is not the right place to do that.

No, it is not competence, but rather attention issue. More people with
(or without) the same problem more likely notice essential fact in the
text, then single person do.

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #87 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>, 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 1 Dec 2011 16:24:07 +0400

On Thu, Dec 01, 2011 at 03:50:18PM +0400, Michael Tokarev wrote:

> Vladimir, you said the problem does not occur with 2.6.32 kernel.

Great! You have opened Your eyes.

> Care to give some more details about your environment, -- which

What details

> _kernel_ reproduces the issue?

Starting this conversation, I guess, and now see: as usual the problem
arise when people don't listening or don't reading carefully. Look at
very first message (from Kein Kommentar) in this bug report and You see
the kernel 3.0.0. I think, if not only You, but upstream saw this
conversation too, they noticed this fact. Summary, the problem exists
when:

kernel >= 3.0.0, kvm >= 0.14 and winXP.

In my case kernel version is 3.1.0

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #92 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>, 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 01 Dec 2011 15:50:18 +0400

Vladimir, you said the problem does not occur with 2.6.32 kernel.
Care to give some more details about your environment, -- which
_kernel_ reproduces the issue?

Thanks,

/mjt

Message #97 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Fri, 2 Dec 2011 12:28:34 +0400

On Thu, Dec 01, 2011 at 04:22:07PM +0400, Michael Tokarev wrote:

> 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

I have installed winXP just yesterday and there are no problem with
networking. Thus I have two winXP guest installations on the same host:
one is very new and fresh and other is many years used . First is
working, second don't. So we have chance to find out what You ask me:
the way to reproduce this strange problem. I will try.

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #102 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>, 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Fri, 02 Dec 2011 12:50:34 +0400

On 02.12.2011 12:28, Vladimir Stavrinov wrote:
> I have installed winXP just yesterday and there are no problem with
> networking. Thus I have two winXP guest installations on the same host:
> one is very new and fresh and other is many years used . First is
> working, second don't.

This is exactly what I'm talking about, and this is something that
has been observed by other 2 reporters too: only _older_ installs
of winXP shows this issue, fresh installs does not.  Hence I tried
to install wiXP in older version of kvm, starting with 0.11, but
all my guests shows perfectly working networking after switching
to 0.15.

Maybe - very unlikely but may be - this is related to a combination
of kernel + kvm - so I tried running 2.6.32 kernel and 0.11 kvm
to install one of my guests - but it too is running fine after
upgrading kvm (and kernel) to current versions.

I have older winXP guests - installed long time ago, I dunno the
kvm version of their install however, maybe 0.12 maybe earlier.
These all works fine too.

This also may be due to a combination of kernel + kvm + libvirt,
but so far I never ever used libvirt, always using command line
directly to run kvm guests.  Maybe it was due to some extra
kvm switch (-no-acpi or something) used when installing the guest -
I dunno.

Maybe you can provide me your non-working guest image for testing,
- maybe that will help.  But I think I already asked this question
before, with no answer from either 3 of you.

Just don't damage the non-working guest yet, keep it safe, because
currently it is priceless since there's no known way to reproduce
it, and any networking-related manipulation may just fix it... ;)

(But if such fixing manipulation is found we may consider this bug
fixed, too, which is a great progress).

Thank you!

/mjt

Message #107 received at 647312@bugs.debian.org (full text, mbox, reply):

From: deb@kagisoft.co.uk

To: 647312@bugs.debian.org

Subject: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Fri, 02 Dec 2011 11:38:27 +0000

I also see this using kernel 3.1.0-1-amd64 with an old winxp vm.

Using qemu-kvm 0.15.1+dfsg-1 I see two issues:
(1) The VM fail to receive the responses to its dhcp requests
(2) The mouse on its' SDL/VNC display does not move.

Reverting back to qemu-kvm 0.14.1+dfsg-4 fixes both these issues.

My winxp installation is old - was originally installed under xen - but 
currently uses pc-0.14 model, with rtl8139 network driver.

Unfortunately it is not an option for me to reinstall winxp or provide 
you with a copy of the vm for debug purposes.

/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 2048 -smp 
1,sockets=1,cores=1,threads=1 -name winxp -uuid 
c1754d2a-bfe9-ab4c-c484-c25805be4a82 -nodefconfig -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime 
-drive 
file=/var/lib/libvirt/images/winxp,if=none,id=drive-ide0-0-0,format=raw 
-device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 
-netdev tap,fd=20,id=hostnet0 -device 
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:30:26:9a,bus=pci.0,multifunction=on,addr=0x3.0x0 
-chardev pty,id=charserial0 -device 
isa-serial,chardev=charserial0,id=serial0 -usb -device 
usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device 
intel-hda,id=sound0,bus=pci.0,multifunction=on,addr=0x4.0x0 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x5.0x0

Message #112 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Mon, 5 Dec 2011 12:32:23 +0400

On Fri, Dec 02, 2011 at 12:28:34PM +0400, Vladimir Stavrinov wrote:

> working, second don't. So we have chance to find out what You ask me:
> the way to reproduce this strange problem. I will try.

Good news: we have succeed. In short: the core problem is type of HAL:
"ACPI Uniprocessor PC" have no problem, but "Standard PC" have a
problem with networking. Don't try to switch HAL on the installed
system - it will not boot after that. Instead do the new installation:
start kvm with -no-acpi option and follow instruction:

http://support.microsoft.com/kb/299340

But may be it is not necessary if "Standard PC" is default setting for
"-no-acpi" option.

So, now You can reproduce and then investigate this problem.


-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #117 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Mon, 05 Dec 2011 13:05:41 +0400

retitle 647312 windows XP Standard PC HAL does not work with qemu-kvm >= 0.14
tags 647312 - moreinfo unreproducible
tags 647312 + confirmed
thanks

On 05.12.2011 12:32, Vladimir Stavrinov wrote:
> On Fri, Dec 02, 2011 at 12:28:34PM +0400, Vladimir Stavrinov wrote:
> 
>> working, second don't. So we have chance to find out what You ask me:
>> the way to reproduce this strange problem. I will try.
> 
> Good news: we have succeed. In short: the core problem is type of HAL:
> "ACPI Uniprocessor PC" have no problem, but "Standard PC" have a
> problem with networking. Don't try to switch HAL on the installed

Aha.  It was, actually, one of the possibilities I outlined before,
but didn't check it.

Switching computer type in the device manager works just fine (provided
you actually enabled acpi on the "hardware").  If you're not sure, you
always may run it with -snapshot so it wont write anything to disk, try
to change the HAL type and reboot windows to see if it will still work.
If it boots fine, repeat changing the HAL type but now without -snapshot.

[]
> But may be it is not necessary if "Standard PC" is default setting for
> "-no-acpi" option.

Yes, "Standard PC" will be used when installed on a machine run with
-no-acpi option.  Or at least it WAS used with some previous version
of kvm (I remember seeing it) -- now when installing winXP with -no-acpi,
it defaults to "Uniprocessor PC with MPS" (iirc) - with that one,
networking works.  But when set to "Standard PC" there and rebooted,
neither networking nor USB works (including USB mouse/tablet - which
was mentioned in this thread).

> So, now You can reproduce and then investigate this problem.

Yes, confirmed, this is a bug.  But it seems to be a bug in windows,
or an operator error when performing initial install.  It may be
possible to find what exactly changed on the kvm side, but for now
I think it is better to find out how to fix this bug on windows
side.

For fun, once you change the HAL to "Standard PC", it does not offer
any other variant anymore, so the question actually remains how to
force it to rebuild hal from "Standard PC" to something else.
I can switch from "Uniprocessor PC with MPS" to "PC with ACPI" or
to "Standard PC", but can't switch from "Standard PC" to anything
else.

Note also that both this HALs ("Standard PC" and "Uniprocessof with MPS")
works noticeable slower than usual ACPI variant.

Give me some more time.

Thanks,

/mjt

Message #130 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Mon, 5 Dec 2011 13:46:46 +0400

On Mon, Dec 05, 2011 at 01:05:41PM +0400, Michael Tokarev wrote:

> Aha.  It was, actually, one of the possibilities I outlined before,
> but didn't check it.

Just after starting new system and compared it to old one first of all
I have noticed the type of HAL was only meaningful difference in
two systems.

> Switching computer type in the device manager works just fine (provided

Microsoft warned and the system actually crash after switching from
"Standard PC" to "ACPI Uniprocessor PC". kvm options don't help.

> always may run it with -snapshot so it wont write anything to disk, try

It take disk space from /tmp directory. Use lsof to see files.

> I can switch from "Uniprocessor PC with MPS" to "PC with ACPI" or
> to "Standard PC", but can't switch from "Standard PC" to anything
> else.

Other possibilities to do this is upgrade option in setup.

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #135 received at 647312-close@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: 647312-close@bugs.debian.org

Subject: Bug#647312: fixed in qemu-kvm 1.0+dfsg-2

Date: Fri, 16 Dec 2011 08:49:19 +0000

Source: qemu-kvm
Source-Version: 1.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
qemu-kvm, which is due to be installed in the Debian FTP archive:

kvm_1.0+dfsg-2_i386.deb
  to main/q/qemu-kvm/kvm_1.0+dfsg-2_i386.deb
qemu-kvm-dbg_1.0+dfsg-2_i386.deb
  to main/q/qemu-kvm/qemu-kvm-dbg_1.0+dfsg-2_i386.deb
qemu-kvm_1.0+dfsg-2.debian.tar.gz
  to main/q/qemu-kvm/qemu-kvm_1.0+dfsg-2.debian.tar.gz
qemu-kvm_1.0+dfsg-2.dsc
  to main/q/qemu-kvm/qemu-kvm_1.0+dfsg-2.dsc
qemu-kvm_1.0+dfsg-2_i386.deb
  to main/q/qemu-kvm/qemu-kvm_1.0+dfsg-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 647312@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Tokarev <mjt@tls.msk.ru> (supplier of updated qemu-kvm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 16 Dec 2011 12:12:38 +0400
Source: qemu-kvm
Binary: qemu-kvm qemu-kvm-dbg kvm
Architecture: source i386
Version: 1.0+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Michael Tokarev <mjt@tls.msk.ru>
Changed-By: Michael Tokarev <mjt@tls.msk.ru>
Description: 
 kvm        - dummy transitional package from kvm to qemu-kvm
 qemu-kvm   - Full virtualization on x86 hardware
 qemu-kvm-dbg - Debugging info for qemu-kvm
Closes: 624070 647312 648853
Changes: 
 qemu-kvm (1.0+dfsg-2) unstable; urgency=low
 .
   * mention: (closes: #647312)
     for 1.0 upload
   * upload to unstable
 .
 qemu-kvm (1.0+dfsg-1) experimental; urgency=low
 .
   * new upstream release (1.0) (Closes: #624070, #647312)
   * removed obsolete patches, refreshed old patches
   * --disable-smartcard-nss && --disable-smartcard - the
     linkage requiriments (nspr) is too heavy and the link/library
     needs some work still (linking to too many unused libs)
   * require seabios >>1.6.3 (Closes: #648853)
Checksums-Sha1: 
 a815a00d9cf84847c4e2206cfc0df896183af71e 1877 qemu-kvm_1.0+dfsg-2.dsc
 d93f1c490210fdc1543dd782c0fd03938e6e93c2 20966 qemu-kvm_1.0+dfsg-2.debian.tar.gz
 c1b978aabe8306b95790c3d240932c337b9d21d9 1593588 qemu-kvm_1.0+dfsg-2_i386.deb
 a3e11e7905b106f81a7f18fdee77be24f5034822 3809388 qemu-kvm-dbg_1.0+dfsg-2_i386.deb
 464a14c35aa7acaccb99b145fc3ace7cda43cfe1 9966 kvm_1.0+dfsg-2_i386.deb
Checksums-Sha256: 
 c17b930d921c5764333ef84a66a32af3aa8b7bf6eae93e81cf6cfc90e988978e 1877 qemu-kvm_1.0+dfsg-2.dsc
 64e1ecb54fb008195d29b092b7883a8060ae2d9ca049626b31d6eaf14d0e4021 20966 qemu-kvm_1.0+dfsg-2.debian.tar.gz
 14e8d2e784cb36d2af6e17545a0027f16abef286197516cc750a267e806b640b 1593588 qemu-kvm_1.0+dfsg-2_i386.deb
 1aef466c7fa58a16acab212c4c98ed1714de292ad53af60de0c9d65b3faa5276 3809388 qemu-kvm-dbg_1.0+dfsg-2_i386.deb
 cdff247a88f50be2aee29e2b163b1cb2065a8f568004522b68123f6735a3f676 9966 kvm_1.0+dfsg-2_i386.deb
Files: 
 fd0f9e3a96de5d90c50af1912d1c9596 1877 misc optional qemu-kvm_1.0+dfsg-2.dsc
 adb64a7b5aaceeffb25a4edae1af8b98 20966 misc optional qemu-kvm_1.0+dfsg-2.debian.tar.gz
 1fd2a665eb462629539b02355a45d25e 1593588 misc optional qemu-kvm_1.0+dfsg-2_i386.deb
 acc1952d9e7414ee1b0b2e551c473236 3809388 debug extra qemu-kvm-dbg_1.0+dfsg-2_i386.deb
 ea8cf920393f90f211ea50cdbd5ff3d3 9966 oldlibs extra kvm_1.0+dfsg-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iJwEAQECAAYFAk7q/usACgkQUlPFrXTwyDhqBwP9Hx5l+duPFpfKpzMiYkzNMoFC
x/PGnp1CdB9/Z2pHkQ/lC3YoQL6xVCRFUV9KGKhr8d+9VEvDec5I2B479PA5Z6Q5
N3uaFfdhG2ytKy+WKR+8/KNPJ7lQTwo8pFU6teFgXTYZctd1EUT73CrIfQ89poi1
JFkjJRuxX6LNeHhkwV8=
=8ELS
-----END PGP SIGNATURE-----

Message #140 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 22 Dec 2011 11:53:52 +0400

On Mon, Dec 05, 2011 at 01:05:41PM +0400, Michael Tokarev wrote:

> > Good news: we have succeed. In short: the core problem is type of HAL:
> > "ACPI Uniprocessor PC" have no problem, but "Standard PC" have a
> > problem with networking. Don't try to switch HAL on the installed
> 
> Aha.  It was, actually, one of the possibilities I outlined before,
> but didn't check it.

With new version 1.0+dfsg-2 the problem solved for "Standard PC", but it
moved to "ACPI Uniprocessor PC". So, we have the same problem, but vice
verse.  

-- 

****************************
##  Vladimir Stavrinov   
##  vs@playfast.ru   
##  http://playfast.ru/   
****************************

Message #145 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 22 Dec 2011 13:09:47 +0400

On 22.12.2011 11:53, Vladimir Stavrinov wrote:
> On Mon, Dec 05, 2011 at 01:05:41PM +0400, Michael Tokarev wrote:
> 
>>> Good news: we have succeed. In short: the core problem is type of HAL:
>>> "ACPI Uniprocessor PC" have no problem, but "Standard PC" have a
>>> problem with networking. Don't try to switch HAL on the installed
>>
>> Aha.  It was, actually, one of the possibilities I outlined before,
>> but didn't check it.
> 
> With new version 1.0+dfsg-2 the problem solved for "Standard PC", but it
> moved to "ACPI Uniprocessor PC". So, we have the same problem, but vice
> verse.  

And once again, I can't reproduce it.  I can't reproduce the problem at
all in 1.0 anymore with any version of windows and all variants of HAL
which Im able to test (this includes "StandardPC", "ACPI Uniprocessor PC",
"Standard PC with ACPI").  Neither with newly installed winXP nor with
a pre-existing one.  At least, networking works (basic tests anyway,
including flood ping and iperf) and usb mouse works.

Are you using 32 or 64bit _host_ ?

Thanks,

/mjt

Message #150 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Vladimir Stavrinov <vstavrinov@gmail.com>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Thu, 22 Dec 2011 13:37:57 +0400

On Thu, Dec 22, 2011 at 01:09:47PM +0400, Michael Tokarev wrote:

> Are you using 32 or 64bit _host_ ?
 

64bit

It was the same 2 fresh installed systems, I have used for testing
before new version, but now they swapped. Good news for me is that
my old system without ACPI have no problem now.

P.S. Yesterday I have tried to contact You in Russian for private
issue, but You don't respond. Why? I thought you were on vacation now.

-- 

***************************
##  Vladimir Stavrinov
##  vstavrinov@gmail.com
***************************

Message #159 received at 647312@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Vladimir Stavrinov <vstavrinov@gmail.com>

Cc: 647312@bugs.debian.org

Subject: Re: Bug#647312: qemu-kvm: windows xp - no network connection after 0.14.1+dfsg-4

Date: Sun, 24 Feb 2013 12:06:16 +0400

[Replying to an old email]

22.12.2011 13:37, Vladimir Stavrinov wrote:
> On Thu, Dec 22, 2011 at 01:09:47PM +0400, Michael Tokarev wrote:
> 
>> Are you using 32 or 64bit _host_ ?
> 
> 64bit
> 
> It was the same 2 fresh installed systems, I have used for testing
> before new version, but now they swapped. Good news for me is that
> my old system without ACPI have no problem now.
> 
> P.S. Yesterday I have tried to contact You in Russian for private
> issue, but You don't respond. Why? I thought you were on vacation now.

Vladimir, I'm not sure how but I don't remember what happened with this
email and this (#647312) bugreport.  Someone else referred to this
bugreport and I found your email which went unanswered since Dec-2011,
which is more than a year ago already.  I don't remember whenever I
read any further replies on this.  The bugreport has been archived
(I just unarchived it).

So, do you have issues with winXP networking in qemu-kvm still?  The
issue which #647312 is about is now fixed (it was actual bug in qemu
regarding windows "standard PC" HAL), but you said there's something
else which is problematic?  If that's the case, let's open another
bugreport (since it must be something else).

Thanks,

/mjt

Send a report that this bug log contains spam.