similar to: Re: txftrans.c:4498 -- TXF_HARD_ERROR

Apologies for missing Subject. On Wed, Jan 9, 2013 at 3:21 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > Hello List, > > Please help me in diagnosing below error in /var/log/messages > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: > fffff8800d099000 > > Im unable to find any google reference related to above C file or its > source

Hi everyone, We faced a dom0 crash on XCP1.1 and Xen 3.4.2. I''ve attached the log file for reference. On dom0 we could find only "Xc.Error" and then reboot of host. There is no information in /var/crash/ or other log files. Interestingly the "INTERNAL_ERROR" variable keeps growing until a length and then host reboots. Possible memory overlap ? Could someone please

Hi List, Please refer below email from Igor Kozhukhov. Illumos ( DilOS ) is back as dom0 for Xen. Give it a shot :) Both PV and HVM guests are working well. Illumos ( DilOS ) also works as PV guest with recent updates. You can send dilos related queries to dilos-dev@lists.illumos.org. Regards, Rushikesh -------- Original Message -------- Subject: [dilos-dev] DilOS 1.3.4 has been release

Hi List, I'm trying to work out the balloon driver on CentOS6 HVM but it seems to be not working with default 2.6.32 or newer 3.4 kernel. Does balloon driver work on HVM linux guests with Linux Kernel 3.4 from centos repo ? PV is fine and is able to balloon. My host is Xen 4.1.2 with dom0 as 3.4.46-8.el6.centos.alt.x86_64 My guest is CentOS6.4 with kernel 3.4.46-8.el6.centos.alt.x86_64

I apologize if this has been covered before. I have not seen a blow-by-blow installation guide for Ubuntu onto an iSCSI target. The install guides I have seen assume that you can make a target visible to all, which is a problem if you want multiple iSCSI installations on the same COMSTAR target. During install Ubuntu generates three random initiators and you have to deal with them to get things

I am confused, because I would have expected a 1-to-1 mapping, if you create an iscsi target on some system, you would have to specify which LUN it connects to. But that is not the case... I read the man pages for sbdadm, stmfadm, itadm, and iscsiadm. I read some online examples, where you first "sbdadm create-lu" which gives you a GUID for a specific device in the system, and then

I''m posting here as this seems to be a zfs issue. We also have an open ticket with Sun support and I''ve heard another large sun customer also is reporting this as an issue. Basic Problem: Create a zfs file system and set shareiscsi to on. On a vmware esx server discover that iscsi target. It shows up as 249 luns. When attempting to then add the storage esx server eventually

Hi, I could not find any option to set iSCSI initiator iqn while using guestfish, although the underlying qemu command has this option. It appears that each time guestfish tries to connect to iSCSI LUN, a randomly generated initiator iqn is being used. This is preventing guestfish to connect to the iSCSI target in our environment as the target allows incoming connection based on the preconfigured

Paul, > While testing iscsi targets exported from thumpers via 10GbE and > imported 10GbE on T2000s I am not seeing the throughput I expect, > and more importantly there is a tremendous amount of read IO > happending on a purely sequential write workload. (Note all systems > have Sun 10GbE cards and are running Nevada b65.) The read IO activity you are seeing is a direct

This add an iscsi initiator name setup option to the main menu in ovirt-config-setup and can also be accessed via ovirt-config-iscsi. Also accepts AUTO setup by running ovirt-config-iscsi AUTO and generates a random name as before --- Makefile.am | 1 + ovirt-node.spec.in | 3 ++ scripts/ovirt-config-boot | 4 --- scripts/ovirt-config-iscsi | 56

I just updated one of my virtual hosts to 5.6 and on rebooted I spotted an error about iscsi. Which surprised me, since I don't use iscsi. Yet there it is... % rpm -qf /etc/init.d/iscsi iscsi-initiator-utils-6.2.0.872-6.el5 And they're configured to start iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsid 0:off 1:off 2:off 3:on 4:on

> -----Original Message----- > From: Ian Pratt [mailto:Ian.Pratt@cl.cam.ac.uk] > Sent: 15 May 2004 09:59 > To: Kip Macy > Cc: Neugebauer, Rolf; Ian Pratt; Keir Fraser; xen- > devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk > Subject: Re: [Xen-devel] telnet xend > > > > I now have secondary domains up and running with iSCSI luns as the root > > device.

Hi All, I'm running KVM host on CentOS 5.6 x64, all of my guests are CO 5.6 x64 as well. I create / run VMs via libvirt. Here are the packages I have: # rpm -qa | egrep "kvm|virt" kvm-83-224.el5.centos python-virtinst-0.400.3-11.el5 kvm-qemu-img-83-224.el5.centos kmod-kvm-83-224.el5.centos libvirt-python-0.8.2-15.el5 etherboot-zroms-kvm-5.4.4-13.el5.centos libvirt-0.8.2-15.el5

Hi, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10

CentOS Errata and Bugfix Advisory 2016:1284 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1284.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8e44f277f695473fd93e4e46f507973bb20c14a3d690493b9d006969831f5a5b iscsi-initiator-utils-6.2.0.873-33.el7_2.1.i686.rpm

CentOS Errata and Bugfix Advisory 2016:1530 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1530.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 684e67a738b7dce51fd91736f404ec13e2816f48d8474478ac10336b93c03a0e iscsi-initiator-utils-6.2.0.873-33.el7_2.2.i686.rpm

Hello, I?m using ZFS to export some iscsi targets for the virtual box iscsi initiator. It works ok if I try to install the guest OS manually. However, I?d like to be able to import my already prepared guest os vdi images into the iscsi devices but I can?t figure out how to do it. Each time I tried, I cannot boot. It only works if I save the manually installed guest os and re-instate the same

Hello all. We recently purchased HP Proliant DL380 G7 server and also a HP Lefthand P4500 G2 24TB iSCSI box. The server itself has Quad Ethernet based on the BCM5709 Chipset from Broadcom (NetXtreme II). My main question is about iSCSI offload mechanism, as iSCSI itself is pretty new to me but I have gotten a good hold on it tho. I have managed to setup and configured our Lefthand box into

CentOS Errata and Bugfix Advisory 2016:1999 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1999.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 99e4b99cf132eac84807aea4eaaa2fb498b390a138ec89bc6a6342e3ae55546b iscsi-initiator-utils-6.2.0.873-22.el6_8.i686.rpm

CentOS Errata and Bugfix Advisory 2017:1725 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1725.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bb20f5019d41d5a7e53b75e8955288aa082ec9c50f924e762ccbe8a96623154b iscsi-initiator-utils-6.2.0.873-27.el6_9.i686.rpm