similar to: Xen 3.2 and Big Real Mode support?

Hi Jan Beulich, > changeset 15414: 3cf5052ba5e5 x86: machine check exception handling With the c/s, when creating HVM guest, I can only see a white Qemu window. :( Can you have a look? Thanks. PS: the serial log follows: (XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f2000000 (XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c101 (XEN) HVM1: pci dev 03:0 bar 14 size 01000000:

Hi all don''t get such envionment to try now. so ask for help here. imagine that two os installed. Xen3.1 + Linux is installed in /dev/hda and windows xp is installed in /dev/hdb I don''t want to reboot to use windows. Is it possiable to boot the hdb windows in xen? i saw there are some threads about P2V in this mail list. will the P2V tools help? thanks

Hi all don''t get such envionment to try now. so ask for help here. imagine that two os installed. Xen3.1 + Linux is installed in /dev/hda and windows xp is installed in /dev/hdb I don''t want to reboot to use windows. Is it possiable to boot the hdb windows in xen? i saw there are some threads about P2V in this mail list. will the P2V tools help? thanks

Hello, I can''t load the network in unprivileged domain with xen-unstable (Changset 8612). Xen boots fine and domain0 is OK. When I start a new domain I have the following report when booting: ----------------B<----------------------------- * Not running depmod because /lib/modules/2.6.12.6-xenU/ is not writeable. Loading modules... All modules loaded. FATAL: Could not load

Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > "Daniel P. Berrange" <berrange@redhat.com> a écrit : >> If you have new enough libvirt and Xen >= 4.2 then libvirt will >> automatically >> use the libxl APIs instead of XenD. I have compiled a version 1.1.2 (with xapi and xl support) and installed it in /usr/local. I started the

On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote: > Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > > >According to [1] it seems that libvirt is using Xend daemon to communicate. > > After reading more documentation it seems that Xend is mandatory. As > everything is not up to date I'd like to know if it is still the > case or

Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) :

Like others on this list I am trying to employ the VTD-NEO patches in Xen 3.2 unstable to assign the internal graphics device to Dom1/Vista. I have removed the Cirrus Logic emulated device from qemu and replaced the Cirrus Logic vgabios with the the actual vgabios from my GPU. However I am hitting an xen assert and was hoping someone might be able to point me in the right direction. Below

Hello, I''m trying to use the VT technology on box but when I start Xen VMX is disabled by Feature Control MSR as shown in the following message: Xen version 3.0.2-3 (guill@frec.bull.fr) (gcc version 3.3.5 (Debian 1:3.3.5-13)) Wed May 31 16:07:00 CEST 2006 Latest ChangeSet: Tue May 30 18:14:05 2006 +0100 9697:18e8e613deb9 ... (XEN) Initializing CPU#0 (XEN) Detected 3391.682 MHz

Hello, I'm trying to install and use libvirt 1.0.4 on an Ubuntu 12.04.2. I compiled libvirt by doing: $ ./configure --with-selinux=no --with-gnutls $ make $ sudo make install Everything works fine and are installed under /usr/local Then I started the libvirtd manually and try to start a linux container that has the following configuration: $ virsh -c lxc:/// dumpxml lxcvm1 <domain

Hi, Keir, This patch is to fix the problem of Linux guest installation failure and Windows 2000 boot failure.       In the early code, we use vmx_vmexit_handler() -> vmx_io_instruction() function to emulate I/O instructions. But now, we use vmx_vmexit_handler() -> handle_mmio -> hvm_emulate_one() -> x86_emulate() to emulate I/O instructions. Also nowadays, the realmode

All, in the light of erratum #573 I''m wondering if we need to tweak or conditionally suppress fsincos emulation. The question is whether there is any possibility for getting the emulator to hit this instruction on AMD (as no real mode emulation ought to be taking place there), i.e. whether there are places where emulation gets continued eagerly in anticipation of the need for emulation

I was trying to install Ubuntu 7.10 on an HVM domain, when when the install kept hanging at a particular point. xm dmesg shows the following : (XEN) realmode.c:132:d28 Failed to emulate insn. (XEN) realmode.c:174:d28 Real-mode emulation failed @ 0000:00007f34: 0f 2c 06 08 6b 04 (XEN) domain_crash called from realmode.c:175 (XEN) Domain 28 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.4-unstable

Thank you. I notice the system then jumps to F000:FFF0 to execute. But because VMX is turned on, switching to real-mode would incur problems? I don’t find any clue to turn on the vm86 mode as Readme in the tools/firmware directory puts. Best regards, Hu Jia Yi Ext: 20430 Tel: 65-67510430 -----Original Message----- From: Cui, Dexuan [mailto:dexuan.cui@intel.com] Sent: Thursday,

Trivial change to emulate CLTS instruction in vmxassist. Relevant file - tools/firmware/vmxassist/vm86.c Signed-off-by: Kamala Narasimhan <kamala.narasimhan@citrix.com> Kamala _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I can''t find network device in domU. Debian domU shows Configuring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device and Fedora domU shows: eth0: unknown interface: No such device Dom0 is using Fedora with: kernel-xen-guest.i686 2.6.15-1.29_FC5 installed kernel-xen-hypervisor.i686

This patch adds a number of fp instructions needed for OS/2 to boot as a HVM guest on Intel/VT hardware. It appears to work fine, and OS/2 is now finally working on Intel/VT as well as AMD/SVM. I''m a little concerned about the "correctness" of the FSTSW emulation and the use of inline assembly directly using the corresponding ops for emulation. Wrt FSTSW, it is really two ops

Hi, xencomm is the ppc infrastructure to do hypercalls with guest physical addresses instead of virtual address. Because ia64 should also use physicall address, I think it''s better to re-use the ppc code and to put into common code. I''d propose to submit this patch is every part is OK (ie no NAK). This patch creates include/xen/xencomm_access.h which is to be included by

I am having reports of PCI passthrough problems with SR-IOV, in particular it looks like we are hitting the warning at msi:635 and msi:648 in xen; see the following log: (XEN) [VT-D]iommu.c:1785: VT-d page table not sharing with EPT table xenbus dev backend/vbd/1/5696 error 6 opening device (XEN) PCI add Virtual Function 04:1a.0 (XEN) HVM1: HVM Loader (XEN) HVM1: Detected Xen v4.1.0.rc2.pre (XEN)

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list