https://bugzilla.suse.com/show_bug.cgi?id=1201994 https://bugzilla.suse.com/show_bug.cgi?id=1201994#c3 --- Comment #3 from James Fehlig <jfehlig@suse.com> --- (In reply to Erwin Pacua from comment #2)
(In reply to James Fehlig from comment #1)
The message is from qemu, and it is only a deprecation warning. '-soundhw ac97' still works, but '-device AC97' is preferred. Is it not working for you?
That is correct. Neither '-soundhw ac97' or '-device AC97' works. The only difference is that with '-soundhw', xl complains and failed to start the domU while with '-device AC97', domU runs but without an emulated sound card. That is happening on all my vms (fedora, ubuntu, windows xp/7/10).
That's odd. It works fine for me. With '-soundhw ac97' I see the warning in qemu-dm-<vm-name>.log, but either form gives me a sound card in the VM. E.g. from within my linux VM # hwinfo --sound 15: PCI 05.0: 0401 Multimedia audio controller [Created at pci.386] Unique ID: CvwD.Wvt18xt+7v7 SysFS ID: /devices/pci0000:00/0000:00:05.0 SysFS BusID: 0000:00:05.0 Hardware Class: sound Model: "Red Hat QEMU Virtual Machine" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2415 "82801AA AC'97 Audio Controller" SubVendor: pci 0x1af4 "Red Hat, Inc." SubDevice: pci 0x1100 "QEMU Virtual Machine" Revision: 0x01 Driver: "snd_intel8x0" Driver Modules: "snd_intel8x0" I/O Ports: 0xc000-0xc3ff (rw) I/O Ports: 0xc600-0xc6ff (rw) IRQ: 36 (2 events) Module Alias: "pci:v00008086d00002415sv00001AF4sd00001100bc04sc01i00" Driver Info #0: Driver Status: snd_intel8x0 is active Driver Activation Cmd: "modprobe snd_intel8x0" Config Status: cfg=new, avail=yes, need=no, active=unknown In the configurations where the VM actually starts, you don't see a sound card at all in the VM?
name = "fedora" type = "hvm" xen_platform_pci = 1 memory = 3000 maxmem = 3000 vcpus = 2 soundhw = "ac97" opengl = 0 vga = "stdvga" vnc = 1 spice = 1 spicehost = "127.0.0.1" spiceport = 2006 spicedisable_ticketing = 1 spicevdagent = 1 spice_image_compression = "off" vif = [ 'bridge=xenbr20, mac=00:16:3e:4e:f9:29, model=e1000' ] disk = [ '/home/erwinp/xen/images/x86_64/linux/fedora35/fedora35.img,raw,xvda,rw', ] on_poweroff = "destroy" serial = "pty" boot = "c"
My config is very similar to this one, with things such as 'vif' and 'disk' the only difference.
And here's the output when I tried to fire up one of them
[root@pc1:/etc/xen/vm]# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 4000 4 r----- 2057.3 Xenstore 1 31 1 -b---- 0.2 [root@pc1:/etc/xen/vm]# [root@pc1:/etc/xen/vm]# xl create fedora.cfg Parsing config from fedora.cfg libxl: warning: libxl_dm.c:1220:libxl__suse_node_to_path: replacing '/home/erwinp/xen/images/x86_64/linux/fedora35/fedora35.img' with '/dev/loop0' from /local/domain/0/backend/vbd/13/51712/node, just for qemu-xen libxl: error: libxl_dm.c:3173:device_model_spawn_outcome: Domain 13:domain 13 device model: spawn failed (rc=-3)
So apparently spawning qemu failed...
libxl: error: libxl_dm.c:3393:device_model_postconfig_done: Domain 13:Post DM startup configs failed, rc=-3 libxl: error: libxl_create.c:1869:domcreate_devmodel_started: Domain 13:device model did not start: -3 libxl: error: libxl_aoutils.c:652:libxl__kill_xs_path: Device Model already exited libxl: error: libxl_domain.c:1202:libxl__destroy_domid: Domain 13:Non-existant domain libxl: error: libxl_domain.c:1156:domain_destroy_callback: Domain 13:Unable to destroy guest libxl: error: libxl_domain.c:1083:domain_destroy_cb: Domain 13:Destruction of domain failed [root@pc1:/etc/xen/vm]# [root@pc1:/etc/xen/vm]# [root@pc1:/etc/xen/vm]# cat /var/log/xen/qemu-dm-fedora.log char device redirected to /dev/pts/8 (label serial0) qemu-system-i386: warning: '-soundhw ac97' is deprecated, please use '-device AC97' instead audio: warning: Using timer based audio emulation
but no failure message in the log. Maybe more debug info from xl (try 'xl -vvv create fedora.cfg'), another peek at /var/log/xen/qemu-dm-fedora.log, and scanning syslog for any messages from dom0 kernel, xen scripts, etc. will give us some hints. -- You are receiving this mail because: You are on the CC list for the bug.