similar to: Multiple Serial Port Passthrough in HVM domU

I have installed two 4-port serial cards (http://www.startech.com/ Product/ItemDetail.aspx?productid=PCI4S550&c=US) on a CentOS 4.4 system. The hardware appears to be recognized correctly, as kudzu added 2 entries to /etc/sysconfig/hwconf and lscpi shows both cards (output of lspci -vv for both cards included at the end of this email): # lspci 00:00.0 Host bridge: Intel Corporation

I am in the process of migrating from running CentOS 4.8 (32-bit) to CentOS 5.4 (64-bit) on my AMD Sempron(tm) Processor LE-1300 system (it is running CentOS 4.8 32-bit because the disk images are from a previous PIII system), and things are 'interesting' WRT how the Lava Computer mfg Inc Quattro-PCI card is being handled. lspci (on CentOS 4.8 32-bit) yields: 01:0a.0 Serial controller:

Can someone please help me with writing a udev rule? I need /dev/ttyUSB0 to automatically have 777 rights when plugged in. I'd like it to only apply to that one specific device. I'm not sure where to start, what files to look at and also what to write to make it work. TIA Brad This e-mail transmission contains information that is confidential and may be privileged. It is intended only

So yesterday I got was able to get a domU successfully using a PCI SCSI card. This morning I restarted the host server. When I try to start up the same domU I get this error: Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must be co-assigned to the same guest with 0000:0e:04.0, but it is not owned by pciback. How do I make this card owned by pciback on reboot. Do I need to

I have been investigating pci pass-through for virtualized guests and the documentation I have found seems to me to lack a certain consistency in its example. This may be due to my not understanding what it is trying to inform me. What I wish to do is to configure a pci multi-port serial i/o card for use by a single virtual host. I start by running lspci -v on the host to identify the serial

I have samba 2.2.5 and cups -1.1.15 from rpm packages on RH 7.3. I try to configure printers by localhost:631 and haven't smb device. ldd 'which smbd' gives: libcups.so.2 => /usr/lib/libcups.so.2 (0x40013000) libssl.so.2 => /lib/libssl.so.2 (0x40045000) libcrypto.so.2 => /lib/libcrypto.so.2 (0x40072000) libnsl.so.1 => /lib/libnsl.so.1 (0x40135000)

Compilation failure on c/s 17194 is as follows: /root/randy/vtd-stage/xen/common/built_in.o: In function `guest_remove_page'': /root/randy/vtd-stage/xen/common/memory.c:172: undefined reference to `__bitop_bad_size'' /root/randy/vtd-stage/xen/common/memory.c:172: relocation truncated to fit: R_X86_64_PC32 against undefined symbol `__bitop_bad_size''

Hi, DomU is a Win2008 R2 64 When i install the GPLPV drivers the network latency goes from 15ms to random numbers up to 1200ms and eventually dies. If you run a ping from the DomU to another host the network stays alive but the high latency is still there. Further more if i try and uninstall the network driver i am unable to use the old one (realtek) as it cannot detect the device.

Attached is a patch for shared interrupt between dom0 and HVM domain for vtd. Most of problem is caused by that we should inject interrupt to both domains and the physical interrupt deassertion then may be delayed by the device assigned to the HVM. The patch adds a timer, and the time out value is sufficient large to tolerant the delaying used to wait for the physical interrupt deassertion.

Well, I seem to have developed a strange issue with the GPL PV drivers in Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some Windows XP HVM domUs. Most (12-15) of my Windows machines work just fine. Two of them, though, have started exhibiting a strange behavior with intermittent network connectivity. Basically, the network starts up and connects initially. After some

Hey, everyone, I''m having some issues with a Xen DomU right related to performance. We have an application that cross-compiles a Linux distribution from scratch for embedded systems. We''re attempting to run this application inside a Xen DomU (paravirtualized, modified guest kernel), and the performance is really bad. The culprit seems to be high I/O wait times related to the

Hey, everyone, I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU to run correctly. I''ve followed a couple of the instruction sets out on the Xen wiki and other folks blogs, but I''m running into an issue with the domU crashing. The OpenSolaris version is the latest development release - 5.11-0.128. The config looks like this:

When trying to use the GPL PV drivers with Windows 7 x64 (and testsigning turned on), I get a BSOD with a STOP 0x00000101 error. There''s also an error at the top that says "A clock interrupt was not received on a secondary processor within the allocated time interval." Is this STOP error related to the HPET or other timing adjustments for Xen? Any advice on things I should

This may be a better question for the Xen-Devel list, but I''ll start here... Does anyone know if there is any easy way to replace the gPXE ROM with a newer version in Xen? Also, anyone know if there are any plans to have some sort of option in the domU config file to specify a boot rom? Looks like qemu-dm has an "-option-rom" option - is there any way in Xen to make use of

I'm attempting to configure Samba with CUPS as a centralized print server. I've done this in the past - my current production server is running Samba 3.2.14. On my current production server, I have several users set up as either "admin users" or "print admin" users so that they can manage the drivers, etc., on the Samba server. In setting up my new server, I'm

I''m trying to contain my frustration...but I''m wondering if *anyone* has *ever* gotten the Import functionality to work in XCP? I''ve tried several times, and keep getting the same obnoxious and useless error that is absolutely no help to anyone: Failed to Import. I have made sure that the transfer VM is installed (View -> Show Hidden Objects, transfer VM is there),

This fixes a bug in changeset 22526:7a5ee3800417, where the wrong value is read when deciding whether to flush the VTd tables. The effect is minor: in situations where the p2m entry is changed but the mfn is the same, the VTd tables will be unnecessarily flushed. old_entry is left untouched in the second case, since having a present old_entry will cause the an unnecessary check to be taken at

Hello I have a xen node, everydays for a few minutes, the bridge will send all income traffic to all interfaces, it makes our traffic statistics incorrect, Any help is appreciated. Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I build a DomU kernel on RHEL AS5.1. But when I boot this Guest DomU with the kernel, it gives me error message: Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') Can someone give me any suggestion about this problem? Thank you! Joe _______________________________________________ Xen-users

diff -r e6266fc76d08 -r 6feac926cf80 xen/drivers/passthrough/vtd/iommu.c --- a/xen/drivers/passthrough/vtd/iommu.c Fri Jul 27 12:22:13 2012 +0200 +++ b/xen/drivers/passthrough/vtd/iommu.c Mon Jul 30 15:35:16 2012 -0700 @@ -2137,6 +2137,15 @@ int __init intel_vtd_setup(void) { iommu = drhd->iommu; + printk("Intel VT-d supported page sizes: 4kB"); + if