similar to: Destroying device model, Xen 4 Windows 2008 domU problem.

Dear All, am new to xen and recently implemented it. i had some issues initially but googling arround and some wise replies from you guys out there managed to clear them. now I have 2 virtual machines on my xen domains one is windows 2003 and other windows2008 both the virtual machines were working fine for about a week jus 2 days back we had a change in our network . i mean we rearanged the

Hi, I''m new to Xen and I''ve set up a few domUs using Debian (I suspect there may be a problem there, see at end). To begin with everything worked OK, I rebooted domUs without any problems, but twice now when I try when I try to restart or shutdown a domain, the xm command locks up. # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information

Hi, I''m using the xen-3.4-unstable version with Debian Lenny. Next to that I use a HVM Guest. The error message from the Xend.log is: 2009-02-26 14:44:15 2325] INFO (XendDomain:1180) Domain ExampleHVMDomain (35) unpaused. [2009-02-26 14:44:15 2325] INFO (XendDomainInfo:1781) Domain has shutdown: name=ExampleHVMDomain id=35 reason=poweroff. [2009-02-26 14:44:15 2325] DEBUG

Hi I m trying to install a full virtualized guest on my dell poweredge 1950 with centos 5.1 64 bits. I just launched the following command virt-install -n elaphe -r 4096 -f /var/lib/xen/images/elaphe -s 40 -b vlanbr15 --hvm Would you like to enable graphics support? (yes or no) yes What is the virtual CD image, CD device or install location? /var/lib/xen/F-7-i386-DVD.iso Starting

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

Hello, I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the following versions... ii libc6-xen:i386 2.13-38 i386 Embedded GNU C Library: Shared libraries [Xen version] ii libxen-4.1 4.1.4-3+deb7u1 i386 Public libs for Xen ii libxenstore3.0 4.1.4-3+deb7u1 i386

Hi, How do I view the libvirt virsh domxml-to-native function implementation? I think this function contains some error. Because we use libvirt to manage some host and vms on vmware hypervisor. We use openenbula generate a template for libvirt ,such as my attachment windows2008.xml. but when i use domxml-to-native to convert xml file to vmware config file vmx as below. This may not be

I get the error while starting hvm doms. Any workarounds... suggestions.. Thanks /Jd Some thiings that might be useful are cut-pasted below. ifconfig -a udevmonitor output (as suggested in prev posts) qemu-dm log xend.log xend-debug does not seem to have anything interesting. ifconfig -a =========== eth0 Link encap:Ethernet HWaddr 00:0F:EA:53:5C:79 inet addr:192.168.12.103

Hallo, I have an installed Windows 7 on one partition and running Debain Squeeze on the other. Both are 64 bit. I want to use Xen to run Windows as virtual guest from a physical disk. Once I get this working the Window will never be booted directly. When I try to create the virtual machine by "xm create -c win.xen" it hangs. The versions I use Xen 4.0.1-4 Kernel 2.6.32-5-xen-amd64

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-1 Severity: normal File: xen Tags: sid I can't start new domain. xend logs writes [2011-08-04 14:24:29 1905] INFO (XendDomainInfo:169) Recreating domain 18394, UUID 879e3aba-7d21-4767-80e9-851c562ee8e6. at /local/domain/18394 [2011-08-04 14:24:29 1905] INFO (XendDomainInfo:2078) Domain has shutdown: name=windows_2008 id=18394 reason=reboot.

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains

I''ve been using Xen strictly for PV for a while now, but I recently upgraded to hardware capable of HVM domUs. I''m trying to get a really basic HVM instance going so I can get my hands around making them work, in anticipation of using one to run a BSD to act as a firewall for other domUs on the machine. (I like PF.) Also, I might need run windows at some point, I suppose.

Hi, We have upgrade samba from 3.6.23-36 to 4.6.4, but we got "*Logon Failure Unknown user name or bad password*" error while trying to access samba form window 2003. And we use usename and password to login, not by the AD. We also test on windows2008 windows2008-R2 window7 windows10, it works. Thanks. Lifeng Ren

After changeset 18030 and 18064 were checked in, I found some issues when creating HVM domains with devices assigned: In XendDomainInfo.py, we have the call trace: the global function create() => vm.start() => _constructDomain(). In _constructDomain(), we invoke xc.test_assign_device() and when the function fails (maybe because iommu=1 is not specified in grub entry since iommu is 0 by

delete xend entry when destroying pv usb host controller of a guest os which has no pv-frontend driver loaded. -James (Song Wei) Signed-off-by: James (Song Wei) <jsong@novell.com> diff -r f42ff98a2cdc tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Thu Mar 25 09:32:21 2010 +0000 +++ b/tools/python/xen/xend/XendDomainInfo.py Fri Mar 26 13:27:25

Hi All, Please help me. I am now installing the XEN on my PC and trying to config the pci pass through. My motherboard is intel DQ45CB which is vtd enabled. I downloaded the latest xen4.0 source from xen.org which is the latest release. I downloaded stable-2.6.32-x dom0 kernel source from jeremy''s repository. After compiling the xen and dom0 kernel, I could play it. I could create

Hi All, Please help me. I am now installing the XEN on my PC and trying to config the pci pass through. My motherboard is intel DQ45CB which is vtd enabled. I downloaded the latest xen4.0 source from xen.org which is the latest release. I downloaded stable-2.6.32-x dom0 kernel source from jeremy''s repository. After compiling the xen and dom0 kernel, I could play it. I could create

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

Hello, on my xen host, Debian 5.0 I have few domU''s running, most of them are Lenny''s, a couple is running at Etch (Debian 4.0). All domU''s are running stable except of one (Etch / Debian 4.0). This one crashes almost daily and I wasn''t able figure out the reason why. Inside the domU there is nothing installed except of base system and Zimbra ZCS 5.0 and its