similar to: Data broken during FTP test

Hi All, I sent the patch to make blktap work with PV-on-HVM. I corrected the part that had been pointed out in the Xen community. ・All xvdN disk is looked like hdN. ・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.) We cannot use blktap for the volume of the system with PV-on-HVM and are embarrassed. Could you apply this patch? Or, please give the comment to me. Signed-off-by:

Hi All, We tested with Japanese keyboard. Then, the local keys that was not able to be input with a Japanese keyboard was found. This patch added the key that was not able to be input to the keymap. The key that cannot be input is as follows. ・Katakana ・Eisu_Toggle Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com> Signed-off-by: Junko Ichino

Hi All, My name is Takanori Kasai. This is a first time to send mail. I found the key that was not able to be input to HVM Domain (VTx and VTi Domain) through VNC Server with Japanese keyboard. I think that it is a cause by lack of some keys in Japanese keymap and the key symbol table in qemu-dm. This patch is addition of the keys for Japanese keyboard. My best regards. - Takanori Kasai

Hi All, It is natural that there is quit command in original QEMU. However, I don''t think that the HVM domain on Xen is necessary. Because there is a possibility of shutting down GuestOS due to the mistake. I think that I should prohibit the quit command of qemu-dm. Thanks -- Takanori Kasai _______________________________________________ Xen-devel mailing list

Hi All, We contributed the problem when CD-ROM was changed as follows. There was especially no comment though we confirmed the correction method. Therefore, the patch that corrects these problems is contributed. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com> Best Regards, --- Takanori Kasai ----- Original Message ----- From: "Kasai Takanori"

Changeset 10742:3e07ec30c445 made it possible to switch to the QEMU monitor terminal when using the VNC display protocol. Unfortunately the VNC key handling is rather crazy, so even if you have the shift key pressed, a VNC client will send a lowercase letter, expecting the server to interpret the state of the shift key as desired. Normally in HVM guests, the guest OS does this interpretation

Hi All, We tested the xm block-attach/detach command. It repeats block-attach/detach command for DomU and pv-on-hvm on HVM Domain. (block-attach -> block-detach -> block-attach -> block-detach -> ...) The block-attach command failed when repeating 256 times. It is because the channel had not been freed in blkfront. Therefore, it remain using the event channel. This patch is

Hi All, The interface of the evtchn has been changed as follows. ・xen-unstable.hg : cs13198 [PV-ON-HVM] Update evtchn interface to match new PV Linux interfaces. ・xen-unstable.hg : cs13197 [LINUX] Extend the event-channel interfaces to provide helper methods However, the following errors occur if pv-on-hvm is done in insmod. This patch corrected this issue. --- # insmod xen-vbd.ko

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 all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Hi All, We tested the PV driver on HVM domain. When ten vif was defined in configuration file for VNIF, the HVM domain was not able to be created. ---------------------------------------------------------- # grep vif RHEL5GA_test.conf vif = [ ''mac=02:17:42:2f:01:11, bridge=xenbr0'', ''mac=02:17:42:2f:03:11, bridge=xenbr2'',

Hi All, I sent the patch to allow blktap to be able to booted as system bolume for PV-on-HVM. However, there was a problem that hdN and xvdN were not able to be specified at the same time. I made the patch to correct it as follows. - Whether hdN is defined first is checked. - If hdN is defined, xvdN is not replaced with hdN. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

Hi All, We tested with Japanese keyboard. The Windows keys had been converted by mistake. It is opposite between right and left. ・Super_R -> Super_L ・Super_L -> Super_R This patch corrected the keymap to convert it. Even if the keymap is not corrected, it is the same working. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com> Signed-off-by: Junko Ichino

Hi All, When xm block-detach command was done on PV-ON-HVM, the response of other disks was lost. It is because a wrong event channel was invalidated when detaching it. Not the evtchn number but the irq number is invalidated specifying it. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com> Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by:

Hello, it''s not the first time but ... Who know? Well, I use xen in HVM. All works fine, my keyboard in Dom0 is AZERTY, but this keyboard become QWERTY when i enter in VM, it''s not useful to type password. How can i keep my keyboard AZERTY in my VM and in Dom0? -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé

Hi, This patch adds more user registers to show them to xenctx for ia64. Tested domU/domVTi on ia64. Sample is the below. # ./xenctx 1 0 iip: e000000000000810 ipsr: 00001012087a6010 b0: a000000100068a70 b6: a00000010014ff60 b7: e000000000000800 cr_ifs: 800000000000050a ar_unat:

Hi all, I'm testing on debian/unstable SR-IOV feature with Broadcom BCM57810 cards and KVM hypervisor: Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 bnx2x -> firmware 7.8.17 -> driver from kernel 3.12.7 8 VFs are created on the first PF. For each VF, a specific mac address is set manually using "ip

Hi, I''m having problems using Xen (2.0.7 and 3.0.0) on newer IBM HS-20 blades, which uses Broadcom network card (tg3 kernel module). Here''s the relevant entry from lspci : 05:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) 05:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) If xend is

Matthias, Sorry I should have wrote more details. I agree with your message and I understand that template12 is not meant to be a share. What I tried to say is: when I have this configuration: [template12] writable = yes browsable = yes valid users = alex [alex] path = /home/alex copy = template12 I can see this error in /var/log/samba/log/smbd [2016/04/25 16:44:14.719192,

I''ve idendified the problem... description: problem in XEN bridged-network. Dom0 doesn''t respond at external network activity (DomUs may work correctly) problem: something related to Broadcom NetXtreme II menagement solution: follow all this instructions: http://article.gmane.org/gmane.linux.hardware.dell.poweredge/23276 bye, s.