summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/mistranslation/1179731
blob: 4e0f890be7c7c095b2ea5ec5f42e771bf05281df (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
mistranslation: 0.903
network: 0.890
instruction: 0.819
KVM: 0.800
other: 0.788
graphic: 0.770
device: 0.767
semantic: 0.750
socket: 0.691
vnc: 0.656
boot: 0.499
assembly: 0.387

is networking broken on windows hosts?

just wondering as i just compiled the latest git and qemu goes into none responding mode when i try to do any networking stuff on guests (both linux and windows)

On Tue, May 14, 2013 at 12:02:24AM -0000, therock247uk wrote:
> just wondering as i just compiled the latest git and qemu goes into none
> responding mode when i try to do any networking stuff on guests (both
> linux and windows)

Works for me on qemu.git/master on Linux:

  $ git rev-parse HEAD
  b087143b4d010451208264b7c841436aafe1cbb1
  $ x86_64-softmmu/qemu-system-x86_64 -m 1024 -enable-kvm -cpu host \
          -drive if=virtio,cache=none,file=test.img

Please include more information, like the QEMU command-line and commit
ID.

Stefan


latest git as of yesterday compiled under mingw using qemu-system-i386 -localtime -m 512 windows.img when ever it connects to the internet qemu hangs.

trying other network adapters does not help either i tried the model=rtl8139 and the xp guest says limited or no connectivty.

tried the patch did not work though still hangs/crashes has issues

On 05/16/2013 10:59 AM, Paolo Bonzini wrote:
> Il 16/05/2013 07:52, TeLeMan ha scritto:
>> The patch is working on 134a03e0b3d34b01b68107104c525c3bff1211d4 and
>> is not working from cbff4b342b000a7642125dbdabf61113e05eee44.
> 
> Thanks.
> 
> Fabien or Stefan, can you take a look?
> 

Unfortunately I don't have time to investigate these days.

-- 
Fabien Chouteau


Looking at http://lists.gnu.org/archive/html/qemu-devel/2013-05/msg02268.html it seems this has been fixed with commits 8db165b36ef893ac69af045 and 3cb8c205e36531a07dff1d84 ==> setting status to "Fix released"