[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AMD Working On VirtIO GPU Support For Xen Virtualization issues


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: ZHANG Zewei <zewei.zhang@xxxxxxxxxx>
  • Date: Mon, 20 Nov 2023 11:33:27 +0000
  • Accept-language: zh-CN, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=forvia.com; dmarc=pass action=none header.from=forvia.com; dkim=pass header.d=forvia.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=YGtWT7JFZxkumB/qMbpOR70Et4y4gLvFZSY12LXpFsE=; b=NgilxGWQMeJ3+a0WgC+Gb22+nlB+9k5pr6BEvCuVYYBsQkIQ9sWIz038/pEgY+NS31e955yNKbLXlXH26n874A0S+E0/DGrG6yLtXkbTxWcYYWWNdwjarhO8qfueBphaxvzQHIB+xVWmWGlufRZm0oCI6+/8tr9vX0KV1SysYd6bfq9j+hv4griln1fo+TySqJ2kjj0Z8r00s0Cmk6ezPqBHwNhBBLY2Mn9ZflBhmz69JVmDcAjy75LH//iTxBXRt5/sVaRPV+inclKAN8fi5QXWjUk4H8ZJTAMqUVD1q5+lWFtQuhp5HlDLzeKzfyxXpOW5DIj8cTqmJh1Yf6+QZw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ac/q8AJY54fCEv611g8R+slqWUFTlH3uHCtM6/S5BxkZDic9xBhl3OEdOsNsMEJ0PTK/dXBhSIa51PN0ofgjbwLT+q2MTJgRDu0bb0iUrB4hz6LmyrYMRR9hvXYe4aoOV05GDqhjoVx/1Zh3xvo8PWI52uelLtkQCDPRwhwORbsFaSAgImadiOq3pZxcdp1f3aPOy3jHZS5OY4cemM2iLv2pOtY3mc3s6iUo+udn0b2+Lo90EmlahIslQhHM2wqx0RR4vy9SMBNXaEEVZsp7Djmrbdc8I4PPtHdMiTVW/McnT3yVVDlKY9ThyDRlroGkBeRieiaSxU6faCVcjpfA7Q==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=forvia.com;
  • Cc: "ray.huang@xxxxxxx" <ray.huang@xxxxxxx>
  • Delivery-date: Mon, 20 Nov 2023 11:40:08 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Msip_labels: MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_ActionId=d715e922-4bf3-4286-8029-b832696e087e;MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_ContentBits=0;MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_Enabled=true;MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_Method=Standard;MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_Name=InternalAndPartners;MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_SetDate=2023-11-20T07:42:12Z;MSIP_Label_eafdac3b-4115-4c64-bf62-f9099ec36d84_SiteId=5047bca2-da88-442e-a09a-d9b8af692adc;
  • Thread-index: Adobo1s+5ZENqT0uQjS822lVvDb6Fg==
  • Thread-topic: AMD Working On VirtIO GPU Support For Xen Virtualization issues

INTERNAL & PARTNERS


HiXen-devel

       We are trying to implement the igpu sharing function for domU on the AMD (v2000 series) development board environment, and the software architecture is xen + ubuntu 22.04 (dom0) + Ubuntu 22.04 (Dom U). We found that AMD engineers like Mr. Huang @ray.huang@xxxxxxx have posted information about virtio-gpu  for Xen virtualization to the open source community and uploaded the relevant code.

 

       And We refer to the relevant information linked below to deploy on my AMD hardware platform:

[RFC PATCH 0/5] Add Xen PVH dom0 support for GPU - Huang Rui (kernel.org)

 

       However, when we deploy virtio-GPU related software, we encounter the following issues:

1.    My code of xen /qemu /Virglrenderer checkout to the upstream-for-xen or upstream-for-xen-v2 branch, the xl configuration file is set as follows, see< ubuntuhvm_virtIO-gpu.cfg>:

              device_model_args_hvm= ["-display", "sdl,gl=on", "-device", "virtio-vga-gl,context_init=true,blob=true,hostmem=4G"]

 

2.    After the domU is started with the xl command, qemu and xen hypervisor will report the following errors:

         xen hypervisor report < xl_dmesg_upstream-for-xen-v2.txt>:

              (XEN) d0v8 Over-allocation for d1: 1048833 > 1048832

(XEN) common/memory.c:277:d0v8 Could not allocate order=0 extent: id=1 memflags=0xc0 (192 of 2048)

              qemu report  in log file < qemu-dm-ubuntuU_b.hvm.log>:

              qemu-system-i386: -device virtio-vga-gl,context_init=true,blob=true,hostmem=4G: xen: failed to populate ram at 110080000

 

3.    I tried to start pvh dom0 but it didn't work, it looks the same regardless of whether I'm using upstream-for-xen-v2 or upstream-for-xen branch linux

Logs in attachment:< serial_xen_hypervisor-linux-upstream-for-xen-v2.txt>

 

 

       So I have some questions for you :

1.     Does Dom 0 need to be configured with PVH for VirtIO-GPU?

2.     What may cause the above issues?

 

We look forward to hearing from you!

 

Thanks & Best regards!

 

 

 

 

 


5acXjzUk

Attachment: serial_xen_hypervisor-linux-upstream-for-xen-v2-txt.zip
Description: serial_xen_hypervisor-linux-upstream-for-xen-v2-txt.zip

Attachment: qemu-dm-ubuntuU_b.hvm-log.zip
Description: qemu-dm-ubuntuU_b.hvm-log.zip

Attachment: xl_dmesg_upstream-for-xen-v2-txt.zip
Description: xl_dmesg_upstream-for-xen-v2-txt.zip

Attachment: ubuntuhvm_virtIO-gpu-cfg.zip
Description: ubuntuhvm_virtIO-gpu-cfg.zip


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.