similar to: 32bit HVM PV drivers on 64bit hypervisor

Hi folk, I''m recently doing some work on VNIF driver, however, when I enabled both qemu-dm devices and pv devices, the pv driver complains. It seems two kinds of devices have very similar entries in xenstore, which misled the driver. I remembered in the past, there is a `type:ioemu'' entry in xenstore to represent dm devices, but it was removed. There used to be a

I am trying to get PV drivers running on both Centos 5.1 and Centos 5.3 HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. For the network drivers to work I had to unload the Realtek NIC driver and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias to modprobe.conf then got the PV NICs working nicely (Much

(The list appears to have eaten my previous attempt to send this. Apologies if you receive multiple copies.) The attached patches allow you to use paravirtualised network and block interfaces from fully virtualised domains, based on Intel''s patches from a few months ago. These are significantly faster than the equivalent ioemu devices, sometimes by more than an order of magnitude.

Hi all, my name is Hirofumi Tsujimura. We are porting and testing a PV-on-HVM in the IPF. This is a first time to send mail. I probably found the problem when I tested the VNIF. My operation for the test is following. 1. create a domain VTx and attach the VNIF in it. 2. create a domain U. 3. send a packet to the domain VTx from the domain U with ping command. Then, the domain VTx

On Thursday, 6 April 2017 12:04:20 CEST Richard W.M. Jones wrote: > Our previous test was wrong. It tested whether the xennet.ko module > exists. This module was renamed in more recent kernels (to > xen-netfront.ko), so it happened to not detect modern kernels as > PV-only, but this was by chance. Just stumbled upon this bit in v2v/convert_linux.ml: if family = `SUSE_family

Hi all, This is today''s xen nightly test report, changeset: 16481 unstable tree.  Linux-xen:323 No new issue today. But I include full validation failure in this list.    Old issues : ================================================= 1) Can not install 32bit Fedora 7 with vcpu > 1 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1084 2) [Installation] Fedora8 IA32e guest

Hi All, There are two new issues found in Xen 3.2 RC2 compared with last time nightly testing. Save/Restore failed and local live migration failed. There is also another installation issue found in regular testing: HVM domain would be blue scree when install 32bit up acpi winXP on 32e host It is reported in HVM domain, if using SCSI emulation (disk = [

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

New issues (0) ================================================= No new issue. Old issues (3): ================================================= 1).time latency is a negative number on window guest when vcpu > 1 http://losvmm-bridge.sh.intel.com/bugzilla/show_bug.cgi?id=991 You can reproduce it on SMP windows, it will not happen on UP Windows 2) IA32E/PAE: 32bit Vista RTM network

This is better suited to llvm-dev, so I'm directing it there. From: llvm-commits <llvm-commits-bounces at lists.llvm.org> on behalf of Qing Shan Zhang via llvm-commits <llvm-commits at lists.llvm.org> Reply-To: Qing Shan Zhang <qshanz at cn.ibm.com> Date: Sunday, August 19, 2018 at 10:10 PM To: "llvm-commits at lists.llvm.org" <llvm-commits at lists.llvm.org>

we are migrating our standalone Samba sever (3.0.14a) on a Solaris 10 box to an RHEL 6.3 box. Testing shows that on Solaris 3.0.14a works with both the OpenLDAP server we are currently using and the IPA2.2 server as LDAP backend. But 3.5.10-125.el6 on a RHEL 6.3 box does not work with either. I can still map a share with 3.5 as owner of the shared directory, but secondary group ownership does

Hello, I am not sure about the p.adjust( , fdr). How do these adjusted p-values get? I have read papers of BH method. For independent case, we compare the ordered p-values with the alfa*i/m, where m is the number of tests. But I have checked that result based on the adjusted p-values is different with that by using the independent case method. Then how do the result of p.adjust( , fdr) come? And

PCmark2005 running in Windows XP is known to need this mmio decoder. This patch also fixes some inconsistencies, the comments of mmio decoder use AT&T ordering for operands, but the syntax looks like Intel asm. This leads to much confusion. Signed-off-by: Qing He <qing.he@intel.com> Thanks, Qing _______________________________________________ Xen-devel mailing list

New issues (0) ================================================= No new issue. Old issues (4): ================================================= 1) IA32E/PAE: 32bit Vista RTM network doesn''t work. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=840 2)time latency is a negative number on window guest when vcpu > 1 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895 You

Dear all, I am running R 2.4.1. > library(siggenes); > library(multtest); > cl<-rep(c(0,1),c(3,3)); > sub<-exprs(AffyExpData[,c(1:3,7:9)]); > gn<-geneNames(AffyRAwData); > sam.out<-sam(sub,cl,rand=123,gene.names=gn); We're doing 20 complete permutations > sam.out SAM Analysis for the Two-Class Unpaired Case Assuming Unequal Variances Delta p0

Steven, I found where the difference is, it may be my fault: My changeset number + 1 = your changeset number. My 11160 is your 11159, and my 11161 is your 11160. Attached please see those patches, Thanks, Winston, -----Original Message----- From: Steven Smith [mailto:sos22@hermes.cam.ac.uk] On Behalf Of Steven Smith Sent: Wednesday, October 11, 2006 10:33 AM To: Wang, Winston L Cc: Stefan Berger;

I am enclosing the patch I have been working on. I have tested this on sles9 (2.6.5) and RHEL 4 (2.6.9). The patch applies cleanly on ChangeSet 11635. This patch was cleaned up based on Ian''s and DOI''s work. Signed-off-by: K. Y. Srinivasan (ksrinivasan@novell.com) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi Stefan, The problem is cause by the VBD/VNIF PCI device in DM checked in changeset 11160: PCI Device ID: 5853(Xen),class:ff80 (unknown) ACPI Window does not understand this device and can not find device driver associate with it. To verify this just revert the patches of changset 11161/11160 We are working on the fix now, revert patch is not the solution anyway... Thanks, Winston

Hi list, I''ve read about recent efforts to push pv-on-hvm drivers to Linux mainline and I''m curious to know the cause for this. What''s the advantage over using pv_ops directly and booting the kernel paravirtualized? Are there plans to move Linux domUs closer to the KVM way (from an architectural point of view)? Hope you can help. Regards, Markus