This patch should be submitted on qemu-devel.
** Changed in: qemu
Status: New = Invalid
--
libdis and libdis-user not ignored
https://bugs.launchpad.net/bugs/568442
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in
** Changed in: qemu
Status: Fix Committed = Fix Released
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU:
This patch doesn't seem correct as the spec is pretty clear that THRE
interrupt enable is set to high, then an interrupt is rased if
LSR.THRE=1. Does the following also make DOSPlus boot again:
No it doesn't. Same as unpatched.
--
QEMU fails to boot DR DOS Plus since 0.6.1
Re: 68a1c816868b3e35a1da698af412b29e61b1948a
In general, I like the idea (especially since I've proposed it before. ;-)
However:
+if (have_guest_base) {
+flags |= MAP_FIXED;
+}
I think this is broken. If the user specifies -G n -R m they're hoping
or
Hi,
I disagree. Anything that depends on device creation order is
fundamentally broken. If you want to create globally unique
user-friendly tags for devices or busses then that is a completely
different problem, and should be done via explicit aliases.
For anything created via
From pthread man:
These functions manipulate the calling thread's stack of
thread-cancellation clean-up handlers. A clean-up handler is
a function that is automatically executed when a thread is canceled
[...] it might, for example, unlock a mutex so that it becomes
available to
From: Jan Kiszka jan.kis...@siemens.com
As long as we allow /dev.1 as shortcut for /dev1/bus1, we also have to
make sure that /dev1/dev2 works for /dev1/bus1/dev2/bus2 - as long as
there is only one child bus per device.
How about we make this explicit in the syntax by having a different
201 - 207 of 207 matches
Mail list logo
