Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1114030 > unrolled thread

Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host Usama Makhzoum <osmakh1@gmail.com> - 2022-08-22 01:40 +0200
    Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host Michael Tokarev <mjt@tls.msk.ru> - 2022-08-22 09:40 +0200
    Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host أسامة مخزوم <osmakh1@gmail.com> - 2022-08-28 15:40 +0200
      Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host Michael Tokarev <mjt@tls.msk.ru> - 2022-08-29 11:10 +0200

#1114030 — Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host

Package: qemu-system-x86
Version: 1:7.0+dfsg-7+b1
Severity: important
X-Debbugs-Cc: osmakh1@gmail.com


I use qemu as the following:

/usr/bin/qemu-system-x86_64  -soundhw ac97 -machine accel=kvm -m 1033 -cdrom
windowsxp.iso -hda windowsxp.img -boot once=d,menu=off -net nic,model=rtl8139
-net user -net user,smb="/path/to/shared/folder/inside/my/home" -rtc
base=localtime -name "Windows XP x32"


it boots normally after installation, but when i access shared folder (just by
typing qemu user network ip "\\10.0.2.2\qemu") inside the run dialog everything
freezed , i can't even grab my pointer outside qemu window without
restarting window manager.


i also have this inside my smb.conf



########################################################################
==============
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-
muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:*
%n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account"
-d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/tmp
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[qemu]
path=/path/to/my/shared/folder
read only=no
guest ok=true
force user=os
acl allow execute always = True



########################################################################


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu           1.0.0+git-20190125.36a4c85-5.1
ii  libaio1             0.3.112-13
ii  libbpf0             1:0.5.0-1
ii  libc6               2.34-4
ii  libcapstone4        4.0.2-5
ii  libfdt1             1.6.1-1
ii  libfuse3-3          3.10.5-1
ii  libgcc-s1           11.2.0-16
ii  libglib2.0-0        2.72.3-1+b1
ii  libgnutls30         3.7.6-2
ii  libibverbs1         39.0-1
ii  libjpeg62-turbo     1:2.1.2-1
ii  libnettle8          3.7.3-1
ii  libnuma1            2.0.14-3
ii  libpixman-1-0       0.40.0-1
ii  libpmem1            1.11.1-3
ii  libpng16-16         1.6.37-3
ii  librdmacm1          39.0-1
ii  libsasl2-2          2.1.28+dfsg-2+b1
ii  libseccomp2         2.5.3-2
ii  libslirp0           4.6.1-1
ii  libudev1            250.3-2
ii  liburing2           2.1-2
ii  libvdeplug2         4.0.1-3
ii  libzstd1            1.5.2+dfsg-1
ii  qemu-system-common  1:7.0+dfsg-7+b1
ii  qemu-system-data    1:7.0+dfsg-7
ii  seabios             1.15.0-1
ii  zlib1g              1:1.2.11.dfsg-2

Versions of packages qemu-system-x86 recommends:
ii  ovmf              2021.11-2
ii  qemu-block-extra  1:7.0+dfsg-7+b1
ii  qemu-system-gui   1:7.0+dfsg-7+b1
ii  qemu-utils        1:6.2+dfsg-2

Versions of packages qemu-system-x86 suggests:
ii  samba  2:4.16.4+dfsg-2
pn  vde2   <none>

-- no debconf information

[toc] | [next] | [standalone]

#1114054

Control: tag -1 + moreinfo
Control: severity -1 normal

22.08.2022 02:30, Usama Makhzoum wrote:
> Package: qemu-system-x86
> Version: 1:7.0+dfsg-7+b1
> Severity: important
> X-Debbugs-Cc: osmakh1@gmail.com
> 
> 
> I use qemu as the following:
> 
> /usr/bin/qemu-system-x86_64  -soundhw ac97 -machine accel=kvm -m 1033 -cdrom
> windowsxp.iso -hda windowsxp.img -boot once=d,menu=off -net nic,model=rtl8139
> -net user -net user,smb="/path/to/shared/folder/inside/my/home" -rtc
> base=localtime -name "Windows XP x32"

You have:

  -net nic,model=rtl8139  -net user
  -net user,smb=...

The -net thing comes in pairs (one is guest side, another is host side).
You have 3 of them, and the last one is not paired with the guest side.

I suspect this is your problem - qemu does not know how to handle the
unpaired -net user.

The whole -net syntax is obsolete - partly because of this common
misunderstanding and partly because whole architecture behind -net is
wrongly designed. You should use -netdev..-device instead of -net..-net.
(Unfortunately, many old guides in the internet still suggest to use
-net, but this is something we can't change in a moment).

Now, you use both -net user,smb=... which redirects ports used by
windows networking to custom samba instance with its own configuration,
with nothing shared from host samba. Yet you attach your smb.conf file.
Why?

I suggest you to use -netdev..-device syntax (which has, among other
things, detection of disconnected halves like you have now) as a start.
Personally I see no reason to try to debug issues coming from -net..-net.

Thanks,

/mjt

[toc] | [prev] | [next] | [standalone]

#1114860

> You have:
>
> -net nic,model=rtl8139 -net user
> -net user,smb=...
>
> The -net thing comes in pairs (one is guest side, another is host side).
> You have 3 of them, and the last one is not paired with the guest side.
>
> I suspect this is your problem - qemu does not know how to handle the
> unpaired -net user.

you were right, i change it now and it works. seems AQEMU generates
buggy qemu's cmds, i have used it for the vm but i copy cmdline only

shall i report separate bug for aqemu ?


> The whole -net syntax is obsolete - partly because of this common
> misunderstanding and partly because whole architecture behind -net is
> wrongly designed. You should use -netdev..-device instead of -net..-net.
> (Unfortunately, many old guides in the internet still suggest to use
> -net, but this is something we can't change in a moment).


> Now, you use both -net user,smb=... which redirects ports used by
> windows networking to custom samba instance with its own configuration,
> with nothing shared from host samba. Yet you attach your smb.conf file.
> Why?

I was just mistaken about samba and qemu , thought it used smbd for
its internals...

[toc] | [prev] | [next] | [standalone]

#1115314

28.08.2022 16:33, أسامة مخزوم wrote:
>> You have:
>>
>> -net nic,model=rtl8139 -net user
>> -net user,smb=...
>>
>> The -net thing comes in pairs (one is guest side, another is host side).
>> You have 3 of them, and the last one is not paired with the guest side.
>>
>> I suspect this is your problem - qemu does not know how to handle the
>> unpaired -net user.
> 
> you were right, i change it now and it works. seems AQEMU generates
> buggy qemu's cmds, i have used it for the vm but i copy cmdline only
> 
> shall i report separate bug for aqemu ?

At the time aqemu has been written, the -net syntax was the only one
available. No doubt it is using that syntax.

Now, aqemu is not maintained for several years, even if it said there's
a new development started in 2016.  You're free to do so ofcource ;)

[]
>> Now, you use both -net user,smb=... which redirects ports used by
>> windows networking to custom samba instance with its own configuration,
>> with nothing shared from host samba. Yet you attach your smb.conf file.
>> Why?
> 
> I was just mistaken about samba and qemu , thought it used smbd for
> its internals...

Yes qemu uses smbd. But it uses smbd with its own entirely private
configuration, not touching your main smbd/smb.conf in any way.

If you want to connect to the "main" smbd, do not override -smb, -
this way your main samba "instance" will be used.

/mjt

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web