add gitlab issues in toml format

1 files changed, 18 insertions, 0 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1468.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1468.toml
new file mode 100644
index 000000000..0b1bcca00
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/1468.toml
@@ -0,0 +1,18 @@
+id = 1468
+title = "qemu hangs on white windows when connecting to virtual port using -serial option when using Windows OS"
+state = "opened"
+created_at = "2023-01-27T23:27:36.518Z"
+closed_at = "n/a"
+labels = []
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1468"
+host-os = "Windows 22H2"
+host-arch = "x86_64"
+qemu-version = "QEMU emulator version 7.2.0 (v7.2.0-11948-ge6523b71fc-dirty)"
+guest-os = "Windows Server 2003 SP1"
+guest-arch = "x86_64"
+description = """I was trying to connect windbg with a qemu vm. 
+First I try using named pipes but all the tutorials I found online result in the qemu windows not even showing. So I give up and trying to use virtual COMs to connect the qemu machine with  windbg over serial port. So I created using professional Virtual come driver a link between COM2 and COM4. Now I run qemu with  -serial COM2 and I do not run windbg than it run correctly and no problem is present. As soon as I run windbg qemu hangs at startup just after the main window is created. The qemu window remains white and windows shows the normal "The application is not responding". It's like the program is in a infinite loop situation. 
+Also I noted that If I run qemu and not windbg as soon as the other COM port is connected qemu would stop working and remain frozed. Again showing the "The application is not responding".
+If instead of qemu I use other "commercial" software with the same setup (of course there I could use named pipes anyway) I can connect windbg with the machine and do the debug session."""
+reproduce = "n/a"
+additional = "n/a"