similar to: pass-though Intel gpu int o a vm

Displaying 20 results from an estimated 10000 matches similar to: "pass-though Intel gpu int o a vm"

2020 Aug 12
2
Re: pass-though Intel gpu int o a vm
Greetings Erik, > Sent: Tuesday, August 11, 2020 at 10:11 AM > From: "Erik Skultety" <eskultet@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: pass-though Intel gpu int o a vm > > On Sat, Aug 08, 2020 at 06:44:26PM +0200, daggs wrote: > > Greetings, > > > > I have a server that run a vm
2020 Aug 12
1
Re: pass-though Intel gpu int o a vm
what is the proper uri to use? > Sent: Wednesday, August 12, 2020 at 7:23 PM > From: "Erik Skultety" <eskultet@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: pass-though Intel gpu int o a vm > > > > PS: You can even try assigning the GPU from within virt-manager which produces > > > the
2020 Aug 11
0
Re: pass-though Intel gpu int o a vm
On Sat, Aug 08, 2020 at 06:44:26PM +0200, daggs wrote: > Greetings, > > I have a server that run a vm with several nic pcie cards as pass-though. > the board has an intel gpu and the hdmi output is not used. > I thought of booting up another vm and pass the gpu into it. > I found several discussions on the subject stating that it isn't possible but all of them are several
2020 Jul 20
2
host and vm on isolated network, there is ip (via dhcp) but not ping
Greetings, I've setup an vm with openwrt in it, defined a isolated lan between the vm and the host and booted the vm up. I see the vm is up, made sure the vnic is visible in both the host and guest and added it to the br in the guest. I've issued an dhcpd call on the vnic (labeled vnic0) in the host and got an ip, see: dagg@NCC-5001D ~ $ dhcpcd vnet0 DUID
2020 Aug 12
0
Re: pass-though Intel gpu int o a vm
> > PS: You can even try assigning the GPU from within virt-manager which produces > > the right XML bits for libvirt. I've never tried assigning an integrated Intel > > GPU on my laptop (for obvious reasons), so I can't give you the kind of answer > > guaranteeing this would work 100%. > > > > > the system in question is a headless server so
2018 May 02
2
Re: connecting host and guest vm using a dummy nic
Greetings Laine, > Sent: Wednesday, May 02, 2018 at 5:56 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 05/01/2018 12:12 PM, daggs wrote: > > > > I want to see if I understood you correctly, I add: >
2018 May 01
2
Re: connecting host and guest vm using a dummy nic
Greetings Laine, > Sent: Tuesday, May 01, 2018 at 5:30 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 04/30/2018 03:16 PM, daggs wrote: > > Greetings Laine, > > > >> Sent: Monday, April 30,
2019 Jan 04
4
Re: script called from qemu hook freezes.
Greetings Peter, > Sent: Friday, January 04, 2019 at 4:47 PM > From: "Peter Krempa" <pkrempa@redhat.com> > To: daggs <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: [libvirt-users] script called from qemu hook freezes. > > On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs wrote: > > Greetings, > > > > I'm executing an
2020 Nov 17
2
image works in native but not in vm when cpu mode='host-passthrough' is set
Greetings. I have an image I've created with a bunch of chost flags which works on my machine when it comes to native boot. if I take that same image into a vm managed via libvirt, I get kernel panic. I'd assume that something is missing from my vm config, question is what and what I can do about it? here is the flags part of lscpu in native and vm: https://dpaste.com/3TR8QJ5G8 and the
2019 Dec 26
2
aarch64 vm doesn't boots
Greetings, I'm trying to bring up a alpine rpi aarch64 image within kvm but I'm ended up with a stuck system, here is the xml: <domain type='qemu'> <name>alpine_rpi4_dev_machine</name> <uuid>b1b155fc-cb92-4f22-8904-c934dd24415b</uuid> <memory unit='KiB'>4194304</memory> <currentMemory
2018 May 02
2
Re: connecting host and guest vm using a dummy nic
Greetings Laine, > Sent: Wednesday, May 02, 2018 at 8:09 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 05/02/2018 12:05 PM, daggs wrote: > > Greetings Laine, > > > >> Sent: Wednesday, May 02,
2018 Dec 10
2
unable to add pci network to existing vm
Greetings, I'm trying to add a virtual nic to an existing and active vm and I'm getting this error: error: internal error: No more available PCI slots the cmd I'm trying to run is: virsh -c qemu:///system attach-interface --domain router --type bridge --source virbr0 --model virtio --config --live the lspci output within the vm is this: # lspci 00:00.0 Host bridge: Intel Corporation
2020 Oct 14
2
scsi passthrough differs between guests
Greetings, I have two machines running the same distro, both running qemu 5.1.0, one runs libvirt 6.7.0, the other 6.8.0. I've decided to test the viability of passing through my sata cdrom into a vm, so I went to the libvirt docs, read a bit and added the following to a debian10 uefi vm running on libvirt 6.8.0: <controller type='scsi' index='0'
2018 May 05
1
Re: changing pci addr of SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
Greetings Jano, > Sent: Thursday, May 03, 2018 at 1:44 PM > From: "Ján Tomko" <jtomko@redhat.com> > To: daggs <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: [libvirt-users] changing pci addr of SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) > > On Wed, May 02, 2018 at 07:29:23PM +0200, daggs wrote: > >Greetings,
2018 May 02
2
changing pci addr of SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
Greetings, when execute lspci inside my vm linux guest, I see this: :/# lspci | grep -i scsi 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) I don't see any such address in my xml file, is it possible to move that controller to another pci addr? Thanks, Dagg.
2018 Nov 05
2
usb post passthough stopped workng after kernel upgrade
Greetings, I have a vm on debian 9.5 to which I pass an specific usb from the host. here is the relevant part in the vm's xml file: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x148f'/> <product id='0x5572'/> </source> <address type='usb'
2020 Sep 04
2
network config not working on newer libvirt
Greetings, up until a year ago, I was running a server with Debian 10 (stable) on it with the latest versions of libvirt, qemu and kernel 4.19.x Debian 10 had to offer (both libvirt and qemu versions were really old). the network config was simple, one of the vm acted as a router and provided the ip for both the host and the vm. I've recently switched distro and now I'm running latest
2020 Sep 20
1
redirecting guest serial to file on the host
Greetings, I have a vm to which I can access using virsh console vm1/ I'd like in addition to be able to dump the serial of the vm in to a file on the host. I've found this https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sub-section-libvirt-dom-xml-devices-host-interface but it seems that the first second example which
2020 Jan 06
2
Re: aarch64 vm doesn't boots
Greetings Andrea, > Sent: Monday, January 06, 2020 at 11:37 AM > From: "Andrea Bolognani" <abologna@redhat.com> > To: daggs <daggs@gmx.com>, libvirt-users@redhat.com > Subject: Re: [libvirt-users] aarch64 vm doesn't boots > > On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > > Greetings, > > > > I'm trying to bring up a alpine rpi
2020 Oct 15
2
Re: scsi passthrough differs between guests
Greetings Peter, > Sent: Thursday, October 15, 2020 at 9:52 AM > From: "Peter Krempa" <pkrempa@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > Subject: Re: scsi passthrough differs between guests > > I don't see anything wrong with you configs. There were some changes