Aurelien Jarno wrote:
> Hi all,
>
> While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I
> am having problems with running a 32-bit FreeBSD under the same KVM:
>
> INIT: version 2.86 booting
> INIT: PANIC: segmentation violation! sleeping for 30 seconds.
> pid 34 (init), uid 0: e
Barry Silverman wrote:
> I am curious what techniques are being used to debug problems with KVM.
>
> Are you using the qemu GDB stub to step the guest, or using KDB/KGDB to debug
> the driver-level code, or just using a kernel printfs?
>
>
Various techniques are used depending on the bug and th
Bugs item #1669582, was opened at 2007-02-26 19:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1669582&group_id=180599
Please note that this message will contain a full copy
Hi all,
While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I
am having problems with running a 32-bit FreeBSD under the same KVM:
INIT: version 2.86 booting
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
pid 34 (init), uid 0: exited on signal 11
INIT: PANIC: segm
- This mail is in HTML. Some elements may be ommited in plain text. -
Tel: +46 (0)8 625 46 40
ULTRA-TYST LUFTRENARE FÖR KONTOR OCH HEM
Lider du av allergiska besvär på våren?
Besväras du av illaluktande ämnen på din arbetsplats eller i hemmet? En
luftrenare kan göra underverk på din hälsa! Vi re
I am curious what techniques are being used to debug problems with KVM.
Are you using the qemu GDB stub to step the guest, or using KDB/KGDB to debug
the driver-level code, or just using a kernel printfs?
-
Take Surveys. E
Hi Avi, all,
> I tried it now, it's simple and it even works:
>
> 1. Add BRIDGE=sw0 to ifcfg-eth0
> 2. Create a new ifcfg-sw0 that has TYPE=Bridge, and any dhcp/ip
> configuration you previously had in ifcfg-eth0
I've now managed to get several KVM hosts working in a local intranet
based on you
Avi Kivity wrote:
> Hollis Blanchard wrote:
>> On Sun, 2007-02-25 at 10:58 +0200, Avi Kivity wrote:
>>
>>> I'm changing the kvm userspace interface to be more friendly to other
>>> archs. One issue is the PIO port size. x86 uses 16 bits to hold the
>>> port size (64K ports). Is that an issu
Avi Kivity wrote:
> Laurent Vivier wrote:
>>
>>> Would it be possible to merge the kvm part, and maybe to send it to the
>>> qemu mailing list?
>>>
>>
>> I can try to send it to qemu mailing list but I think it is not useful
>> for pure
>> qemu. It seems to improve performance only with kvm.
Laurent Vivier wrote:
>
>> Would it be possible to merge the kvm part, and maybe to send it to the
>> qemu mailing list?
>>
>
> I can try to send it to qemu mailing list but I think it is not useful for
> pure
> qemu. It seems to improve performance only with kvm.
>
> Avi, your opinion ?
Aurelien Jarno wrote:
> Laurent Vivier a écrit :
>> Anthony Liguori wrote:
>>> Laurent Vivier wrote:
Avi Kivity wrote:
> Aurelien Jarno wrote:
>
>>
>>
>>> What is your disk image file format, or are you using a partition?
>>>
>>>
Laurent Vivier a écrit :
> Anthony Liguori wrote:
>> Laurent Vivier wrote:
>>> Avi Kivity wrote:
>>>
Aurelien Jarno wrote:
>
>
>> What is your disk image file format, or are you using a partition?
>>
>>
> I am using a raw image file
richard lucassen wrote:
Kernel: 2.6.20.1
kvm-15
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
1G memory
After modprobing kvm-amd, the system becomes very very unstable and I
have to reboot te get things right (after modprobing kvm-amd e.g. the
ssh daemon is unaccessible)
This was fixed by
Andreas Hasenack wrote:
> On Monday 26 February 2007 03:39:28 Avi Kivity wrote:
>
>> richard lucassen wrote:
>>
>>> Kernel: 2.6.20.1
>>> kvm-15
>>> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
>>> 1G memory
>>>
>>> After modprobing kvm-amd, the system becomes very very unstable and I
>>>
On Monday 26 February 2007 03:39:28 Avi Kivity wrote:
> richard lucassen wrote:
> > Kernel: 2.6.20.1
> > kvm-15
> > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> > 1G memory
> >
> > After modprobing kvm-amd, the system becomes very very unstable and I
> > have to reboot te get things right (afte
Gerd Hoffmann wrote:
> Avi Kivity wrote:
>
>> - new userspace interface (work in progress)
>>
>
> kvmfs in kvm-15 kernel code does not to build with older kernels (2.6.16
> fails, 2.6.18 works ok), looks like the reason are some changes in
> superblock handling.
>
> Do you intend to fix tha
>Avi Kivity wrote:
>> - new userspace interface (work in progress)
>
>kvmfs in kvm-15 kernel code does not to build with older kernels
(2.6.16
>fails, 2.6.18 works ok), looks like the reason are some changes in
>superblock handling.
>
>Do you intend to fix that?
Did you run the make sync under th
Avi Kivity wrote:
> - new userspace interface (work in progress)
kvmfs in kvm-15 kernel code does not to build with older kernels (2.6.16
fails, 2.6.18 works ok), looks like the reason are some changes in
superblock handling.
Do you intend to fix that?
cheers,
Gerd
--
Gerd Hoffmann <[EMAIL P
18 matches
Mail list logo