Am Montag, den 24.05.2021 um 11:52:22 Uhr +0100 schrieb Michael
:
> On Monday, 24 May 2021 02:01:15 BST Oliver Dixon wrote:
> > Hi,
> >
> > I decided to bite the bullet yesterday and switch from clunky, and generally
> > untoward, VirtualBox to QEMU/KVM for developing kernel modules. I have a
> >
On Wed, May 26, 2021 at 07:43:59PM +0200, Branko Grubi?? wrote
>
> Hi,
>
> What comes to my mind is actually describe in here[1]. Possibly
> virtualization is disabled in BIOS/Firmware.
>
>
> [1] https://wiki.gentoo.org/wiki/QEMU#BIOS_and_UEFI_firmware
Thank you very much; that was it. QEMU
On Wed, 2021-05-26 at 12:50 -0400, Walter Dnes wrote:
> With my older machine locking up once too often at in-opportune
> times,
> I've switched over to a newer machine, which I've tried to set up
> identically. QEMU is not laumching. It worked on the older system.
> The error message is...
>
With my older machine locking up once too often at in-opportune times,
I've switched over to a newer machine, which I've tried to set up
identically. QEMU is not laumching. It worked on the older system.
The error message is...
[x8940][waltdnes][~] /home/misc/qemu/arca/boot
Could not access KV
On Monday, 24 May 2021 02:01:15 BST Oliver Dixon wrote:
> Hi,
>
> I decided to bite the bullet yesterday and switch from clunky, and generally
> untoward, VirtualBox to QEMU/KVM for developing kernel modules. I have a
> working Gentoo VM with all the bells and whistles I need/want (UEFI
> booting,
Hi,
I decided to bite the bullet yesterday and switch from clunky, and generally
untoward, VirtualBox to QEMU/KVM for developing kernel modules. I have a working
Gentoo VM with all the bells and whistles I need/want (UEFI booting, NIC
passthrough, SSH forwarding, NFSv4 support, etc.), but it's run
On 12/5/19 12:22 PM, n952162 wrote:
But, since it's included in the package, and apparently (from the name)
will use a NBD device, then I think the dependency is logical
I disagree.
QEMU itself does not use NBD. Thus QEMU does not need to depend on
qemu-nbd. QEMU uses files on mounted file
On 12/5/19 12:50 PM, Neil Bothwick wrote:
No, but since it is provided by the ebuild, the ebuild should check
that the target system is capable of supporting it. The qemu ebuild
already spits out warnings about missing kernel options, not all of them
essential, so why not this one too?
I thin
On Thu, 5 Dec 2019 12:01:33 -0700, Grant Taylor wrote:
> qemu-nbd is a utility to act as a NBD server to allow the Linux kernel
> to be an NBD client to access qcow(2) image files.
>
> qemu-nbd is not /needed/ for normal QEMU operation.
No, but since it is provided by the ebuild, the ebuild sho
Very informative explanation.
On 12/05/19 20:01, Grant Taylor wrote:
On 12/4/19 11:03 PM, Walter Dnes wrote:
nbd is a "Network Block Device" driver along the lines of NFS, but it
doesn't handle concurrency. https://nbd.sourceforge.io/
I think I'd liken NBD to iSCSI more so than NFS. Primari
On 12/4/19 11:03 PM, Walter Dnes wrote:
nbd is a "Network Block Device" driver along the lines of NFS, but
it doesn't handle concurrency. https://nbd.sourceforge.io/
I think I'd liken NBD to iSCSI more so than NFS. Primarily because both
NBD and iSCSI provide local block devices that are bac
On Thu, 5 Dec 2019 08:05:46 +0100, n952162 wrote:
> Or maybe the assumption is wrong - after emerging *nbd*, I still get
> this when I try to modprobe nbd, which is required for running
> *qemu-nbd*:
>
> modprobe: FATAL: Module ndb not found in directory
> /lib/modules/4.19.72-gentoo
The assumpt
On 12/05/19 08:17, Arve Barsnes wrote:
On Thu, 5 Dec 2019 at 08:11, n952162 wrote:
Or maybe the assumption is wrong - after emerging nbd, I still get this when I
try to modprobe nbd, which is required for running qemu-nbd:
modprobe: FATAL: Module ndb not found in directory /lib/modules/4.19.
On Thu, 5 Dec 2019 at 08:11, n952162 wrote:
>
> Or maybe the assumption is wrong - after emerging nbd, I still get this when
> I try to modprobe nbd, which is required for running qemu-nbd:
>
> modprobe: FATAL: Module ndb not found in directory /lib/modules/4.19.72-gentoo
>
> Can anyone explain h
Or maybe the assumption is wrong - after emerging *nbd*, I still get
this when I try to modprobe nbd, which is required for running *qemu-nbd*:
modprobe: FATAL: Module ndb not found in directory
/lib/modules/4.19.72-gentoo
Can anyone explain how to run *qemu-nbd* on gentoo?
On ubuntu, one would
But qemu includes qemu-nbd, and it seems that qemu-nbd requires nbd.ko,
which is presumably provided by sys-block/nbd.
In other words, qemu provides a facility which seems to only work with
nbd - or is that a wrong assumption?
On 12/05/19 07:03, Walter Dnes wrote:
On Wed, Dec 04, 2019 at 04:28
On Wed, Dec 04, 2019 at 04:28:26PM +0100, n952162 wrote
> do I understand this correctly? In order to run qemu-nbd, you emerge
> app-emulation/qemu
>
> but that isn't all, you've also got to emerge sys-block/nbd?
nbd is a "Network Block Device" driver along the lines of NFS, but it
doesn't ha
Hello,
do I understand this correctly? In order to run qemu-nbd, you emerge
app-emulation/qemu
but that isn't all, you've also got to emerge sys-block/nbd?
Why doesn't qemu have a dependency on nbd? I don't find any relevant
USE flags.
Am 2018-06-07 um 09:33 schrieb Stefan G. Weichinger:
> Am 2018-05-30 um 17:06 schrieb Marko Weber:
>> hello,
>>
>> Am 2018-05-30 12:09, schrieb Stefan G. Weichinger:
>>> Am 2018-05-30 um 10:46 schrieb Bill Kenworthy:
error messages? - I get this happening sometimes from the oom killer
whe
Am 2018-05-30 um 17:06 schrieb Marko Weber:
> hello,
>
> Am 2018-05-30 12:09, schrieb Stefan G. Weichinger:
>> Am 2018-05-30 um 10:46 schrieb Bill Kenworthy:
>>> error messages? - I get this happening sometimes from the oom killer
>>> when the server runs out of memory - semi-random (usually but
hello,
Am 2018-05-30 12:09, schrieb Stefan G. Weichinger:
Am 2018-05-30 um 10:46 schrieb Bill Kenworthy:
error messages? - I get this happening sometimes from the oom killer
when the server runs out of memory - semi-random (usually but not
always the same vm)
And the VM itself idles at 1,8 G
Am 2018-05-30 um 10:46 schrieb Bill Kenworthy:
> error messages? - I get this happening sometimes from the oom killer
> when the server runs out of memory - semi-random (usually but not
> always the same vm)
And the VM itself idles at 1,8 GB RAM used right now.
Am 2018-05-30 um 10:46 schrieb Bill Kenworthy:
> On 30/05/18 15:52, Stefan G. Weichinger wrote:
>> maybe someone has hit that as well:
>>
>> https://bugs.gentoo.org/656886
>>
>> bug report at redhat is from yesterday (!)
>>
>> -
>>
>> That windows guest is shutting down and/or crashing now and then
On 30/05/18 15:52, Stefan G. Weichinger wrote:
> maybe someone has hit that as well:
>
> https://bugs.gentoo.org/656886
>
> bug report at redhat is from yesterday (!)
>
> -
>
> That windows guest is shutting down and/or crashing now and then.
> Same QEMU/libvirt combo at another site runs >20 VMs w
maybe someone has hit that as well:
https://bugs.gentoo.org/656886
bug report at redhat is from yesterday (!)
-
That windows guest is shutting down and/or crashing now and then.
Same QEMU/libvirt combo at another site runs >20 VMs without problems.
I'd be happy to find some workaround or fix a
On Fri, Mar 2, 2018 at 5:56 PM, Grant Taylor
wrote:
> I've found that removing not-strictly-needed layers of abstraction reduces
> complexity and makes things faster.
>
I can't find it again, but there was a neat writeup investigating the
TCP over TCP "tunnel collapse" phenomena. When two layers
On 03/02/2018 09:45 AM, Mick wrote:
Does it make a measurable difference, after the guest OS has booted?
IMHO, /bin/yes
I'll need to try this out. :-)
Yes, you should try it out for yourself.
I've found that removing not-strictly-needed layers of abstraction
reduces complexity and makes
On 03/02/2018 08:33 AM, R0b0t1 wrote:
You can pass a block device directly to QEMU, and this is recommended
for performance reasons. I have a Windows 10 VM that was passed an
entire SSD; it runs fine, and you can take the disk and plug it into
other computers. Passing a partition is a little di
On Fri, Mar 2, 2018 at 10:45 AM, Mick wrote:
> On Friday, 2 March 2018 15:33:02 GMT R0b0t1 wrote:
>> You can pass a block device directly to QEMU, and this is recommended
>> for performance reasons.
>
> Does it make a measurable difference, after the guest OS has booted?
>
> I'll need to try this
On Friday, 2 March 2018 15:33:02 GMT R0b0t1 wrote:
> You can pass a block device directly to QEMU, and this is recommended
> for performance reasons.
Does it make a measurable difference, after the guest OS has booted?
I'll need to try this out. :-)
--
Regards,
Mick
signature.asc
Description:
On Fri, Mar 2, 2018 at 9:00 AM, Mick wrote:
> On Friday, 2 March 2018 11:34:09 GMT Peter Humphrey wrote:
>> On Friday, 2 March 2018 11:12:36 GMT Helmut Jarausch wrote:
>> > Hi,
>> >
>> > I'd like to install a second Gentoo system on a partition by running
>> > QEMU using that partition (directly)
On Friday, 2 March 2018 11:34:09 GMT Peter Humphrey wrote:
> On Friday, 2 March 2018 11:12:36 GMT Helmut Jarausch wrote:
> > Hi,
> >
> > I'd like to install a second Gentoo system on a partition by running
> > QEMU using that partition (directly) - this is to create and update a
> > Gentoo
> > sys
On Friday, 2 March 2018 11:12:36 GMT Helmut Jarausch wrote:
> Hi,
>
> I'd like to install a second Gentoo system on a partition by running
> QEMU using that partition (directly) - this is to create and update a
> Gentoo
> system with different CFLAGS (for an older machine).
>
> Having no experien
Hi,
I'd like to install a second Gentoo system on a partition by running
QEMU using that partition (directly) - this is to create and update a
Gentoo
system with different CFLAGS (for an older machine).
Having no experience in such setups my initial problem is how to
install grub2 on that par
On 11/25/2016 11:10 AM, john wrote:
> On Thu, 24 Nov 2016 13:12:33 +
> john wrote:
>
>> Hi,
>>
>> I am trying to run qemu virtual machine with virtio_gpu using the
>> following command
>>
>> /usr/bin/qemu-system-x86_64 -enable-kvm -m 4096 -smp 8 -localtime
>> -cdrom Fedora-Workstation-Live-x
On Thu, 24 Nov 2016 13:12:33 +
john wrote:
> Hi,
>
> I am trying to run qemu virtual machine with virtio_gpu using the
> following command
>
> /usr/bin/qemu-system-x86_64 -enable-kvm -m 4096 -smp 8 -localtime
> -cdrom Fedora-Workstation-Live-x86_64-25_Beta-1.1.iso -boot
> once=d,menu=off
Hi,
I am trying to run qemu virtual machine with virtio_gpu using the
following command
/usr/bin/qemu-system-x86_64 -enable-kvm -m 4096 -smp 8 -localtime
-cdrom Fedora-Workstation-Live-x86_64-25_Beta-1.1.iso -boot
once=d,menu=off -vga virtio -display gtk,gl=on
but getting the following error w
On Sat, 2 Jan 2016 13:27:52 -0500 waltd...@waltdnes.org wrote:
> On Sat, Jan 02, 2016 at 02:56:58PM +0300, Andrew Savchenko wrote
>
> > For 32-bit distcc on 64-bit host there is no need to chroot or
> > create VM (hey, they're hellishly slow!). Just add -m32 to your
> > *FLAGS to force 32-bit arch
On Sat, 2 Jan 2016 22:34:24 -0600, Jc García wrote:
> > I serve the binpkg host from my
> > desktop to my LAN with nginx but I'm considering git from the booted
> > container
> Correction:
> * I'm considering doing it from the booted container
Why not just use a shared NFS directory?
--
Neil
2016-01-02 22:31 GMT-06:00 Jc García :
> I serve the binpkg host from my
> desktop to my LAN with nginx but I'm considering git from the booted
> container
Correction:
* I'm considering doing it from the booted container
2016-01-02 14:25 GMT-06:00 :
> On Sat, Jan 02, 2016 at 12:55:56PM -0600, Jc García wrote
>
>> Then why the recently introuced multilib method of bulding 32bit
>> libraries for packages that need it on 64 bit works? I don't think the
>> devs would have bothered to introudce the variable ABI_X86 an
On Sat, Jan 02, 2016 at 12:55:56PM -0600, Jc García wrote
> Then why the recently introuced multilib method of bulding 32bit
> libraries for packages that need it on 64 bit works? I don't think the
> devs would have bothered to introudce the variable ABI_X86 and a
> mulitib eclass just to compile
2016-01-02 12:27 GMT-06:00 :
> On Sat, Jan 02, 2016 at 02:56:58PM +0300, Andrew Savchenko wrote
>
>> For 32-bit distcc on 64-bit host there is no need to chroot or
>> create VM (hey, they're hellishly slow!). Just add -m32 to your
>> *FLAGS to force 32-bit arch. (In some rare cases ebuild ignores
On Sat, Jan 02, 2016 at 02:56:58PM +0300, Andrew Savchenko wrote
> For 32-bit distcc on 64-bit host there is no need to chroot or
> create VM (hey, they're hellishly slow!). Just add -m32 to your
> *FLAGS to force 32-bit arch. (In some rare cases ebuild ignores
> {C,CXX,F,FC}FLAGS, while this is a
On 2 January 2016 11:56:58 GMT+00:00, Andrew Savchenko
wrote:
> On Sat, 2 Jan 2016 10:42:31 + Neil Bothwick wrote:
> > On Fri, 1 Jan 2016 22:11:34 -0500, waltd...@waltdnes.org wrote:
> >
> > > I'm trying to run a distccserver in a 32-bit VM on a 64-bit
> host, for
> > > the benefit of my a
On Sat, 2 Jan 2016 10:42:31 + Neil Bothwick wrote:
> On Fri, 1 Jan 2016 22:11:34 -0500, waltd...@waltdnes.org wrote:
>
> > I'm trying to run a distccserver in a 32-bit VM on a 64-bit host, for
> > the benefit of my ancient 32-bit-only netbook. Yeah, "it'll work" using
> > the native 64-bit
On Fri, 1 Jan 2016 22:11:34 -0500, waltd...@waltdnes.org wrote:
> I'm trying to run a distccserver in a 32-bit VM on a 64-bit host, for
> the benefit of my ancient 32-bit-only netbook. Yeah, "it'll work" using
> the native 64-bit host OS. But any stuff that links against 32-bit
> libraries is
First, basic definitions.
distcc ==> compile on machine A for machine B. No mention of whether
the processors are different architectures.
cross-compile ==> compile under architecture A for architecture B
I'm trying to run a distccserver in a 32-bit VM on a 64-bit host, for
On Fri, Dec 25, 2015 at 04:10:40AM +, Ian Bloss wrote
> I was saying the libsdl packages have a USE flag "sound" which builds the
> sound module for sdl. So if qemu makes any calls to the sound module not
> pure alsa calls, that might be causing your issue.
>
> Wabes USE flag output shows he's
I was saying the libsdl packages have a USE flag "sound" which builds the
sound module for sdl. So if qemu makes any calls to the sound module not
pure alsa calls, that might be causing your issue.
Wabes USE flag output shows he's building sdl with the "sound" use flag
enabled and not just alsa al
waltd...@waltdnes.org wrote:
> On Thu, Dec 24, 2015 at 10:48:28PM +, Ian Bloss wrote
> > Libsdl and libsdl2 built with sound use flag on host?
>
> I didn't bother enabling alsa except for packages that actually need
> it. I've enabled it for libsdl, but not for sdl2, because I didn't
> rea
On Thu, Dec 24, 2015 at 10:48:28PM +, Ian Bloss wrote
> Libsdl and libsdl2 built with sound use flag on host?
I didn't bother enabling alsa except for packages that actually need
it. I've enabled it for libsdl, but not for sdl2, because I didn't
realize libsdl2 even existed. According to e
Libsdl and libsdl2 built with sound use flag on host?
On Thu, Dec 24, 2015, 16:04 wrote:
> Any ideas? The error message is...
>
> sdl: SDL failed to initialize audio subsystem
> sdl: Reason: No available audio device
> audio: Could not init `sdl' audio driver
>
> I get this both with a Gen
Any ideas? The error message is...
sdl: SDL failed to initialize audio subsystem
sdl: Reason: No available audio device
audio: Could not init `sdl' audio driver
I get this both with a Gentoo guest...
#!/bin/bash
qemu-system-i386 -enable-kvm \
-cpu host -display gtk \
-drive file=gento
On Tue, Jun 10, 2014 at 5:36 PM, Rich Freeman wrote:
> On Tue, Jun 10, 2014 at 5:31 PM, Heiko Zinke wrote:
>>
>> So if I "sudo virsh edit vmname" and substitute "/usr/bin/qemu-kvm" by
>> "/usr/bin/qemu-system-x86_64 -machine accel=kvm -enable-kvm" I only get this
>> error :(
>> "error: Cannot che
On Tue, Jun 10, 2014 at 5:31 PM, Heiko Zinke wrote:
>
> So if I "sudo virsh edit vmname" and substitute "/usr/bin/qemu-kvm" by
> "/usr/bin/qemu-system-x86_64 -machine accel=kvm -enable-kvm" I only get this
> error :(
> "error: Cannot check QEMU binary /usr/bin/qemu-system-x86_64 -machine
> accel=k
Hi,
with my recent qemu update from 1.6 to 2.0 I got the following error:
* The kvm/qemu-kvm wrappers no longer exist, but your libvirt
* instances are still pointing to it. Please update your
* configs in /etc/libvirt/qemu/ to use the -enable-kvm flag
* and the right system binary (e.g. qemu
On Tue, Aug 6, 2013 at 10:41 AM, Walter Dnes wrote:
> I've got a 32-bit QEMU Gentoo guest on my machine. For some reason,
> it comes up readonly, and other partitions aren't being mounted.
> Unfortunately, the initial messages flash by so quickly I can't read
> them to get an idea of what's go
I've got a 32-bit QEMU Gentoo guest on my machine. For some reason,
it comes up readonly, and other partitions aren't being mounted.
Unfortunately, the initial messages flash by so quickly I can't read
them to get an idea of what's going wrong. Since /usr isn't mounted,
"less" isn't available.
On Thu, Jul 25, 2013 at 10:17:41AM +0100, Kerin Millar wrote
> That's correct if you want optimal performance in
> X.org. The best option is -vga vmware in conjunction with
> x11-drivers/xf86-video-vmware.
The last time I used qemu a few years ago, I ended up running wine
from the guest as an X
On Thu, Jul 25, 2013 at 11:26:36AM +0200, J. Roeleveld wrote
> Not all VNC-clients do this.
> Which do you use?
In my case, it's tightvnc, which does not auto-resize. And in linux
tightvnc, {F8} brings up the dialogue.
--
Walter Dnes
I don't run "desktop environments"; I run useful applicat
On 25/07/2013 10:26, J. Roeleveld wrote:
On Thu, July 25, 2013 11:17, Kerin Millar wrote:
On 25/07/2013 09:54, Walter Dnes wrote:
On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
I stumbled over the solution to my final problem by accident. When
booting off the install cd, yo
On Thu, July 25, 2013 11:17, Kerin Millar wrote:
> On 25/07/2013 09:54, Walter Dnes wrote:
>> On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
>>I stumbled over the solution to my final problem by accident. When
>> booting off the install cd, you have 15 seconds to "hit any key",
On 25/07/2013 09:54, Walter Dnes wrote:
On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
2) What "vncviewer" or "vncconnect" parameters do I use to get to the
qemu session?
Assuming both server and client are run locally, connecting to either
"localhost:0" or "localhost:5900" sho
On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
>
> > 2) What "vncviewer" or "vncconnect" parameters do I use to get to the
> > qemu session?
>
> Assuming both server and client are run locally, connecting to either
> "localhost:0" or "localhost:5900" should work.
Thanks. That h
On 25/07/2013 04:24, Walter Dnes wrote:
Thanks to all who replied. sys-firmware/seabios needed the "binary"
flag and sys-firmware/ipxe needed the "qemu" and "vmware" flags. It's
starting now, and most of my problems are solved.
I still have permission problems as a regular user with qemu
Thanks to all who replied. sys-firmware/seabios needed the "binary"
flag and sys-firmware/ipxe needed the "qemu" and "vmware" flags. It's
starting now, and most of my problems are solved.
I still have permission problems as a regular user with qemu-kvm, but
qemu-system-i386 works. Root can
On 24/07/2013 14:16, Neil Bothwick wrote:
On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you are
not). If you are intending to use this build
On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
> >> WARN: pretend
> >> You have decided to compile your own SeaBIOS. This is not supported
> >> by upstream unless you use their recommended toolchain (which you are
> >> not). If you are intending to use this build with QEMU, realize you
>
On 24/07/2013 10:50, Walter Dnes wrote:
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recomme
On 24/07/13 17:50, Walter Dnes wrote:
> So I emerged QEMU, which pulled in some dependancies. Things are not
> going well...
>
> 1) The following warning shows up in elog...
>
>> WARN: pretend
>> You have decided to compile your own SeaBIOS. This is not supported
>> by upstream unless you use
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
> WARN: pretend
> You have decided to compile your own SeaBIOS. This is not supported
> by upstream unless you use their recommended toolchain (which you are
> not).
Am 09.10.2012 22:45, schrieb Stefan G. Weichinger:
> Unfortunately I still don't see what to compile in for this unknown
> PCI-device: the old kernel seems not to know what to do with PIIX3
> (although exactly the same kernel uses PIIX4 fine on vmware).
>
> Maybe some different PCI-bus .. ?
afte
Am 09.10.2012 22:06, schrieb Stefan G. Weichinger:
> Worth a try, sure. Although that old suse isn't exactly gentoo ... you
> know ;)
Apart from testing the software inside the VM ... I got my first own
2.2-kernel booted in there ;-)
I was able to add some other features I missed before, looks O
Am 09.10.2012 21:34, schrieb Florian Philipp:
> Given that the kernel is old and unsupported anyway, couldn't you
> just compile a slightly newer one with the right modules? Or
> transplant it from the other VM you mentioned?
Yes and no ... the software running in the VM is somehow compiled
"agai
Am 09.10.2012 21:21, schrieb Stefan G. Weichinger:
> Am 09.10.2012 20:52, schrieb Stefan G. Weichinger:
>
>> When I cp a file within that VM it takes ages ... unfortunately the OS
>> doesn't bring much modules with it so I can't just swap the virtual
>> controller for SCSI or so :-(
>
> addition:
Am 09.10.2012 20:52, schrieb Stefan G. Weichinger:
> When I cp a file within that VM it takes ages ... unfortunately the OS
> doesn't bring much modules with it so I can't just swap the virtual
> controller for SCSI or so :-(
addition:
within vmware-context I get a virtual PIIX4-IDE-controller.
Sorry folks, I get OT again.
I already spent around 3 days now fiddling around with a new and shiny
virtualization server running am64.
Issue:
I have to run a guest which is old:
Suse Linux 6.1, with a 2.2.5 kernel.
ext2-filesystems in there ...
I run that one OK on an older gentoo-host with
Whenever I run a qemu-kvm when xscreensaver starts it stops guest os from
working. Eg if I am emerging on guest or downloading a file when xscreensaver
starts on the host the guest freezes. Stopping xscreensaver and guest continues
where left off.
I can cure this by disabling xscreensaver but s
Whenever I run a qemu-kvm when xscreensaver starts it stops guest os from
working. Eg if I am emerging on guest or downloading a file when xscreensaver
starts on the host the guest freezes. Stopping xscreensaver and guest continues
where left off.
I can cure this by disabling xscreensaver but s
I have been using qemu to run windows and gentoo vms on gentoo for some
years and moved to qemu-kvm a while back - works well on my current
Intel core 2 desktop
I have decided to give VMware-workstation the boot off my work laptop
(even with work paying for a licence its just too hard to keep it
r
On Sat, 16 Jul 2011 19:04:51 +
j...@jdm.myzen.co.uk wrote:
> No unfortunately
> --Original Message--
> From: Matthew Finkel
> To: Gentoo
> ReplyTo: Gentoo
> Subject: Re: [gentoo-user] qemu-kvm
> Sent: 16 Jul 2011 17:51
>
> On 07/15/11 20:24, john wrote
No unfortunately
--Original Message--
From: Matthew Finkel
To: Gentoo
ReplyTo: Gentoo
Subject: Re: [gentoo-user] qemu-kvm
Sent: 16 Jul 2011 17:51
On 07/15/11 20:24, john wrote:
> I am running a gentoo amd64 qemu-kvm virtual image on my gentoo amd64
> box.
>
> Everything is
On 07/15/11 20:24, john wrote:
> I am running a gentoo amd64 qemu-kvm virtual image on my gentoo amd64
> box.
>
> Everything is running well. Machine boots up and all looks to be ok.
>
> When I startx the screen goes purple (on guest) and locks up. The only
> error message I get is on host.
>
> KVM
, 15 Jul 2011 23:02:45
To:
Reply-to: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] qemu-kvm
On Saturday, July 16 at 01:24 (+0100), john said:
> I am running a gentoo amd64 qemu-kvm virtual image on my gentoo amd64
> box.
>
> Everything is running well. Machine boots up a
On Saturday, July 16 at 01:24 (+0100), john said:
> I am running a gentoo amd64 qemu-kvm virtual image on my gentoo amd64
> box.
>
> Everything is running well. Machine boots up and all looks to be ok.
>
> When I startx the screen goes purple (on guest) and locks up. The only
> error message I
I am running a gentoo amd64 qemu-kvm virtual image on my gentoo amd64
box.
Everything is running well. Machine boots up and all looks to be ok.
When I startx the screen goes purple (on guest) and locks up. The only
error message I get is on host.
KVM internal error. Suberror: 1 emulation failur
On Mon, Jul 11, 2011 at 7:37 PM, Albert Hopkins wrote:
>
>
> On Monday, July 11 at 18:28 (+0300), Kfir Lavi said:
>
> > Hi,
> > I'm looking for xen like manager to manage my virtual machines when
> > computer
> > boots.
> > Is there any such project?
>
>
> libvirt (can also manage Xen):
>
> http:/
On Monday, July 11 at 18:28 (+0300), Kfir Lavi said:
> Hi,
> I'm looking for xen like manager to manage my virtual machines when
> computer
> boots.
> Is there any such project?
libvirt (can also manage Xen):
http://libvirt.org/
Hi,
I'm looking for xen like manager to manage my virtual machines when computer
boots.
Is there any such project?
Regards,
Kfir
On Wed, 2011-04-06 at 12:00 +0300, Kfir Lavi wrote:
>
> Hi Albert,
> Can you paste your USE flags for qemu?
>
> Thanks,
> Kfir
USE="aio sdl vde -alsa -bluetooth -brltty -curl -esd -fdt -hardened
-jpeg -ncurses -png -pulseaudio -qemu-ifup -sasl -ssl -static"
On Wed, Apr 6, 2011 at 1:42 AM, Albert Hopkins wrote:
> On Tue, 2011-04-05 at 18:06 +0300, Kfir Lavi wrote:
> > Hi,
> > After updating qemu-kvm to 0.13.0-r2 I get an infinite loop when running
> > qemu.
> > You can spot the loop with strace.
> > This problem shows on Redhat
> > https://bugzilla.re
On Wed, Apr 6, 2011 at 1:42 AM, Albert Hopkins wrote:
> On Tue, 2011-04-05 at 18:06 +0300, Kfir Lavi wrote:
> > Hi,
> > After updating qemu-kvm to 0.13.0-r2 I get an infinite loop when running
> > qemu.
> > You can spot the loop with strace.
> > This problem shows on Redhat
> > https://bugzilla.re
On Tue, 2011-04-05 at 18:06 +0300, Kfir Lavi wrote:
> Hi,
> After updating qemu-kvm to 0.13.0-r2 I get an infinite loop when running
> qemu.
> You can spot the loop with strace.
> This problem shows on Redhat
> https://bugzilla.redhat.com/show_bug.cgi?id=553689#c5
> and they say that it is related
Hi,
After updating qemu-kvm to 0.13.0-r2 I get an infinite loop when running
qemu.
You can spot the loop with strace.
This problem shows on Redhat
https://bugzilla.redhat.com/show_bug.cgi?id=553689#c5
and they say that it is related to the seabios.
Does anyone have this problem too?
I'm compiling
Am 11.02.2011 11:39, schrieb Stefan G. Weichinger:
> The logo stays there for about 10 sec or so ... and the clock gets slooower.
It *seems* solved now.
Enabled high res timers in host-kernel and DISabled "internet time"
(=ntp-client) in Windows7-guest. Now it is quicker and no drifting clock
(w
Am 11.02.2011 10:46, schrieb Petri Rosenström:
> I use kvm on gentoo, I really don't use the clock on the windows
> guests (I don't use windows vm) :). But I could guess that the issue
> might be with localtime, so you could try using "-rtc base=localtime"
> parameter with starting the windows ho
Am 11.02.2011 10:46, schrieb Petri Rosenström:
> I use kvm on gentoo, I really don't use the clock on the windows
> guests (I don't use windows vm) :). But I could guess that the issue
> might be with localtime, so you could try using "-rtc base=localtime"
> parameter with starting the windows ho
On Fri, Feb 11, 2011 at 11:12 AM, Stefan G. Weichinger wrote:
>
> Greets,
>
> does anyone else run KVM on gentoo as well?
>
> I delivered a amd64-server these days and a Win7-pro-guest runs on it.
>
> Now they tell me they have clock issues in the guest :-(
>
> I found
>
> http://docs.fedoraprojec
Am 11.02.2011 10:12, schrieb Stefan G. Weichinger:
> Now they tell me they have clock issues in the guest :-(
[...]
> I don't know where to start.
Another fact:
When I access the guest via RDP, it is slower than when I access it via
the libvirt-console (which in fact is VNC, right?)
hmm
1 - 100 of 166 matches
Mail list logo
