Here's the problem :
running Qemu 0.8.1 binary (as provided on the download page),
both with and without kqemu accelerator.
I want to be able to run a virtual LAN of Virtual machines
within my PC, that is seperate from the physical LAN the host PC
is connected to.
I don't want to use the socke
Public bug reported:
QEMU Version: 2.12 (Binary installer qemu-w64-setup-20180424.exe from Stefan
Weil's website so I am not sure I should report it to Weil by email or by this
bug report system.)
Host System: Windows 7 64bit
Guest System: 9front 6350 (Codename“CONTENTS, MAINTAINED, STABLE”, Re
Rechecked in my site, the new installer (20180430) had solved the 1st
problem, but it leads to another problem: When uninstall QEMU, the
loaders.cache file cannot be deleted automatically.
For 2nd warning, I checked it again, when I choosed fully installing,
the icons are displayed correctly; But
how to run without binfmt support in the kernel.
/usr/bin/qemu-i386 /usr/bin/wineserver
/usr/bin/qemu-i386 /usr/bin/wine-pthread notepad.exe
or
/usr/bin/qemu-i386 -L /usr/gnemul/qemu-i386 /usr/bin/wineserver
/usr/bin/qemu-i386 -L /usr/gnemul/qemu-i386 /usr/bin/wine-pthread notepad.exe
If you do h
HOW TO COMPILE ON ARM AND UBUNTU 12.04
This will run wine if you compile with 0.13 or 0.14
sudo apt-get install zlib1g-dev
sudo apt-get install libsdl1.2-dev
./configure --target-list=i386-linux-user --enable-sdl --prefix=/usr
--cross-prefix=arm-linux-gnueabi- --host-cc=gcc4.6 --extra-cflags=-ma
I do now know... I compile on my phone and tablet. In fact I loaded
Ubuntu on my Touchpad last night, native.
http://code.google.com/p/hp-touchpad-ubuntu/wiki/Installation
No more chroot to deal with.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is su
I am now able to run winecfg... you have to have wine-pthread run winecfg
qemu-i386 /usr/bin/qemu-i386 wine-pthread winecfg
All the tabs load except audio.. For that it hangs..
Trying to fix that.. I want to run an app that hangs and it uses audio.
--
You received this bug notification because y
Interesting stuff.
With 0.14 and 1.2
wineserver will run if you say wineserver -d2 -f -p for example.
I believe it is forking when you run plain old wineserver because it really is
getting an invalid argument.
I am running Wine 1.1.14 and Qemu 0.14 and I can run many apps.
I cannot run a NeoB
Does this have anything to do with Memory Mapping? I have a feeling it
does
I notice the mmap_min_addr setting for arm is 4096
For x86 its 65536
http://www.onsitedentalsystems.com/error.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
The app I am testing does run on qemu-i386 compiled for x86.. and the
host is x86.
The screen shot I posted in the last post is what happens when you run
qemu and wine on arm instead of qemu and wine on x86.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Public bug reported:
Qemu fails to build on powerpc64, ELFv1 ABI, since the introduction of
the ELFv2 ABI support. On FreeBSD/powerpc64 I see the following error
building HEAD from today (8/14/2014):
In file included from /home/chmeee/qemu-git/tcg/tcg.c:264:
/home/chmeee/qemu-git/tcg/ppc/tcg-tar
I would like to run wine. I have compiled qemu 0.15.5 from git and I
noticed we can enable nptl without a patch. I can run an x86 nptl bash
but I havent tried to chroot. I have the posix wine running with qemu...
So i tried it with wine and I am able to get a --version out of it, but
when I actuall
Here is a strace.. fumex calls???
strace -ff -o /ls-strace-alignment-6.log /usr/bin/qemu-i386 /usr/bin
/wine-pthread notepad.exe
** Attachment added: "wine.log"
https://bugs.launchpad.net/qemu/+bug/739785/+attachment/2426371/+files/wine.log
--
You received this bug notification because you
linux/pci_hotplug.h:141:19: note: previous definition of
‘pci_hp_reset_slot’ was here
static inline int pci_hp_reset_slot(struct hotplug_slot *slot, int probe)
^
make[3]: *** [drivers/pci/hotplug/pci_hotplug_core.o] Error 1
Justin
git/drivers/vfio/pci/vfio_pci.c
>
Oops, that's embarrassing. I'm pretty sure I pulled the wrong qemu branch.
With that goof eliminated, everything is working flawlessly: the host
doesn't freeze up anymore, and I no longer need to suspend between VM runs.
Very nice!
Thanks for the patches and the help,
Justin
ilesystems, providing a hint to
the caller about how effective the guest-fstrim request was.
Signed-off-by: Justin Ossevoort
---
qga/commands-posix.c | 19 +++
qga/qapi-schema.json | 5 +++--
2 files changed, 14 insertions(+), 10 deletions(-)
diff --git a/qga/commands-posix.c b/qg
with their status. If the
trime operation succeeded it returns the amount of bytes trimmed and
the effective minimum chunk size. On error it returns the value of
the errno for that filesystem operation (instead of aborting the
request).
Signed-off-by: Justin Ossevoort
---
qga/commands-pos
his is how one would want to use this return type.
Pherhaps it would be better to drop the "result" field and mirror the
basic return logic: "error" attribute on error and a "return" attribute
with a dictionary containing the per mountpoint result?
Regards,
Just
Wine works! =) Didn't know if you knew... no more old qemu.
You da man!
On Tue, Aug 6, 2013 at 3:33 AM, Peter Maydell
wrote:
> Commits aa004f5f9 to 24cb36a61c (13 in total) are the patchset that fix
> this.
>
> --
> You received this bug notification because you are subscribed to the bug
> repo
If you do ALL that... Then winecfg will run. About to start testing
programs.
Pinball runs VERY FAST! VERY PLAYABLE NOW!!! :D
Justin Shafer
OnsiteDentalSystems.com
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs
I still have one program that refuses to run.. I think its having a
problem with an x86 library on the gnemul side... I noticed libpng.so.3
wanted to be in the gnemul folder by wine.. even though it didn't exist
on the X86 machine I was using to compile.. so I copied it from
libpng12.so..
Anyone h
Oh yeah.. wine goes in /usr/local/bin. I created a symbolic link from
/usr/gnemul/qemu-i386/usr/local/lib/libwine* /usr/local/lib. Same with
the wine folder.. it needs to be seen as /usr/local/lib/wine.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is sub
with those 3
lines I removed.. So I am recompiling my kernel and then I am going to
recompile qemu and I bet I can compile it without removing those 3
lines.
-Justin
Wine 1.5.11 is a lot funner to play with then 0.9.14
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonic
Open GL Works with wglgears.
ubuntu@hptp-u1210b1:~/.wine/drive_c$ wine ./wglgears.exe
qemu: Unsupported syscall: 254
Unsupported ancillary data: 1/2
qemu: Unsupported syscall: 242
Unsupported ancillary data: 1/2
qemu: Unsupported syscall: 242
Unsupported ancillary data: 1/2
qemu: Unsupported sysca
http://forum.winehq.org/viewtopic.php?f=2&t=17701
Here is where I got... Read the whole thing..
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of James
Le Cuirot
Sent: Monday, January 21, 2013 4:16 PM
To: justinsha...@gmail.com
Subject: [Bug 7397
Moonman, you know what I realized. I have the posix version of wine
running okay with qemu-i386... But I have never been able to compile my
own working version.. I realized that last night. I can compile, and it
will run, but wine never actually runs, and Im compiling with --enable-
sdl and all tha
See this can run the posix wine.. But I cant recreate it. Its running
qemu-0.12.2 which you can download and compile but I still cant get it
to play solitaire like I can with the one below.
wget http://a.trap.me.uk/qemu-i386
--
You received this bug notification because you are a member of qemu
Okay I found that 12.5 I can run posix wine and that is compiling on my
own. gonna try the patch on 12.5 to see if it can run dynamic nptl
binaries
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Odd.. If I do ./configure --static --enable-sdl --target-list=i386
-linux-user this will work fine with 12.5 but on say 15 it cant find
SDL. I am on 1.2.13 I think.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpa
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/855630
I decided to give it, its own bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails (b
Something odd. I installed VMWare with Ubuntu 11.04. Then I installed
wine and qemu with apt-get. Same exact errors using qemu-i386. Verbatim.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Tit
No armel at all in #44. Perhaps if qemu cant run wine with user
emulation using x86.. it will not be able to do arm as well?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 us
.3]# make
> ./qemu-linux-user.sh
> [qemu-i386]
> ../qemu-0.14.0/i386-linux-user/qemu-i386 -L ./gnemul/qemu-i386 i386/ls
> -l dummyfile
> BUG IN DYNAMIC LINKER ld.so: dl-version.c: 210: _dl_check_map_versions:
> Assertion `needed != ((void *)0)' failed!
> make: *** [t
.
If a previous filesystem would have trimmed 0 bytes, than the next
filesystem would report an error 'Invalid argument' because a FITRIM
request with length 0 is not valid.
This change resets the fstrim_range structure for each filesystem.
Signed-off-by: Justin Ossevoort
---
qga/comman
some mountpoints that error is returned and the
guest-fstrim continue with any additional mountpoints.
Signed-off-by: Justin Ossevoort
---
qga/commands-posix.c | 54 ++--
qga/qapi-schema.json | 32 ---
2 files changed, 69
timate details about
the filesystem layout of the guest.
Justin Ossevoort (2):
qga/commands-posix: Fix bug in guest-fstrim
qga/commands-posix: Return per path fstrim result
qga/commands-posix.c | 63
qga/qapi-schema.json | 32
On 30-04-15 18:35, Thomas Huth wrote:
On Thu, 30 Apr 2015 16:29:58 +0200
Justin Ossevoort wrote:
The current guest-fstrim support only returns an error if some
mountpoint was unable to be trimmed, skipping any possible additional
mountpoints. The result of the TRIM operation itself is also
h 2 to indicate returned values are
filesystem, storage stack and kernel version dependant
Justin Ossevoort (2):
qga/commands-posix: Fix bug in guest-fstrim
qga/commands-posix: Return per path fstrim result
qga/commands-posix.c | 63
.
If a previous filesystem would have trimmed 0 bytes, than the next
filesystem would report an error 'Invalid argument' because a FITRIM
request with length 0 is not valid.
This change resets the fstrim_range structure for each filesystem.
Signed-off-by: Justin Ossevoort
---
qga/comman
some mountpoints that error is returned and the
guest-fstrim continue with any additional mountpoints.
The returned values for errors, minimum and trimmed are dependant on the
filesystem, storage stacks and kernel version.
Signed-off-by: Justin Ossevoort
---
qga/commands-posix.c | 54
Hiya,
I have found a bug in the implementation of the load/store multiple
instructions in ARM (LDM and STM). These are defined in the ARM ARM to
ignore bits 0 and 1 of the address when the load takes place - that is the
base register for these operations is always treated as a 32bit aligned
v
value is non-zero. Within the OS I'm using, the N flag's value is seldom
intentionally changed, but the Z flag is regularly manipulated.
Justin Fletcher wrote:
Hiya,
I've been using qemu to test an ARM OS with. I hope this is the right
address to contact with patches; I coul
On Sun, 10 Sep 2006, Paul Brook wrote:
---8<---
if (n != 1)
gen_op_addl_T1_im(-((n - 1) * 4));
}
}
j = 0;
/* Insert something like gen_op_bicl_T1_im(3); here */
for(i=0;i
Hiya,
Tiny fix for the bit manipulation in the PL110 rendering code,
hw/pl110_template.h. There is a sequence of three definitions used in the
graphic routines :
#define FN_2(x, y) FN(x, y) FN(x+1, y)
#define FN_4(x, y) FN_2(x, y) FN_2(x+1, y)
#define FN_8(y) FN_4(0, y) FN_4(4, y)
In the FN_
On Thu, 23 Nov 2006, Wolfgang Schildbach wrote:
I very much doubt there is any problem with the CPSR. The ARM emulation
has correctly run hundreds of millions of instructions coming from many
different compilers and hand-written assembly. Can you be more precise in
what the effect is that you se
On Fri, 2 Feb 2007, Scott Oom wrote:
Hello,
Found a problem when using small pages and getting permission faults.
This patch corrects the decoding of access permissions for small pages
on ARM, was just off by 2 bits.
I may be confused on this, but it still doesn't seem right to me.
You have..
On Fri, 2 Feb 2007, Justin Fletcher wrote:
On Fri, 2 Feb 2007, Scott Oom wrote:
Hello,
Found a problem when using small pages and getting permission faults.
This patch corrects the decoding of access permissions for small pages
on ARM, was just off by 2 bits.
I may be confused on this, but
The attached very trivial patch fixes a startup bug that prevents at
least Qemu 3.1 and later from working on FreeBSD/powerpc64.
- Justin
>From 74a70fdcfa5347e7637aa36276c55781f19de72a Mon Sep 17 00:00:00 2001
From: Justin Hibbits
Date: Fri, 7 Jun 2019 13:44:51 -0500
Subject: [PATCH]
ies in guest when switching evdev input
Status in QEMU:
Fix Released
Status in qemu package in Fedora:
Fix Released
Bug description:
justin@justin-3900x:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20
put dies in guest when switching evdev input
Status in QEMU:
Fix Released
Status in qemu package in Fedora:
Fix Released
Bug description:
justin@justin-3900x:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20
I haven't attempted to reproduce the issue recently, I'm afraid. I've
changed jobs twice in the intervening time, so the immediate issue for
me has gone away. If I find an opportunity, I shall try to reproduce
with the most recent versions.
--
You received this bug notification because you are a
It looks like this has been fixed in the intervening 3 years. I just
tried building head on FreeBSD/powerpc64, and was successful.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1357175
Title:
qemu
It looks like this has been fixed in the intervening 3 years. I just
tried building head on FreeBSD/powerpc64, and was successful.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1357175
Title:
qemu
The last email's diff got mangled due to long lines. The original
source has long lines still but it shouldnt get cut off his time.
Justin,
diff --git a/vioinput/sys/HidMouse.c b/vioinput/sys/HidMouse.c
index 69dac235..528bd3d6 100644
--- a/vioinput/sys/HidMouse.c
+++ b/vioinput/sys/HidMo
more robust fix and deeper
look at the HIDMouseProbe function.
Thanks,
Justin
diff --git a/vioinput/sys/HidMouse.c b/vioinput/sys/HidMouse.c
index 69dac235..ea188991 100644
--- a/vioinput/sys/HidMouse.c
+++ b/vioinput/sys/HidMouse.c
@@ -325,7 +325,11 @@ HIDMouseProbe(
DynamicArrayReserve(&am
I upgraded to Ubuntu 20.10 (Groovy Gorilla) and the issue was resolved.
Here's a list of relevant package versions:
root@justin-3900x:/home/justin# apt list --installed | grep virt
(etc...)
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
gir1.2-libvirt-gli
On Wed, 26 Jun 2019 18:16:36 +0200
Laurent Vivier wrote:
> Le 26/06/2019 à 18:14, Laurent Vivier a écrit :
> > Le 07/06/2019 à 20:56, Justin Hibbits a écrit :
> >> The attached very trivial patch fixes a startup bug that prevents
> >> at least Qemu 3.1 and la
On Wed, 26 Jun 2019 18:47:42 +0200
Laurent Vivier wrote:
> Le 26/06/2019 à 18:37, Justin Hibbits a écrit :
> > On Wed, 26 Jun 2019 18:16:36 +0200
> > Laurent Vivier wrote:
> >
> >> Le 26/06/2019 à 18:14, Laurent Vivier a écrit :
> >>> Le
On Wed, Jun 26, 2019, 13:04 Justin Hibbits wrote:
> On Wed, 26 Jun 2019 18:47:42 +0200
> Laurent Vivier wrote:
>
> > Le 26/06/2019 à 18:37, Justin Hibbits a écrit :
> > > On Wed, 26 Jun 2019 18:16:36 +0200
> > > Laurent Vivier wrote:
> > >
> >
On Wed, Jun 26, 2019, 19:08 Laurent Vivier wrote:
> Le 27/06/2019 à 02:02, Justin Hibbits a écrit :
> >
> >
> > On Wed, Jun 26, 2019, 13:04 Justin Hibbits > <mailto:chmeeed...@gmail.com>> wrote:
> >
> > On Wed, 26 Jun 2019 18:47:42 +0200
&g
On Mon, Jul 1, 2019, 03:54 Laurent Vivier wrote:
> Le 27/06/2019 à 02:15, Justin Hibbits a écrit :
> >
> >
> > On Wed, Jun 26, 2019, 19:08 Laurent Vivier > <mailto:laur...@vivier.eu>> wrote:
> >
> > Le 27/06/2019 à 02:02, Justin Hibbits a écrit :
On Mon, 1 Jul 2019 15:17:06 +0200
Laurent Vivier wrote:
> Le 01/07/2019 à 15:02, Justin Hibbits a écrit :
> >
> >
> > On Mon, Jul 1, 2019, 03:54 Laurent Vivier > <mailto:laur...@vivier.eu>> wrote:
> >
> > Le 27/06/2019 à 02:15, Justin Hibbits
On Wed, 21 Aug 2019 10:25:45 +0200
Laurent Vivier wrote:
> This is the patch originally sent by Justin, modified
> to change the parameter size on FreeBSD only.
>
> Justin, could you review and test on FreeBSD?
> Peter, could you run "make check" on your MacOS X hos
On Wed, 21 Aug 2019 10:25:45 +0200
Laurent Vivier wrote:
> This is the patch originally sent by Justin, modified
> to change the parameter size on FreeBSD only.
>
> Justin, could you review and test on FreeBSD?
> Peter, could you run "make check" on your MacOS X hos
t; +}
> > +}
> > #endif
> > /* If we don't have any way of figuring out the actual
> > executable location then try argv[0]. */
> >
>
Apologies, I don't have context for this. Why was I CC'd on this?
Does proc_pidpath() not NUL-terminate its written string? And, given
from my quick google search, it looks like this function is private and
subject to change, so can you guarantee that the returned length is the
*written* length, not the full string length? If not, you could be
overwriting other arbitrary data.
- Justin
On Wed, 3 Jun 2020 16:36:27 +0200
Philippe Mathieu-Daudé wrote:
> On 6/3/20 4:09 PM, Justin Hibbits wrote:
> > On Wed, 3 Jun 2020 08:08:42 +0200
> > Philippe Mathieu-Daudé wrote:
> >
> >> Cc'ing more developers.
> >>
> >> O
Public bug reported:
justin@justin-3900x:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
justin@justin-3900x:~$ apt list --installed | egrep '*qemu*|*kvm*'
WARNING: apt does not hav
eger no
> …
>
> In fact, it is in sysctl(3):
>
> SYSCTL(3)BSD Library Functions Manual
> SYSCTL(3) …
>CTL_HW
> The string and integer information available for the CTL_HW
> level is detailed below. The changeable column shows whether a
> process with appropriate privilege may change the value.
>
>Name Type Changeable
> ...
>hw.cachelinesize int64_t no
>
> I will try to check on MacOS/X ppc and ppc64.
>
> Thanks,
> Laurent
>
It's not listed in the man page for ppc(64), but examining the XNU
source for the version that matches 10.5.8 (last ppc-supporting kernel)
it's a CTLTYPE_INT. So, it may be different depending on arch and/or
OS X version. Does QEmu even support 10.5.x or Mac OS/ppc* anymore? I
had read somewhere that it was unsupported now (2.4.x is the latest one
in Tigerbrew).
- Justin
I tried to build a 64-bit Precise desktop virt using libvirt manager,
itself running on a 64-bit AMD 4-core box with Precise. When
specifying the vmvga/vmware option, qemu keeled over and died as soon as
(in VNC) it looked like the card was going into graphics mode.
I then built the image specif
...@nongnu.org by Wednesday Jan 11th to give time for testing
before the release is cut.
Thanks,
Justin
On Tue, 2012-01-10 at 14:33 +0100, Andreas Färber wrote:
> Justin,
>
> Am 09.01.2012 19:00, schrieb Justin M. Forbes:
> > Due to the repository move, holidays and other bits, we are a bit late
> > getting out the door, but I want to get qemu 1.0.1 stable release done this
; > argument is of type ‘TCGv_i64’
> > make[1]: *** [translate.o] Error 1
> > make: *** [subdir-x86_64-softmmu] Error 2
>
> I see this, too.
I will take a look, I am not seeing it right now with the full stable
tree, though I am doing a much larger config.
Justin
Fedora 14
- We have 101 open bugs, 5 of which have fixes in awaiting updates.
- 1 bug has been closed in the last week
Fedora 15
- Release tomorrow!
- We have 36 open bugs 2 of which have fixes in awaiting updates.
- 6 bugs have been closed in the last week
- GA images have been cleared for releas
buted
to make this release happen!
Regards,
Justin M. Forbes
CONFIG_PRODUCTVERSION 1,0,1,0
> >
> >
> >Patch:
> >--- VERSION.ORIG2012-02-18 18:56:16.62500 -0500
> >+++ VERSION 2012-02-18 18:56:31.609375000 -0500
> >@@ -1 +1 @@
> >-1.0,1
> >+1.0.1
>
> Acked-by: Stefan Weil
Ack, wow do I feel silly. Thanks for the catch.
--
Justin M. Forbes
Fedora 15
- We have 65 open bugs 11 of which have fixes in awaiting updates.
- 12 bugs have been closed in the last week
Fedora 16
Fedora 16 Feature Freeze is just 1 week away. It is time to make sure
things are in shape for alpha. Important dates for the Fedora 16 Schedule:
2011-07-26 F
On Mon, Oct 31, 2011 at 08:09:31PM +0100, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
>
> Thanks, Juan.
>
> PD. Tomorrow is a Spanish holiday, so I would not attend the call.
As there are no agenda items, todays call is cancelled.
Justin
k on OpenBSD.
>
Pulled, thanks.
Justin
table-0.15 of upstream QEMU.
>
> So I guess Justin should be CCed?
>
> Kevin
Thanks for the CC, and pulled.
Justin
e been for a few weeks.
Justin
see them.
Thanks,
Justin
grab the full set of drivers from the ISO or another
location. Later versions of Windows can install using the ISO for
drivers and do not need the vfd at all.
Justin
On Wed, 2011-10-12 at 05:41 -0400, Brad wrote:
> On 26/09/11 9:16 AM, Justin M. Forbes wrote:
> > With the current patch queue I would like to start getting qemu-0.15.1
> > stable into shape. With this in mind, the plan is to tag the release on
> > Monday Oct 3rd. If you hav
e who contributed
to make this release happen!
Regards,
Justin M. Forbes
come lend a
hand, we can use as many testers as possible. If you cannot make it
on Thursday, please feel free to run through test plans as you have
time,the feedback is still relevant and helps to make Fedora a better
platform for virtualization.
Thanks,
Justin
Fedora 14
- We have 95 open bugs, 5 of which have fixes in awaiting updates.
- 17 bugs have been closed in the last week
Fedora 15
- We have 22 open bugs.
- 9 bugs have been closed in the last week
- Beta is released, go test!
- Upcoming Dates of importance:
2011-05-09 Final Change Deadline
2
It has come time to do the 0.14.1 stable release. If there are any patches
which should make this release, please send them along. Remember, to be
included, they need to be in the development tree already, and bug fixes
only. I will cherry pick as appropriate.
Thanks,
Justin
e who contributed
to make this release happen!
Regards,
Justin M. Forbes
ow do people feel about this?
Justin
On Fri, 2011-12-09 at 13:55 +0100, Andreas Färber wrote:
> Am 05.12.2011 21:08, schrieb Justin M. Forbes:
> > Typically I get a flurry of patches shortly after
> > a release (and they have already started for 1.0). I have tried to get
> > a .1 release out in a timely mann
I've been looking at libvirt and qemu for other work, I'm doing, and
I've criceld back to take another look at this.
Since I first looked at this, my testbed has updated to use the
"oneiric-proposed"
qemu-kvm package '0.14.1+noroms-0ubuntu6.1'
while retaining the libvirt-bin package
0.9.2
Some incremental findings:
In 'qemu-kvm' the DeviceState for the peer device of the
BlockDeviceState that gets created when a disk attached by 'virsh
attach-disk' references the 'QemuOpts' options structure that lists the
options and the device ID string (ex: as 'virtio-disk4') that will (on a
r
>
> Okay, as long as stable is just there for CC and qemu-devel stays in the
> loop. Can't do it right now but remind me again when Savannah is back up.
I would agree, a different list makes things a bit easier to track, but
discussions need to happen on qemu-devel so that the right people stay
involved. Tagging a patch isn't always a good thing because the patch
is likely sent to the list for the dev branch, and only CCed to stable
because it applies and is needed.
Justin
Public bug reported:
Filed from Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=589130
Guests can access USB Mass Storage Device, but fail to mark them as
removable.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are
Fedora 14
- We have 79 open bugs, 9 of which have fixes in awaiting updates.
- 1 bug has been closed in the last week
- Virt-preview has been opened for Fedora 14, more details below
Fedora 15
- Upcoming Deadlines:
2011-01-25 Feature Submission Deadline (2 Weeks!)
2011-02-08 Feature Freeze--
Fedora 14
- We have 90 open bugs, 9 of which have fixes in awaiting updates.
- 4 bugs have been closed in the last week
Fedora 15
- Upcoming Deadlines:
2011-03-15 Software Translation Deadline
2011-03-22 Beta Change Deadline Features 100% Complete
2011-04-05 Beta Release
2011-04-25 Fin
Fedora 14
- We have 91 open bugs, 10 of which have fixes in awaiting updates.
- 7 bugs have been closed in the last week
Fedora 15
- Upcoming Deadlines:
2011-03-29 Software Translation Deadline
2011-04-05 Beta Change Deadline Features 100% Complete
2011-04-19 Beta Release
2011-05-09 Fi
Fedora 14
- We have 103 open bugs, 16 of which have fixes in awaiting updates.
- 1 bugs have been closed in the last week
Fedora 15
- Upcoming Deadlines:
2011-04-05 Beta Change Deadline Features 100% Complete *today*
2011-04-19 Beta Release
2011-05-09 Final Change Deadline
2011-05-10 C
llow the tree to develop a life of its own over time.
> >
> > I'd like to begin this process with 0.14 and as such, have created a
> > new stable tree at git://git.qemu.org/qemu-stable-0.14.git.
> >
> > Justin Forbes has volunteered to help collect patches for thi
On Wed, 2011-02-09 at 14:52 +0100, Kevin Wolf wrote:
> Hi Justin,
>
> Am 08.02.2011 15:12, schrieb Markus Armbruster:
> > Markus Armbruster (2):
> > blockdev: Plug memory leak in drive_uninit()
> > blockdev: Plug memory leak in drive_init() error paths
1 - 100 of 155 matches
Mail list logo
