similar to: VMX status daily report Nov. 3

We have test latest xen (ChangeSet 7646) on VT platform with Intel 915 chipset : The VMX can not be created for the known issue http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=388 <http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=382> But it is ok after adding xiaofeng''s patch. IA32: Build&Boot SMP xen0 without problem Can startup XenU with different

We have test latest xen on VT platform with Intel 915 chipset and Here is the test summary: IA32: Build&Boot SMP xen0 without problem Can startup unmodified 2.4/2.6 linux on VMX domain Can startup VMX & Xen with different configuration Part of LTP runs well in VMX domain(2.6) IA32E: Build&Boot SMP xen0 without problem Can startup unmodified 2.6 linux on

Hi all, I''m trying to get a pci card working on a guest os (ast01) on dum0 I hided the pci card w/: # modprobe pciback hide=''(0b:08.0)'' then added this line to the guest os config file (/etc/xen/ast01) pci = [ "0000:08:0e.0" ] Whenever I try to start it fails w/: # xm create ast01 Using config file "/etc/xen/ast01". Error: function takes exactly 4

I have problem to start domU with errors: # xm create -c x335-hien1-vm4.cfg Using config file "x335-hien1-vm4.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working in changeset: changeset: 7700:98bcd8fbd5e36662c10becdcd0222a22161bb2b6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Nov 8 09:48:42 2005 summary: Fix alloc_skb()

Hello I use xen and I am trying to use the parallel port of Centos 5.2 host from a Windows XP (HVM) guest. I have tried to transfer control of the port by blacklisting lp, parport and parport_pc + adding: ioports = [ "0378-037a" ] to the xen configuration file. However, in the presence of this line, xm create replies with: Error: function takes exactly 4 arguments (3

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

Hi, Hoping someone can help me with some question on Xen 3.x and Intel VT (Vanderpool) hardware. Can IBM OS/2 or Serenity Systems eComStation now be run with Xen and Intel Vanderpool enabled CPUs? If not, what is needed? Are any drivers needed? Do you know of anyone working on getting Xen to support OS/2 or eComStation? > Jan 21,2004, Mark A. Williamson wrote: > Afraid so. > With

We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. issues: - No bocking issues. IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain Can bootup unmodified IA-32 WindowsXP SP1/SP2 in VMX domain Can bootup VMX & XenU with different memory size(VMX:128MB,256MB,512MB.XenU:256MB)

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

Hello, I noticed a bug in Xen-4.1-3, which is also still present in xen+git. I know that the Python xend is deprecated, but I''m stuck with xen-4.1 until xen is usable with libvirt, so my patch might still be helpful for others. This is a follow-up to <http://lists.xen.org/archives/html/xen-users/2012-11/msg00069.html>, which still keeps me busy. /xen/xend/server/SrvDomain.py

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

Hi all, Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. [ 240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds. [ 240.172388]

We have tested the latest xen on VT platform with Intel 965/5000P chipset. Here is the test summary: Issues: ========================= 1). VBD could not work well Partial support is added in c/s 13198, but the loader still complains that symbol "irq_to_evtchn_port" is missing. 2). IA32E: IA32E vista can''t boot up normally, it gives a blue screen. Then the qemu window

Hi, I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux dom0. I''m using a file backed VBD. I used the iso image to first launch and install OpenSolaris into the file VBD. Once that process is complete, I''m trying to run it using the config file below: name = ''opensolaris'' vcpus = 1 memory = "512" vif =

We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. Issues: - IA-32 VMX guest will hang when booting on IA-32PAE host with acpi=1 and apic=1.(Bug 594) - Failed to created VMX after tens of VMXs have been created & destroyed on IA-32e.(Bug593) IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX

We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Cannot boot Windows 2000 - Only one CPU is detected in SMP dom0 - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: + Build&Boot UP xen0 without problem + Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain + Can bootup unmodified IA-32 WindowsXP SP1/SP2

I''ve compiled xen-3.0.2-2 from sources. I''ve went to the end without errors. The ./install.sh script have been created the /etc/grub.conf file as it : # initrd /boot/initrd-version.img #boot=/dev/hdc default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.15-1.2054_FC5) root (hd0,0) kernel

Hi, If `hda'' is used in a domain config file and domain-0 has /dev/hda, creating the domain failed by TypeError: File "//usr/lib/python/xen/xend/server/blkif.py", line 84, in getDeviceDetails (device_path, devid) = blkif.blkdev_name_to_number(dev) TypeError: unpack non-sequence Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> -- KUWAMURA