similar to: [PATCH] qemu-dm monitor doesn''t support the quit command

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, 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, 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, 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"

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

Hi all, Currently we have severe problem and are struggling to investigate it. The problem is data broken. Reproduce pocess is following, 0. test FTP function between guest domain and FTP client(other PC). 1. put data from FTP client to guest domain. 2. get data from guest domain to FTP client. 3. compare put data and get data on FTP client. 4. repeat process from step1 to step3.

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 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

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, I have a question about memory page tables in Xen. As far as I understood, every modification to page table will go through Xen(hypervisor). Is it so that all page tables are actually allocated in Xen(hypervisor) instead of guest OS(domain)? Also, is it the case that Xen(hypervisor) needs to maintain a page table for each process running in every domain? Thanks Haifeng

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: I''ve confronted one of my HVM domain frequently crash due to qemu-dm quit abnormally. Xend.log [2011-05-18 14:32:44 24651 1301875008] INFO (XendDomain:1259) Domain 322-2.vhd (2645) unpaused. [2011-05-18 14:38:26 24651 1201162560] WARNING (image:552) domain 322-2.vhd: device model failure: pid 8637: died due to signal 7; see /var/log/xen/qemu-dm-322-2.vhd.log [2011-05-18

Hi all, I''m not sure what qemu-dm does or how to debug its high CPU usage. Any one mind giving me a clue? - Brian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

RHEL 4's mkinitrd will fail to recognise that root is on LVM when running on a recent kernel/udev due to changes in naming. This patch detects LVM root for RHEL 4, and uses a dirty hack to frig mkinitrd if required. Fixes RHBZ#580461 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 21 +++++++++++++++++++-- 1 files changed, 19 insertions(+), 2 deletions(-) diff --git

Hi. I can''t use the vnc option (VNC=1 in my xmexample.hvm file), when I use RedHat or Fedora on 64 bits. The qemu log, say /usr/lib64/xen/bin/qemu-dm: invalid option -- ''-vncconnect'' But when I use RedHat or Fedora 32 bits, works fine. There is a problem or incompatibility in the 64 bits Xen kernel and the VNC option ? Best regards Luis

I tried using http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-3.4/xen-qemu-dm-3.4_3.4.2-1_amd64.deb But my hvm instance wouldn't start. I got this in the qemu-dm log domid: 22 qemu: the number of cpus is 2 Watching /local/domain/0/device-model/22/logdirty/next-active Watching /local/domain/0/device-model/22/command char device redirected to /dev/pts/0

Hi, Sorry, I should not have removed infomation on xend. image.py, line 399, in configVNC config.remove([''vncpasswd'', vncpasswd_vmconfig]) When vncpasswd is removed, qemu-dm cannot be started in reboot of hvm domain. Because necessary information disappears. It cannot be helped though information in config list remains in xenstore. This patch corrects above. Regards,

Package: xcp-xapi Version: 1.3.2-14 Severity: important I imported a HVM from a legacy xm environment. It is attached to one vif, the xenapi management vif It fails to start: # xe vm-start uuid=f2ba4767-7b4f-b416-3da6-3fe059ebfc37 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: device model

hi, I want to pass through "01:00.0",declared as pci=['01:00.0'] in cfg file. but found error log "pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log In fact, /dev/xen/pci_iomul does not exist. So where /dev/xen/pci_iomul implemented ? I have searched xen and linux code,

Hi all, we are running two servers with Ubuntu 8.04 LTS Server with Xen 3.2 and two dual-core CPUs: processor : {0-3} vendor_id : AuthenticAMD cpu family : 15 model : 65 model name : Dual-Core AMD Opteron(tm) Processor 2218 HE stepping : 3 cpu MHz : 2613.394 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu :