from:"manuel baesler"

[Qemu-devel] [Bug 1832281] Re: tcg bug master / 4.0.0 v8 operation >>> and |=

2019-08-06 Thread manuel baesler

result:

node
Welcome to Node.js v12.4.0.
Type ".help" for more information.
> a = undefined
undefined
> a >>> 0
0
> let buffer
undefined
> buffer |= 0
0


Thanks for the patch :-)

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1832281

Title:
  tcg bug master / 4.0.0 v8 operation >>> and |=

Status in QEMU:
  New

Bug description:
  vm guest is linux, executed with tcg
  running this Node.js snippet leads to

  $ node
  > a = undefined
  undefined
  > a >>> 0
  4294967295

  host node
  $ node
  > a = undefined
  undefined
  > a >>> 0
  0

  same with |=

  node
  Welcome to Node.js v12.4.0.
  Type ".help" for more information.
  > let buffer
  undefined
  > buffer |= 0
  0

  vm with tcg:

  $ ./out/Release/node --version
  v12.4.0
  ./out/Release/node -e "let buffer; buffer |= 0; console.log(buffer);"
  -1

  vm guest is debian x86_64 latest release
  vm guest is started with ./x86_64-softmmu/qemu-system-x86_64 -vnc :0 -cdrom 
debian-9.9.0-amd64-netinst.iso -m 4G -smp cores=6,threads=1,sockets=1 -nic 
user,hostfwd=tcp:ipv4addr:2233-:22 -cpu qemu64 debian.img

  git tag v4.0.0 and master, commit
  a578cdfbdd8f9beff5ced52b7826ddb1669abbbf, for building qemu-system-
  x86_64 was used.

  Node.js is compiled on the vm guest (v12.4.0 / master)

  see also
  https://github.com/nodejs/node/issues/19348#issuecomment-500465502

  I need further assistance to track down the cause of the bug.

  Kind regards
  Manuel

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1832281/+subscriptions

[Qemu-devel] [Bug 1832281] Re: tcg bug master / 4.0.0 v8 operation >>> and |=

2019-08-06 Thread manuel baesler

Hi Peter,

I will try the tag and report back.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1832281

Title:
  tcg bug master / 4.0.0 v8 operation >>> and |=

Status in QEMU:
  New

Bug description:
  vm guest is linux, executed with tcg
  running this Node.js snippet leads to

  $ node
  > a = undefined
  undefined
  > a >>> 0
  4294967295

  host node
  $ node
  > a = undefined
  undefined
  > a >>> 0
  0

  same with |=

  node
  Welcome to Node.js v12.4.0.
  Type ".help" for more information.
  > let buffer
  undefined
  > buffer |= 0
  0

  vm with tcg:

  $ ./out/Release/node --version
  v12.4.0
  ./out/Release/node -e "let buffer; buffer |= 0; console.log(buffer);"
  -1

  vm guest is debian x86_64 latest release
  vm guest is started with ./x86_64-softmmu/qemu-system-x86_64 -vnc :0 -cdrom 
debian-9.9.0-amd64-netinst.iso -m 4G -smp cores=6,threads=1,sockets=1 -nic 
user,hostfwd=tcp:ipv4addr:2233-:22 -cpu qemu64 debian.img

  git tag v4.0.0 and master, commit
  a578cdfbdd8f9beff5ced52b7826ddb1669abbbf, for building qemu-system-
  x86_64 was used.

  Node.js is compiled on the vm guest (v12.4.0 / master)

  see also
  https://github.com/nodejs/node/issues/19348#issuecomment-500465502

  I need further assistance to track down the cause of the bug.

  Kind regards
  Manuel

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1832281/+subscriptions

[Qemu-devel] [Bug 1832281] [NEW] tcg bug master / 4.0.0 v8 operation >>> and |=

2019-06-10 Thread manuel baesler

Public bug reported:

vm guest is linux, executed with tcg
running this Node.js snippet leads to

$ node
> a = undefined
undefined
> a >>> 0
4294967295

host node
$ node
> a = undefined
undefined
> a >>> 0
0

same with |=

node
Welcome to Node.js v12.4.0.
Type ".help" for more information.
> let buffer
undefined
> buffer |= 0
0

vm with tcg:

$ ./out/Release/node --version
v12.4.0
./out/Release/node -e "let buffer; buffer |= 0; console.log(buffer);"
-1

vm guest is debian x86_64 latest release
vm guest is started with ./x86_64-softmmu/qemu-system-x86_64 -vnc :0 -cdrom 
debian-9.9.0-amd64-netinst.iso -m 4G -smp cores=6,threads=1,sockets=1 -nic 
user,hostfwd=tcp:ipv4addr:2233-:22 -cpu qemu64 debian.img

git tag v4.0.0 and master, commit
a578cdfbdd8f9beff5ced52b7826ddb1669abbbf, for building qemu-system-
x86_64 was used.

Node.js is compiled on the vm guest (v12.4.0 / master)

see also
https://github.com/nodejs/node/issues/19348#issuecomment-500465502

I need further assistance to track down the cause of the bug.

Kind regards
Manuel

** Affects: qemu
 Importance: Undecided
 Status: New

** Description changed:

  vm guest is linux, executed with tcg
  running this Node.js snippet leads to
  
  $ node
- > a = undefined 
+ > a = undefined
  undefined
  > a >>> 0
  4294967295
  
  host node
  $ node
  > a = undefined
  undefined
  > a >>> 0
  0
  
  same with |=
  
  node
  Welcome to Node.js v12.4.0.
  Type ".help" for more information.
  > let buffer
  undefined
  > buffer |= 0
  0
  
  vm with tcg:
  
  $ ./out/Release/node --version
  v12.4.0
  ./out/Release/node -e "let buffer; buffer |= 0; console.log(buffer);"
  -1
  
- 
  vm guest is debian x86_64 latest release
  vm guest is started with ./x86_64-softmmu/qemu-system-x86_64 -vnc :0 -cdrom 
debian-9.9.0-amd64-netinst.iso -m 4G -smp cores=6,threads=1,sockets=1 -nic 
user,hostfwd=tcp:ipv4addr:2233-:22 -cpu qemu64 debian.img
  
  git tag v4.0.0 and master, commit
  a578cdfbdd8f9beff5ced52b7826ddb1669abbbf, for building qemu-system-
  x86_64 was used.
  
- Node.js as compiled on the vm guest (v12.4.0 / master)
- 
+ Node.js is compiled on the vm guest (v12.4.0 / master)
  
  see also
  https://github.com/nodejs/node/issues/19348#issuecomment-500465502
  
  I need further assistance to track down the cause of the bug.
  
  Kind regards
  Manuel

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1832281

Title:
  tcg bug master / 4.0.0 v8 operation >>> and |=

Status in QEMU:
  New

Bug description:
  vm guest is linux, executed with tcg
  running this Node.js snippet leads to

  $ node
  > a = undefined
  undefined
  > a >>> 0
  4294967295

  host node
  $ node
  > a = undefined
  undefined
  > a >>> 0
  0

  same with |=

  node
  Welcome to Node.js v12.4.0.
  Type ".help" for more information.
  > let buffer
  undefined
  > buffer |= 0
  0

  vm with tcg:

  $ ./out/Release/node --version
  v12.4.0
  ./out/Release/node -e "let buffer; buffer |= 0; console.log(buffer);"
  -1

  vm guest is debian x86_64 latest release
  vm guest is started with ./x86_64-softmmu/qemu-system-x86_64 -vnc :0 -cdrom 
debian-9.9.0-amd64-netinst.iso -m 4G -smp cores=6,threads=1,sockets=1 -nic 
user,hostfwd=tcp:ipv4addr:2233-:22 -cpu qemu64 debian.img

  git tag v4.0.0 and master, commit
  a578cdfbdd8f9beff5ced52b7826ddb1669abbbf, for building qemu-system-
  x86_64 was used.

  Node.js is compiled on the vm guest (v12.4.0 / master)

  see also
  https://github.com/nodejs/node/issues/19348#issuecomment-500465502

  I need further assistance to track down the cause of the bug.

  Kind regards
  Manuel

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1832281/+subscriptions

[Qemu-devel] [Bug 1574327] [NEW] qemu-system-x86_64 -net nic, model=help outputs to stderr instead of std

2016-04-24 Thread Manuel Baesler

Public bug reported:

qemu-system-x86_64 -net nic,model=help

output comes to stderr instead of std


qemu-system-x86_64 -net nic,model=help  -> stdout
qemu-system-x86_64 -machine help -> stdout
qemu-system-x86_64 -cpu help -> stdout

as of
https://github.com/qemu/qemu/blob/044d65525f6ac2093042ae18dbf8c1300b5c1c18/net/net.c#L831

I run qemu 2.5 on x86_64

kind regards

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1574327

Title:
  qemu-system-x86_64 -net nic,model=help outputs to stderr instead of
  std

Status in QEMU:
  New

Bug description:
  qemu-system-x86_64 -net nic,model=help

  output comes to stderr instead of std

  
  qemu-system-x86_64 -net nic,model=help  -> stdout
  qemu-system-x86_64 -machine help -> stdout
  qemu-system-x86_64 -cpu help -> stdout

  as of
  
https://github.com/qemu/qemu/blob/044d65525f6ac2093042ae18dbf8c1300b5c1c18/net/net.c#L831

  I run qemu 2.5 on x86_64

  kind regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1574327/+subscriptions

[Qemu-devel] [Bug 1455254] [NEW] Segmentation fault. __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69

2015-05-14 Thread Manuel Baesler

Public bug reported:

compiled qemu at commit 1eeace9c237a729d11c7acd7c0338ab4562af637

with ./configure --enable-debug --enable-vnc --target-
list=x86_64-softmmu


gdb --args ./qemu-system-x86_64 -nographic -parallel none -serial none 
-nodefconfig -nodefaults -machine accel=kvm -enable-kvm -m 1024M -vga qxl -k de 
-cpu qemu64 -smp cpus=1,cores=1,threads=1,sockets=1 -net 
nic,model=rtl8139,macaddr=xxx -net tap -drive 
file=freebsd.img,media=disk,if=ide -vnc :18
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./qemu-system-x86_64...done.
(gdb) run
Starting program: /root/qemu/x86_64-softmmu/qemu-system-x86_64 -nographic 
-parallel none -serial none -nodefconfig -nodefaults -machine accel=kvm 
-enable-kvm -m 1024M -vga qxl -k de -cpu qemu64 -smp 
cpus=1,cores=1,threads=1,sockets=1 -net nic,model=rtl8139,macaddr=xxx-net tap 
-drive file=freebsd.img,media=disk,if=ide -vnc :18
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x744a0700 (LWP 25946)]
ifconfig up for tap2
add bride for tap2
[New Thread 0x73c9f700 (LWP 25957)]
[New Thread 0x72e99700 (LWP 25958)]
[New Thread 0x70dd4700 (LWP 25959)]
[New Thread 0x7fff9bfff700 (LWP 25961)]

Program received signal SIGSEGV, Segmentation fault.
__memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69
69  ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or directory.
(gdb) backtrace
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69
#1  0x558be7a3 in qemu_spice_create_update (ssd=0x57240140) at 
ui/spice-display.c:222
#2  0x558bf610 in qemu_spice_display_refresh (ssd=0x57240140) at 
ui/spice-display.c:495
#3  0x557d106e in display_refresh (dcl=0x57240148) at 
hw/display/qxl.c:1857
#4  0x558b763d in dpy_refresh (s=0x573a0e80) at ui/console.c:1493
#5  0x558b3e5a in gui_update (opaque=0x573a0e80) at ui/console.c:197
#6  0x558e9651 in timerlist_run_timers (timer_list=0x562cbab0) at 
qemu-timer.c:502
#7  0x558e9699 in qemu_clock_run_timers (type=QEMU_CLOCK_REALTIME) at 
qemu-timer.c:513
#8  0x558e9983 in qemu_clock_run_all_timers () at qemu-timer.c:621
#9  0x558e830b in main_loop_wait (nonblocking=0) at main-loop.c:500
#10 0x55729903 in main_loop () at vl.c:1799
#11 0x557311c7 in main (argc=29, argv=0x7fffe9e8, 
envp=0x7fffead8) at vl.c:4385


Linux is 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) x86_64 
GNU/Linux


the segfault occurs after I log into the gnome session. virtualized os is 
FreeBSD

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1455254

Title:
  Segmentation fault. __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch
  /memcmp-sse4.S:69

Status in QEMU:
  New

Bug description:
  compiled qemu at commit 1eeace9c237a729d11c7acd7c0338ab4562af637

  with ./configure --enable-debug --enable-vnc --target-
  list=x86_64-softmmu


  gdb --args ./qemu-system-x86_64 -nographic -parallel none -serial none 
-nodefconfig -nodefaults -machine accel=kvm -enable-kvm -m 1024M -vga qxl -k de 
-cpu qemu64 -smp cpus=1,cores=1,threads=1,sockets=1 -net 
nic,model=rtl8139,macaddr=xxx -net tap -drive 
file=freebsd.img,media=disk,if=ide -vnc :18
  GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./qemu-system-x86_64...done.
  (gdb) run
  Starting program: /root/

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

2014-02-12 Thread Manuel Baesler

RIght, with '-usb' qemu creates then 'piix3-usb-uhci' device:

00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB
[Natoma/Triton II] (rev 01)

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096

Title:
  USB Passthrough not working for Windows 7 guest

Status in QEMU:
  Confirmed
Status in “qemu-kvm” package in Ubuntu:
  Incomplete

Bug description:
  USB Passthrough from host to guest is not working for a 32-bit Windows
  7 guest, while it works perfectly for a 32-bit Windows XP guest.

  The device appears in the device manager of Windows 7, but with "Error
  code 10: device cannot start". I have tried this with numerous USB
  thumbdrives and a USB wireless NIC, all with the same result. The
  device name and functionality is recognized, so at least some USB
  negotiation is taking place.

  I am trying this with the latest git-pull of QEMU-KVM.

  The command line to launch qemu-kvm for win7 is:
  sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 
-smp 2 -vga std -hda ./disk_images/win7.qcow -vnc :1 -boot c -usb -usbdevice 
tablet -usbdevice host:0781:5150

  The command line to launch qemu-kvm for winxp is:
  sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 
-smp 2 -usb -vga std -hda ./winxpsp3.qcow -vnc :0 -boot c -usbdevice tablet 
-usbdevice host:0781:5150

  Any help is appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/685096/+subscriptions

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

2014-02-01 Thread Manuel Baesler

followup:

my understanding is there are a bunch of usb interfaces:

uhci is usb 1.0
ehci is usb 2.0
xhci is usb 3.0
…

-device piix3-usb-uhci will create an usb 1.0 interface. I guess usb 1.0
is insufficent for modern usb devices so windows errors with code 10.
ehci have enough to bring full support for modern usb devices.

qemu is like LEGO where you can wire it all together :-)

refference:
https://github.com/qemu/qemu/blob/master/docs/usb2.txt
https://en.wikipedia.org/wiki/Host_controller_interface_(USB,_Firewire)#USB

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096

Title:
  USB Passthrough not working for Windows 7 guest

Status in QEMU:
  Confirmed
Status in “qemu-kvm” package in Ubuntu:
  Confirmed

Bug description:
  USB Passthrough from host to guest is not working for a 32-bit Windows
  7 guest, while it works perfectly for a 32-bit Windows XP guest.

  The device appears in the device manager of Windows 7, but with "Error
  code 10: device cannot start". I have tried this with numerous USB
  thumbdrives and a USB wireless NIC, all with the same result. The
  device name and functionality is recognized, so at least some USB
  negotiation is taking place.

  I am trying this with the latest git-pull of QEMU-KVM.

  The command line to launch qemu-kvm for win7 is:
  sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 
-smp 2 -vga std -hda ./disk_images/win7.qcow -vnc :1 -boot c -usb -usbdevice 
tablet -usbdevice host:0781:5150

  The command line to launch qemu-kvm for winxp is:
  sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 
-smp 2 -usb -vga std -hda ./winxpsp3.qcow -vnc :0 -boot c -usbdevice tablet 
-usbdevice host:0781:5150

  Any help is appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/685096/+subscriptions

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

2014-02-01 Thread Manuel Baesler

Hi, I had the same problem. Tested a lot. My solution to passthrough usb
devices to a windows 7 x64 guest:

parameter part:

-device usb-ehci,id=usb,bus=pci.0,addr=0x4 -device usb-
host,vendorid=0x{},productid=0x{},id=hostdev0,bus=usb.0

I also tried the device
piix4-usb-uhci

instead of usb-ehci

piix4-usb-uhci caused the Code 10 error in the windows device manager.

lsusb will give you a list of plugged in usb devices. eg.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

1d6b:0002
and
1d6b:0003

are vendorid:prouctid

replace {} with the ids and it should work. I tested it with

- ssd usb 3.0 drive 
- retail usb seagate usb 2.0 hdd drive.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096

Title:
  USB Passthrough not working for Windows 7 guest

Status in QEMU:
  Confirmed
Status in “qemu-kvm” package in Ubuntu:
  Confirmed

Bug description:
  USB Passthrough from host to guest is not working for a 32-bit Windows
  7 guest, while it works perfectly for a 32-bit Windows XP guest.

  The device appears in the device manager of Windows 7, but with "Error
  code 10: device cannot start". I have tried this with numerous USB
  thumbdrives and a USB wireless NIC, all with the same result. The
  device name and functionality is recognized, so at least some USB
  negotiation is taking place.

  I am trying this with the latest git-pull of QEMU-KVM.

  The command line to launch qemu-kvm for win7 is:
  sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 
-smp 2 -vga std -hda ./disk_images/win7.qcow -vnc :1 -boot c -usb -usbdevice 
tablet -usbdevice host:0781:5150

  The command line to launch qemu-kvm for winxp is:
  sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 
-smp 2 -usb -vga std -hda ./winxpsp3.qcow -vnc :0 -boot c -usbdevice tablet 
-usbdevice host:0781:5150

  Any help is appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/685096/+subscriptions

[Qemu-devel] [Bug 1832281] Re: tcg bug master / 4.0.0 v8 operation >>> and |=

[Qemu-devel] [Bug 1832281] Re: tcg bug master / 4.0.0 v8 operation >>> and |=

[Qemu-devel] [Bug 1832281] [NEW] tcg bug master / 4.0.0 v8 operation >>> and |=

[Qemu-devel] [Bug 1574327] [NEW] qemu-system-x86_64 -net nic, model=help outputs to stderr instead of std

[Qemu-devel] [Bug 1455254] [NEW] Segmentation fault. __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

8 matches

Site Navigation

Mail list logo

Footer information