similar to: test

_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Morning all, I have a doubt on what''s the xen version installed in my dom0. If I list the rpm installed (yum list | grep xen), version is 3.0.3-64.el5_2.9 (thus 3.0.3). On the other hand if I inquiry xm directly with "xm info" I get: xen_major : 3 xen_minor : 1 xen_extra : .2-92.1.18.el5 Cheers, N. --

Dear *, I''m more used to work with RedHat like OSes. Still, I did not denied the request from a user who wants a domU based on ubunto. I usually use virt-install to do the job, with a script similar to this one: #!/bin/sh BASE=SL-4.7-i386-pv \ virt-install --nographics \ --nonsparse \ --paravirt \ --noreboot \

Hi *.*, This is a continuation on the 2 NICs thread after some more testing. Just to remember my goal. --------------------------- I want to create a domU with 2 virtual NICS. One of them will contact the outside world, the other one will contact a VPN. No reason in concrete for choosing the bridging protocol, only because its the default one. I installed the dom0 with the 2 NICs active, with

flight 8865 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8865/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 1 xen-build-check(1) blocked n/a test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked

Hi, I''m trying to use a kickstart file to install VMs on a Scientific Linux 5.2 (repackaged RHEL52) host, but the install process seems to ignore my kickstart file. The command I''m using is: virt-install -n sl4vm01 --ram=1024 --vcpus=1 --os-type=linux --os-variant=rhel4 --extra-args="ks=http://particle.phys.uvic.ca/~fransham/ks.cfg" --paravirt --nographics

flight 8273 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8273/ Regressions :-( Tests which did not succeed and are blocking: build-amd64 4 xen-build fail REGR. vs. 8257 build-amd64-pvops 4 kernel-build fail REGR. vs. 8257 build-amd64-oldkern 4 xen-build fail REGR. vs. 8257

flight 7341 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/7341/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 7285 build-amd64 4 xen-build fail REGR. vs. 7285 build-i386-oldkern 4 xen-build fail REGR. vs. 7285

flight 8774 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8774/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-xl-multivcpu 4 xen-install fail REGR. vs. 8763 test-amd64-i386-pv 4 xen-install fail REGR. vs. 8763 test-amd64-i386-xl 4 xen-install fail REGR. vs. 8763

flight 6714 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/6714/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 6658 build-amd64 4 xen-build fail REGR. vs. 6658 build-i386-oldkern 4 xen-build fail REGR. vs. 6658

Hi All, Here is the test report for Xen-4.0.0-rc6(Xen C/S 21022). Our testing covers following features, like VT-x/VT-x2, VT-d, SR-IOV, Power Management, RAS, and TXT. There are 2 new RAS bugs exposed in this testing compared with RC5 testing. 2 bugs are fixed. VT-d/SR-IOV and TXT can work without major bug. Most bugs are in RAS side. Dom0 S3 cannot work on Gulftown-HEDT platform. We use latest

Hi, all This is the test report of Xen 4.1-rc7. There have no new bug and fixing. Now there are 11 bugs in total. Version info xen-changeset: changeset: 23007:cf66f6d8e41e pvops git: commit ea954f6ff4ff5c15c9e2120e86335f6d6490ae0f branch: xen/stable-2.6.32.x New issue(0) Fix issue(0) Old issues (11) 1.[ACPI] System cann''t resume

flight 8181 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8181/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail never pass test-amd64-i386-xl-multivcpu 15 guest-stop fail

flight 5665 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5665/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 5640 build-amd64 4 xen-build fail REGR. vs. 5640 build-i386-oldkern 4 xen-build fail REGR. vs. 5640

flight 8832 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8832/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail

Hi, I am working of Intel 82576 device to test the SRIOV functionality. I want to assign VFs to a VMs(domU) and verify the control and data path. I installed Xen-unstable with 2.6.30-rc3(dom0). But the SRIOV functionality isn''t working, because MSI is not supported. Please let me know, what version of Xen and dom0 supports above functionality? Is there any tool available to manage SRIOV

Hello, Hi have the same problem. How did you solve it? Thanks Nuno Fernandes On Wednesday 09 May 2007 16:25:09 Bjoern Metzdorf wrote: > Hello Mark, > > > How is this manifesting? Does the bladecentre just grumble at you, do > > you get garbage output or something else? > > No, it just display the standard message that there is no vga output > (blade may be offline

flight 14649 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/14649/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvops 2 host-install(2) broken REGR. vs. 14472 build-i386-pvops 2 host-install(2) broken REGR. vs. 14472

flight 5685 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5685/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-i386-xcpkern-i386-pv 5 xen-boot fail pass in 5680 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable:

Hi, http://xenbits.xensource.com/xen-unstable.hg?rev/aab9fbd6ffa0 from http://lists.xensource.com/archives/html/xen-devel/2008-07/msg00518.html restricts the CPUID masking feature to model 0x1d or model 0x17 with stepping >=4: if (!((model == 0x1d) || ((model == 0x17) && ((eax & 0xf) >= 4)))) { /* fail ... */ A Xeon E5520 which is supposed to