similar to: virt-install -L

On Wed, January 7, 2009 04:29, Peter Korn wrote: > Decision #4: file system layout > I''d like to have ZFS root mirrored. Do we simply use a portion of the existing disks for this, or add two disks just for root? Use USB-2 flash as those 2 disks? And where does swap go? The default install in Osol 0811 (which is what I just upgraded my home NAS to) gives you a zfs root pool that

Using Centos 5.2 with Xen. I'm making a group of nodes behind an LVS load-director to perform computing services. Those nodes are only accessible from the LVS nodes (I'm using LVS NAT mode). Actually it's Xen virtual servers on the physical nodes behind the LVS boxes that I'm mostly concerned with. When you create a guest with virt-install, there's a vnc param and a vncport

If I can log in to the guest through the console, I can of course find out what IP DHCP has assigned it. If I configure a static IP I can of course connect to the system there (if it runs services, the firewall allows it, all the usual caveats). Does there happen to be any way to determine from dom0 what IPs are participating in the network and which guests they belong to? (I'm configuring

If I type "xm console 6", say (when I have a virtual machine 6 running), what should I get? The documentation seems to indicate that I should get something that behaves like a telnet to a serial console. What I actually get is a connection that might show me a couple of lines of output that do look like they belonged on the console, but doesn't seem to accept any input (except that

Solaris and/or ZFS are badly confused about drive IDs. The "c5t0d0" names are very far removed from the real world, and possibly they''ve gotten screwed up somehow. Is devfsadm supposed to fix those, or does it only delete excess? Reason I believe it''s confused: zpool status shows mirror-0 on c9t3d0, c9t2d0, and c9t5d0. But format shows the one remaining Seagate

Had some trouble getting Centos x64 installed as a guest in my new Centos 5.5 x64 server using Xen (thanks again for all the help getting the hardware virtualization turned on and confirmed yesterday!). When I chose OS Linux, and whatever they called the detailed OS subtype I chose the Red Hat Enterprise 5.4 and greater, and then tried to install Centos 5.5, the install started and I got into the

Looks like just starting the nfs service turns on V2, 3, and 4 (based on reading the script, reading the man pages, and looking at the ports using netstat -l). However, I can connect using -t nfs in the mount, and -t nfs4 fails. I don't believe this is a firewall issue, internal IPs are fully open to each other according to an early rule in iptables. $ sudo mount host03:/home/ddb /mnt/ddb

It appears that the liveCD (CentOS-5.2-i386-LoveCD.iso that I downloaded late last week) does not contain either netcat or tcpdump. Given the frequent use of a livecd for testing and debugging, those would seem to be key tools that should be available. Obviously a LiveCD can't contain everything anybody might ever want, but I'd give those two tools a pretty high priority; certainly much

The virtualization manual doesn't seem to say; does one have to do anything to get the Centos 5.5 paravirtualization drivers installed? Or is it sufficient to specify a paravirtualized guest, and the Centos install will then detect that and load the right things? And, is there a way to check in the guest that the right drivers are loaded? What are they? -- David Dyer-Bennet, dd-b at

I've got a Centos guest and a Windows 2003 server guest running in Xen under Centos (5.2 in both cases), and they can get out to the network, and I can ping them from dom0. This is my first Xen install, and I haven't used Linux as a router before (I'm very familiar with it as a webserver and development platform) so I'm a bit weak on the bridging code and NAT / IP masquerading.

Every time I touch something, pieces fall off! It's a good thing this stuff isn't in production yet (for me I mean). So I had an LVS, configured with Piranha, directing http test transactions across two servers. I used Piranha to add another realserver. It appeared in the lvs.cf file, but didn't appear in the ipvsadm output. So I stopped and restarted Pulse. And now *none* of the

I'm installing Centos 5.5 on a new Dell R301 server. I wanted to run Xen and have the full virtualization possibilities (this is our development support server, so it runs a few real services and is available for playing with things; putting the "playing with things" functions into virtual servers would protect the "few real services", and make it easier to clean up

On Sat, February 7, 2009 14:32, Alan.M.Wright wrote: >>> Also, does this end up taking up extra metadata space compared to not >>> having to have an ACL entry for each file? > > No, ZFS only stores ACLs. It doesn''t have or store a separate > representation of the UNIX permissions bits. So I won''t worry about it. I still worry when I see 11 ACL

I made the mistake of looking at disk IO numbers in two different ways -- now I'm confused, because they give inconsistent answers. First way was using 'vmstat 10'. This gave me (apologies for wrapped lines): r b swpd free buff cache si so bi bo in cs us sy id wa st 2 0 2162944 4071928 162444 4218456 0 0 0 286 1103 528 3 2 95 0 0 1 0

Looks like my main data pool is borked. I''ve got one essentially current backup, and one older backup, plus the photos are mostly backed up on archival optical disks, so this isn''t as disastrous as it might be, but still, recovering several hundred gigabytes on home equipment is a pain. Hence I''d prefer to recover the pool if that''s reasonably possible. When

I'm not looking to move virtual machines between physical platforms; just want some protection between applications sharing a physical server. They'll all be using local disk in one form or another. Much the easiest to manage is just having the virtual machine use a file in dom0 as its disk. Without pre-allocating, this lets me over-commit somewhat to cover unknown future needs, for

I've got a Xen domU running Centos 5.2 (dom0 is also Centos 5.2) with two NICs configured. Both NICs show up in the Xen hardware details display. Looking at dmesg output from rebooting the domU, I see both eth0 and eth1 appearing there. But network configuration only knows about eth0, the one that was installed originally (eth1 was added later). There's options to create another NIC in

My most common use of Samba is to export the home directories and possibly some others from a Linux server so that people working on local Windows boxes can easily move files to and from the Linux box. All these people have user accounts on the Linux box, so I just want them to authenticate using that. I've had this running on several servers at home, including one that's still extant.

My full backup script errorred out the last two times I ran it. I''ve got a full Bash trace of it, so I know exactly what was done. There are a moderate number of snapshots on the zp1 pool, and I''m intending to replicate the whole thing into the backup pool. After housekeeping, I take make a current snapshot on the data pool (zp1). Since this is a new full backup, I then

I've got small numbers of connections moving through a load balancer configured in NAT mode. So I've got an iptables table called "nat", which has in it a line "-A POSTROUTING -o eth0 -j MASQUERADE" (lan connect is eth0, private lan inside the cluster is eth1). The load balancer is working; connections made to the virtual ip on that host do get routed to one of the