[qubes-users] Re: Again on vga passthrough
I was able to make further tests in the time available. the result did not go well, but some doubts came. Summary: QWT (working and correct resolution!) Ok UEFI boot OK stubdom-linux-rootfs.gz *(only Dom0 starts) KO* even with only Dom0 started and giving 12gb Ram the VM windows goes wrong. with the fix stubdom-linux-rootfs it only works for me Dom0, so I immediately restored it. _ I saw that the ATI Radeon card shares the IRQ 16 with these others: 00: 01.0 PCI bridge: Intel Corporation Xeon 00: 1a.0 USB controller: Intel Corporation 7 Series / C216 Chipset Family USB Enhanced Host Controller # 2 00: 1c.0 PCI bridge: Intel Corporation 7 Series / C216 Family PCI Express Root Port Chipset 1 But if I try to connect one or all the devices to the HVM, these (besides the vga radeon) I always get: ... has failed to start: internal error: PCI end devices can not be assigned to guest 1. I MUST also exclude these devices at startup in EFI.cfg ??? all devices that share the same interrupt ?? 2. in lspci -t (show bus tree) which means this representation ?? (*+ -01.0- [02-03] 00.0*) ?? sudo lspci -vt - [: 00] - + - 00.0 Intel Corporation 3rd Gen Core processor DRAM Controller + -01.0- [02-03] 00.0 Advanced Micro Devices, Inc. [AMD / ATI] Thames [Radeon HD 7550M / 7570M / 7650M] 3. is the kernel driver loaded on the card no good? (*Kernel modules: radeon) * 4. In the conclusions of the guide, where can I find more info to try with libvirt and libxl ?? "If it doesn’t work and you need to debug more things, you can go deeper. Virsh (start, define, ...) /etc/libvirt/libxl/ xl /etc/qubes/templates/libvirt/xen/by-name/ /usr/lib/xen/boot/ virsh -c xen:/// domxml-to-native xen-xm /etc/libvirt/libxl/..." *Thanks to those who want to explain these doubts.* sudo lspci -v -d 1002:6841 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] (prog-if 00 [VGA controller]) Flags: fast devsel, IRQ 16 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f7e2 (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at f7e0 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: pciback Kernel modules: radeon sudo lspci -vt -[:00]-+-00.0 Intel Corporation 3rd Gen Core processor DRAM Controller +-01.0-[02-03]00.0 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] +-02.0 Intel Corporation 3rd Gen Core processor Graphics Controller +-14.0 Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller +-16.0 Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 +-1a.0 Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 +-1b.0 Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller +-1c.0-[04]-- sudo lspci -vv 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=02, subordinate=03, sec-latency=0 I/O behind bridge: e000-efff [size=4K] Memory behind bridge: f7e0-f7ef [size=1M] Prefetchable memory behind bridge: e000-efff [ size=256M] Capabilities: [88] Subsystem: Dell Device 057e Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Kernel driver in use: pcieport 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 057e Flags: medium devsel, IRQ 16 Memory at f7f18000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: pciback Kernel modules: ehci_pci 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondar
Re: [qubes-users] Again on vga passthrough
Il giorno martedì 22 ottobre 2019 21:49:11 UTC+2, awokd ha scritto: > > Have you seen > > https://github.com/Qubes-Community/Contents/blob/master/docs/customization/windows-gaming-hvm.md? > > > Thanks awokd, you gave me more hours of tweaking and still a lot of hope. I didn't think QWT was necessary. The mystery of how to modify the configuration xml remains. See you soon for updates. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5c9646d1-cf98-4b65-b200-1855e1edc298%40googlegroups.com.
[qubes-users] Again on vga passthrough
Every three months for several years I spend a whole day trying to make the second video card work on my laptop. Some will say that it cannot work on laptops for several reasons, in particular because the consumer GPU does not support vitualization, because on a MUXed system (radeon 7570M) it is impossible to switch two video cards simultaneously on the same monitor, almost certainly will not even work on the external video output, because the ACPI call fails to load the firmware. I keep doing so many tests, I find out about dozens and dozens of sites, but I only make small steps forward. Now I can load Windows 7 without having the blue screen, I see the card in the device manager, but it seems to be off. (error code 43). I put all the options, even though they are probably useless. rd.qubes.hide_pci=02:00.0 modprobe=xen-pciback.passthrough=1 xen-pciback.permissive xen-pciback.hide=(02:00.0) kernelopts - iommu=soft swiotlb=16384 gfx_passthru True (qvm-features ??) But I don't understand why: 1. The windows 7 VM with the attached video card loads only with less than 4GB of RAM (otherwise it is blue screen) 2. I don't find in any way the possibility to edit the virtual machine configuration XML. 2.1 under "/ var / lib / qubes / appvms / WIN-7-2 /" the configuration file no longer exists. 2.2 I found the way to export the XML with virsh dumpxml, but with the qvm-start command there is no longer the "--custom-config" option 2.3 I force editing the XML from virsh edit (VM) in VIM, but then resume the values entered in qvm-features. 2.4 I can't change the amount of vram? (qvm-feature video-vram?) 3. the Windows guest video drive (both cirrus and vga) there is no monitor resolution (1366x768) Valid and working alternatives: spice? ovmf? dgpu on usb3? Dell precision 7000 series? I need windows only because there isn't a valid alternative to photoshop and other Adobe products, I don't find myself with gimp and krita. thanks bye -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a7a097c0-450c-4f01-b95b-12984b80251d%40googlegroups.com.
[qubes-users] further discussion on video resolution
Good evening, I can not set the resolution on HVM's in Qubes 3.2. Beyond the fact that I have a second GPU Radeon on the Dell laptop which I assume can not only use for Hvm in gpu/pci passthrough mode, considering it a utopia. (Trying to devote the second GPU in vm-manager/vm-setting/device get a machine crash) I made many tests, I do not seek prompt solution. For now I only have 2 HVM, a Windows 10 machine and a debian based distro. On Windows 10 I can choose different resolutions, even the largest, but 1366x768 is not present. On debian within only with the setting grub deprecated vga=792 to boot. Changes in terminal with Xandr give it full of artifacts screen, making it unusable (ctrl+F1 does not work). Commands vbeinfo and vbetest in grub console cause the crash. On debian based I had ssh server install when I had the screen unusable. Although fortunately so far the login screen is always accessible, so I can set the test resolutions of another user, if it is unusable can easily reset the configuration. I have read that there are still some problems, which might have already been fixed in version 4.0, and perhaps there is a great desire to operate the 3.2. IMPORTANT:I do not seek the possibility of having the fullscreen, I would just have the windows of Hvm the desired resolution. I did not expect to have all these problems only to change resolution, and I am conscious of not being a super user in linux. Maybe I could use VNC or similar software, but in addition to not be safe to customize the resolution should install the client in dom0, otherwise I would have another vm and therefore use of resources and opening firewall ports. On Windows 10 only needed xen video drive that accepts the 1366x768 resolution On Debian based disto I read that with xfce would solve the problems. Thanks for your help. good things -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fe804fec-fa8c-46f4-ab08-86251c7dc939%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Linux StandaloneVM - Problems with X
Il giorno sabato 11 febbraio 2017 22:47:32 UTC+1, adoni...@gmail.com ha scritto: > I've "fixed it" by modifying the GDM config file and setting it to > automatically login without entering credentials. > > Not entirely happy tho, this won't create a xorg.conf file, and when I try to > generate 1 with X -configure :1 I get an error saying it failed as number of > created screens do not match number of detected devices. This means I'm stuck > with 640x480 for now... > > Any ideas are appreciated! hello, I too have problems to change resolution. Kali has by default a strange resolution, even to me by a gray bar below. I tried changing resolution with xrandr but without results, I always found myself with the screen unusable and unable to gain access to the keyboard commands in the guest os. If you can still help, I can at least access to 800x600 putting this command at startup (E key) in Grub (instead of quiet) put vga=792. You can also put this persistent setting in the Grub configuration file, but maybe it would be better to use the new command gfxpayload=resolution. For Windows 10 instead I can not set the 1366x768 resolution, other resolutions work. I think it is the fault of the Xen drive. I hope someone help both. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e96e08ad-86d4-482b-9e1c-6ee9429cc7b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] AttributeError: 'Qstring' from qubes-manager updated to 3.2.7-1
> Until this is fixed, you can always downgrade to the previous version. > 'dnf downgrade qubes-manager-3.2.6' would do it, I think. > > Or you could download the package from yum.qubes-os.org, and install it > using 'dnf downgrade blah.rpm' Thanks Unman, I downloaded manually from your link and now works again. dnf downgrade did not find the package, do not know why. the important thing is that it works now. I let the discussion open again for a short time, maybe someone will tell us how to fix this error the last version. Thanks again. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/68c89cd9-cb0b-45f2-a611-a5972f8ba925%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] AttributeError: 'Qstring' from qubes-manager updated to 3.2.7-1
Hello guys,
after the qubes-manager update to 3.2.7-1 I get an error that prevents me from
access to configure the VM's. I tried to do a downgrade of the package at
3.2.6-1 but it tells me that I have the first version and can not install the
previous one. Now I admit my stupidity and a nice quota of bad luck, but I
think that the previous version of qubes-manager has been cleared by the new
installation.
I had just finished installing Windows 10 and was looking for how to set a
resolution of 1366x768 that is not present, before trying anxiously to install
the secondary video adapter with PCI passtrought. But apparently I'm unable to.
This is error:
AttributeError: 'Qstring' object has no attribute ' format'
line: self.setWindowTitle(self.tr("Settings: {vm}").format(vm=self.vm.name))
func: __init__
line no.: 57
file: /usr/lib64/python2.7/site-packages/qubesmanager/settings.py
line: "basic")
func: action_settings_triggered
line no.: 1384
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
Thanks for your patience
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/2828bb40-a529-4908-a958-265d33418fee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Image on secondary disk, it's possible?
I thank you all, I thought I had trawled through all the documents, and yet it was not so. There remains the question of how it can attach images or physical disks rather than symbolic links. If you can then use physical disks to install or load the guest systems. I did not find the command to install from USB devices: qvm-start NewOS --hdd =? or --hardisk =? Since I can not attach USB devices to Dom0, how do I start the installation from USB? A greeting -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3746990f-6760-4cdf-88e7-ae8d59b9684d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Image on secondary disk, it's possible?
Hello to all, I'm using with happiness for a month the latest release of qubesOS, I'd like to know: 1. I have created several virtual disk (vmdk-to-img or new both with DD and with mkfs) to be attached to a StandaloneVM. [For now, Qubes is installed on a 30GB SSD in the laptop, I had not read the specifications with automatic partition so much occupied space. I honestly do not understand why a hypervisor occupies so much space, but soon I will turn the disk with a larger one. The problem (in addition to money) is that the ssd is a Msata that I would not be replaced by a more capacious because I knew that Msata quite warm, so as soon as possible'll take one Sata] I would install MS Windows on a virtual disk that I created on the secondary disk, this I attached a StandaloneVM. Unfortunately the installation fails in any way. But I doubt that he had done something wrong in creating the virtual disk. I would like to know if I can install Windows on a virtual disk on the second disc? 2. In general I would like to know if you can install or run the OS on images on the secondary disk or as an alternative to a secondary physical disk (SATA or USB)? 3. On some Linux distributions install or even in Live mode, just imposed the native resolution of the primary display the video freezes. I have not found the Xrandr option to count down to return to the initial setting. In addition, for example, I can not set the full screen on installing Windows OS. There's a reason for this? Thank you ;=) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f153dcb2-bf80-4289-93fc-16abb4dac8a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
