similar to: VGA as vfio-pci and vnc server's blank/black display

I am trying QXL but similarly windows guest says device is not working. (haven't tried connect to spice yet) On 09/10/14 11:42, lejeczek wrote: > in case I wasn't clear I'll only add that that "Standard > VGA" in guest gets exclaimed ONLY when that second VGA is > passed through. > Otherwise it works and VNC display works too. > > On 08/10/14 15:15,

in case I wasn't clear I'll only add that that "Standard VGA" in guest gets exclaimed ONLY when that second VGA is passed through. Otherwise it works and VNC display works too. On 08/10/14 15:15, lejeczek wrote: > hi, > > I'm having a Radeon as vfio-pci, which seems to work > perfectly fine, but... > Qemu's model type='vga' gets

On 20/12/2018 15:33, mark wrote: > lejeczek via CentOS wrote: >> hi guys >> >> I wonder if any Centosian here have done something different than only >> contemplated using Fedora Server, actually worked on it in test/production >> envs. >> >> If here are some folks who have done it I want to ask if you deem it to >> be a viable option to put it on

hi everyone I realise this not exactly on topic, I'm hoping an expert or two could confirm that following is not caused somehow by samba: I try xfreerdp to connect to a Win10 which is a member of NT-style domain and it fails this way: [14:55:33:905] [8048:8055] [ERROR][com.freerdp.core.nla] - SPNEGO failed with NTSTATUS: 0xC0000017 [14:55:33:905] [8048:8055] [ERROR][com.freerdp.core] -

hi everybody by an assumption I expected VM guests to be shut down/off gracefully when the host is being powered down or rebooted, but this does not seem to be the case so I wonder.. Am I missing some libvirt components/packages ? Or my assumption is incorrect and guests have to be shutdown manually? it's all SL 7 and guest are M$ regards P.

I''d like to be able to use OpenGL on a remote Windows box (WS2012), so I''ve been experimenting with Xen for the past few days. Most of the work-throughs for 3D acceleration with Windows that people post/blog are for local machines, that is the display is shown on the local screen. Is it possible to forward accelerated video through VNC or RDP with Xen? Thanks, --steve

hi guys I wonder if any Centosian here have done something different than only contemplated using Fedora Server, actually worked on it in test/production envs. If here are some folks who have done it I want to ask if you deem it to be a viable option to put it on at least portion of servers stack. Anybody? Many thanks, L.

I'm experimenting with using WinXP Xen guests as an alternative to upgrading workstations. The administrative advantages seem overwhelming. Please share thoughts about using VNC vs RDP for remote desktop connections. Please share any anecdotal information regarding user reactions and/or implementation issues.

hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device LXC guest which uses the same source network starts just fine. I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from centos-openstack-pike repo and

Hi all, Recentlly, I have installed a Windows 7 Enterprise kvm guest under a CentOS 5.4 kvm host (fully updated) using virtio drivers and all works ok except two things: sound and vga resolution. a) How can I increase vga resolution to 1440x900 or is not possible to configure more than 1024x768 when virt-manager is used?? b) I have assigned a sound device to this windows guest (ac97)

hi everybody a qemu-kvm guest gets 16 cpus and Windows in "Device Manager" sees all sixteeen but "Task Manager" shows only 4, the same "System" properties say "(4 processors)" I'd like to learn a bit about this - is it some sort of "resources management" on the libvirt/qemu causing this? And what does it do to a guest performance-wise

When using vfio, callers might want to know whether device is added to a regular group or an non-iommu group. Report this status from vfio_add_group_dev. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vfio/pci/vfio_pci.c | 2 +- drivers/vfio/platform/vfio_platform_common.c | 2 +- drivers/vfio/vfio.c | 5 ++++-

On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > Alex, > > I'm trying to think through how binding/unbinding of devices will > work with VFIO for platform devices and have a couple of questions > about how vfio-pci works. > > When you bind a device to vfio-pci, e.g.: > # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id > > ...I understand

On 2016?08?30? 10:27, Michael S. Tsirkin wrote: > Legacy virtio devices always bypassed an IOMMU, so using them with vfio was > never safe. And it actually won't work since GPA is assumed in the device. So I'm not sure this is must since we should get a IOMMU fault in this case. > This adds a quirk detecting these and disabling VFIO unless the > noiommu mode is used. At

On 2020/7/13 ??5:06, Michael S. Tsirkin wrote: > On Sun, Jul 12, 2020 at 10:49:21PM +0800, Zhu Lingshan wrote: >> We used to detect assigned device via VFIO manipulated device >> conters. This is less flexible consider VFIO is not the only >> interface for assigned device. vDPA devices has dedicated >> backed hardware as well. So this patch tries to detect >> the

On 14/02/18 15:26, Alex Williamson wrote: > On Wed, 14 Feb 2018 14:53:40 +0000 > Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote: > >> When enabling both VFIO and VIRTIO_IOMMU modules, automatically select >> VFIO_IOMMU_TYPE1 as well. >> >> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> >> --- >>

When enabling both VFIO and VIRTIO_IOMMU modules, automatically select VFIO_IOMMU_TYPE1 as well. Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> --- drivers/vfio/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig index c84333eb5eb5..65a1e691110c 100644 --- a/drivers/vfio/Kconfig +++

On Tue, Jul 14, 2020 at 08:52:43AM +0800, Zhu, Lingshan wrote: > > On 7/13/2020 6:52 PM, Michael S. Tsirkin wrote: > > On Mon, Jul 13, 2020 at 04:13:35PM +0800, Jason Wang wrote: > > On 2020/7/13 ??5:06, Michael S. Tsirkin wrote: > > On Sun, Jul 12, 2020 at 10:49:21PM +0800, Zhu Lingshan wrote: > > We used to detect

On Wed, 14 Feb 2018 14:53:40 +0000 Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote: > When enabling both VFIO and VIRTIO_IOMMU modules, automatically select > VFIO_IOMMU_TYPE1 as well. > > Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> > --- > drivers/vfio/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

On Wed, 14 Feb 2018 14:53:40 +0000 Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote: > When enabling both VFIO and VIRTIO_IOMMU modules, automatically select > VFIO_IOMMU_TYPE1 as well. > > Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com> > --- > drivers/vfio/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)