search for: reintroduce

...hin the "new vm" wizard, one is forced to use a Qcow2 file (selectable in the global preferences). No sparse RAM images can be created within such wizard. As a heavy consumer of RAW disk files, I would really like to have the checkbox back, especially in RHEL/CentOS 7.x Do you plan to reintroduce it? For RHEL/CentOS, should I open a Bugzilla ticket? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@assyoma.it - info@assyoma.it GPG public key ID: FF5F32A8

...wizard, one is forced to use a Qcow2 file > (selectable in the global preferences). No sparse RAM images can be > created within such wizard. > > As a heavy consumer of RAW disk files, I would really like to have the > checkbox back, especially in RHEL/CentOS 7.x > Do you plan to reintroduce it? For RHEL/CentOS, should I open a Bugzilla > ticket? If you change the disk image format from qcow2 to raw in Edit->Preferences, then new disk images are set to fully allocated raw. Check the image details with 'qemu-img info $filename' to confirm. So I think by default we are doi...

On 06/19/2018 03:37 PM, Gionatan Danti wrote: > Il 19-06-2018 20:14 Cole Robinson ha scritto: >> If you change the disk image format from qcow2 to raw in >> Edit->Preferences, then new disk images are set to fully allocated raw. >> Check the image details with 'qemu-img info $filename' to confirm. So I >> think by default we are doing what you want? >>

On 06/19/2018 07:06 PM, Gionatan Danti wrote: > Il 19-06-2018 22:16 Cole Robinson ha scritto: >> Sorry, I misunderstood. You can still achieve what you want but it's >> more clicks: new vm, manage storage, add volume, and select raw volume >> with whatever capacity you want but with 0 allocation. > > Sure, but the automatic disk creation is very handy and much less

On Thu, Jun 28, 2018 at 12:35:56PM +0200, Gionatan Danti wrote: > Il 26-06-2018 23:49 Cole Robinson ha scritto: > > I see it as another test case and larger UI surface in the common path > > for something that will save clicks for a corner case. I still don't see > > it asworth exposing in the UI. > > > > - Cole > > I can not force this decision,

Hi list, in virt-manager ver. 2.2.1 (fully upgraded CentOS 8.1), the CPU model list only shows ancient CPU (the most recent is Nehalem-IBRS). On the other hand, in virt-manager 1.5.x (fully upgraded CentOS 7.8) we have a rich selection of CPU (as recent as Icelake). Why was the list in newer virt-manager so much trimmed? Is it possible to enlarge it? Thanks. -- Danti Gionatan Supporto

Il 29/05/2013 09:49, Michael S. Tsirkin ha scritto: > On Tue, May 28, 2013 at 07:40:18PM +0200, Paolo Bonzini wrote: >> The original idea of the VIRTIO_BALLOON_F_MUST_TELL_HOST feature was to >> let drivers skip usage of the deflate queue when leaking the balloon >> ("silent deflation"). Guests may benefit from silent deflate by >> aggressively inflating the

On Thu, 04 Jul, at 08:45:33AM, Andreas Heinlein wrote: > Looks like you're right. I added '*.tr *.hlp *.pcx back.jpg > gfxboot.cfg langlist' to the 'bootlogo' archive, and now I get the > menu, and everything seems to work! > > If that's really the only problem, I wouldn't consider this a bug. > IIRC, the 'unpacked' form of gfxboot archives is

Il 19-06-2018 20:14 Cole Robinson ha scritto: > If you change the disk image format from qcow2 to raw in > Edit->Preferences, then new disk images are set to fully allocated raw. > Check the image details with 'qemu-img info $filename' to confirm. So I > think by default we are doing what you want? > > - Cole Er, the point is that I would really like to have a

The original idea of the VIRTIO_BALLOON_F_MUST_TELL_HOST feature was to let drivers skip usage of the deflate queue when leaking the balloon ("silent deflation"). Guests may benefit from silent deflate by aggressively inflating the balloon; they know that they will be able to use ballooned pages without issuing a (blocking) request to the device. The previous patch redefined the

Il 26-06-2018 23:49 Cole Robinson ha scritto: > I see it as another test case and larger UI surface in the common path > for something that will save clicks for a corner case. I still don't > see > it asworth exposing in the UI. > > - Cole I can not force this decision, obviously. However, let me recap why I found it important to have the "allocate disk now"

Il 19-06-2018 22:16 Cole Robinson ha scritto: > Sorry, I misunderstood. You can still achieve what you want but it's > more clicks: new vm, manage storage, add volume, and select raw volume > with whatever capacity you want but with 0 allocation. Sure, but the automatic disk creation is very handy and much less error prone. As it is now, if using a fallocate-less filesystem (eg:

Hey, I just updated from the edge and it looks like this _issue_ has resurfaced. Yesterday things were working (stories and specs). No code base changes, only rspec and rspec_on_rails After updating today I now need to set <config.txn...fixtures> to false in the spec_helper.rb to get the specs running, the stories are fine. Looks like the fixture loading is trying to start a txn. I

...ck in unstable. One reason is the following: xen-api depends on xmlm and they must go together, and xen-api depends on (a new binary package of) openvswitch, which FTBFS (and has been for > 32 days). Is there anyone working on fixing openvswitch? Or can the dependency in xen-api be dropped, and reintroduced later, when openvswitch works and has migrated to testing? Cheers, -- St?phane

I don't know since when, but this file has been changed to remove all the trickery (aka defines) needed for MinGW-w64 (and probably everything else that as forgotten) to succesfully compile it. Attached is a patch that reintroduces the compiler checking. I would like to see this in LLVM 3.0, otherwise (by the looks of the reintroduced code) anything newer than _MSC_VER_1500 will be broken. Thanks! Ruben PS: any replies please "reply-to-all", only subscribed to cfe-dev -------------- next part -------------- An H...

...it; the problem occurs only when PAM support is enabled. However, if I remove line 430 of session.c, "do_pam_session(s->pw->pw_name, NULL);" inside of do_exec_no_pty, the problem goes away. It looks like the following entry in the Changelog may be responsible: 20010627 - (djm) Reintroduce pam_session call for non-pty sessions. Let me know if you need any additional info to track this down. Thanks, Brent Nelson Director of Computing Dept. of Physics University of Florida

...st a mistake ? Is there something I can do > to help get this package back ? > I removed llvm-lit, among other utilities, after receiving guidance that they were not intended for distribution to LLVM users. Sounds like that was wrong. You would have to update CMake to install them; and then reintroduce them into the Debian packaging. Cheers, Andrew 2016-03-30 2:34 GMT-07:00 Sylvestre Ledru via llvm-dev < > llvm-dev at lists.llvm.org>: > >> Le 29/03/2016 à 14:17, Yury V. Zaytsev a écrit : >> > Hi Sylvestre, >> > ri >> > On Sat, 12 Mar 2016, Sylvestre...

On Wed, 13 Apr 2016 at 09:38 Amaury SECHET <deadalnix at gmail.com> wrote: > I'd be happy to do it, but this is a bit much high level for me to be > actionable. Can you explain me what I should do to reintroduce them int he > debian packaging ? > On the CMake side, I'm not sure. I think it's just a matter of using the "install()" functions to install them into the appropriate place in the tree. They weren't installed by CMake in the first place; I was going to do that, which is...

...an i32 multiply into an i64 >> multiply in order to eliminate a cast. This does simplify/reduce the >> number of IR operations, but an i64 multiply is dramatically more >> expensive than an i32 multiply on CellSPU. > > I basically agree with Scott on this: we shouldn't reintroduce > types that > are illegal for the target after Legalize. I'm sorry, to be clear, this is mostly talking about an instcombine change. Obviously anything in codegen should respect current restrictions. The question is whether the mid-level optimizer should try to avoid introduci...

...unt Information got replicated.When I disconnected the Windows Server most Clients (Windows 7) did work -- except those with blanks in the username. Tests (adding/removing) blanks to the names made the problem reproducible (removed the blank from an exising account with blanks -> login did work. Reintroduced the blank -> login did not work). With a Linux Client kinit did work (with or without blanks in usernames). The Samba Server is currently disconnected from the network (as it prevents clients from login), but can be reactivated if needed. cheers, Andreas -- GPG-Key-Id: DD436203 Github:...