Which OS distribution are you using?
Do you have a broken packages update?
Now you know the module kvm_amd works, but may not be loading
automatically on boot.
El 08/04/16 a les 08:37, Mahmood Naderan ha escrit:
>># modprobe kvm_amd
>
> OK I saw nothing strange in the boot logs. Then I decided
If it's CentOS 6, you have updates upto 6.7
You could apply these pending updates and see if it fixes some boot issue.
Any other measuse is to analyze boot logs to the detail.
El 08/04/16 a les 09:26, Mahmood Naderan ha escrit:
>> Which OS distribution are you using?
>
> Cenos-6.5
>
>
>>Do yo
OK I will try. Thank you very much. Regards,
Mahmood
On Thu, 7 Apr 2016 11:48:27 +0200
Pradeep Kiruvale wrote:
> Hi All,
>
> I am using virtio-9p for sharing the file between host and guest. To test
> the shared file I do read/write options in the guest.To have controlled io,
> I am using cgroup blkio.
>
> While using cgroup I am facing two issue
On 08/04/2016 08:37, Mahmood Naderan wrote:
># modprobe kvm_amd
OK I saw nothing strange in the boot logs. Then I decided to run that
command and finally I was able to use -enable-kvm!
For me its a bit odd because the output of 'lsmod' showed only 'kvm' and
not 'kvm_amd' and running 'modprobe
Hi Greg,
Thanks for your reply.
Below is the way how I add to blkio
echo "8:16 8388608" >
/sys/fs/cgroup/blkio/test/blkio.throttle.write_bps_device
The problem I guess is adding these task ids to the "tasks" file in cgroup
These threads are started randomly and even then I add the PIDs to the
In order to find out where certain QEMU functions are called from, using
test output is not practical.
Therefore I set out to use gdb to debug qemu-system-ppc64.exe (the
unstripped version):
gdb /cygdrive/c/MinGW/msys/1.0/local/qemu/qemu-system-ppc64
b pci_host_config_write_common
gdb responds
On Fri, 8 Apr 2016 11:51:05 +0200
Pradeep Kiruvale wrote:
> Hi Greg,
>
> Thanks for your reply.
>
> Below is the way how I add to blkio
>
> echo "8:16 8388608" >
> /sys/fs/cgroup/blkio/test/blkio.throttle.write_bps_device
>
Ok, this just puts a limit of 8MB/s when writing to /dev/sdb for all
Hi Greg,
FInd my replies inline
>
> > Below is the way how I add to blkio
> >
> > echo "8:16 8388608" >
> > /sys/fs/cgroup/blkio/test/blkio.throttle.write_bps_device
> >
>
> Ok, this just puts a limit of 8MB/s when writing to /dev/sdb for all
> tasks in the test cgroup... but what about the tasks
On 08/04/2016 13:50, trasmus...@ddci.com wrote:
In order to find out where certain QEMU functions are called from,
using test output is not practical.
Therefore I set out to use gdb to debug qemu-system-ppc64.exe (the
unstripped version):
gdb /cygdrive/c/MinGW/msys/1.0/local/qemu/qemu-system-p
On Fri, 8 Apr 2016 14:55:29 +0200
Pradeep Kiruvale wrote:
> Hi Greg,
>
> FInd my replies inline
>
> >
> > > Below is the way how I add to blkio
> > >
> > > echo "8:16 8388608" >
> > > /sys/fs/cgroup/blkio/test/blkio.throttle.write_bps_device
> > >
> >
> > Ok, this just puts a limit of 8MB/s whe
11 matches
Mail list logo
