similar to: domU: no audio device

i created a centos 5.3 hvm domU. i have tried any one of the following in the xen config without luck soundhw = "all" or "sb16" or "es1370" dom0: #virsh version Compiled against library: libvir 0.7.0 Using library: libvir 0.7.0 Using API: Xen 3.0.1 Running hypervisor: Xen 3.1.0 # uname -a Linux localhost.localdomain 2.6.18-128.4.1.el5xen # /usr/lib/xen/bin/qemu-dm

[HVM] enable sound card support for qemu Signed-off-by: Edwin Zhai <edwin.zhai@intel.com> diff -r 2abb1c801ab7 tools/examples/xmexample.hvm --- a/tools/examples/xmexample.hvm Wed Jul 19 16:09:59 2006 +0800 +++ b/tools/examples/xmexample.hvm Thu Jul 20 21:19:07 2006 +0800 @@ -153,8 +153,8 @@ serial=''pty''

Hi all, Please make sure that your sound card could work correctly in advance. Follow the next steps: 1. re-compile xen0''s kernel to support you specific audio device; 2. modify configure file as follows: soundhw=''es1370'' or soundhw=''sb16'' =======================> I am not sure that either could work, please test. ''es1370'' on

i want to create a domU using iscsi disk. Since virt-manager and virt-install do not support, pls advise the config file which will be used by xm create to create a xen guest. Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Unable to connect to my HVM # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3869 2 r----- 368.6 vm00 45 128 1 -b---- 62.3 The vm00 changes state from "r" to "b" after about a minute. (I have a fedora dvd in the drive.) #cat

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

i am trying to install fedora11 hvm guest on centos 5.4 dom0 but failed.   after loading vmlinuz, initrd.img and probing edd...ok, it stopped. dom0: [root@localhost images]# virsh version Compiled against library: libvir 0.6.3 Using library: libvir 0.6.3 Using API: Xen 3.0.1 Running hypervisor: Xen 3.1.0 pls advise. Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/

Hi, This patch makes it possible for Qemu to use the SDL library, to conveniently replace VNC, which has horrible mouse support. It also adds a IOEMU_CONFIGURE_OPTIONS option in tools/Makefile, so that later on, we can call: $(MAKE_CLEAN) -C $(DIR)/tools $(CONFIG) IOEMU_CONFIGURE_OPTIONS="--audio-drv-list=\"pa oss alsa sdl esd\" --audio-card-list=\"ac97 es1370 sb16 cs4231a

stubdom: add example config file Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r e69570f85e85 tools/examples/stubdom-ExampleHVMDomain --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tools/examples/stubdom-ExampleHVMDomain Thu Jul 17 19:31:13 2008 +0100 @@ -0,0 +1,21 @@ +# Not to be started directly, +# See xmexample.hvm-stubdom and stubdom/README for more details

after shutdown many domu, the memory is not release to dom0, before:  host: 8g phy memory 16g swap (4g used) dom0: 600m domu: consumed all memory, no new domu could be created after shutdown many domu:  host: 8g phy memory 16g swap (4g used) dom0: 600m domu: 2g why memory of dom0 is still 600m? how to release more to dom0? pls advise. Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往

my server has intel q9550 cpu (which supports intel-vt) and intel s3200 motherboard. BIOS has enabled intel virtualisation. centos 5.4, 64bit [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:03:03 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# grep vmx /proc/cpuinfo flags           : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36

Hi, Has anyone come across this problem please? Couldn''t see it in the list archives: This is the error message generated by make tools (run twice, so the successful object creation has been removed.) Thanks Install prefix /usr BIOS directory /usr/share/qemu binary directory /usr/bin Manual directory /usr/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path

Package: xen Version: 4.1.1 Severity: wishlist On the xen-qemu-dm-4.0 package, I enabled audio support, but since this is packaged in 4.1, audio support is gone. What I did for squeeze, is: --- a/configure 2010-03-23 17:08:39.000000000 +0800 +++ b/configure 2010-03-23 17:09:30.000000000 +0800 @@ -1382,6 +1382,9 @@ echo "#define CONFIG_VDE 1" >> $config_h echo

(Reply directly, as I''m not subscribed here.) As you may have seen, ARC recently approved my case to remove the ancient sbpro driver Solaris. I''m intent on doing that, because it really helps with our OSS integration effort, which I''m now leading. The problem is, will this impact qemu? I''m not sure of the answer. I *think* qemu emulates an older ESS1370

(Reply directly, as I''m not subscribed here.) As you may have seen, ARC recently approved my case to remove the ancient sbpro driver Solaris. I''m intent on doing that, because it really helps with our OSS integration effort, which I''m now leading. The problem is, will this impact qemu? I''m not sure of the answer. I *think* qemu emulates an older ESS1370

I am using xen3.3.1, I added following 2 options in the DomU config file which is a Win2k3 server(64bit). When I start the DomU, it shows a multimedia audio controller detected, but no driver suitable. I am using the PV driver (Xen <http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.12-pre13.exe> PV Drivers 0.9.12-pre13.exe) audio=1 soundhw=''es1370''

Hello, rdesktop (I''m using tsclient) can only connect to Win XP if I''ve started vncviewer before and have logged in. I want only start the XP instance and then loggin in with rdesktop only. How can I achieve this? kind regards, Oliver kernel = ''/usr/lib/xen-ioemu-3.1/boot/hvmloader'' builder = ''hvm'' memory = ''1024''

Hello, I''ve got xen installed on a box running Fedora Core 6. In addition I''m running a Windows 2003 server as a domU. Everything work fine and I am quite satisfied with the setup. However, in win 2003''s device manager there is a unknown PCI device that I not able to find a suitable driver for. Windows update can''t find one either. Is there a way to find what

Hello, On Thu, Jul 03, 2014 at 10:58:11PM +1000, Michael D. Setzer II wrote: > I've been using various versions of syslinux as the boot loader for the g4l > project that I have been the maintainer of since 2004. It was already using > syslinux, so I've just updated it over the years, and currently have it use 5.10 > version, but have done test builds with the 6.x versions.

Instead of storing the number of sockets, cores, and threads separately with the possibility to have each of them optional, store them together, so either we have a CPU topology or none. This slightly simplifies the handling of CPU topology. Most of the output modes/producers already considered a missing information of a topology as "1" when any of the other was specified, so the