similar to: Guest Reboot After Plug HDMI

On Mon, Dec 04, 2017 at 04:02:33PM +0800, Lying wrote: > Hello, Everybody. I encounter a problem when i using my guest. > > I booting my guest without HDMI primarily, Then i add it, but my guest is be rebooted. > > > To know what cause it, i do it again, especially i check my guest is running normal or not with "ping" before plugging, that's well. > >

Yes, I can use guest with this way, But when i hot-add my graphics card , Guest will reboot. So i want to try it with <hostdev>. Somehow , If i use "hostdev" without xvga , my screen will be black. If we have no hostdev, do you have other methods can help me to use hot-plug my graphics card? At 2018-01-04 23:27:52, "Laine Stump" <laine@redhat.com> wrote:

Hello,my system info: virsh verison Compiled against library: libvirt 3.9.0 Using library: libvirt 3.9.0 Using API: QEMU 3.9.0 Running hypervisor: QEMU 2.10.90 And i want to pass through my gpu to my window 7 guest with <hostdev>, next line is comand i use: <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'>

Hello, friends. I encounter a problem when i use ivshmem with my guest, my ivshmem server is not start, and output a error : Example code, do not use in production ,cannot bind. Detail distribution: Today, I know ivshmem from a topic "QEMU version 2.10.93 User Documentation", Ivshmem: it can create a shared memory that guest device use, so we can use this memory to do something

On 12/20/2017 09:40 PM, Rogue S.T wrote: > Hello,my system info: >     virsh verison >     Compiled against library: libvirt 3.9.0 >     Using library: libvirt 3.9.0  >     Using API: QEMU 3.9.0 >     Running hypervisor: QEMU 2.10.90 > And i want to pass through my gpu to my window 7 guest with <hostdev>, > next line is comand i use: >      <hostdev

On Fri, Aug 24, 2018 at 11:42 PM, Peter Wu <peter at lekensteyn.nl> wrote: > Are these systems also affected through runtime power management? For > example: > > modprobe nouveau # should enable runtime PM > sleep 6 # wait for runtime suspend to kick in > lspci -s1: # runtime resume by reading PCI config space > > On laptops from

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.11.1-rc1 DAHDI-Tools-v2.11.1-rc1 dahdi-linux-complete-2.11.1-rc1+2.11.1-rc1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete Notable changes:

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.11.1-rc1 DAHDI-Tools-v2.11.1-rc1 dahdi-linux-complete-2.11.1-rc1+2.11.1-rc1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete Notable changes:

Hi, > update.packages(ask='graphics') gives me multiple warning (one per updated package?) similar to ... Warning: unable to move temporary installation '\\Server02\stats\R\library\2.10\file3de56e0d\locfit' to '\\Server02\stats\R\library\2.10\locfit' The final, updated, folders do not end up where they should be. I can move them 'by hand', but it is an

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.11.0-rc1 DAHDI-Tools-v2.11.0-rc1 dahdi-linux-complete-2.11.0-rc1+2.11.0-rc1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete * This release

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.11.0-rc1 DAHDI-Tools-v2.11.0-rc1 dahdi-linux-complete-2.11.0-rc1+2.11.0-rc1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete * This release

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.11.0 DAHDI-Tools-v2.11.0 dahdi-linux-complete-2.11.0+2.11.0 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete * This release adds automake

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.11.0 DAHDI-Tools-v2.11.0 dahdi-linux-complete-2.11.0+2.11.0 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete * This release adds automake

Full_Name: Manuel L?pez-Ib??ez Version: R version 2.6.2 (2008-02-08) OS: linux-gnu Submission from: (NULL) (164.15.10.156) This is only relevant for CPU intensive child processes. Otherwise, the problem is not obvious. Therefore, we need a CPU intensive program like this one: /************************************/ /*** Compile with: gcc -o timer-test -O0 timer-test.c -lm */ #include

On Tue, Aug 28, 2018 at 5:57 PM, Peter Wu <peter at lekensteyn.nl> wrote: > Only non-bridge devices can be passed to a guest, but perhaps logging > access to the emulated bridge is already sufficient. The Prefetchable > Base Upper 32 Bits register is at offset 0x28. > > In a trace where the Nvidia device is disabled/enabled via Device > Manager, I see writes on the enable

Thanks Ján! >What were the exact changes you were trying to make? I was following this guide: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Passing_keyboard/mouse_via_Evdev Specifically, I was updating the domain tag to include `xmlns:qemu=' http://libvirt.org/schemas/domain/qemu/1.0'` >both call virDomainDefineXMLFlags under the hood. That is good to know,

Hi, We are facing a suspend/resume problem with many different Asus laptop models (30+ products) with Intel chipsets (multiple generations) and nvidia GPUs (several different ones). Reproducers include: 1. Boot 2. Suspend/resume 3. Load nouveau driver 4. Start X 5. Observe slow X startup and many many errors in logs (primarily nouveau fifo faults) or 1. Boot 2. Load nouveau driver 3. Start X

Hello, I'm trying to migrate a working qemu command line configuration to libvirt. The part I'm currently failing on is: $ qemu-system-x86_64 -M Q35 ... -device vfio-pci,host=05:00.0,bus=pcie.0 The right way to translate this into libvirt XML seems to be using <hostdev>, but I seem to be unable to plug it into the pcie-root port This is how the interesting part looks like when

This may be user error, I am new to libvirt. I am using libvirt 5.0.0. I have created a VM (win10) in the system URI using virt-manager. I stopped the VM to edit it. I set my LIBVIRT_DEFAULT_URI="qemu:///system" and am able to read the domain configuration with `EDITOR=nano virsh edit win10`. When I save (ctrl+o) and exit (ctrl+x) I see the message "Domain win10 XML configuration

Am 19.11.2013 11:36, schrieb Laine Stump: > On 11/15/2013 03:35 PM, Thomas Kuther wrote: >> Hello, >> >> I'm trying to migrate a working qemu command line configuration to >> libvirt. >> The part I'm currently failing on is: >> >> $ qemu-system-x86_64 -M Q35 ... -device >> vfio-pci,host=05:00.0,bus=pcie.0 >> >> The right