similar to: How to enable audio in vmx guest

Displaying 20 results from an estimated 10000 matches similar to: "How to enable audio in vmx guest"

2006 Jul 26
0
[PATCH] [HVM] enable sound card support for qemu
[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''
2009 Sep 18
0
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
2009 Sep 18
0
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
2011 Jul 23
1
Bug#635166: Please enable audio support in xen-qemu
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
2008 Jul 17
0
[PATCH] stubdom: add example config file
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
2006 Feb 20
1
help VMX guest and networking xen 3.0.1
Hi, I''m working with Xen 3.0.1 and I have the following problem: I''m running Xen in a VT enabled Intel processor, I have successful installed a Fedora Core 4 32 bits Guest using VT. But the Network interface doesn''t appear in the Guest. I mean, running the commands "ifconfig –a" doesn''t show any eth0 interface just lo. In the /sys/class/net directory
2008 Dec 28
1
vncviewer <defunct> under HVM
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
2018 Apr 20
1
[PATCH] v2v: rework handling of CPU topology
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
2005 Nov 08
1
VMX domain status report Nov. 8 7646
We have test latest xen (ChangeSet 7646) on VT platform with Intel 915 chipset : The VMX can not be created for the known issue http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=388 <http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=382> But it is ok after adding xiaofeng''s patch. IA32: Build&Boot SMP xen0 without problem Can startup XenU with different
2010 Jun 06
3
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
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 = [
2011 Aug 29
1
[patch] Activate Qemu options
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
2005 Nov 03
7
VMX status daily report Nov. 3
We have test latest xen (ChangeSet 7608) on VT platform with Intel 915 chipset and Here is the test summary: IA32: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32 issues contain: VMX can not be created IA32E: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32E issues
2006 Jun 19
0
VMX status report 10426:840f33e54054
We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Cannot boot Windows 2000 - Only one CPU is detected in SMP dom0 - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: + Build&Boot UP xen0 without problem + Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain + Can bootup unmodified IA-32 WindowsXP SP1/SP2 in
2006 May 31
0
VMX status report 10177:d5f98d23427a
We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Only one CPU is detected in SMP dom0 - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: + Build&Boot UP xen0 without problem + Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain + Can bootup unmodified IA-32 WindowsXP SP1/SP2 in VMX domain + Can bootup
2007 Apr 19
0
vmx status report against changeset 14875 - 3 fixed issues, 3 old issues.
New issues (0) ================================================= No new issue. Fixed issue ================================================= 1) save&restore hvm guest will cause dom0 crash http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=962 2) xen0 hang when destroying a XenU guest http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=963 3) Build HVM PV driver failed
2006 Mar 24
3
VMX status chgset 9425:96e3b02ec931
We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. issues: - No bocking issues. IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain Can bootup unmodified IA-32 WindowsXP SP1/SP2 in VMX domain Can bootup VMX & XenU with different memory size(VMX:128MB,256MB,512MB.XenU:256MB)
2006 Jun 16
4
VMX status report 10358:73c73fb8875c
We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Cannot boot Windows 2000 - Only one CPU is detected in SMP dom0 - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: + Build&Boot UP xen0 without problem + Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain + Can bootup unmodified IA-32 WindowsXP SP1/SP2
2006 Apr 03
1
VMX status report 9514:4ad317429111
We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. Issues: - IA-32 VMX guest will hang when booting on IA-32PAE host with acpi=1 and apic=1.(Bug 594) - Failed to created VMX after tens of VMXs have been created & destroyed on IA-32e.(Bug593) IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX
2007 Feb 08
5
vmx status report against changeset 13826
We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Three platforms (32/PAE/32E) test all are based on SMP, It means that we boot up SMP guest OS in VMX. Here is the test summary: New issue ================================================ No new issue Issues List: ================================================ 1) IA32E/PAE: 32bit Vista RTM network doesn''t
2007 Mar 13
4
vmx status report against changeset 14356 - 1 new issue
Hi,All We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Two platforms (PAE/32E) test all are based on SMP, It means that we boot up SMP guest OS in VMX. Here is the test summary: New issue (1) ================================================ 1) Fails to restore VMX guests http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=929 Issues List (3):