similar to: Xen sound card for Windows DomU

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

[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''

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

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

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.

strange problem!! I think the xen 3.3.1 has been installed successfully.(detail info appended below). when I use "xm create" command, it said"Started domain opensolaris0811". opensolaris0811 is my installed domain name. However, when I use "xm list" command, I cannot find the new build domain opensolaris0811. Only show domain-0 and win2k3 (which is a guest OS

I have been using syslinux-6.x along with isohybrid --mac and --efi option to create a usb hybrid iso with EFI support. The thing with EFI is that you'll need to use grub as your bootloader for EFI but isohybrid does setup the proper partition schema for EFI. You'll need to use the following to generate an iso that works. xorriso -as mkisofs -J -R -l -V some-vol-label \ -o ../image.iso

My dom0 is uing Centos 5.2 x64. I have just upgraded Xen from 3.3.0 to 3.3.1. After upgraded, I find that I cannot hotplug additional vcpu anymore. I have a domU "linux1" which is a paravirtualized vm with centos 5.2. I try to "xm vcpu-set linux1 4", it does not have any error message, but those vcpu cannot be displayed. I also tried to add vcpu using "virsh setvcpus

On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled

> Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. > > below are results of me testing - i did each a few times to make sure they are valid results. > > hope it helps identify something that's gone awry ? > so far, 6.03

Hi James, I''m testing GPLPV 0.9.12-pre13 on Windows 2008 x64, and found some interesting results : - The drivers are NOT signed, even though I''ve install certs. Had to use F8 on boot. - both QEMU and Xen block device are active, which usually means corruption is coming. Is this a known issue? http://i44.tinypic.com/2vmypvk.png http://i42.tinypic.com/2mewnia.png Regards, Fajar

https://bugs.freedesktop.org/show_bug.cgi?id=104291 Bug ID: 104291 Summary: Virgl broken on current mesa (17.4+), with nouveau/nv50 as host Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

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

Hello! after update of GPLPV drivers from 0.9.12-pre13 to 0.10.0.86 on windows 2008 server domU I cant use xm shutdown <domU> in dom0 (nothing happens exactly for this domU, other domU with old drivers shutdowns normally), how to fix? opensuse11.1x64 xen 3.3.1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello, I have installed rpm version of xen 3.4.3+ libvirt 0.7.0-6 on my server with Centos 5.4 (kernel 2.6.18-238.12.1.el5xen) When I run reboot a domU (para virtualized Linux) by command "virsh reboot [vm]", sometimes domU cannot be rebooted but sometimes can, pattern is random. Also sometimes when domU reboots by "virsh reboot [vm]" , my ssh connection to dom0

I am having difficulty configuring a DomU running WinXP for audio. My hardware is as follows: 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2) I tried all sorts of settings in my config soundhw=''snd_hda_intel'' soundhw=''snd'' The domain hangs (runs fine with no sound setting) and I get the following: [root@localhost

Just reporting some iperf results. In each case, Dom0 is iperf server, DomU is iperf client: (1) Dom0: Intel Core2 3.16 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 1.17 Gbits/sec (2) Dom0: Intel Core2 2.33 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 725 Mbits/sec (3) Dom0: Intel Core2 2.33 GHz,