Displaying 5 results from an estimated 5 matches for "vnconfig".
Did you mean:
vconfig
2003 May 14
0
vnconfig(8), bin/45754
Hello,
I am going to commit a patch below, it fixes several cases when
vnconfig(8) fails but returns zero exit status.
Are there any objections?
http://www.freebsd.org/cgi/query-pr.cgi?pr=45754
Index: vnconfig.c
===================================================================
RCS file: /home/ncvs/src/usr.sbin/vnconfig/vnconfig.c,v
retrieving revision 1.13.2.6
diff -u -r1...
2003 Apr 07
0
vnconfig
Hi!
vnconfig(8) sometimes return incorrect exit status,
I've filled a PR http://www.FreeBSD.org/cgi/query-pr.cgi?pr=bin/45754
last year but nobody took it.
It's hard to write safe scripts when system utility does not
signal an error with exit status.
Please, look at PR. It contains a patch.
Eugene Gr...
2005 Jun 12
7
help with "error extent to vbd failed: ... error 8"
Good morning everybody,
I get a:
Error: Adding extent to vbd failed: device (vbd (uname file:/xen/slackware-linux-10/linu.img) (dev hda1) (mode w)), error 8
What is "error 8"? Where are those error-codes listed?
My linux.conf:
kernel="/xen/slackware-linux-10/vmlinuz-install" # <- the one from Xen
memory=64
name="Linux" # <- is it right that this cannot have
2003 Apr 10
0
panic: vinvalbuf: flush failed
...IPFIREWALL_DEFAULT_TO_ACCEPT
options IPFW2 # Use next-generation IPFW.
options DUMMYNET
options IPFILTER
options IPFILTER_LOG
options DEVICE_POLLING
options HZ=1000
pseudo-device vn # Vnode driver, see vnconfig(8)
options MSGBUF_SIZE=81920
options AUTO_EOI_1
options MAXCONS=16 # number of virtual consoles
options SC_HISTORY_SIZE=400 # number of history buffer lines
options ALT_BREAK_TO_DEBUGGER # <ENTER> ~ Ctrl-B
device smbus
device...
2012 Jan 31
2
Bug#658100: xl: hangs in qemu-dm when trying to run PV domU
Package: xen-utils-common
Version: 4.1.2-1
Severity: normal
Hi, I was doing some experiments today with XL TOOLSTACK,
and found few problems when trying to do PV domU boot.
I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386,
and with simple configuration without any disks, nics or virtual framebuffer,
kernel boots (and then kernel itselfs correctly fails with information