similar to: (updated) test report for xen-unstable tree with upstream QEMU

Guest needs the ability to enable and disable MSI-X interrupts by setting the MSI-X control bit, for a passed-through device. Guest is allowed to write MSI-X mask bit only if Xen *thinks* that mask is clear (interrupts enabled). If the mask is set by Xen (interrupts disabled), writes to mask bit by the guest is ignored. Currently, a write to MSI-X mask bit by the guest is silently ignored. A

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

Hi All, We did a round testing for Xen 4.2 RC1 (CS#25692) with Linux 3.4.7 dom0. We covered VT-d, SR-IOV, Power Management, TXT, IVB new features, HSW new features. We covered many cases for HVM guests (both Redhat Linux and MS Windows guest). We tested on Westmere-EP, SandyBridge-EP, IvyBridge desktop, and Haswell hardware platforms. We found no new issues, and verified 1 fixed bug. Fixed bug

Hi folks, From the roadmap for Xen 4.3 development, Xen 4.3 will use upstream QEMU (partially done). So I''d like to confirm the following questions. 1. Will Xen 4.3 really use upstream QEMU by default ? I have the question because so far the xen.git tree still uses qemu-xen-unstable by default. 2. If ''yes'' for 1st question, which QEMU upstream will be used in Xen

Hi Yongjie, I have just compiled and installed Xen 4.3-unstable changeset 26666 and Linux kernel 3.8.1, according to your specifications. However, I still cannot get success with Intel HD Graphics 4600 IGD VGA passthrough. Although in Device Manager in Windows 7 HVM domU, it says "This device is working properly" for Intel HD Graphics 4600, I can only get 16 colors. Please refer to

Hi Yongjie, I have just compiled and installed Xen 4.3-unstable changeset 26666 and Linux kernel 3.8.1, according to your specifications. However, I still cannot get success with Intel HD Graphics 4600 IGD VGA passthrough. Although in Device Manager in Windows 7 HVM domU, it says "This device is working properly" for Intel HD Graphics 4600, I can only get 16 colors. Please refer to

Hi All, The ipxe git commit version changed, but its release version should still stay at v1.0.0 Signed-off-by: Yongjie Ren <yongjie.ren@intel.com<mailto:yongjie.ren@intel.com>> ------ diff -r 4086e4811547 tools/firmware/etherboot/Makefile --- a/tools/firmware/etherboot/Makefile Thu Jan 05 17:25:23 2012 +0000 +++ b/tools/firmware/etherboot/Makefile Fri Jan 06 14:30:54 2012 +0800 @@

Hi Tim, Could you please have a look at this bug? Thanks a lot. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1774 Best Regards, Yongjie Ren (Jay) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

hi, i am trying to find out the max vcpus supported for any domain by my hypervisor, however i am having some trouble with the below: vcpu=5 maxvcpus=libvirt.virConnect.getMaxVcpus(conn,'kqemu') if maxvcpus <= vcpu: logging.debug('checkmaxvcpus: max vcpus on hypervisor %i is less than requested vcpu of %i' % (maxvcpus, vcpu)) return 0 else: return 1

Hi list, According to the libvirt documentation [1] "Show maximum number of virtual CPUs for guest domains on this connection" This may not be a complete definition. My first guess from the above was that this returns the number of virtual CPUs that can exist at the same time on the host, either one or several VMs. In fact it returned 16 in my fedora 20 desktop running with KVM,

document update in xl.cfg.pod.5 for ''stdvga=1'' by default Signed-off-by: Yongjie Ren <yongjie.ren@intel.com> diff -r b98feb4d6359 docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 Tue Jun 26 12:56:31 2012 +0800 +++ b/docs/man/xl.cfg.pod.5 Tue Jun 26 13:27:19 2012 +0800 @@ -718,9 +718,10 @@ =item B<stdvga=BOOLEAN> Select a standard VGA card with VBE (VESA BIOS

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

Dear Sir/Madam, After installing R, I saw this warning message in red when I open the R... During startup - Warning messages: 1: Setting LC_CTYPE failed, using "C" 2: Setting LC_COLLATE failed, using "C" 3: Setting LC_TIME failed, using "C" 4: Setting LC_MESSAGES failed, using "C" 5: Setting LC_PAPER failed, using "C" how shall I solve this ?

Hey Ian and Stefano, Please see this thread: http://lists.xen.org/archives/html/xen-devel/2013-05/msg01053.html for the debug patches and some of the discussion. These three patches fix an race that has been in QEMU traditional for a long time. The guts of the bug is that if you have a guest with these options: vcpus=1 maxvcpus=32 and do ''xl vcpu-set <guest> 32'' the

All, These days I am trying to understand the interaction relationship between the libvirt and KVM kernel module, eg. kvm_intel.ko. We know that KVM kernel module expose an entry in form of device file "/dev/kvm" which can be accessed by user space application to control, for example, create a VM using KVM_CREATE_VM with help of ioctl. Now let's say the tool virsh based upon

Hi, I''m trying to build a xen-qemu-dm-4.0 package to support the HVM part of the Xen 4.0 package that will be soon in Debian experimental. When I start an HVM domain, I have the following subject line of this thread in my /var/log/xen/qemu-dm-XXXX.log file, and then it stops here. Any idea what I should do to fix? Thomas P.S: my build is using a clone of

The xen_platform_pci xl configuration parameter currently has no effect on upstream QEMU; creation of the platform device is hardcoded. I have created a patch to QEMU to remove this hardcoded creation. This patch specifies the appropriate -device argument on the QEMU command line (and hence creates the device) only when xen_platform_pci is true. Signed-off-by: Paul Durrant

Hello all! I have a problem to extract values greater that for example 1820. I try this code: x[x[,1]>1820,]->x1 Please help me! Thank you! The data structure is: structure(c(2.576, 1.728, 3.434, 2.187, 1.928, 1.886, 1.2425, 1.23, 1.075, 1.1785, 1.186, 1.165, 1.732, 1.517, 1.4095, 1.074, 1.618, 1.677, 1.845, 1.594, 1.6655, 1.1605, 1.425, 1.099, 1.007, 1.1795, 1.3855, 1.4065, 1.138, 1.514,

Hi all, This is the test report of xen-unstable tree. There are one bug found. Version Info: ================================================================= xen-changeset: 25256 Dom0: linux.git 3.1.0-rc7 (commit: d93dc5c...) ================================================================= New issue(1) ============== 1. cpu weight out of range error when create hvm domU