similar to: VMX status report. Xen:25256 & Dom0:d93dc5c...

Displaying 20 results from an estimated 4000 matches similar to: "VMX status report. Xen:25256 & Dom0:d93dc5c..."

2019 Oct 22
2
C8 regression / tmp on tmpfs
Am 22.10.19 um 04:52 schrieb Orion Poplawski: > On 10/21/19 3:42 PM, Leon Fauster via CentOS wrote: >> Does someone have a working tmp on tmpfs via >> >> systemctl enable tmp.mount >> >> under CentOS8/RHEL8? This seems to work straight in EL7 ... >> >> >> # LANG=C systemctl enable tmp.mount >> The unit files have no installation config
2006 Jun 26
1
Cannot startup IA32/IA32pae VMX domain on IA32e platform
We cannot startup IA32/IA32pae unmodified linux guest OS. Booting 32bit VMX domain will stop at printing "ACPI: Unable to locate RSDP". Booting 32pae VMX domain will get a kernel panic. No abnormal info found in serial output. It''s interesting that sometime we can boot Windows 2003. Booting Windows SP1/SP2 Guest will crash with attached serial output. Bests Jeff
2012 Jun 26
1
[PATCH 2/2] document update in xl.cfg.pod.5 for 'stdvga=1' by default
document update in xl.cfg.pod.5 for ''stdvga=1'' by default Signed-off-by: Yongjie Ren <yongjie.ren@intel.com> diff -r b98feb4d6359 docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 Tue Jun 26 12:56:31 2012 +0800 +++ b/docs/man/xl.cfg.pod.5 Tue Jun 26 13:27:19 2012 +0800 @@ -718,9 +718,10 @@ =item B<stdvga=BOOLEAN> Select a standard VGA card with VBE (VESA BIOS
2007 Jul 19
6
Anyone succeeds HVM on latest x86-64 xen
I tried latest xen and linux-xen staging tree, but failed to run HVM domain on x86-64 environment. domU creation is OK. However the weird thing is not HVM domain itself. Instead system crashed on dom0 context. I saw once with some stack dump that xen''s page fault handler is executed on a dom0''s stack which then causes nested page fault due to unable to fetch vcpu pointer.
2019 Oct 21
2
C8 regression / tmp on tmpfs
Does someone have a working tmp on tmpfs via systemctl enable tmp.mount under CentOS8/RHEL8? This seems to work straight in EL7 ... # LANG=C systemctl enable tmp.mount The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible
2013 Jun 12
9
Test report for xen-unstable and qemu-xen
Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone
2007 May 14
1
Updating to Qemu 0.90 breaks save/restore
Save/restore is ok against staging tree''s changeset 15020: d2ef85c6bf84, but is NOT ok against changeset 15021: 00618037d37d (Update to qemu 0.90). I use IA32pae HV; both SMP Windows 2K3 and FC5 can''t be saved properly. After "xm save dom_id 1.save" returns, Qemu window disappears, but "xm vcpu-list" still shows the domain has not been killed. If I
2012 Sep 02
1
[PATCH] xl.cfg: videoram and stdvga documentation improvements
Hello, xl.cfg.pod.5 documentation tweaks/improvements: - videoram: Document that only qemu-xen-traditional device-model currently supports changing the amount of video memory for stdvga graphics device. - videoram: Better document the default amount of videoram for both stdvga and Cirrus. - stdvga: Add a note that stdvga allows bigger amount of videoram and bigger resolutions.
2015 Mar 26
2
[virtio-dev] Re: [PATCH] Add virtio gpu driver.
Hi, > I don't know. This seems exactly like the kind of thing > we had in mind when we added the virtio pci capability. > For example, we have text in spec that requires drivers > to skip unknown capabilities. > > And yes, if bios pokes at a specific bar then we do > need to list this info in the virtio spec so this makes > it an issue that is virtio related. Hmm,
2015 Mar 26
2
[virtio-dev] Re: [PATCH] Add virtio gpu driver.
Hi, > I don't know. This seems exactly like the kind of thing > we had in mind when we added the virtio pci capability. > For example, we have text in spec that requires drivers > to skip unknown capabilities. > > And yes, if bios pokes at a specific bar then we do > need to list this info in the virtio spec so this makes > it an issue that is virtio related. Hmm,
2018 Aug 21
2
Re: [PATCH 1/2] v2v: rhv-upload-plugin: Handle send send failures
On Tue, Aug 21, 2018 at 01:15:02AM +0300, Nir Soffer wrote: > The oVirt server may fail a PUT request before reading all request body. > However before closing the connection, it writes a detailed error > response, that will make debugging issues like expired tickets much > easier to handle. If we don't get the response and log the error, the > error may be lost when the daemon
2013 Sep 18
1
[PATCH] Allow 4 MB of video RAM for Cirrus graphics on traditional QEMU
Signed-off-by: Rob Hoes <rob.hoes@citrix.com> --- docs/man/xl.cfg.pod.5 | 18 +++++++------- tools/libxl/libxl_create.c | 57 ++++++++++++++++++++++++++++++++++---------- 2 files changed, 55 insertions(+), 20 deletions(-) diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 769767b..c18604d 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -1009,14
2013 Jan 17
4
[PATCH v4] tools/libxl: Improve videoram setting
2007 Dec 10
10
[PATCH] ioemu/qemu vga: save and restore vram buffer
The existing stdvga driver from xen-unstable tools/ioemu/hw/vga* does not save the emulated VGA memory contents. The symptoms include video malfunction after restore, including black screen (which can often be fixed by asking the guest to redraw) but also missing font setup etc. The attached patch fixes this by saving the entire VGA memory buffer, just like the Xen ioemu Cirrus emulator does. I
2018 Feb 12
2
[PATCH v3 1/2] drm/virtio: Add window server support
On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to
2018 Feb 12
2
[PATCH v3 1/2] drm/virtio: Add window server support
On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to
2008 Nov 14
9
Connect to Xen console
hi, I''m new on this list and i need help from experienced users to give andswer for some questions. I sen up a dom0 (debian) and would like it to be very minimalist, just xen tools, some gnu utils and other usefull utilities. This dom0 will be used to virtualize many hvm OS like windows and some other *nix paravirtualized. Till there are no problem to view/connect to console of paravirt
2013 Jul 25
11
Call for testing: OpenSSH-6.3
Hi, OpenSSH 6.3 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This release contains some substantial new features and a number of bugfixes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is
2012 Aug 06
1
Xen4.2-rc1 test result
Hi All, We did a round testing for Xen 4.2 RC1 (CS#25692) with Linux 3.4.7 dom0. We covered VT-d, SR-IOV, Power Management, TXT, IVB new features, HSW new features. We covered many cases for HVM guests (both Redhat Linux and MS Windows guest). We tested on Westmere-EP, SandyBridge-EP, IvyBridge desktop, and Haswell hardware platforms. We found no new issues, and verified 1 fixed bug. Fixed bug
2015 Mar 26
3
[virtio-dev] Re: [PATCH] Add virtio gpu driver.
Hi, > Absolutely, it's pretty common to mix regions in a BAR. > For example, we have virtio kick (ioeventfd backed, > handled in kernel) in same BAR as common and device > specific configuration. > We did the same thing you are now doing with the > virtio BAR, and now we have to maintain two code > bases, virtio pci config was designed to be future proof > so why not