[Xen-devel] PV drivers 8.2.2. only testsigned?
Hi there, after downloading the drivers from https://xenproject.org/windows-pv-drivers/ I discovered that the 8.2.2. driverset is only testsigned - making it difficult to install and use them. I understand that signing is a complicated process and that development build drivers are always only testsigned - but the development build drivers are on the right side of the page and the 8.2.2. download is on the left. To me it seems to suggest "left side has release drivers with valid signing, right side has development builds with test signing" I just wanted to ask about any plans to release the 8.2.2. drivers with valid signing... or how the decision wether to sign or only to testsign is made... ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [...], USB-passthru only works with qemu-traditional
Hello, you're probably right about the malformed commandline for USB-passthru: With upstream qemu I get qemu-system-x86_64: -usbdevice tablet: '-usbdevice' is deprecated, please use '-device usb-...' instead qemu-system-x86_64: -usbdevice host:0d46:3003: '-usbdevice' is deprecated, please use '-device usb-...' instead qemu-system-x86_64: -usbdevice host:0d46:3003: could not add USB device 'host:0d46:3003' I'm not quite sure if this ever worked (without trad), but if it did, it was some years ago... perhaps at the times of xen 4.1 ? Am 06.01.2020 um 11:23 schrieb Durrant, Paul: -Original Message- From: win-pv-devel On Behalf Of Steffen Einsle Sent: 05 January 2020 00:44 To: win-pv-de...@lists.xenproject.org Subject: [win-pv-devel] Driver 9.0.0 no keyboard in vncviewer, USB- passthru only with qemu-traditional Hello, I just installed a Windows 2019 Server with the new 9.0.0 PV drivers under xen 4.12.1. I use gentoo and since I need usb-passthru I have to use the qemu-traditional useflag (or device_model_version = 'qemu-xen-traditional'). - USB-passthru works only with qemu-traditional That seems odd, but I guess nor many people use USB passthru so it could have got broken with upstream somewhere along the way. Is there a general trick to get USB-passthru working with qemu-xen? (without qemu-traditional my usbdevice = ['tablet', 'host:0d46:3003'] prevents domu creation - device-model-exited-error) I think that is probably something to post on xen-users or xen-devel. Have you ever had USB passthrough working with upstream QEMU? There's nothing at https://wiki.xenproject.org/wiki/Xen_USB_Passthrough to suggest it is only supported using trad so if it is broken it needs fixing. What does your qemu log (under /var/log/xen) say was the reason for failure? (I'm guessing it was probably malformed command line, which would mean there's a bug in libxl). Paul smime.p7s Description: S/MIME Cryptographic Signature ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
DomU Windows Server Essentials crashes with xen 4.16 but works with xen 4.14
Hello Everyone, I have some xen servers I recently tried to update from xen 4.14 to xen 4.16 Everything worked without problem, except for the Windows Server Essentials DomUs. With xen 4.16 those domains crashed (reproducable) during boot - KMODE_EXCEPTION_NOT_HANDLED. I tried to install a new DomU Windows Server 2019 Essentials - this VM crashed at the first reboot (still in the installation routine) with the same error. No PV-drivers installed yet. I switched back to xen 4.14 and all VMs booted ok without problem. All other VMs (Linux-PV, Windows-HVM (2008r2, 2012r2, 2016, 2019, 2022) show no problems, only the Windows Server Essentials crashes with xen 4.16. The system is a gentoo kernel 5.17.3, qemu-6.2.0-r4, xen-4.16.0-r5, xen-tools-4.16.0-r1 My working configuration is gentoo kernel 5.17.3, qemu-5.2.0-r2, xen-4.14.3-r2, xen-tools-4.14.3 My DomU config file looks like this name = 'DC-Server' type = 'hvm' memory = '8192' vcpus = '6' vif = [ 'mac=00:16:3E:ab:cd:50,bridge=br0' ] disk = [ '/dev/vg1/ServerSys,raw,hda,rw', '/dev/vg1/ServerData,raw,hdb,rw' ] viridian = 'all' localtime = '1' vnc = '1' keymap = 'de' vnclisten = '0.0.0.0:10,websocket' usb = '1' usbdevice = 'tablet' on_crash = 'restart' boot = 'c' xen_platform_pci = '1' max_grant_frames = 128 I tried disabling viridian but this made no change. Is this a known problem? -- Steffen
Re: DomU Windows Server Essentials crashes with xen 4.16 but works with xen 4.14
Hello, I can confirm that "msr_relaxed = 1" solves the problem with Server 2019 Essentials crashing. Am 26.04.2022 um 09:06 schrieb Roger Pau Monné: On Mon, Apr 25, 2022 at 07:19:08PM +0200, Steffen Einsle wrote: Hello Everyone, I have some xen servers I recently tried to update from xen 4.14 to xen 4.16 Everything worked without problem, except for the Windows Server Essentials DomUs. With xen 4.16 those domains crashed (reproducable) during boot - KMODE_EXCEPTION_NOT_HANDLED. I tried to install a new DomU Windows Server 2019 Essentials - this VM crashed at the first reboot (still in the installation routine) with the same error. No PV-drivers installed yet. I switched back to xen 4.14 and all VMs booted ok without problem. All other VMs (Linux-PV, Windows-HVM (2008r2, 2012r2, 2016, 2019, 2022) show no problems, only the Windows Server Essentials crashes with xen 4.16. The system is a gentoo kernel 5.17.3, qemu-6.2.0-r4, xen-4.16.0-r5, xen-tools-4.16.0-r1 My working configuration is gentoo kernel 5.17.3, qemu-5.2.0-r2, xen-4.14.3-r2, xen-tools-4.14.3 My DomU config file looks like this name = 'DC-Server' type = 'hvm' memory = '8192' vcpus = '6' vif = [ 'mac=00:16:3E:ab:cd:50,bridge=br0' ] disk = [ '/dev/vg1/ServerSys,raw,hda,rw', '/dev/vg1/ServerData,raw,hdb,rw' ] viridian = 'all' localtime = '1' vnc = '1' keymap = 'de' vnclisten = '0.0.0.0:10,websocket' usb = '1' usbdevice = 'tablet' on_crash = 'restart' boot = 'c' xen_platform_pci = '1' max_grant_frames = 128 Could you try adding: msr_relaxed=1 And see if that makes a difference? Thanks, Roger.
