similar to: Bug#428685: kernel bugs when running xen in HVM mode

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

Processing commands for control at bugs.debian.org: > reassign 428685 xen-ioemu-3.0.3-1 Bug#428685: kernel bugs when running xen in HVM mode Warning: Unknown package 'xen' Bug reassigned from package `xen' to `xen-ioemu-3.0.3-1'. > Debian Bug Tracking System wrote: Unknown command or malformed arguments to command. > > Thank you for the problem report you have sent

Hi, I''m kinda new to XEN stuff, and I''ve been trying to create a fully virtualized guest on CentOS 5.3 for almost 3 months and no luck yet. I approached this process through several methods, one with virt-install and creating config file manually. Following is what happens when I try to create a guest, and I have included qemu-dm and last part of xend.log logs below too.

Hi, im trying to attach another volume aka disk to win HVM, however it doesn''t seem to work: + xm block-attach win2008ss phy:/dev/zvol/dsk/pool1/win2008ss.dsk2 \ hdd:disk w 0 results in: elkner.sol ~ > + xm block-list win2008ss --long (0 (vbd (uuid 7cb8fadf-619d-dde6-bda9-dcc18023c7d5) (bootable 1) (devid 768) (driver paravirtualised)

Hi, I have a running LVM-DRBD-Xen-HVM/Win2k3 cluster-stack under debian/ lenny managed by heartbeat/crm. At takeover/failover heartbeat first is stopping my HVM-domU with success apparently: -------------- corresponding heartbeat log line ----------------- greatmama-n2 lrmd: [3382]: info: RA output: (xendom_infra_win:stop:stdout) Domain infra-win2003sbs terminated All domains terminated

Hi, I cannot boot Windows XP domU on SXCE104 dom0. It was running for weeks.. Is it a known bug? # virsh start wxpp01 & # virsh dumpxml wxpp01 <domain type=''xen'' id=''-1''> <name>wxpp01</name> <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> <os> <type>hvm</type>

Hello I am trying to boot/install VM on XenClient. I would like to learn the way to install VM. Please teach the example of the operation and config file. (Especially, configuration file of method of displaying screen.) thanks. ========================================= [My Executed History] (1) I made a config file for VM(Windows XP:below). (2) I executed the following commands. # xenvm

Hello. Im trying to get hvm running on my amd64 am2 socket 2gb ram. 1st it as a Debian amd64 etch. 2st xen 3.0.3-2 debian build (more configs below) 3st acpi=1 apic=1 Problem is I can install winXP but after reboot i get black screen. If i press F8 i get menu of XP but can''t select anything ->frozen again If i try acpi=0 apic=0 and install XP it freezes before it XP boots

Hello, I'm wondering if anyone out there is doing tap:aio disk devices on a Xen HVM vm with any success. Please let me know if you are, and perhaps your version info and a config file snippet. I've posted this to the xen-users list, and what I'm trying to do seems to be correct, works on Ubuntu, Debian, and XenSource; but it doesn't work on CentOS. Here's the snippet from my

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Dear,Beg for your help. I am really puzzled with this problem.HVM domain can not boot up with Qcow incremental image(using command: qcow-create size incremental_file original_Qcow_img_file), but it can boot up with the original Qcow disk image file. When using Qcow incremental image, the guest qemu window would disappear before loading grub, and `xm list` can not find this guest domain.The VM

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

Package: xen-utils-3.2-1 Version: 3.2.1-2 If I try to create an HVM domain I get the following error message: araminta:~# xm create -c heceptor.cfg Using config file "/etc/xen/heceptor.cfg". Error: Creating domain failed: name=heceptor xend-log has a Python backtrace in it: [2009-03-21 14:14:46 25927] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name',

Hi, I am running Xen 3.1 on Ubuntu Gutsy, AMD64 distro. When I try to migrate a Windows XP domain, the domain migrates, but does not get restored in the destination node. The block device is provided by open-iscsi/iet and is accessible from both nodes. Below are logs from both source and destination nodes: Please throw some light on where the problem could be: TIA, Regards, -- Shuveb Hussain.

Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =

Anybody out there running Windows XP, Windows XP SP2 or Windows 2003 server with the default XEN 3.0.3 on Ubuntu Feisty ? Have Ubuntu Feisty Dom0 with a number of Ubuntu 6.1/7.04, Debian and FC6 DomUs all working lovely. But it will not work for any windows versions. The install gets as far as the blue "Setup is Starting Windows" screen. Intel VT extensions are enabled and the F5 trick

>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang >Sent: 2006年9月12日 8:57 >To: xen-users@lists.xensource.com >Subject: [Xen-users] Help: Xen HVM Domain can ONLY support four hard >drivesat most??? > >Hi, > >I have 5 SATA hard drives and I want to expose all these five

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

the contexts are as follows, looking forward to your reply, thanks [1]enviromention : xen3.4.2+CentOS-5.5 [2]config file: xp.hvm, as follows _s_name = 'xp-101' _s_vnc_display = 5310 _s_vm_id = 101 _s_vm_mac = '00:16:3e:eb:ca:65' _s_memory = 512 _s_allow_destroy = False _s_use_vnc = True # -*- mode: python; -*-