Displaying 5 results from an estimated 5 matches for "496m".
Did you mean:
496
2016 Nov 16
2
Re: [ovirt-users] OVA import of FC21 VM hangs during virt-v2v conversion?
"Richard W.M. Jones" <rjones@redhat.com> writes:
> On Wed, Nov 16, 2016 at 09:06:29AM +0200, Michal Skrivanek wrote:
>>
>> > On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote:
>> >
>> > Hi,
>> >
>> > My last VM imported in 2 minutes. This one has been sitting for three
>> > hours. I think this is
2016 Nov 16
2
Re: [ovirt-users] OVA import of FC21 VM hangs during virt-v2v conversion?
...o add timestamps to
each output line?
FWIW, here's the disk usage from within that VM:
Filesystem Size Used Avail Use% Mounted on
/dev/vda3 44G 4.6G 37G 12% /
devtmpfs 487M 0 487M 0% /dev
tmpfs 497M 0 497M 0% /dev/shm
tmpfs 497M 348K 496M 1% /run
tmpfs 497M 0 497M 0% /sys/fs/cgroup
tmpfs 497M 4.0K 496M 1% /tmp
/dev/vda1 969M 130M 773M 15% /boot
tmpfs 100M 0 100M 0% /run/user/1000
tmpfs 100M 0 100M 0% /run/user/0
For the record, Fedora 23, which imported in...
2005 Jul 09
5
pxelinux and 2.6.9 kernel parameters
I am using RHEL4 with kernel 2.6.9. I can load this on my hardware by
passing the following kernel parameter: memmap=496M at 16M, and it loads up
and runs OK. If I do not use this parameter, I get a kernel panic.
When I try to load the same software onto the same hardware using PXE, I
add the same parameter on the server's
tftpboot/pxelinux/pxelinux.cfg/default file:
append initrd=some_file.gz memmap=496M at 16M...
2006 Feb 01
1
Resizing Freebsd mdroot domU, on a RHEL4 dom0 machine.
I''ve gotten freebsd 7.0 domU working using the files here:
http://www.fsmware.com/xenofreebsd/7.0/downloads
on a rhel4 system using xen-3.0.0-7.1_rhel4.1 rpms.
but the root filesystem for freebsd is quite small:
demo# df -h | grep /
/dev/xbd1793a 496M 274M 182M 60% /
I''m wanting to resize the mdroot filesystem, but am unsure how. I have
no issues resizing ext* loopback files, but don''t really know a
procedure to get something like ''growfs'' to work on a loopback file on
freebsd.
Does anyone ha...
2006 May 19
25
iptables CLASSIFY and MARK not working?
I have to match my packets based on MAC address, which I cannot do in
the POSTROUTING chain, so I do it in PREROUTING using MARK. Then, I
match on the MARK in the POSTROUTING chain to do a CLASSIFY. But this
does not seem to work:
wireless-r1 bwlimit # iptables -L -v -n -t mangle
Chain PREROUTING (policy ACCEPT 3353K packets, 941M bytes)
pkts bytes target prot opt in out source